Skip to content

Latest commit

 

History

History
55 lines (47 loc) · 1.41 KB

File metadata and controls

55 lines (47 loc) · 1.41 KB

DevSecOps Pipelines

Security integration

  • SAST: scan application code for vulnerabilities.
  • Dependency scan: check third-party libraries for CVEs.
  • IaC scan: validate Terraform/Bicep templates for misconfigurations.
  • Secret scan: prevent accidental credential exposure.
  • Gated deployments: block releases on critical findings.

Definition of done (security)

  • No critical vulnerabilities open.
  • Policy compliance checks passed.
  • Secrets scan shows no leaked credentials.
  • Logging and monitoring enabled.

Example pipeline snippets

# Example: security checks stage
steps:
  - name: sast
    run: ./tools/run-sast.sh
  - name: dependency-scan
    run: ./tools/dependency-scan.sh
  - name: iac-scan
    run: ./tools/iac-scan.sh
  - name: secret-scan
    run: ./tools/secret-scan.sh
# Example: gated deployment
steps:
  - name: deploy
    run: ./tools/deploy.sh
  - name: validate-policy
    run: ./tools/policy-validate.sh

Policy-as-code loop (visual)

flowchart LR
  A[Author] --> B[Test]
  B --> C[Deploy]
  C --> D[Monitor Drift]
  D --> E[Fix]
  E --> A
Loading

Diagram

Policy-as-code lifecycle: 22-diagrams/policy-as-code-loop.mmd

Related docs