NIST SP 800-171 Rev 3 covers 70.3% of ASD Strategies to Mitigate Cyber Security Incidents
26 of the 37 controls in ASD Strategies to Mitigate Cyber Security Incidents are already satisfied by evidence you collected for NIST SP 800-171 Rev 3. 11 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.
What this leaves you to do
ASD Strategies to Mitigate Cyber Security Incidents has 37 controls. Holding NIST SP 800-171 Rev 3 already evidences 26 of them, so the work in front of you is 11 controls, not 37, which is 30% of the standard rather than all of it.
That is the whole claim. Every number in that sentence comes from the two counts above it and can be re-derived from the free tools without taking our word for any of it.
In money, using only our numbers. The full report is $299 and names 26 controls of ASD Strategies to Mitigate Cyber Security Incidents you do not have to implement again, which is $11.50 per control identified. That arithmetic uses our price and our count and assumes nothing about you.
In your hours, using your assumption. We do not know what a control costs you to implement, so pick the column that looks like your organisation. These are your figures, not our claim.
| If a control takes you | 4 hours | 8 hours | 16 hours |
|---|---|---|---|
| the 26 already evidenced are | 104 hours | 208 hours | 416 hours |
| and the 11 remaining are | 44 hours | 88 hours | 176 hours |
Multiply by your own rate. We publish no rate because we have not measured yours, and a number built on an invented rate is the kind of claim this platform exists to argue against.
This number is directional. It says how much of ASD Strategies to Mitigate Cyber Security Incidents your NIST SP 800-171 Rev 3 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.
44 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.
Authorized software identified with a deny-all allow-by-exception execution policy.
Flaw remediation installs security-relevant updates within defined periods after release.
Acceptable mobile code defined and its use authorized, monitored and controlled.
Least functionality prohibits or restricts unnecessary functions and services in applications.
Configuration settings set to the most restrictive mode consistent with operations.
Malicious code protection at system entry points covers inbound mail content.
Communications monitored and controlled at managed interfaces to external networks.
External network connections permitted only through managed interfaces.
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