Azure Security Benchmark
What is Azure Security Benchmark?
Microsoft Azure cloud security best practices and controls. It comprises 85 controls organised across 12 domains, and applies in International.
How Azure Security Benchmark maps to other frameworks
All 85 controls, each one mapped to the equivalent requirement in other standards, with the evidence that carries across and the mappings that were judged and rejected shown alongside. No account needed to look.
See the control mappings →The 12 domains Azure Security Benchmark groups its controls into
Frameworks that share controls with Azure Security Benchmark
Each of these has at least one control mapped to a control in Azure Security Benchmark. The number is how many Azure Security Benchmark controls are shared, counted from the mapping graph.
Implementation guides for frameworks that overlap Azure Security Benchmark
Training on frameworks that overlap Azure Security Benchmark
There is no course on Azure Security Benchmark itself. These cover frameworks that share controls with it, so the material carries across even though the standard named is different.
Where Azure Security Benchmark overlaps with the standards you already hold
What an auditor will ask you for
All 85 Azure Security Benchmark controls, each with what it requires, the artefacts an auditor will ask you for, and where it commonly fails. Free to read, nothing to fill in.
Read the Azure Security Benchmark evidence request listWhat Azure Security Benchmark means in your sector
What Azure Security Benchmark means for your job
Questions people ask about Azure Security Benchmark
What is Azure Security Benchmark?
How many controls does Azure Security Benchmark have?
Where does Azure Security Benchmark apply?
What frameworks does Azure Security Benchmark map to?
How do I get started with Azure Security Benchmark compliance?
Query Azure Security Benchmark programmatically
Azure Security Benchmark, its 85 controls and every mapping into other standards are available over a REST endpoint and an MCP server, so an agent can read them directly. The free tier is 10 calls a day and needs no signup.
Azure Security Benchmark API reference and MCP config →What Azure Security Benchmark requires, control by control
Each page carries the requirement text for one Azure Security Benchmark control and what an assessor expects to see as evidence.
- ASB-V3-AM-1 Track asset inventory and their risks
- ASB-V3-AM-2 Use only approved services
- ASB-V3-AM-3 Ensure security of asset lifecycle management
- ASB-V3-AM-4 Limit access to asset management
- ASB-V3-AM-5 Use only approved applications in virtual machine
- ASB-V3-BR-1 Ensure regular automated backups
- ASB-V3-BR-2 Protect backup and recovery data
- ASB-V3-BR-3 Monitor backups
- ASB-V3-BR-4 Regularly test backup
- ASB-V3-DP-1 Discover, classify, and label sensitive data
How much of another standard Azure Security Benchmark already covers
Each crosswalk is judged control by control, and the mappings that were rejected are kept alongside the ones that held.
- ACSC Essential Eight to Azure Security Benchmark crosswalk
- ANSSI Guide d'hygiene informatique (42 mesures, v2.0) to Azure Security Benchmark crosswalk
- Azure Security Benchmark to APEC Cross-Border Privacy Rules (CBPR) System crosswalk
- ASD Strategies to Mitigate Cyber Security Incidents to Azure Security Benchmark crosswalk
- Australia Consumer Data Right - Banking (CDR) to Azure Security Benchmark crosswalk
- AWS Well-Architected Security Pillar to Azure Security Benchmark crosswalk
- Azure Security Benchmark to C5 (Germany) crosswalk
- CFTC System Safeguards (17 CFR 37, 38, 39, 49) to Azure Security Benchmark crosswalk
How ready are you for Azure Security Benchmark?
Answer 25 questions and get a professional readiness report with gap analysis, maturity scores, and prioritised action items. Results in 5 minutes.