CI/CD Security Audit — Compliance Mapping (ISO 27001 / SOC 2 / DORA)

This compliance-oriented audit table maps CI/CD security controls to common regulatory and assurance frameworks.
It is intended to support internal audits, external assessments, and regulatory readiness in enterprise environments.


🔐 Identity & Access Management (IAM)

ControlISO 27001SOC 2DORAYesNo
Least privilege enforced for CI/CD service accountsA.8.2 / A.5.15CC6.1ICT Risk Mgmt
Segregation between human and pipeline identitiesA.6.3CC6.3Governance
Role-based access for pipeline configurationA.5.18CC6.2Access Control
MFA enforced for CI/CD administratorsA.5.17CC6.1ICT Security
Approval required for privileged pipeline actionsA.5.19CC7.2Change Mgmt

🔑 Secrets Management

ControlISO 27001SOC 2DORAYesNo
Secrets not stored in source controlA.8.12CC6.1ICT Security
Runtime injection of secretsA.8.24CC6.7ICT Risk Mgmt
Environment-scoped secretsA.5.15CC6.2Governance
Regular secret rotationA.8.15CC6.1ICT Security
Secret values excluded from logsA.8.16CC7.2Monitoring

📦 Artifact Integrity & Software Supply Chain

ControlISO 27001SOC 2DORAYesNo
Hardened CI/CD build environmentsA.8.20CC6.6ICT Resilience
Artifact signing enforcedA.8.23CC7.3Supply Chain
Provenance linking code, pipeline, artifactA.8.9CC7.2Traceability
Artifact repositories enforce immutabilityA.8.10CC6.5ICT Security
Promotion limited to trusted artifactsA.8.21CC6.6Change Mgmt

🔗 Third-Party & CI/CD Integrations

ControlISO 27001SOC 2DORAYesNo
Third-party CI/CD plugins formally approvedA.5.22CC6.3Third-Party Risk
Integrations pinned to specific versionsA.8.8CC7.3Supply Chain
Integrity verification of external actionsA.8.23CC7.3ICT Security
Restriction of community-maintained pluginsA.5.23CC6.6Risk Mgmt
Monitoring of integration usageA.8.16CC7.2Monitoring

📊 Logging, Monitoring & Audit Evidence

ControlISO 27001SOC 2DORAYesNo
CI/CD pipeline activity fully loggedA.8.15CC7.2Monitoring
Logs include approvals and security checksA.8.14CC7.3Governance
Centralized log collectionA.8.16CC7.2ICT Risk Mgmt
Log retention aligned with policyA.5.34CC7.4Record Keeping
Evidence supports audit and investigationsA.5.31CC2.2Compliance

🛡️ Change Management & Governance

ControlISO 27001SOC 2DORAYesNo
Changes reviewed and approved via pipelineA.8.32CC8.1Change Mgmt
Separation between build and deploy rolesA.6.3CC6.3Governance
Policy enforcement via automated gatesA.5.19CC7.2ICT Security
Exceptions formally approved and loggedA.5.31CC2.3Compliance
CI/CD governance reviewed periodicallyA.5.36CC1.2Oversight

How to Use This Compliance Audit Table

  • Use during ISO 27001 internal audits
  • Attach to SOC 2 readiness assessments
  • Support DORA ICT risk management evidence
  • Track remediation actions in the Notes column
  • Review periodically as CI/CD pipelines evolve

Related Resources


Audit-ready context

Written for regulated environments: controls before tools, policy enforcement in CI/CD, and evidence-by-design for audits.

Focus areas include traceability, approvals, exception governance, and evidence retention across build, release, and operations.

See methodology on the About page.