Cross-Framework Mapping

PCI 3DS Core Security StandardvsPCI DSS 4.0

See exactly how PCI 3DS Core Security Standard controls map to PCI DSS 4.0. Pre-computed mappings, identified gaps, and coverage analysis.

138
Controls Mapped
5
Gaps Found
82%
Coverage

Need this as a report you can hand to an assessor? A coverage crosswalk for this pair can be built to order.

According to the TheArtOfService Compliance Knowledge Graph:

PCI 3DS Core Security Standard maps to PCI DSS 4.0 with 82% coverage across 117 directly mapped controls. Analysis of 143 PCI 3DS Core Security Standard controls identifies 76 compliance gaps, primarily concentrated in Part 2 Requirement P2-6: Cryptography and key management – PCI 3DS Core Security Standard.

Source: TheArtOfService Knowledge Graph | 143 controls analysed | 908 frameworks | 315K+ cross-framework mappings

Control Mappings

Showing 20 of 138 mapped controls across 14 domains. Sign up to explore all 315K+ mappings across 908 frameworks.

Part 1 Requirement P1-1: Maintain security policies for all personnel – PCI 3DS Core Security Standard(10 mappings)

pci-3ds-core-security-standard::P1-1.1.1P1-1.1.1 Organisation-wide security policy exists and reaches everyone concerned
→12.1.112.1.1 Overall information security policy established and disseminated
pci-3ds-core-security-standard::P1-1.1.2P1-1.1.2 Policy revised when business aims or risks change
→12.1.212.1.2 Security policy reviewed annually and updated as needed
pci-3ds-core-security-standard::P1-1.1.3P1-1.1.3 Policy changes communicated to the people affected
→12.1.112.1.1 Overall information security policy established and disseminated
pci-3ds-core-security-standard::P1-1.1.4P1-1.1.4 Management approval of the security policy
→12.1.412.1.4 Executive ownership of information security formally assigned
pci-3ds-core-security-standard::P1-1.1.5P1-1.1.5 Personnel confirm they have read and understood the policy
→12.6.312.6.3 Security awareness training on hire and annually with acknowledgment
pci-3ds-core-security-standard::P1-1.3.1P1-1.3.1 Security awareness programme in operation
→12.6.112.6.1 Formal security awareness program
pci-3ds-core-security-standard::P1-1.3.2P1-1.3.2 Awareness training at set intervals, fitted to the role
→12.6.312.6.3 Security awareness training on hire and annually with acknowledgment
pci-3ds-core-security-standard::P1-1.3.3P1-1.3.3 Staff know the policy and their own security duties
→12.1.312.1.3 Security roles defined and acknowledged by all personnel
pci-3ds-core-security-standard::P1-1.4.1P1-1.4.1 Background screening before 3DE access
→12.7.112.7.1 Pre-hire screening of personnel with CDE access
pci-3ds-core-security-standard::P1-1.4.2P1-1.4.2 Screening criteria and decision process defined
→12.7.112.7.1 Pre-hire screening of personnel with CDE access

Part 1 Requirement P1-2: Secure network connectivity – PCI 3DS Core Security Standard(9 mappings)

pci-3ds-core-security-standard::P1-2.1.1P1-2.1.1 Boundary-protection policy and procedures for the 3DE
→1.1.11.1.1 Requirement 1 policies and procedures governed
pci-3ds-core-security-standard::P1-2.1.2P1-2.1.2 Current network and data-flow records for every 3DS path2 targets
→1.2.31.2.3 Accurate network diagram of CDE connections
→1.2.41.2.4 Accurate data-flow diagram for account data
pci-3ds-core-security-standard::P1-2.1.3P1-2.1.3 Physical or logical limits between trusted and untrusted zones
→1.4.11.4.1 NSCs between trusted and untrusted networks
pci-3ds-core-security-standard::P1-2.1.4P1-2.1.4 Only necessary 3DS traffic permitted, rest denied2 targets
→1.3.11.3.1 Inbound CDE traffic restricted
→1.3.21.3.2 Outbound CDE traffic restricted
pci-3ds-core-security-standard::P1-2.1.5P1-2.1.5 Network controls monitored or reviewed for effectiveness
→1.2.71.2.7 Six-monthly review of NSC configurations
pci-3ds-core-security-standard::P1-2.2.1P1-2.2.1 Detection or blocking of known and unknown network attacks
→11.5.111.5.1 IDS/IPS monitoring of CDE traffic
pci-3ds-core-security-standard::P1-2.2.2P1-2.2.2 Suspicious traffic blocked or alerted and acted upon
→11.5.111.5.1 IDS/IPS monitoring of CDE traffic

Part 1 Requirement P1-3: Develop and maintain secure systems – PCI 3DS Core Security Standard(1 mappings)

pci-3ds-core-security-standard::P1-3.1.1P1-3.1.1 Secure development lifecycle policy and procedures
→6.2.16.2.1 Secure development of bespoke and custom software

+118 more mappings

Plus AI-powered gap analysis, compliance advisory, PDF exports, and cross-mapping for all 908 frameworks.

Create Free Account →

Free forever, no credit card required

Coverage crosswalk

A PCI 3DS Core Security Standard to PCI DSS 4.0 crosswalk, built to order

The table above lists candidate mappings. A crosswalk answers the narrower question you are probably here for: which PCI DSS 4.0 controls your existing PCI 3DS Core Security Standard work already satisfies, which are real gaps, and the reasoning behind every claim so you can check it. One pair, $299, one time.

PCI 3DS Core Security Standard into PCI DSS 4.0
Not published yet

This direction has not been through crosswalk review and sign off, so no coverage figure is published for it. Reporting an unreviewed number would be worse than reporting none. It can be built to order at the same price as a pair that is already on the shelf.

If the two frameworks turn out to have too little in common for a crosswalk to help you, we say so and refund it rather than send a number worth nothing.

PCI DSS 4.0 into PCI 3DS Core Security Standard
Not published yet

This direction has not been through crosswalk review and sign off, so no coverage figure is published for it. Reporting an unreviewed number would be worse than reporting none. It can be built to order at the same price as a pair that is already on the shelf.

If the two frameworks turn out to have too little in common for a crosswalk to help you, we say so and refund it rather than send a number worth nothing.

PCI 3DS Core Security Standard to PCI DSS 4.0 (built to order)
$299
per framework pair, one time
  • 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 82% in the header counts how many PCI 3DS Core Security Standard controls carry at least one candidate mapping in the graph, before any review. The crosswalk percentage counts something stricter: how many PCI DSS 4.0 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.

Stop Paying Consultants to Read Spreadsheets

Cross-framework mappings across 908 frameworks, at a fraction of consulting costs.

$0/forever

Free

  • ✓ 908 framework browser
  • ✓ Cross-framework mappings (315K+)
  • ✓ 824 compliance assessments
  • ✓ 3 AI queries & searches per day
Get Started Free
Recommended
$149/month

Professional

  • ✓ Unlimited AI Compliance Advisory
  • ✓ Unlimited full-text search
  • ✓ Framework self-assessment
  • ✓ PDF, Excel & CSV exports
Start 7-Day Free Trial →

What are the key differences between PCI 3DS Core Security Standard and PCI DSS 4.0?

PCI 3DS Core Security Standard has 143 controls across its framework, while PCI DSS 4.0 covers 280 controls. Direct mapping analysis identifies 117 overlapping controls (82% coverage). The frameworks diverge most significantly in Part 2 Requirement P2-6: Cryptography and key management – PCI 3DS Core Security Standard, where 14 PCI 3DS Core Security Standard controls have no direct PCI DSS 4.0 equivalent.

How many controls map between PCI 3DS Core Security Standard and PCI DSS 4.0?

Of 143 total PCI 3DS Core Security Standard controls, 117 map directly to PCI DSS 4.0 controls, representing 82% coverage. The remaining 76 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping PCI 3DS Core Security Standard to PCI DSS 4.0?

76 PCI 3DS Core Security Standard controls have no direct equivalent in PCI DSS 4.0. The highest concentration of gaps is in Part 2 Requirement P2-6: Cryptography and key management – PCI 3DS Core Security Standard with 14 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 3DS Core Security Standard and PCI DSS 4.0?

The domain with the highest gap count is Part 2 Requirement P2-6: Cryptography and key management – PCI 3DS Core Security Standard (14 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

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.