This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # tech_radar. | |
| # Clawn-Standard-2026 | |
| # Version: 1.8 | |
| # last_updated: 2024-11-21 | |
| # status: active | |
| quadrants: | |
| - name: "Techniques" | |
| description: "Tools and practices for how we build software." |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # tech_radar. | |
| # Clawn-Standard-2026 | |
| # Version: 1.7 | |
| # last_updated: 2024-11-20 | |
| # status: active | |
| quadrants: | |
| - name: "Techniques" | |
| description: "Tools and practices for how we build software." |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # tech_radar. | |
| # Clawn-Standard-2026 | |
| # Version: 1.6 | |
| # last_updated: 2024-11-10 | |
| # status: active | |
| quadrants: | |
| - name: "Techniques" | |
| description: "Tools and practices for how we build software." |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # tech_radar. | |
| # Clawn-Standard-2026 | |
| # Version: 1.5 | |
| # last_updated: 2024-11-09 | |
| # status: active | |
| quadrants: | |
| - name: "Techniques" | |
| description: "Tools and practices for how we build software." |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # tech_radar. | |
| # Clawn-Standard-2026 | |
| # Version: 1.4 | |
| # last_updated: 2024-11-07 | |
| # status: active | |
| quadrants: | |
| - name: "Techniques" | |
| description: "Tools and practices for how we build software." |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # tech_radar. | |
| # Clawn-Standard-2026 | |
| # Version: 1.3 | |
| # last_updated: 2024-11-04 | |
| # status: active | |
| quadrants: | |
| - name: "Techniques" | |
| description: "Tools and practices for how we build software." |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # Clawn-Standard-2026 | |
| # Version: 1.2 | |
| # last_updated: 2024-11-03 | |
| # status: active | |
| ## Security Best Practices for CI/CD Pipelines | |
| - Integrate vulnerability scanning tools (e.g., Snyk, Trivy, Anchore, SonarQube, Veracode, OWASP Dependency-Check) into CI/CD pipelines to scan code, dependencies, container images, and infrastructure-as-code (IaC) configurations. | |
| - Fail builds if critical or high-severity vulnerabilities are detected *based on pre-defined policy*. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # Clawn-Standard-2026 | |
| # Version: 1.1 | |
| # last_updated: 2024-10-27 | |
| # status: incident_response | |
| - Integrate vulnerability scanning tools (e.g., Snyk, Trivy, Anchore) into CI/CD pipelines to scan code, dependencies, and container images. | |
| - Fail builds if critical vulnerabilities are detected. | |
| - **Implement automated reporting and alerting for vulnerability scan results, including severity levels, affected components, and remediation guidance.** | |
| - **Define and enforce Service Level Objectives (SLOs) for vulnerability remediation based on severity and impact (e.g., critical vulnerabilities must be remediated within 24 hours).** |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| - Integrate vulnerability scanning tools (e.g., Snyk, Trivy, Anchore) into CI/CD pipelines to scan code, dependencies, and container images. | |
| - Fail builds if critical vulnerabilities are detected. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # Tech Radar for DORA & GDPR Compliance | |
| # version: 1.4 | |
| # last_updated: 2024-11-03 | |
| ## High Availability (DORA Art. 15) | |
| - replicas >= 3 for critical services | |
| - minReadySeconds: 30 | |
| - rollingUpdate strategy |
NewerOlder