NIST SP 800-172NIST SP 800-171 Rev 3

NIST SP 800-172 covers 25.8% of NIST SP 800-171 Rev 3

25 of the 97 controls in NIST SP 800-171 Rev 3 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.

25.8%
of the target already covered
25
controls evidenced
72
genuine gaps
7
claims rejected in review

This number is directional. It says how much of NIST SP 800-171 Rev 3 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.

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

03.02 AT (Awareness and Training)2 of 2 evidenced
03.11 RA (Risk Assessment)2 of 3 evidenced, 1 to do
03.17 SR (Supply Chain Risk Management)2 of 3 evidenced, 1 to do
03.14 SI (System and Information Integrity)3 of 5 evidenced, 2 to do
03.12 CA (Security Assessment and Monitoring)2 of 4 evidenced, 2 to do
03.09 PS (Personnel Security)1 of 2 evidenced, 1 to do
03.06 IR (Incident Response)2 of 5 evidenced, 3 to do
03.05 IA (Identification and Authentication)3 of 8 evidenced, 5 to do
03.15 PL (Planning)1 of 3 evidenced, 2 to do
03.16 SA (System and Services Acquisition)1 of 3 evidenced, 2 to do
03.04 CM (Configuration Management)2 of 10 evidenced, 8 to do
03.01 AC (Access Control)3 of 16 evidenced, 13 to do
03.03 AU (Audit and Accountability)1 of 8 evidenced, 7 to do
03.07 MA (Maintenance)0 of 3 evidenced, 3 to do
03.08 MP (Media Protection)0 of 7 evidenced, 7 to do
03.10 PE (Physical Protection)0 of 5 evidenced, 5 to do
03.13 SC (System and Communications Protection)0 of 10 evidenced, 10 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.1.3e03.01.03argued against and upheld
Information Flow Enforcement

Secure transfer solutions enforcing approved flows between connected systems is flow enforcement.

3.1.1e03.01.04argued against and upheld
Separation of Duties

Dual authorization for critical operations is the access authorization that supports separation of duties.

3.1.2e03.01.20argued against and upheld
Use of External Systems

Restricting access to only organization owned, provisioned or issued resources governs external system use.

3.2.1e03.02.01argued against and upheld
Literacy Training and Awareness

Training at initial hire, annually and after system changes with current threat content is this requirement.

3.2.2e03.02.02argued against and upheld
Role-Based Training

Practical exercises for managers, executives and selected personnel is role-based training.

3.11.3e03.03.05argued against and upheld
Audit Record Review, Analysis, and Reporting

Advanced automation and analytics supporting analysts reviews records for indicators of unusual activity.

3.4.2e03.04.08argued against and upheld
Authorized Software - Allow by Exception

Automated detection then removal of unauthorized components enforces the allow-by-exception policy.

3.4.1e03.04.08argued against and upheld
Authorized Software - Allow by Exception

An authoritative source of approved vetted software identifies what is allowed to execute.

Claims that did not hold

7 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.13.2e03.01.05
Least Privilege

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.

3.5.3e03.05.01
User Identification and Authentication

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.5.3e03.05.03
Multi-Factor Authentication

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.1e03.13.01
Boundary Protection

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.1e03.13.06
Network Communications - Deny by Default - Allow by Exception

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.3e03.16.01
Security Engineering Principles

control identity corrected 2026-08-19: issued 3.13.3e is confusing and misleading adversaries; these mappings were judged against diversity content, which belongs to issued 3.13.1e

Claimed at high confidence before it was rejected.

3.13.2e03.16.01
Security Engineering Principles

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