PCI DSS 4.0 covers 42.9% of NIST SP 800-172
15 of the 35 controls in NIST SP 800-172 are already satisfied by evidence you collected for PCI DSS 4.0. 20 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.
This number is directional. It says how much of NIST SP 800-172 your PCI DSS 4.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.
77 candidate mappings were examined and 4 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.
Network security controls implemented between trusted and untrusted networks control flows between domains.
Documenting the customised control, its objective and the risk determination is this requirement.
Monitoring provider compliance status at least annually is the continuing monitoring limb.
An established engagement process with due diligence is the supply chain risk assessment.
A documented process for engaging providers with due diligence is the supply chain plan.
External penetration testing at least annually completes the coverage.
Internal penetration testing at least annually matches the required cadence.
A documented penetration testing methodology with tester independence is this requirement.
Claims that did not hold
4 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.
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.
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.
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.
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