Code Security within the Pipeline
Validations of the pipeline's own code (YAML, scripts, linters), including control of logic, permissions and the use of external components.
Validations of the pipeline's own code (YAML, scripts, linters), including control of logic, permissions and the use of external components.
Secure coding practices, curation and selection of guidelines, automated validation and governance during development
Rules and tools for security validation directly in the development environment (pre-commit, IDE, CLI)
Organisational policy that defines the requirements for the selection, tailoring, publication, versioning and periodic review of secure development guidelines per technology stack, including the conversion of rules into automatic linter and SAST configurations, proportional to the criticality level (L1, L2, L3).
Canonical catalogue of security requirements for the development process (DEV-001 to DEV-009), with applicability by risk level and acceptance criteria for code guidelines, linters, formal review, exception management, provenance and traceable annotations.