Cross-Framework Mapping

SOC 2vsPCI DSS 4.0

See exactly how SOC 2 controls map to PCI DSS 4.0. Pre-computed mappings, identified gaps, and coverage analysis.

778
Controls Mapped
0
Gaps Found
79%
Coverage

A reviewed coverage crosswalk for this pair is available. See which PCI DSS 4.0 controls you already evidence.

According to the TheArtOfService Compliance Knowledge Graph:

SOC 2 maps to PCI DSS 4.0 with 79% coverage across 48 directly mapped controls. Analysis of 61 SOC 2 controls identifies 13 compliance gaps, primarily concentrated in P - Privacy.

Source: TheArtOfService Knowledge Graph | 61 controls analysed | 686 frameworks | 309K+ cross-framework mappings

Control Mappings

Showing 20 of 778 mapped controls across 5 domains. Sign up to explore all 309K+ mappings across 686 frameworks.

A - Availability(8 mappings)

SOC2-A1.1Maintains capacity to meet availability commitments
12.1.3Information security roles and responsibilities defined and acknowledged
SOC2-A1.2Environmental protections, data backups, and recovery infrastructure support availability4 targets
10.3.3Logs backed up to central server
12.3.1Targeted risk analysis documented for requirements that specify one
9.4.1.1Offline media backup security
9.4.1.2Offsite backup location reviewed
SOC2-A1.3Recovery plan procedures support system recovery from failures3 targets
10.7.3Failure response timeline
12.10.2IRP reviewed and tested annually
12.3.1Targeted risk analysis documented for requirements that specify one

C - Confidentiality(12 mappings)

SOC2-C1.1Confidential information is identified and protected during receipt, processing, storage12 targets
1.2.4Data flow diagram of account data
1.4.5Internal IP and routing information protected
10.1.1Requirement 10 policies and operational procedures documented and maintained
10.1.2Requirement 10 roles and responsibilities documented and assigned
12.5.1Inventory of system components in scope
3.3.1.1Full track data not stored after authorization
3.3.2SAD stored prior to authorization is encrypted
3.3.3SAD storage by issuers limited
3.5.1PAN rendered unreadable wherever stored
3.5.1.1Hashes of PAN use keyed cryptographic functions
3.5.1.2Disk-level encryption with logical access controls
3.5.1.3Disk-level encryption key management

+758 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

Coverage crosswalk

The SOC 2 to PCI DSS 4.0 crosswalk

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 SOC 2 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. SOC 2 into PCI DSS 4.0 lands at 16.1%, while PCI DSS 4.0 into SOC 2 lands at 37.7%, 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 SOC 2 evidence buys you for PCI DSS 4.0, the other asks the reverse.

SOC 2 into PCI DSS 4.0
16.1%

40 of 249 PCI DSS 4.0 controls are evidenced by work you have already done for SOC 2. 209 are genuine gaps.

21.6%Req 12: Information Security Policies
26.9%Req 9: Restrict Physical Access
41.7%Req 7: Restrict Access by Need to Know
21.1%Req 1: Network Security Controls
Machine verified. Claude Code on the Max plan, judged in context, signed off 2026-08-19. 753 candidate mappings were examined and 620 were removed by a pass whose job was to argue against them.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.

A sample of what the report says

Evidenced: 1.2.2 Changes to NSC reviewed and approved

Changes are authorized, documented, tested and approved before implementation, including network controls.

Grounded in SOC2-CC8.1 Change management processes are in place. Confidence high, survived the refutation pass.

Gap: 1.1.1 NSC policies and procedures documented

All security policies and operational procedures for Requirement 1 are documented, kept current, in use, and known to affected parties.

Every one of the 40 evidenced controls and 209 gaps in the report carries this much reasoning, so you can check the claim rather than take it on trust.

PCI DSS 4.0 into SOC 2
37.7%

23 of 61 SOC 2 controls are evidenced by work you have already done for PCI DSS 4.0. 38 are genuine gaps.

63.6%CC - Common Criteria (Security)
100%C - Confidentiality
0%A - Availability
0%P - Privacy
Machine verified. Claude Code on the Max plan, judged in context, signed off 2026-08-19. 121 candidate mappings were examined and 56 were removed by a pass whose job was to argue against them.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.

A sample of what the report says

Evidenced: SOC2-C1.1 Confidential information is identified and protected during receipt, processing, storage

PCI classifies media according to the sensitivity of the data it holds

Grounded in 9.4.2 Media classified by sensitivity. Confidence high, survived the refutation pass.

Gap: SOC2-A1.1 Maintains capacity to meet availability commitments

Maintains, monitors, and evaluates current processing capacity and use of system components (infrastructure, data, and software) to manage capacity demand and to enable the implementation of additional capacity to help meet its objectives

Every one of the 23 evidenced controls and 38 gaps in the report carries this much reasoning, so you can check the claim rather than take it on trust.

SOC 2 to PCI DSS 4.0
$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 79% in the header counts how many SOC 2 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

AI-powered compliance intelligence across 686 frameworks, at a fraction of consulting costs.

$0/forever

Free

  • 686 framework browser
  • Cross-framework mappings (309K+)
  • 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 SOC 2 and PCI DSS 4.0?

SOC 2 has 61 controls across its framework, while PCI DSS 4.0 covers 249 controls. Direct mapping analysis identifies 48 overlapping controls (79% coverage). The frameworks diverge most significantly in P - Privacy, where 8 SOC 2 controls have no direct PCI DSS 4.0 equivalent.

How many controls map between SOC 2 and PCI DSS 4.0?

Of 61 total SOC 2 controls, 48 map directly to PCI DSS 4.0 controls, representing 79% coverage. The remaining 13 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping SOC 2 to PCI DSS 4.0?

13 SOC 2 controls have no direct equivalent in PCI DSS 4.0. The highest concentration of gaps is in P - Privacy with 8 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 SOC 2 and PCI DSS 4.0?

The domain with the highest gap count is P - Privacy (8 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.