ACSC Essential EightISO 27001:2022

ACSC Essential Eight covers 12.9% of ISO 27001:2022

12 of the 93 controls in ISO 27001:2022 are already satisfied by evidence you collected for ACSC Essential Eight. 81 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.

12.9%
of the target already covered
12
controls evidenced
81
genuine gaps
0
claims rejected in review

This number is directional. It says how much of ISO 27001:2022 your ACSC Essential Eight 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.

46 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.

Technological controls9 of 34 evidenced, 25 to do
Organizational controls3 of 37 evidenced, 34 to do
People controls0 of 8 evidenced, 8 to do
Physical controls0 of 14 evidenced, 14 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.

E8-APP-ML25.25argued against and upheld
Assessment and decision on information security events

Cyber security events are analysed in a timely manner to decide which are incidents.

E8-ADMIN-ML25.26argued against and upheld
Response to information security incidents

On identifying an incident the cyber security incident response plan must be enacted.

E8-BACKUP-ML15.30argued against and upheld
ICT readiness for business continuity

Backups follow business continuity requirements and restoration is tested in disaster recovery exercises.

E8-BACKUP-ML38.13argued against and upheld
Information backup

Backup administrators cannot modify or delete backups during the retention period.

E8-BACKUP-ML28.13argued against and upheld
Information backup

Privileged accounts other than backup administrators cannot access, modify or delete backups.

E8-BACKUP-ML18.13argued against and upheld
Information backup

Backups of data, applications and settings are performed, retained and restoration tested.

E8-ADMIN-ML28.15argued against and upheld
Logging

Privileged access events are centrally logged, protected from modification and analysed in time.

E8-UAH-ML38.15argued against and upheld
Logging

PowerShell module, script block and transcription logs are produced and centrally collected.

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