CMMC 2.0ASD Strategies to Mitigate Cyber Security Incidents

CMMC 2.0 covers 75.7% of ASD Strategies to Mitigate Cyber Security Incidents

28 of the 37 controls in ASD Strategies to Mitigate Cyber Security Incidents are already satisfied by evidence you collected for CMMC 2.0. 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.

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

This number is directional. It says how much of ASD Strategies to Mitigate Cyber Security Incidents your CMMC 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.

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

Preventing Malicious Insiders1 of 1 evidenced
Detecting Cyber Security Incidents and Responding5 of 6 evidenced, 1 to do
Preventing Malware Delivery and Execution14 of 17 evidenced, 3 to do
Limiting the Extent of Cyber Security Incidents8 of 10 evidenced, 2 to do
Recovering Data and System Availability0 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.

CM.L2-3.4.8ASD37-01argued against and upheld
Application control (Essential)

Both operate a software execution policy allowing only authorized programs to run.

SI.L2-3.14.1ASD37-02argued against and upheld
Patch applications (Essential)

Both require application flaws identified and corrected promptly, though the 48 hour parameter differs.

SC.L2-3.13.13ASD37-03argued against and upheld
Configure Microsoft Office macro settings (Essential)

Office macros are mobile code, and both restrict which mobile code may execute.

CM.L2-3.4.7ASD37-04argued against and upheld
User application hardening (Essential)

Both require unnecessary features and functions to be disabled on user applications.

CM.L2-3.4.2ASD37-04argued against and upheld
User application hardening (Essential)

Both define and enforce security configuration settings for the products in use.

SI.L2-3.14.5ASD37-06argued against and upheld
Email content filtering (Excellent)

Both require files arriving from external sources scanned as they are opened.

SI.L2-3.14.2ASD37-06argued against and upheld
Email content filtering (Excellent)

Email is the entry point where both require malicious code protection.

SC.L2-3.13.1ASD37-07argued against and upheld
Web content filtering (Excellent)

Both monitor and control communications crossing the external system boundary.

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