Cross-Framework Mapping

SOC 2vsDORA

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

81
Controls Mapped
0
Gaps Found
75%
Coverage

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

According to the TheArtOfService Compliance Knowledge Graph:

SOC 2 maps to DORA with 75% coverage across 46 directly mapped controls. Analysis of 61 SOC 2 controls identifies 15 compliance gaps, primarily concentrated in P - Privacy.

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

Control Mappings

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

A - Availability(6 mappings)

SOC2-A1.1Maintains capacity to meet availability commitments
DORA-Art.7ICT systems, protocols and tools
SOC2-A1.2Environmental protections, data backups, and recovery infrastructure support availability2 targets
DORA-Art.12Backup policies and procedures, restoration and recovery
DORA-Art.7ICT systems, protocols and tools
SOC2-A1.3Recovery plan procedures support system recovery from failures3 targets
DORA-Art.11Response and recovery
DORA-Art.12Backup policies and procedures, restoration and recovery
DORA-Art.24General requirements for the performance of digital operational resilience testing

C - Confidentiality(2 mappings)

SOC2-C1.1Confidential information is identified and protected during receipt, processing, storage
DORA-Art.8Identification
SOC2-C1.2Confidential information is disposed of securely
DORA-Art.8Identification

CC - Common Criteria (Security)(12 mappings)

SOC2-CC1.1COSO principle 1: Demonstrates commitment to integrity and ethical values
DORA-Art.5Governance and organisation
SOC2-CC1.2COSO principle 2: Board exercises oversight responsibility
DORA-Art.5Governance and organisation
SOC2-CC1.3COSO principle 3: Management establishes structures, reporting lines, and authorities2 targets
DORA-Art.5Governance and organisation
DORA-Art.8Identification
SOC2-CC1.4COSO principle 4: Demonstrates commitment to attract and retain competent individuals
DORA-Art.13Learning and evolving
SOC2-CC1.5COSO principle 5: Holds individuals accountable for internal control responsibilities
DORA-Art.5Governance and organisation
SOC2-CC2.1COSO principle 13: Obtains and generates relevant, quality information2 targets
DORA-Art.13Learning and evolving
DORA-Art.45Information-sharing arrangements on cyber threat information and intelligence
SOC2-CC2.2COSO principle 14: Internally communicates information including objectives and responsibilities
DORA-Art.14Communication
SOC2-CC2.3COSO principle 15: Communicates with external parties regarding matters affecting controls2 targets
DORA-Art.14Communication
DORA-Art.19Reporting of major ICT-related incidents
SOC2-CC3.1COSO principle 6: Specifies objectives to identify and assess risks
DORA-Art.6ICT risk management framework

+61 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 DORA crosswalk

The table above lists candidate mappings. A crosswalk answers the narrower question you are probably here for: which DORA 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 DORA lands at 46.2%, while DORA 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 DORA, the other asks the reverse.

SOC 2 into DORA
46.2%

12 of 26 DORA controls are evidenced by work you have already done for SOC 2. 14 are genuine gaps.

81.8%DORA Chapter II: ICT Risk Management
25%DORA Chapter III: ICT-Related Incident Management
25%DORA Chapter V: ICT Third-Party Risk Management
33.3%DORA Chapters VI-VII: Information Sharing, Penalties and Data Protection
Machine verified. Claude Code on the Max plan, judged in context, signed off 2026-08-20. 67 candidate mappings were examined and 0 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: DORA-Art.10 Detection

Monitors components for anomalies indicating malicious acts, disasters and errors, then analyses them.

Grounded in SOC2-CC7.2 Monitors system components for anomalies indicating malicious acts. Confidence high, survived the refutation pass.

Gap: DORA-Art.16 Simplified ICT risk management framework

Specified smaller and non-interconnected financial entities are subject to a simplified ICT risk management framework with proportionate requirements (sound systems, monitoring, business continuity, incident handling and testing).

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

DORA into SOC 2
37.7%

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

57.6%CC - Common Criteria (Security)
100%A - Availability
50%C - Confidentiality
0%P - Privacy
Machine verified. Claude Code on the Max plan, judged in context, signed off 2026-08-20. 43 candidate mappings were examined and 0 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-A1.1 Maintains capacity to meet availability commitments

Systems must carry sufficient capacity for additional processing needs under stressed conditions.

Grounded in DORA-Art.7 ICT systems, protocols and tools. Confidence high, survived the refutation pass.

Gap: SOC2-C1.2 Confidential information is disposed of securely

Disposes of confidential information to meet the entity's objectives related to confidentiality

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 DORA
$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 75% 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 DORA 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 (310K+)
  • 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 DORA?

SOC 2 has 61 controls across its framework, while DORA covers 26 controls. Direct mapping analysis identifies 46 overlapping controls (75% coverage). The frameworks diverge most significantly in P - Privacy, where 11 SOC 2 controls have no direct DORA equivalent.

How many controls map between SOC 2 and DORA?

Of 61 total SOC 2 controls, 46 map directly to DORA controls, representing 75% coverage. The remaining 15 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 DORA?

15 SOC 2 controls have no direct equivalent in DORA. The highest concentration of gaps is in P - Privacy with 11 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 DORA?

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