NIST Cybersecurity Framework 2.0 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 NIST Cybersecurity Framework 2.0. 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 NIST Cybersecurity Framework 2.0 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.
71 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.
Both prevent installation and execution of software that is not approved.
Both require software maintained and patched commensurate with the risk carried.
Both require configuration practice applied to reduce exposed application features.
Both require the environment protected by controlling how it reaches external networks.
Both require vendor hardening applied as established configuration practice.
Both require operating system configuration hardened and applied consistently.
Both require software and runtime activity monitored to find adverse events.
Both require personnel given awareness of threats and reporting expectations.
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