CIS Controls v8 covers 67.6% of ASD Strategies to Mitigate Cyber Security Incidents
25 of the 37 controls in ASD Strategies to Mitigate Cyber Security Incidents are already satisfied by evidence you collected for CIS Controls v8. 12 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.
This number is directional. It says how much of ASD Strategies to Mitigate Cyber Security Incidents your CIS Controls v8 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.
89 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.
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.
Library allowlisting covers the DLL limb of application control explicitly.
Script allowlisting by signature and version control covers the script limb.
Application allowlisting so only authorised software executes is the same control.
Restricting browser and email client plugins and extensions is user application hardening.
Blocking unnecessary file types at the gateway is the approved attachment type rule.
Email server anti malware with attachment scanning is the malware inspection required.
Application layer filtering by proxy inspects and controls web traffic in both directions.
Enforced network based URL filtering is web content filtering by approved destination.
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