PCI DSS 4.0 covers 40.5% of NIST SP 800-218
17 of the 42 controls in NIST SP 800-218 are already satisfied by evidence you collected for PCI DSS 4.0. 25 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-218 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.
28 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.
PCI requires bespoke software be developed to industry secure-development standards with security across the lifecycle.
Requirement 6 policies must be documented, current, in use and known to all affected development parties.
Roles and responsibilities for all Requirement 6 development activities are documented, assigned and understood.
Development personnel are trained at least annually in secure design and secure coding for their language.
Applicable security requirements must be confirmed in place on changed systems before the change completes.
Roles and functions are separated between production and pre-production so development access is accountable.
Pre-production environments must be separated from production and the separation enforced by access controls.
Separation of roles means no single person can both author and promote a change unreviewed.
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