CIS Controls v8C5 (Germany)

CIS Controls v8 covers 34.7% of C5 (Germany)

42 of the 121 controls in C5 (Germany) are already satisfied by evidence you collected for CIS Controls v8. 79 are genuine gaps. Every claim below was judged against both control sets and then argued against; the ones that did not survive are published further down with the reason each failed.

34.7%
of the target already covered
42
controls evidenced
79
genuine gaps
1
claims rejected in review

This number is directional. It says how much of C5 (Germany) your CIS Controls v8 evidence satisfies. The reverse pair is a different number, often very different, because a security standard has enormous depth for access control and almost none for lawful basis or data subject rights.

120 candidate mappings were examined and 1 were removed. Signed off 2026-08-19, review level machine verified. 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.

Where the gaps are

Coverage is never evenly spread. A source standard usually satisfies one part of a target almost completely and barely touches another, and which part is which is the thing worth knowing before you plan the work.

C5: Control and Monitoring of Service Providers and Suppliers4 of 5 evidenced, 1 to do
C5: Identity and Access Management7 of 9 evidenced, 2 to do
C5: Communication Security5 of 8 evidenced, 3 to do
C5: Security Incident Management3 of 5 evidenced, 2 to do
C5: Operations11 of 24 evidenced, 13 to do
C5: Product Safety and Security4 of 12 evidenced, 8 to do
C5: Asset Management2 of 6 evidenced, 4 to do
C5: Portability and Interoperability1 of 3 evidenced, 2 to do
C5: Procurement, Development and Modification of Information Systems3 of 10 evidenced, 7 to do
C5: Cryptography and Key Management1 of 4 evidenced, 3 to do
C5: Human Resources1 of 6 evidenced, 5 to do
C5: Business Continuity Management0 of 4 evidenced, 4 to do
C5: Compliance0 of 4 evidenced, 4 to do
C5: Dealing with Investigation Requests from Government Agencies0 of 4 evidenced, 4 to do
C5: Organisation of Information Security0 of 7 evidenced, 7 to do
C5: Physical Security0 of 7 evidenced, 7 to do
C5: Security Policies and Instructions0 of 3 evidenced, 3 to do

Theme level, not control level, deliberately. The per-control list of what is evidenced and what is a gap is the report itself, so publishing it here would be publishing the thing being sold.

Claims that held

A sample. Each one names the control whose evidence does the work, the control it satisfies, and why.

CIS-1.1C5-AM-01argued against and upheld
Asset Inventory

An accurate, detailed and current inventory of every asset that can store or process data is the asset record required

CIS-3.5C5-AM-04argued against and upheld
Decommissioning of Hardware

Secure disposal of data by a method commensurate with its sensitivity is the erasure limb of decommissioning

CIS-13.6C5-COS-01argued against and upheld
Technical safeguards

Collecting network traffic flow logs to review and alert upon is the detection of irregular traffic the criterion requires

CIS-13.4C5-COS-03argued against and upheld
Monitoring of connections in the Cloud Service Provider's network

Traffic filtering between network segments is the zoning and restriction of connections the criterion requires

CIS-13.4C5-COS-04argued against and upheld
Cross-network access

Filtering traffic between segments of differing trust is the perimeter control this criterion requires

CIS-12.8C5-COS-05argued against and upheld
Networks for administration

Dedicated computing resources, physically or logically separated and segmented from the primary network, are the administration network this criterion requires

CIS-12.4C5-COS-07argued against and upheld
Documentation of the network topology

Maintained architecture diagrams and network documentation, reviewed annually, are the topology documentation required

CIS-3.10C5-CRY-02argued against and upheld
Encryption of data for transmission (transport encryption)

Encrypting sensitive data in transit is the transport encryption required

Claims that did not hold

1 proposed mappings for this pair were rejected. They are kept in the graph rather than deleted, so what was thrown out is as inspectable as what survived. A crosswalk that never rejects anything is not being judged.

CIS-8.5C5-OPS-13
Logging and Monitoring - Identification of Events

judged against C5 criterion titles before the framework carried requirement text; does not hold against the real criterion. the title says identification of events but the criterion requires automated analysis of logging data, correlation between events and automatic reporting to the responsible departments; configuring detailed log content is log collection, which belongs to accountability and is now mapped to C5-OPS-15

Claimed at high confidence before it was rejected.

The full report

Everything above is a sample. The report is every evidenced control and every gap, with the reasoning and the source document behind each one, in a form you can hand to an assessor. $299, emailed immediately.

Buy this crosswalk