Azure Security Benchmark
Governance and Strategy

Azure Security Benchmark ASBv3-GS-5: Define and implement security posture management strategy

Define and implement a security posture management strategy establishing policy, procedure and standards for security configuration management and vulnerability management.

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

What else in your programme already covers this

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

C5 (Germany) · 6 controls

  • C5-COM-04 Information on information security performance and management assessment of the ISMS
  • C5-OIS-01 Information Security Management System (ISMS)
  • C5-OIS-07 Application of the Risk Management Policy
  • C5-OPS-18 Managing Vulnerabilities, Malfunctions and Errors - Concept
  • C5-OPS-23 Managing Vulnerabilities, Malfunctions and Errors - System Hardening
  • C5-SP-01 Documentation, communication and provision of policies and instructions

NIST SP 800-53 Rev 5 · 6 controls

FedRAMP High · 5 controls

  • CA-1 Policy and Procedures
  • CM-1 Policy and Procedures
  • CM-9 Configuration Management Plan
  • RA-1 Policy and Procedures
  • SI-1 Policy and Procedures

FedRAMP Moderate · 5 controls

  • CA-1 Policy and Procedures
  • CM-1 Policy and Procedures
  • CM-9 Configuration Management Plan
  • RA-1 Policy and Procedures
  • SI-1 Policy and Procedures
  • AUCDR-IS-STEP1 Step 1 - Define and implement security governance for CDR data
  • AUCDR-IS-STEP3 Step 3 - Have and maintain an information security capability
  • AUCDR-IS-STEP4 Step 4 - Implement a formal controls assessment program
  • CCM-CCC-01 Change Management Policy and Procedures
  • CCM-GRC-05 Information Security Program
  • CCM-TVM-01 Threat and Vulnerability Management Policy and Procedures

HIPAA Security Rule · 3 controls

NIST SP 800-66 Rev 2 · 3 controls

  • ANSSI-HYG-34 Define an Update Policy for Information System Components
  • ANSSI-HYG-38 Carry Out Regular Security Checks and Audits and Apply the Corrective Actions

APRA CPS 234 · 2 controls

  • SEC01-BP03 Identify and validate control objectives
  • SEC01-BP06 Automate deployment of standard security controls

CIS Controls v8 · 2 controls

  • CIS-4.1 Establish and Maintain a Secure Configuration Process
  • CIS-7.1 Establish and Maintain a Vulnerability Management Process

ISO 27002:2022 · 2 controls

  • 5.36 Compliance with policies, rules and standards for information security
  • 8.9 Configuration management
  • NIST-CSF-GV.PO-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced
  • NIST-CSF-PR.PS-01 Configuration management practices are established and applied

NIST SP 800-161 Rev 1 · 2 controls

NIST SP 800-171 Rev 3 · 2 controls

PCI DSS 4.0 · 2 controls

  • 11.1.1 11.1.1 Requirement 11 policies and procedures managed
  • 2.1.1 2.1.1 Requirement 2 policies and procedures governed
  • CFTC-SS-1 Program of Risk Analysis and Oversight

CMMC 2.0 · 1 control

ISO 27001:2022 · 1 control

  • 5.36 Compliance with policies, rules and standards for information security

NIST SP 800-218 · 1 control

SOC 2 · 1 control

  • SOC2-CC4.1 CC4.1 Ongoing and separate evaluations of control (COSO principle 16)

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-5 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 59 it maps to, and the evidence behind each claim, over MCP and REST.