Cross-Framework Mapping

PCI DSS 4.0vsPCI 3DS Core Security Standard

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

138
Controls Mapped
142
Gaps Found
37%
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 DSS 4.0 maps to PCI 3DS Core Security Standard with 37% coverage across 103 directly mapped controls. Analysis of 280 PCI DSS 4.0 controls identifies 257 compliance gaps, primarily concentrated in Req 12: Information Security Policies.

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

Control Mappings

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

Req 1: Network Security Controls(12 mappings)

1.1.11.1.1 Requirement 1 policies and procedures governed
→pci-3ds-core-security-standard::P1-2.1.1P1-2.1.1 Boundary-protection policy and procedures for the 3DE
1.2.31.2.3 Accurate network diagram of CDE connections
→pci-3ds-core-security-standard::P1-2.1.2P1-2.1.2 Current network and data-flow records for every 3DS path
1.2.41.2.4 Accurate data-flow diagram for account data
→pci-3ds-core-security-standard::P1-2.1.2P1-2.1.2 Current network and data-flow records for every 3DS path
1.2.51.2.5 Allowed services, protocols and ports justified
→pci-3ds-core-security-standard::P2-3.1.2P2-3.1.2 ACS and DS reachable only through approved interfaces
1.2.71.2.7 Six-monthly review of NSC configurations
→pci-3ds-core-security-standard::P1-2.1.5P1-2.1.5 Network controls monitored or reviewed for effectiveness
1.2.81.2.8 NSC configuration files secured and consistent
→pci-3ds-core-security-standard::P2-3.2.1P2-3.2.1 Configurations and security documentation protected
1.3.11.3.1 Inbound CDE traffic restricted2 targets
→pci-3ds-core-security-standard::P1-2.1.4P1-2.1.4 Only necessary 3DS traffic permitted, rest denied
→pci-3ds-core-security-standard::P2-3.1.1P2-3.1.1 ACS and DS traffic limited to 3DS functions
1.3.21.3.2 Outbound CDE traffic restricted2 targets
→pci-3ds-core-security-standard::P1-2.1.4P1-2.1.4 Only necessary 3DS traffic permitted, rest denied
→pci-3ds-core-security-standard::P2-3.1.1P2-3.1.1 ACS and DS traffic limited to 3DS functions
1.3.31.3.3 NSCs between wireless networks and the CDE
→pci-3ds-core-security-standard::P2-4.4.1P2-4.4.1 No wireless use by 3DS components
1.4.11.4.1 NSCs between trusted and untrusted networks
→pci-3ds-core-security-standard::P1-2.1.3P1-2.1.3 Physical or logical limits between trusted and untrusted zones

Req 10: Logging and Monitoring(8 mappings)

10.1.110.1.1 Requirement 10 policies and procedures maintained and in use
→pci-3ds-core-security-standard::P1-7.2.1P1-7.2.1 Audit-logging policy and procedures
10.2.110.2.1 Audit logging enabled on all system components
→pci-3ds-core-security-standard::P1-7.2.2P1-7.2.2 Logs tie access to individuals and record security events
10.2.210.2.2 Required details recorded for each auditable event
→pci-3ds-core-security-standard::P1-7.2.2P1-7.2.2 Logs tie access to individuals and record security events
10.3.210.3.2 Audit log files protected from modification
→pci-3ds-core-security-standard::P1-7.2.5P1-7.2.5 Audit logs protected from alteration
10.4.110.4.1 Daily review of security-relevant logs
→pci-3ds-core-security-standard::P1-7.2.4P1-7.2.4 Logs and security events monitored or reviewed
10.4.310.4.3 Exceptions and anomalies from log review addressed
→pci-3ds-core-security-standard::P2-5.5.2P2-5.5.2 Anomalous transaction activity investigated promptly
10.5.110.5.1 Keep logs 12 months, latest three months online
→pci-3ds-core-security-standard::P1-7.2.6P1-7.2.6 Log retention of one year, three months at hand
10.6.110.6.1 System clocks synchronized with time-sync technology
→pci-3ds-core-security-standard::P1-7.2.3P1-7.2.3 Clocks synchronised on 3DS systems

+118 more mappings

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

Create Free Account →

Free forever, no credit card required

Coverage crosswalk

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

The table above lists candidate mappings. A crosswalk answers the narrower question you are probably here for: which PCI 3DS Core Security Standard 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.

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 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 to PCI 3DS Core Security Standard (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 37% 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 PCI 3DS Core Security Standard 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 894 frameworks, at a fraction of consulting costs.

$0/forever

Free

  • ✓ 894 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 DSS 4.0 and PCI 3DS Core Security Standard?

PCI DSS 4.0 has 280 controls across its framework, while PCI 3DS Core Security Standard covers 143 controls. Direct mapping analysis identifies 103 overlapping controls (37% coverage). The frameworks diverge most significantly in Req 12: Information Security Policies, where 28 PCI DSS 4.0 controls have no direct PCI 3DS Core Security Standard equivalent.

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

Of 280 total PCI DSS 4.0 controls, 103 map directly to PCI 3DS Core Security Standard controls, representing 37% coverage. The remaining 257 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 PCI 3DS Core Security Standard?

257 PCI DSS 4.0 controls have no direct equivalent in PCI 3DS Core Security Standard. The highest concentration of gaps is in Req 12: Information Security Policies with 28 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 PCI 3DS Core Security Standard?

The domain with the highest gap count is Req 12: Information Security Policies (28 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.