Azure Security Benchmark
DevOps Security

Azure Security Benchmark ASBv3-DS-3: Secure DevOps infrastructure

Secure the DevOps infrastructure and pipeline across build, test and production stages, including the repositories that hold source code, packages and images.

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

What else in your programme already covers this

This control maps to 53 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.

NIST SP 800-218 · 8 controls

FedRAMP High · 5 controls

  • CM-5 Access Restrictions for Change
  • CM-5(5) Access Restrictions for Change | Privilege Limitation for Production and Operation (CM-5(5))
  • SA-10 Developer Configuration Management
  • SA-15 Development Process, Standards, and Tools (SA-15)
  • SR-3 Supply Chain Controls and Processes (SR-3)

FedRAMP Moderate · 5 controls

  • CM-5 Access Restrictions for Change
  • CM-5(5) Access Restrictions for Change | Privilege Limitation for Production and Operation (CM-5(5))
  • SA-10 Developer Configuration Management
  • SA-15 Development Process, Standards, and Tools (SA-15)
  • SR-3 Supply Chain Controls and Processes (SR-3)

C5 (Germany) · 4 controls

NIST SP 800-53 Rev 5 · 4 controls

  • SEC11-BP05 Centralize services for packages and dependencies
  • SEC11-BP06 Deploy software programmatically
  • SEC11-BP07 Regularly assess security properties of the pipelines

ISO 27001:2022 · 3 controls

  • 8.25 Secure development life cycle
  • 8.31 Separation of development, test and production environments
  • 8.4 Access to source code

ISO 27002:2022 · 3 controls

  • 8.25 Secure development life cycle
  • 8.31 Separation of development, test and production environments
  • 8.4 Access to source code

NIST SP 800-171 Rev 3 · 3 controls

  • 03.04.03 Configuration Change Control
  • 03.04.05 Access Restrictions for Change
  • 03.17.03 Supply Chain Requirements and Processes

CIS Controls v8 · 2 controls

  • CIS-16.7 Use Standard Hardening Configuration Templates for Application Infrastructure
  • CIS-16.8 Separate Production and Non-Production Systems

ISO 27701:2019 · 2 controls

  • 6.6.4 System and application access control
  • 6.9.1 Operational procedures and responsibilities
  • NIST-CSF-GV.SC-09 Supply chain security practices are integrated into cybersecurity and enterprise risk management programs, and their performance is monitored throughout the technology product and service life cycle
  • NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

NIST SP 800-172 · 2 controls

  • 3.13.2e Introduce Unpredictability into System Operations
  • 3.4.1e Authoritative Source for Software and Firmware

CMMC 2.0 · 1 control

PCI DSS 4.0 · 1 control

  • 6.5.3 6.5.3 Separate pre-production from production

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 ASBv3-DS-3 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 53 it maps to, and the evidence behind each claim, over MCP and REST.