Azure Security Benchmark
Governance and Strategy

Azure Security Benchmark ASBv3-GS-10: Define and implement DevOps security strategy

Mandate security controls as part of the organisation's DevOps engineering and operating standard, defining security objectives, control requirements and tooling specifications.

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

What else in your programme already covers this

This control maps to 35 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 · 6 controls

FedRAMP High · 3 controls

  • SA-1 Policy and Procedures
  • SA-15 Development Process, Standards, and Tools (SA-15)
  • SA-3 System Development Life Cycle

FedRAMP Moderate · 3 controls

  • SA-1 Policy and Procedures
  • SA-15 Development Process, Standards, and Tools (SA-15)
  • SA-3 System Development Life Cycle

NIST SP 800-53 Rev 5 · 3 controls

  • SEC01-BP03 Identify and validate control objectives
  • SEC11-BP08 Build a program that embeds security ownership in workload teams
  • CCM-AIS-01 Application and Interface Security Policy and Procedures
  • CCM-AIS-04 Secure Application Design and Development

ISO 27001:2022 · 2 controls

  • 5.8 Information security in project management
  • 8.25 Secure development life cycle

ISO 27002:2022 · 2 controls

  • 5.8 Information security in project management
  • 8.25 Secure development life cycle

NIST SP 800-161 Rev 1 · 2 controls

PCI DSS 4.0 · 2 controls

  • 6.1.1 6.1.1 Requirement 6 policies and procedures maintained and communicated
  • 6.2.1 6.2.1 Secure development of bespoke and custom software
  • ANSSI-HYG-01 Train Operational Teams in Information System Security

C5 (Germany) · 1 control

  • C5-DEV-01 Policies for the development/procurement of information systems
  • CFTC-SS-5 Systems Development and Quality Assurance Category

CIS Controls v8 · 1 control

  • CIS-16.1 Establish and Maintain a Secure Application Development Process

ISO 27701:2019 · 1 control

  • 6.11.2 Security in development and support processes
  • NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle
  • 03.16.01 Security Engineering Principles

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 Governance and Strategy

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

Azure Security Benchmark ASBv3-GS-10 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 35 it maps to, and the evidence behind each claim, over MCP and REST.