PCI DSS 4.0vsNIST SP 800-172
See exactly how PCI DSS 4.0 controls map to NIST SP 800-172. Pre-computed mappings, identified gaps, and coverage analysis.
A reviewed coverage crosswalk for this pair is available. See which NIST SP 800-172 controls you already evidence.
According to the TheArtOfService Compliance Knowledge Graph:
PCI DSS 4.0 maps to NIST SP 800-172 with 32% coverage across 79 directly mapped controls. Analysis of 249 PCI DSS 4.0 controls identifies 170 compliance gaps, primarily concentrated in Req 3: Protect Stored Account Data.
Source: TheArtOfService Knowledge Graph | 249 controls analysed | 686 frameworks | 310K+ cross-framework mappings
Control Mappings
Showing 20 of 100 mapped controls across 12 domains. Sign up to explore all 310K+ mappings across 686 frameworks.
Req 1: Network Security Controls(9 mappings)
Req 10: Logging and Monitoring(9 mappings)
Req 11: Test Security Regularly(2 mappings)
+80 more mappings
Plus AI-powered gap analysis, compliance advisory, PDF exports, and cross-mapping for all 686 frameworks.
Create Free Account →Free forever, no credit card required
The PCI DSS 4.0 to NIST SP 800-172 crosswalk
The table above lists candidate mappings. A crosswalk answers the narrower question you are probably here for: which NIST SP 800-172 controls your existing PCI DSS 4.0 work already satisfies, which are real gaps, and the reasoning behind every claim so you can check it. One pair, $299, one time.
Coverage does not run both ways. PCI DSS 4.0 into NIST SP 800-172 lands at 42.9%, while NIST SP 800-172 into PCI DSS 4.0 lands at 10.8%, on the same two control sets. That is not a rounding difference. It is the whole reason these are two separate reports: one asks what your PCI DSS 4.0 evidence buys you for NIST SP 800-172, the other asks the reverse.
15 of 35 NIST SP 800-172 controls are evidenced by work you have already done for PCI DSS 4.0. 20 are genuine gaps.
A sample of what the report says
Network security controls implemented between trusted and untrusted networks control flows between domains.
Grounded in 1.4.1 NSCs between trusted and untrusted networks. Confidence high, survived the refutation pass.
Employ dual authorization to execute critical or sensitive system and organizational operations affecting CUI.
Every one of the 15 evidenced controls and 20 gaps in the report carries this much reasoning, so you can check the claim rather than take it on trust.
27 of 249 PCI DSS 4.0 controls are evidenced by work you have already done for NIST SP 800-172. 222 are genuine gaps.
A sample of what the report says
Secure transfer solutions control what may enter a security domain from connected systems.
Grounded in 3.1.3e Employ Secure Information Transfer Solutions. Confidence high, survived the refutation pass.
All security policies and operational procedures for Requirement 1 are documented, kept current, in use, and known to affected parties.
Every one of the 27 evidenced controls and 222 gaps in the report carries this much reasoning, so you can check the claim rather than take it on trust.
- Every evidenced control, with the reasoning behind it
- Every gap, with what it requires
- Its level of review stated plainly, not a bare number
Why this page shows two different percentages. The 32% in the header counts how many PCI DSS 4.0 controls carry at least one candidate mapping in the graph, before any review. The crosswalk percentage counts something stricter: how many NIST SP 800-172 controls are actually evidenced, after a pass that argued against each mapping and kept only what survived. They answer different questions and they are not meant to agree.
A crosswalk narrows the work. It does not replace an audit, and your assessor may take a different view on individual controls. Mappings between frameworks are judgements, not text printed in either standard, which is why every claim in the report shows its reasoning. Questions go to support@theartofservice.com.
Related Comparisons
Other PCI DSS 4.0 comparisons
Other NIST SP 800-172 comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 686 frameworks, at a fraction of consulting costs.
Free
- ✓ 686 framework browser
- ✓ Cross-framework mappings (310K+)
- ✓ 824 compliance assessments
- ✓ 3 AI queries & searches per day
Professional
- ✓ Unlimited AI Compliance Advisory
- ✓ Unlimited full-text search
- ✓ Framework self-assessment
- ✓ PDF, Excel & CSV exports
What are the key differences between PCI DSS 4.0 and NIST SP 800-172?
PCI DSS 4.0 has 249 controls across its framework, while NIST SP 800-172 covers 35 controls. Direct mapping analysis identifies 79 overlapping controls (32% coverage). The frameworks diverge most significantly in Req 3: Protect Stored Account Data, where 26 PCI DSS 4.0 controls have no direct NIST SP 800-172 equivalent.
How many controls map between PCI DSS 4.0 and NIST SP 800-172?
Of 249 total PCI DSS 4.0 controls, 79 map directly to NIST SP 800-172 controls, representing 32% coverage. The remaining 170 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.
What are the compliance gaps when mapping PCI DSS 4.0 to NIST SP 800-172?
170 PCI DSS 4.0 controls have no direct equivalent in NIST SP 800-172. The highest concentration of gaps is in Req 3: Protect Stored Account Data with 26 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.
Which control domains have the most gaps between PCI DSS 4.0 and NIST SP 800-172?
The domain with the highest gap count is Req 3: Protect Stored Account Data (26 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.
Related Resources
This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.