Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 covers 78.6% of ANSSI Guide d'hygiene informatique (42 mesures, v2.0)
33 of the 42 controls in ANSSI Guide d'hygiene informatique (42 mesures, v2.0) are already satisfied by evidence you collected for Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1. 9 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.
What this leaves you to do
ANSSI Guide d'hygiene informatique (42 mesures, v2.0) has 42 controls. Holding Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 already evidences 33 of them, so the work in front of you is 9 controls, not 42, which is 21% of the standard rather than all of it.
That is the whole claim. We do not know your hourly rate, how long a control takes you, or how many people you have, so there is no figure here in dollars or weeks. Every number in that sentence comes from the two counts above it and can be re-derived from the free tools without taking our word for any of it.
This number is directional. It says how much of ANSSI Guide d'hygiene informatique (42 mesures, v2.0) your Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 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.
94 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.
Function tuned training for staff handling sensitive data covers role specific security training.
An awareness programme for all employees refreshed on a cycle trains the operational teams.
An approved password policy setting strength requirements and implemented in systems is this measure.
Secure password management across the lifecycle through technical measures covers stored secrets.
Multifactor authentication at minimum for privileged users and sensitive data is this measure.
Hardening hosts, guests and control plane to a technically enforced baseline is the minimum level.
Technically enforcing the organisation's policies on every endpoint is centralised standardisation.
A correctly configured software firewall on managed endpoints is this measure.
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