TheArtOfService
NIST SP 800-218NIST SP 800-161 Rev 1

NIST SP 800-218 covers 8.9% of NIST SP 800-161 Rev 1

17 of the 191 controls in NIST SP 800-161 Rev 1 are already satisfied by evidence you collected for NIST SP 800-218. 174 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.

8.9%
of the target already covered
17
controls evidenced
174
genuine gaps
0
claims rejected in review

This number is directional. It says how much of NIST SP 800-161 Rev 1 your NIST SP 800-218 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.

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

C-SCRM Family: System and Services Acquisition9 of 15 evidenced, 6 to do
C-SCRM Family: System and Information Integrity2 of 8 evidenced, 6 to do
C-SCRM Family: Assessment, Authorization, and Monitoring1 of 6 evidenced, 5 to do
C-SCRM Family: Supply Chain Risk Management2 of 13 evidenced, 11 to do
C-SCRM Family: Configuration Management2 of 14 evidenced, 12 to do
C-SCRM Family: Risk Assessment1 of 7 evidenced, 6 to do
C-SCRM Family: Access Control0 of 14 evidenced, 14 to do
C-SCRM Family: Awareness and Training0 of 4 evidenced, 4 to do
C-SCRM Family: Audit and Accountability0 of 9 evidenced, 9 to do
C-SCRM Family: Contingency Planning0 of 8 evidenced, 8 to do
C-SCRM Family: Identification and Authentication0 of 7 evidenced, 7 to do
C-SCRM Family: Incident Response0 of 9 evidenced, 9 to do
C-SCRM Family: Maintenance0 of 8 evidenced, 8 to do
C-SCRM Family: Media Protection0 of 4 evidenced, 4 to do
C-SCRM Family: Physical and Environmental Protection0 of 9 evidenced, 9 to do
C-SCRM Family: Planning0 of 7 evidenced, 7 to do
C-SCRM Family: Program Management0 of 30 evidenced, 30 to do
C-SCRM Family: Personnel Security0 of 4 evidenced, 4 to do
C-SCRM Family: Personally Identifiable Information Processing and Transparency0 of 1 evidenced, 1 to do
C-SCRM Family: System and Communications Protection0 of 14 evidenced, 14 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.

SP800-218-RV.2.2CA-5argued against and upheld
Plan of Action and Milestones

Tracks each vulnerability to closure with a planned response and rationale.

SP800-218-PS.1.1CM-5argued against and upheld
Access Restrictions for Change

Restricts who may change code and records when the right is exercised.

SP800-218-PS.3.2CM-8argued against and upheld
System Component Inventory

The bill of materials is the software component inventory with supplier and origin.

SP800-218-RV.1.1RA-5argued against and upheld
Vulnerability Monitoring and Scanning

Continuously identifies vulnerabilities including intelligence from component upstreams.

SP800-218-PW.4.4RA-5argued against and upheld
Vulnerability Monitoring and Scanning

Uses dependency analysis and known vulnerability databases against acquired components.

SP800-218-PS.1.1SA-10argued against and upheld
Developer Configuration Management

Restricts and logs all changes to code and build scripts, the developer configuration control.

SP800-218-PO.3.2SA-10argued against and upheld
Developer Configuration Management

Treats toolchain configuration as version controlled code, evidencing developer configuration management.

SP800-218-PO.1.2SA-10argued against and upheld
Developer Configuration Management

Enforces requirements through source control, build systems and artifact repositories.

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