C5 (Germany) covers 61.9% of NIST SP 800-218
26 of the 42 controls in NIST SP 800-218 are already satisfied by evidence you collected for C5 (Germany). 16 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.
This number is directional. It says how much of NIST SP 800-218 your C5 (Germany) 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.
73 candidate mappings were examined and 0 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.
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.
Issued secure development policies grounded in standards, covering requirements, design, implementation and verification.
Source code management and deployment tooling placed under the role and rights concept with enforced authorisation.
Outsourced development contractually bound to recognised secure engineering practice and acceptance testing.
Duties separated across change development, testing, release and system operation on documented risk assessment.
Recurring audience specific training on secure software development and delivery, refreshed as tooling changes.
Top management adopts the security policy and issues it to internal and external personnel.
Tooling configured so every production change is logged and traceable to the executing person or component.
Release into production requires defined criteria such as test results and prior sign-offs.
Claims that did not hold
Nothing proposed for this pair was rejected in review. That is unusual and worth knowing rather than hiding: it means the candidate set was small and every candidate held.
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