Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 covers 57.7% of DORA
15 of the 26 controls in DORA are already satisfied by evidence you collected for Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1. 11 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 DORA 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.
79 candidate mappings were examined and 0 were removed. Signed off 2026-08-20, 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.
Immediate reporting of monitoring system failures and anomalies supplies a further layer of control.
Reviewing logs for activity outside expected patterns and acting within a set time is anomaly detection.
Alerting stakeholders when security events cross defined thresholds is the alert threshold and detection duty.
An approved disaster response plan updated annually is the response measures and procedures duty.
An annual live exercise repeated on significant change, fed back into the plans, is the regular testing duty.
An approved, communicated and maintained business continuity plan implementing the strategies is the recovery plan.
Approved business continuity and operational resilience policies reviewed annually is the ICT continuity policy.
Backups on a defined cycle, protected, with restore testing proving recovery, is the backup and restoration duty.
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