NIST SP 800-172NIST Cybersecurity Framework 2.0

NIST SP 800-172 covers 32.1% of NIST Cybersecurity Framework 2.0

34 of the 106 controls in NIST Cybersecurity Framework 2.0 are already satisfied by evidence you collected for NIST SP 800-172. 72 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.

32.1%
of the target already covered
34
controls evidenced
72
genuine gaps
3
claims rejected in review

This number is directional. It says how much of NIST Cybersecurity Framework 2.0 your NIST SP 800-172 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.

77 candidate mappings were examined and 3 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.

DE - Detect7 of 11 evidenced, 4 to do
ID - Identify11 of 21 evidenced, 10 to do
PR - Protect9 of 22 evidenced, 13 to do
RS - Respond3 of 13 evidenced, 10 to do
GV - Govern4 of 28 evidenced, 24 to do
Govern0 of 3 evidenced, 3 to do
RC - Recover0 of 8 evidenced, 8 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.

3.11.3eNIST-CSF-DE.AE-02argued against and upheld
Potentially adverse events are analyzed to better understand associated activities

Advanced automation and analytics supporting analysts is exactly analysis of potentially adverse events.

3.11.2eNIST-CSF-DE.AE-02argued against and upheld
Potentially adverse events are analyzed to better understand associated activities

Threat hunting analyses adverse activity to detect, track and disrupt threats evading controls.

3.6.1eNIST-CSF-DE.AE-02argued against and upheld
Potentially adverse events are analyzed to better understand associated activities

A 24/7 security operations centre performs the continuous event analysis this subcategory requires.

3.11.3eNIST-CSF-DE.AE-03argued against and upheld
Information is correlated from multiple sources

Advanced analytics predicting and identifying risks correlates information across systems and components.

3.14.6eNIST-CSF-DE.AE-07argued against and upheld
Cyber threat intelligence and contextual information are integrated into analysis

Threat indicator information from external organizations directly informs intrusion detection analysis.

3.11.1eNIST-CSF-DE.AE-07argued against and upheld
Cyber threat intelligence and contextual information are integrated into analysis

Threat intelligence from open, commercial and government sources is integrated into monitoring and hunting analysis.

3.14.2eNIST-CSF-DE.CM-01argued against and upheld
Networks and network services are monitored to find potentially adverse events

Ongoing monitoring with advanced detection capabilities covers networks and network services.

3.11.2eNIST-CSF-DE.CM-01argued against and upheld
Networks and network services are monitored to find potentially adverse events

Threat hunting searches organizational systems for indicators of compromise across the network.

Claims that did not hold

3 proposed mappings for this pair were rejected. They are kept in the graph rather than deleted, so what was thrown out is as inspectable as what survived. A crosswalk that never rejects anything is not being judged.

3.5.3eNIST-CSF-PR.AA-03
Users, services, and hardware are authenticated

corrected 2026-08-19: judged from a title claiming multifactor authentication, while the control carried 3.5.2e password-management text. Issued 800-172 3.5.3e is comply-to-connect: prohibit connection of unknown or unverified components. Authentication evidence does not satisfy it.

Claimed at high confidence before it was rejected.

3.13.1eNIST-CSF-PR.IR-01
Networks and environments are protected from unauthorized access

control identity corrected 2026-08-19: issued 3.13.1e is component diversity to limit malicious code propagation; these mappings are boundary protection and segmentation, judged against 3.1.3e's content which this control was wrongly carrying

Claimed at high confidence before it was rejected.

3.13.2eNIST-CSF-PR.PS-06
Secure software development practices are integrated throughout the SDLC

control identity corrected 2026-08-19: issued 3.13.2e is introducing unpredictability into operations; these mappings are least privilege and secure engineering, a subject that appears nowhere in the issued 800-172

Claimed at high confidence before it was rejected.

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