International

Azure Security Benchmark

85 controls. 144 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

85 controls 144 frameworks share controls with it International verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
AM-2Use only approved services20
AM-3Ensure security of asset lifecycle management29
ASBv3-AM-1Track asset inventory and their risks27
ASBv3-AM-4Limit access to asset management22
ASBv3-AM-5Use only approved applications in virtual machine21
ASBv3-BR-3Monitor backups17
ASBv3-BR-4Regularly test backup21
ASBv3-DP-1Discover, classify, and label sensitive data23
ASBv3-DP-5Use customer-managed key option in data at rest encryption when required19
ASBv3-DP-6Use a secure key management process19
ASBv3-DP-7Use a secure certificate management process13
ASBv3-DP-8Ensure security of key and certificate repository15
ASBv3-DS-1Conduct threat modeling22
ASBv3-DS-3Secure DevOps infrastructure18
ASBv3-DS-4Integrate static application security testing into DevOps pipeline17
ASBv3-DS-5Integrate dynamic application security testing into DevOps pipeline16
ASBv3-DS-7Enable logging and monitoring in DevOps16
ASBv3-ES-3Ensure anti-malware software and signatures are updated22
ASBv3-GS-10Define and implement DevOps security strategy18
ASBv3-GS-2Define and implement enterprise segmentation/separation of duties strategy22
ASBv3-GS-3Define and implement data protection strategy23
ASBv3-GS-4Define and implement network security strategy22
ASBv3-GS-5Define and implement security posture management strategy24
ASBv3-GS-6Define and implement identity and privileged access strategy24
ASBv3-GS-7Define and implement logging, threat detection and incident response strategy23
ASBv3-GS-8Define and implement backup and recovery strategy20
ASBv3-GS-9Define and implement endpoint security strategy19
ASBv3-IM-2Protect identity and authentication systems23
ASBv3-IM-5Use single sign-on (SSO) for application access11
ASBv3-IM-8Restrict the exposure of credential and secrets23
ASBv3-IM-9Secure user access to existing applications9
ASBv3-IR-1Preparation - update incident response plan and handling process30
ASBv3-IR-2Preparation - setup incident notification25
ASBv3-IR-3Detection and analysis - create incidents based on high-quality alerts23
ASBv3-IR-4Detection and analysis - investigate an incident23
ASBv3-IR-5Detection and analysis - prioritize incidents21
ASBv3-IR-6Containment, eradication and recovery - automate the incident handling19
ASBv3-IR-7Post-incident activity - conduct lesson learned and retain evidence25
ASBv3-LT-1Enable threat detection capabilities24
ASBv3-LT-2Enable threat detection for identity and access management21
ASBv3-LT-6Configure log storage retention22
ASBv3-LT-7Use approved time synchronization sources13
ASBv3-NS-10Ensure Domain Name System (DNS) security8
ASBv3-NS-4Deploy intrusion detection/intrusion prevention systems (IDS/IPS)18
ASBv3-NS-6Deploy web application firewall15
ASBv3-NS-7Simplify network security configuration14
ASBv3-NS-8Detect and disable insecure services and protocols24
ASBv3-NS-9Connect on-premises or cloud network privately18
ASBv3-PA-4Review and reconcile user access regularly24
ASBv3-PA-5Set up emergency access14
ASBv3-PA-6Use privileged access workstations21
ASBv3-PA-7Follow just enough administration (least privilege) principle29
ASBv3-PA-8Determine access process for cloud provider support21
ASBv3-PV-1Define and establish secure configurations26
ASBv3-PV-3Define and establish secure configurations for compute resources22
ASBv3-PV-4Audit and enforce secure configurations for compute resources24
ASBv3-PV-6Rapidly and automatically remediate vulnerabilities27
ASBv3-PV-7Conduct regular red team operations26
BR-1Ensure regular automated backups22
BR-2Protect backup and recovery data23
DP-2Monitor anomalies and threats targeting sensitive data21
DP-3Encrypt sensitive data in transit23
DP-4Enable data at rest encryption by default23
DS-2Ensure software supply chain security129
DS-6Enforce security of workload throughout DevOps lifecycle18
ES-1Use Endpoint Detection and Response (EDR)23
ES-2Use modern anti-malware software24
GS-1Align organization roles, responsibilities and accountabilities28
IM-1Use centralized identity and authentication system25
IM-3Manage application identities securely and automatically21
IM-4Authenticate server and services16
IM-6Use strong authentication controls26
IM-7Restrict resource access based on conditions23
LT-3Enable logging for security investigation26
LT-4Enable network logging for security investigation20
LT-5Centralize security log management and analysis24
NS-1Establish network segmentation boundaries24
NS-2Secure cloud services with network controls22
NS-3Deploy firewall at the edge of enterprise network21
NS-5Deploy DDOS protection10
PA-1Separate and limit highly privileged/administrative users25
PA-2Avoid standing access for user accounts and permissions22
PA-3Manage lifecycle of identities and entitlements23
PV-2Audit and enforce secure configurations27
PV-5Perform vulnerability assessments31

Tell me when Azure Security Benchmark files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What an auditor will ask you to produce

The artefacts named on the failure modes this framework speaks to.

  • OT asset inventory
  • Zone and conduit diagram
  • Patch register
  • Remote access policy
  • Infrastructure/virtualization security policy
  • Network segmentation + defense architecture
  • Annual review
  • RACI for infosec roles
  • RACI matrix
  • role descriptions

How programmes fail on this

Failure modes named by this framework and others. Each opens the full record.

What this page is

A control-level reference for Azure Security Benchmark, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition