Azure Security Benchmark
DevOps Security

Azure Security Benchmark DS-6: Enforce security of workload throughout DevOps lifecycle

Integrate security controls into CI/CD pipelines including SAST, secret scanning, and IaC scanning with pipeline failure on critical findings.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 54 controls across 18 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

FedRAMP High · 6 controls

  • CM-3 Configuration Change Control
  • IA-5(7) Authenticator Management | No Embedded Unencrypted Static Authenticators (IA-5(7))
  • SA-10 Developer Configuration Management
  • SA-11 Developer Testing and Evaluation
  • SA-15 Development Process, Standards, and Tools (SA-15)
  • SA-3 System Development Life Cycle

FedRAMP Moderate · 6 controls

  • CM-3 Configuration Change Control
  • IA-5(7) Authenticator Management | No Embedded Unencrypted Static Authenticators (IA-5(7))
  • SA-10 Developer Configuration Management
  • SA-11 Developer Testing and Evaluation
  • SA-15 Development Process, Standards, and Tools (SA-15)
  • SA-3 System Development Life Cycle

NIST SP 800-53 Rev 5 · 6 controls

  • SEC01-BP06 Automate deployment of standard security controls
  • SEC11-BP02 Automate testing throughout the development and release lifecycle
  • SEC11-BP04 Conduct code reviews
  • SEC11-BP06 Deploy software programmatically

C5 (Germany) · 4 controls

  • C5-DEV-01 Policies for the development/procurement of information systems
  • C5-DEV-03 Policies for changes to information systems
  • C5-DEV-06 Testing changes
  • C5-DEV-09 Approvals for provision in the production environment

NIST SP 800-218 · 4 controls

ISO 27001:2022 · 3 controls

  • 8.25 Secure development life cycle
  • 8.28 Secure coding
  • 8.32 Change management

ISO 27002:2022 · 3 controls

  • 8.25 Secure development life cycle
  • 8.28 Secure coding
  • 8.32 Change management

CIS Controls v8 · 2 controls

  • CIS-16.1 Establish and Maintain a Secure Application Development Process
  • CIS-16.12 Implement Code-Level Security Checks

CMMC 2.0 · 2 controls

NIST SP 800-161 Rev 1 · 2 controls

NIST SP 800-171 Rev 3 · 2 controls

PCI DSS 4.0 · 2 controls

  • 6.2.1 6.2.1 Secure development of bespoke and custom software
  • 6.5.1 6.5.1 Change control procedure for production
  • CFTC-SS-5 Systems Development and Quality Assurance Category

ISO/IEC 42001:2023 · 1 control

  • A.6.1.3 Processes for responsible design and development of AI systems
  • NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

SOC 2 · 1 control

  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in DevOps Security

You are reading one control. How much of Azure Security Benchmark have you already done?

Azure Security Benchmark DS-6 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Azure Security Benchmark your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 71 of 85 Azure Security Benchmark controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

The graph holds this control, the 54 it maps to, and the evidence behind each claim, over MCP and REST.