ISO 27001:2022 covers 53.8% of DORA
14 of the 26 controls in DORA are already satisfied by evidence you collected for ISO 27001:2022. 12 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
DORA has 26 controls. Holding ISO 27001:2022 already evidences 14 of them, so the work in front of you is 12 controls, not 26, which is 46% 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 DORA your ISO 27001:2022 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.
65 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.
Monitoring networks, systems and applications for anomalies and acting on them is the detection duty.
Producing, protecting and analysing logs of activities, exceptions and faults supplies the detection layers.
Plan, implement, maintain and test ICT readiness against continuity objectives is the response and recovery duty.
Requires planning to hold security at the right level throughout disruption and recovery.
Backups maintained and regularly tested under a backup policy is the article's core duty.
Current role appropriate security training is the awareness and training programme duty.
Collecting and analysing threat information into decisions is the cyber threat gathering duty.
Feeding incident lessons back into stronger controls is the post incident review and evolve 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