Azure Security BenchmarkACSC Essential Eight

Azure Security Benchmark covers 62.5% of ACSC Essential Eight

15 of the 24 controls in ACSC Essential Eight are already satisfied by evidence you collected for Azure Security Benchmark. 9 are genuine gaps. Every claim below was judged against both control sets and then argued against; the ones that did not survive are published further down with the reason each failed.

62.5%
of the target already covered
15
controls evidenced
9
genuine gaps
0
claims rejected in review

This number is directional. It says how much of ACSC Essential Eight your Azure Security Benchmark evidence satisfies. The reverse pair is a different number, often very different, because a security standard has enormous depth for access control and almost none for lawful basis or data subject rights.

60 candidate mappings were examined and 0 were removed. Signed off 2026-08-19, review level machine verified. Mappings were judged by Claude Code rather than read line by line by a practitioner. Every claim shows its reasoning so you can check it. Ask and a practitioner will review this pair.

Where the gaps are

Coverage is never evenly spread. A source standard usually satisfies one part of a target almost completely and barely touches another, and which part is which is the thing worth knowing before you plan the work.

Restrict Administrative Privileges3 of 3 evidenced
Regular Backups3 of 3 evidenced
Multi-factor Authentication3 of 3 evidenced
Application Control2 of 3 evidenced, 1 to do
Patch Applications2 of 3 evidenced, 1 to do
Patch Operating Systems2 of 3 evidenced, 1 to do
Configure Microsoft Office Macro Settings0 of 3 evidenced, 3 to do
User Application Hardening0 of 3 evidenced, 3 to do

Theme level, not control level, deliberately. The per-control list of what is evidenced and what is a gap is the report itself, so publishing it here would be publishing the thing being sold.

Claims that held

A sample. Each one names the control whose evidence does the work, the control it satisfies, and why.

ASB v3 PA-6E8-ADMIN-ML1argued against and upheld
Restrict Administrative Privileges (ML1)

Privileged access workstations provide the separate privileged operating environment the control requires.

ASB v3 PA-1E8-ADMIN-ML1argued against and upheld
Restrict Administrative Privileges (ML1)

Dedicated separated highly privileged accounts with documented role assignments is the core requirement.

ASB v3 LT-5E8-ADMIN-ML2argued against and upheld
Restrict Administrative Privileges (ML2)

Centralised log management and analysis covers central logging and timely analysis of privileged events.

ASB v3 PA-4E8-ADMIN-ML2argued against and upheld
Restrict Administrative Privileges (ML2)

Regular review and reconciliation of privileged entitlements matches the revalidation requirement.

ASB v3 PA-7E8-ADMIN-ML3argued against and upheld
Restrict Administrative Privileges (ML3)

Just enough administration is precisely limiting privileged access to what duties require.

ASB v3 PA-6E8-ADMIN-ML3argued against and upheld
Restrict Administrative Privileges (ML3)

Secured isolated administrative workstations are the Secure Admin Workstation requirement.

ASB v3 PA-2E8-ADMIN-ML3argued against and upheld
Restrict Administrative Privileges (ML3)

Just in time elevation with approval workflows is exactly the just in time administration requirement.

ASB v3 AM-5E8-APP-ML1argued against and upheld
Application Control (ML1)

An enforced software allow list blocking unauthorised execution is application control.

Claims that did not hold

Nothing proposed for this pair was rejected in review. That is unusual and worth knowing rather than hiding: it means the candidate set was small and every candidate held.

The full report

Everything above is a sample. The report is every evidenced control and every gap, with the reasoning and the source document behind each one, in a form you can hand to an assessor. $299, emailed immediately.

Buy this crosswalk