Cross-Framework Mapping

C5 (Germany)vsSOC 2

See exactly how C5 (Germany) controls map to SOC 2. Pre-computed mappings, identified gaps, and coverage analysis.

173
Controls Mapped
0
Gaps Found
98%
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:

C5 (Germany) maps to SOC 2 with 98% coverage across 119 directly mapped controls. Analysis of 121 C5 (Germany) controls identifies 2 compliance gaps, primarily concentrated in C5: Product Safety and Security.

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

Control Mappings

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

C5: Asset Management(8 mappings)

C5-AM-01Asset Inventory
SOC2-CC6.1Implements logical access security software, infrastructure and architectures over protected information assets
C5-AM-02Acceptable Use and Safe Handling of Assets Policy2 targets
SOC2-CC5.3COSO principle 12: Deploys control activities through policies and procedures
SOC2-CC6.7Transmission of data is restricted to authorized users
C5-AM-03Commissioning of Hardware
SOC2-CC8.1Change management processes are in place
C5-AM-04Decommissioning of Hardware2 targets
SOC2-C1.2Confidential information is disposed of securely
SOC2-CC6.5Discontinues logical and physical protections over physical assets only after the ability to read or recover data and software from those assets has been diminished and is no longer required to meet the entity's
C5-AM-05Commitment to Permissible Use, Safe Handling and Return of Assets
SOC2-CC1.1COSO principle 1: Demonstrates commitment to integrity and ethical values
C5-AM-06Asset Classification and Labelling
SOC2-C1.1Confidential information is identified and protected during receipt, processing, storage

C5: Business Continuity Management(4 mappings)

C5-BCM-01Top management responsibility
SOC2-A1.2Environmental protections, data backups, and recovery infrastructure support availability
C5-BCM-02Business impact analysis policies and instructions
SOC2-CC9.1Identifies, selects and develops risk mitigation activities
C5-BCM-03Planning business continuity
SOC2-CC9.1Identifies, selects and develops risk mitigation activities
C5-BCM-04Verification, updating and testing of the business continuity
SOC2-A1.3Recovery plan procedures support system recovery from failures

C5: Compliance(7 mappings)

C5-COM-01Identification of applicable legal, regulatory, self-imposed or contractual requirements
SOC2-CC3.1COSO principle 6: Specifies objectives to identify and assess risks
C5-COM-02Policy for planning and conducting audits
SOC2-CC4.1COSO principle 16: Selects and develops ongoing and separate evaluations
C5-COM-03Internal audits of the information security management system2 targets
SOC2-CC4.1COSO principle 16: Selects and develops ongoing and separate evaluations
SOC2-CC4.2COSO principle 17: Evaluates and communicates deficiencies in a timely manner
C5-COM-04Information on information security performance and management assessment of the ISMS3 targets
SOC2-CC1.2COSO principle 2: Board exercises oversight responsibility
SOC2-CC2.1COSO principle 13: Obtains and generates relevant, quality information
SOC2-CC4.2COSO principle 17: Evaluates and communicates deficiencies in a timely manner

C5: Communication Security(1 mappings)

C5-COS-01Technical safeguards
SOC2-CC6.1Implements logical access security software, infrastructure and architectures over protected information assets

+153 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 C5 (Germany) 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 C5 (Germany) 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. C5 (Germany) into SOC 2 lands at 54.1%, while SOC 2 into C5 (Germany) lands at 29.8%, 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 C5 (Germany) evidence buys you for SOC 2, the other asks the reverse.

C5 (Germany) into SOC 2
54.1%

33 of 61 SOC 2 controls are evidenced by work you have already done for C5 (Germany). 28 are genuine gaps.

81.8%CC - Common Criteria (Security)
100%A - Availability
100%C - Confidentiality
5.6%P - Privacy
Machine verified. Claude Code on the Max plan, judged in context, signed off 2026-08-19. 110 candidate mappings were examined and 3 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

C5 gives the customer the means to monitor and steer the system resources allocated to it.

Grounded in C5-OPS-03 Capacity Management - Controlling of Resources. Confidence high, survived the refutation pass.

Gap: SOC2-CC1.1 COSO principle 1: Demonstrates commitment to integrity and ethical values

Demonstrates a commitment to integrity and ethical values

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

SOC 2 into C5 (Germany)
29.8%

36 of 121 C5 (Germany) controls are evidenced by work you have already done for SOC 2. 85 are genuine gaps.

37.5%C5: Operations
44.4%C5: Identity and Access Management
50%C5: Human Resources
60%C5: Security Incident Management
Machine verified. Claude Code on the Max plan, judged in context, signed off 2026-08-19. 124 candidate mappings were examined and 9 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: C5-AM-04 Decommissioning of Hardware

Protections are removed only once the ability to read or recover the data has been diminished, which is the erasure limb of decommissioning

Grounded in SOC2-CC6.5 Discontinues logical and physical protections over physical assets only after the ability to read or recover data and software from those assets has been diminished and is no longer required to meet the entity's. Confidence high, survived the refutation pass.

Gap: C5-AM-01 Asset Inventory

Maintain inventory procedures that keep asset records complete, accurate, valid and consistent throughout the asset lifecycle, whether populated automatically or by the responsible owners, hold the attributes the risk procedure needs...

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

C5 (Germany) 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 98% in the header counts how many C5 (Germany) 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 (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 C5 (Germany) and SOC 2?

C5 (Germany) has 121 controls across its framework, while SOC 2 covers 61 controls. Direct mapping analysis identifies 119 overlapping controls (98% coverage). The frameworks diverge most significantly in C5: Product Safety and Security, where 2 C5 (Germany) controls have no direct SOC 2 equivalent.

How many controls map between C5 (Germany) and SOC 2?

Of 121 total C5 (Germany) controls, 119 map directly to SOC 2 controls, representing 98% 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 C5 (Germany) to SOC 2?

2 C5 (Germany) controls have no direct equivalent in SOC 2. The highest concentration of gaps is in C5: Product Safety and Security with 2 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 C5 (Germany) and SOC 2?

The domain with the highest gap count is C5: Product Safety and Security (2 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.