C5 (Germany) covers 69% of ANSSI Guide d'hygiene informatique (42 mesures, v2.0)
29 of the 42 controls in ANSSI Guide d'hygiene informatique (42 mesures, v2.0) are already satisfied by evidence you collected for C5 (Germany). 13 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 ANSSI Guide d'hygiene informatique (42 mesures, v2.0) 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.
77 candidate mappings were examined and 2 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.
C5 runs a target group differentiated security awareness programme completed regularly and refreshed as threats change.
C5 authenticates every user and system component and requires multi-factor authentication to reach the production environment.
C5 enforces password length and complexity technically, expires initial passwords within fourteen days and stores salted hashes.
C5 hands out authentication secrets confidentially, forces initial replacement within fourteen days and stores passwords as strong hashes.
C5 authenticates every user and system component and requires multi-factor authentication to reach the production environment.
C5 hardens production components to industry standards, documents the requirements per component and retains configuration evidence.
C5 applies strong encryption and authentication to customer data transmitted over public networks.
C5 segregates the traffic of different customers at network level under a documented segregation concept.
Claims that did not hold
2 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.
judged against C5 criterion titles before the framework carried requirement text; does not hold against the real criterion; C5-OPS-16 restricts access to the logging and monitoring components and controls their configuration changes; enabling logging on the components being monitored is OPS-10
Claimed at high confidence before it was rejected.
judged against C5 criterion titles before the framework carried requirement text; does not hold against the real criterion; C5-OPS-13 requires automated analysis and correlation of log data; enabling and configuring logging on components is OPS-10
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