Cross-Framework Mapping

PCI DSS 4.0vsSOC 2

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

778
Controls Mapped
0
Gaps Found
99%
Coverage

A reviewed coverage crosswalk for this pair is available. See which SOC 2 controls you already evidence.

According to the TheArtOfService Compliance Knowledge Graph:

PCI DSS 4.0 maps to SOC 2 with 99% coverage across 247 directly mapped controls. Analysis of 249 PCI DSS 4.0 controls identifies 2 compliance gaps, primarily concentrated in Req 11: Test Security Regularly.

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

Control Mappings

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

Req 1: Network Security Controls(20 mappings)

1.1.1NSC policies and procedures documented
SOC2-CC5.3COSO principle 12: Deploys control activities through policies and procedures
1.1.2Roles and responsibilities for Requirement 14 targets
SOC2-CC1.3COSO principle 3: Management establishes structures, reporting lines, and authorities
SOC2-CC1.5COSO principle 5: Holds individuals accountable for internal control responsibilities
SOC2-CC2.2COSO principle 14: Internally communicates information including objectives and responsibilities
SOC2-CC5.3COSO principle 12: Deploys control activities through policies and procedures
1.2.1NSC configuration standards defined4 targets
SOC2-CC5.3COSO principle 12: Deploys control activities through policies and procedures
SOC2-CC6.1Implements logical access security software, infrastructure and architectures over protected information assets
SOC2-CC6.6Measures against threats outside system boundaries are implemented
SOC2-CC8.1Change management processes are in place
1.2.2Changes to NSC reviewed and approved
SOC2-CC8.1Change management processes are in place
1.2.3Network diagrams maintained2 targets
SOC2-CC2.1COSO principle 13: Obtains and generates relevant, quality information
SOC2-CC6.6Measures against threats outside system boundaries are implemented
1.2.4Data flow diagram of account data5 targets
SOC2-C1.1Confidential information is identified and protected during receipt, processing, storage
SOC2-CC2.1COSO principle 13: Obtains and generates relevant, quality information
SOC2-CC3.2COSO principle 7: Identifies risks and analyzes to determine how managed
SOC2-CC6.1Implements logical access security software, infrastructure and architectures over protected information assets
SOC2-CC7.1Detection and monitoring procedures for security events are in place
1.2.5Services, protocols, ports inventoried and justified3 targets
SOC2-CC5.2COSO principle 11: Selects and develops general controls over technology
SOC2-CC6.1Implements logical access security software, infrastructure and architectures over protected information assets
SOC2-CC6.6Measures against threats outside system boundaries are implemented

+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 PCI DSS 4.0 to SOC 2 crosswalk

The table above lists candidate mappings. A crosswalk answers the narrower question you are probably here for: which SOC 2 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 SOC 2 lands at 37.7%, while SOC 2 into PCI DSS 4.0 lands at 16.1%, 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 SOC 2, the other asks the reverse.

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 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 to SOC 2
$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 99% 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 SOC 2 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 PCI DSS 4.0 and SOC 2?

PCI DSS 4.0 has 249 controls across its framework, while SOC 2 covers 61 controls. Direct mapping analysis identifies 247 overlapping controls (99% coverage). The frameworks diverge most significantly in Req 11: Test Security Regularly, where 1 PCI DSS 4.0 controls have no direct SOC 2 equivalent.

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

Of 249 total PCI DSS 4.0 controls, 247 map directly to SOC 2 controls, representing 99% coverage. The remaining 2 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 SOC 2?

2 PCI DSS 4.0 controls have no direct equivalent in SOC 2. The highest concentration of gaps is in Req 11: Test Security Regularly with 1 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 SOC 2?

The domain with the highest gap count is Req 11: Test Security Regularly (1 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.