Financial entities with an ISO/IEC 27001 certificate often assume most of the Digital Operational Resilience Act (DORA) is already done, and then discover during supervision that the certificate answers a different question. ISO/IEC 27001:2022 certifies that an information security management system (ISMS) exists and works within a scope the organisation chose; DORA, Regulation (EU) 2022/2554, imposes legal obligations with fixed clocks, fixed frequencies and fixed formats on the whole financial entity. This guide compares the two as a decision tool: which ISMS records can be reused as DORA evidence, which DORA obligations have no ISO equivalent, and how a supervisory review differs from a certification audit. It is written for CISOs, compliance leads, ISMS managers and internal auditors in banks, insurers, investment firms, payment institutions and crypto-asset service providers. For the regulation itself see the DORA Guide, and for the standard see the ISO 27001 Certification Guide; this page does not repeat them.
Key takeaways
- The ISMS is a strong chassis, not a compliance answer. Clauses 4 to 10 of ISO/IEC 27001 give you governance, risk assessment, internal audit and corrective action processes that DORA Articles 5 and 6 can reuse almost directly.
- ISO lets you choose; DORA has already chosen. Delegated Regulation (EU) 2024/1774 fixes weekly vulnerability scanning and six-monthly firewall rule and access reviews for systems supporting critical or important functions, where ISO leaves frequency to your risk assessment.
- Four obligations have no ISO counterpart. Major incident reporting on a four hour and 24 hour clock, threat-led penetration testing (TLPT) at least every three years for designated entities, the register of information, and mandatory ICT contract clauses under Article 30 all need work beyond the ISMS.
- Scope is the first gap. A certificate covers the scope written on it; DORA covers every ICT system supporting a critical or important function, so a narrow ISMS scope leaves supervised systems with no evidence at all.
- The assessor is different. A certification body samples conformity against a standard for a certificate; a competent authority tests compliance with law, can request the register and reports at any time, and holds sanctioning powers.
Two different instruments: law versus certifiable standard
| Dimension | DORA, Regulation (EU) 2022/2554 | ISO/IEC 27001:2022 |
|---|---|---|
| Legal nature | EU regulation, directly applicable, applying from 17 January 2025, supplemented by delegated and implementing regulations (RTS and ITS) | Voluntary international standard; ISO states that certification is optional and that ISO itself does not certify |
| Who it applies to | Financial entities listed in Article 2, with proportionality and a simplified framework under Article 16 for some smaller entities | Any organisation that chooses to adopt it, for a scope it defines |
| Object | Digital operational resilience of the financial entity: ICT risk, incidents, testing, third parties, information sharing | Confidentiality, integrity and availability of information within the ISMS scope |
| Accountability | Management body "bears the ultimate responsibility" for ICT risk (Art. 5(2)) | Top management demonstrates leadership and commitment (clause 5.1) |
| Control selection | Prescribed requirements, many with fixed frequencies in RTS 2024/1774 | Risk-based; Annex A lists 93 reference controls and the Statement of Applicability (SoA) justifies inclusions and exclusions |
| Assessor | National competent authority (and Lead Overseers for critical ICT third-party providers) | Accredited certification body, on a three-year certificate cycle with surveillance audits |
| Consequence of failure | Supervisory measures and administrative penalties set by Member States under Article 50 | Nonconformity, corrective action, and in serious cases suspension or withdrawal of the certificate |
The practical consequence: ISO conformity can be evidence that a DORA requirement is met, but it is never the requirement. A supervisor will ask "show me how Article 28(8) exit plans are tested", not "are you certified".
Clause-to-article mapping: where evidence carries over
The table maps the ISO/IEC 27001 management system clauses and the closest Annex A controls to DORA articles, with a verdict on reuse. "Strong" means the ISMS artefact is usually acceptable with light adaptation; "Partial" means the process exists but the legal parameter or format must be added; "Weak" means the ISMS rarely produces what DORA needs. For control-level parameters in the RTS, see the ISO 27001 to NIS2 and DORA Mapping Guide.
| DORA obligation | ISO/IEC 27001:2022 source | Reuse | What to add |
|---|---|---|---|
| Management body defines, approves and oversees ICT risk arrangements (Art. 5(2)) | Clause 5.1 leadership, 5.2 policy, 9.3 management review | Partial | Board-level approval minutes, ICT risk tolerance, budget and training of members; ISO accepts "top management" below board level |
| ICT risk management framework documented and reviewed at least once a year and after major incidents (Art. 6(5)) | Clause 6.1.2 risk assessment, 6.1.3 treatment, 7.5 documented information | Strong | Explicit annual review trigger and post-incident review trigger |
| Framework subject to internal audit by auditors on a regular basis (Art. 6(6)) | Clause 9.2 internal audit, 10.2 corrective action | Strong | Auditor independence and ICT knowledge; follow-up tracked to closure for supervisory reporting |
| Digital operational resilience strategy (Art. 6(8)) | Clause 6.2 objectives | Weak | A separate strategy covering risk tolerance, business alignment and the testing programme |
| Report on the review of the framework in searchable electronic format (RTS 2024/1774 Art. 27) | Clause 9.3 management review outputs | Partial | Reformat outputs into the RTS content: approval date, review period, responsible function, findings and remediation |
| Asset identification and classification (Art. 8) | Annex A 5.9 inventory, 5.12 classification | Partial | Link assets to critical or important functions and to ICT third-party arrangements |
| Protection and prevention, including vulnerability management, network security and access control (Art. 9; RTS Arts. 10, 13, 21) | Annex A 8.8 technical vulnerabilities, 8.20 network security, 5.15 and 5.18 access | Partial | Weekly scans, six-monthly firewall and access reviews for critical or important function systems |
| Detection of anomalous activity (Art. 10) | Annex A 8.15 logging, 8.16 monitoring | Strong | Alert thresholds tied to incident classification criteria |
| Response, recovery, backup and restoration (Arts. 11 and 12) | Annex A 5.29, 5.30 ICT readiness for business continuity, 8.13 backup | Partial | Recovery time and point objectives per function, scenario testing and crisis communication plans |
| ICT incident management process (Art. 17) | Annex A 5.24 to 5.28 | Strong | Classification against Delegated Regulation (EU) 2024/1772 criteria |
| Major incident reporting (Art. 19; RTS 2025/301) | None (5.5 contact with authorities is generic) | Weak | Reporting clocks, templates and a named submitter |
| Testing programme, yearly tests for critical or important function systems (Arts. 24 and 25) | Annex A 8.29 security testing, 8.8 | Partial | A documented programme covering the Article 25 test types at the required frequency |
| TLPT at least every three years for identified entities (Art. 26) | None | Weak | A full TLPT programme under Delegated Regulation (EU) 2025/1190 |
| ICT third-party risk strategy, pre-contract assessment and exit strategies (Art. 28(2), (4), (8)) | Annex A 5.19 to 5.23 supplier and cloud controls | Partial | Concentration risk analysis, conflict of interest checks, tested exit plans |
| Register of information (Art. 28(3); ITS 2024/2956) | Annex A 5.19 and 5.20 supplier records | Weak | Structured register in the ITS templates with LEIs, function mapping and supply chain ranking |
| Contract clauses (Art. 30(2) and (3)) | Annex A 5.20 addressing security in supplier agreements | Partial | The full Article 30 clause list, including audit rights and TLPT participation for critical or important functions |
The gaps ISO leaves
Four areas account for most of the extra work in a DORA gap analysis of a certified ISMS. Each one is a legal obligation that the standard does not ask for.
Incident reporting timelines
ISO/IEC 27001 requires an incident management capability but sets no external reporting duty. DORA Article 19(1) requires financial entities to report major ICT-related incidents to their competent authority, and Delegated Regulation (EU) 2025/301 Article 5(1) sets the clocks:
- Initial notification: within four hours from classification as major, and no later than one day after the entity became aware of the incident.
- Intermediate report: at the latest within 72 hours of the initial notification, even if the status has not changed.
- Final report: no later than one month after the intermediate report, or after the last updated intermediate report.
- Weekends and bank holidays: Article 5(4) allows submission by noon of the next working day, but Article 5(5) withholds that relief from banks, central counterparties, trading venue operators and entities that are essential or important under NIS2 for initial and intermediate reports.
An ISO incident process built around internal escalation will not meet these clocks unless classification against the RTS 2024/1772 thresholds is part of triage. Detail is in the DORA Major ICT Incident Reporting Guide.
Threat-led penetration testing
Annex A 8.29 expects security testing in development and acceptance, and 8.8 expects vulnerability management. Neither resembles TLPT. DORA Article 26(1) requires entities identified by their competent authority to carry out TLPT at least every three years, covering critical or important functions on live production systems, and Article 26(8) requires external testers every third test where internal testers are used. Article 27 sets tester requirements, including professional indemnity insurance. Pen test reports produced for ISO evidence count towards the Article 25 testing programme, not towards TLPT. See the Threat-Led Penetration Testing Guide.
Register of information
Supplier lists kept for Annex A 5.19 are rarely structured enough. Article 28(3) requires a register of information on all ICT contractual arrangements, and Implementing Regulation (EU) 2024/2956 fixes the templates (B_01 to B_07 plus B_99), linked by four keys: contract reference, provider or entity identifier, function identifier and ICT service type. Article 3(5) requires a valid and active Legal Entity Identifier (LEI) or European Unique Identifier for legal-person providers, and Article 3(6) extends that to subcontractors underpinning critical or important functions. A procurement spreadsheet fails these validations. See the DORA ICT Third-Party Risk and Register of Information Guide.
Third-party contract terms
Annex A 5.20 asks that relevant security requirements are agreed with each supplier, with the content left to the organisation. Article 30(2) lists clauses every ICT contract must contain, including service descriptions, data locations, data access and return on termination or insolvency, service levels, incident assistance, cooperation with authorities and termination rights. Article 30(3) adds, for critical or important functions, quantitative service targets, business continuity testing, participation in TLPT, audit and access rights, and exit transition periods. These are contractual facts that an ISO auditor does not check line by line. See the DORA Article 30 Contract Provisions Guide.
Parameters: where ISO's flexibility meets DORA's numbers
DORA's RTS removes that choice for systems supporting critical or important functions.
| Activity | ISO/IEC 27001 position | DORA position (RTS 2024/1774 unless stated) |
|---|---|---|
| Vulnerability scanning | Annex A 8.8: timely identification, frequency risk-based | At least weekly for ICT assets supporting critical or important functions (Art. 10) |
| Firewall and connection filter rules | Annex A 8.20: networks secured and managed | Adequacy verified at least every six months for critical or important function systems; network architecture review yearly (Art. 13) |
| Access rights review | Annex A 5.18: reviewed at planned intervals | At least yearly generally, at least every six months for critical or important function systems (Art. 21) |
| Framework review | Clause 9.3: at planned intervals | At least once a year and after major incidents (DORA Art. 6(5)) |
| Resilience testing | Clause 9.1 and Annex A 8.29, risk-based | All systems supporting critical or important functions tested at least yearly (DORA Art. 24(6)) |
| Advanced testing | No equivalent | TLPT at least every three years for identified entities (DORA Art. 26(1)) |
The fix is usually cheap: change the frequency in the ISMS procedure for the systems in DORA scope, record the reason in the SoA justification, and keep the evidence trail. Access reviews are the parameter most often missed, and they increasingly involve machine identities: service accounts, API keys and automation tokens behind critical functions need the same six-monthly review. See the DORA ICT Risk Management Framework Guide.
Supervisory review versus certification audit
- Scope: a certification body audits the scope on the certificate. A supervisor examines the legal entity, including systems and providers outside the ISMS scope.
- Standard of proof: a certification audit samples evidence for conformity and grades nonconformities as major or minor. A supervisor tests compliance with each obligation and can treat one missing clause in a critical contract as a breach.
- Timing: certification runs on a planned three-year cycle. Supervisors receive regular submissions (the register at least yearly, review reports, incident reports) and can request information at any time.
- Independence of the assessed entity's choices: ISO accepts a justified exclusion in the SoA. DORA allows proportionality, but an entity in full scope cannot exclude, for example, Article 30 clauses.
Use the certificate as a supporting exhibit in supervisory dialogue, never as the main answer. Map each certification finding that touches a DORA area into the DORA remediation log so the two trails stay consistent; see Internal Audit vs External Audit for how the assurance lines fit together.
Decision guidance: one system or two
Almost every certified financial entity should run DORA on top of the ISMS rather than beside it. The choice is about how far to extend the ISMS.
| Situation | Recommended approach | Trade-off |
|---|---|---|
| Certified ISMS, scope already covers all critical or important functions | Extend the ISMS: add DORA as a legal requirement under clause 4.2 and Annex A 5.31, add the four missing processes | Lowest cost; certificate scope and DORA scope must then stay aligned at every change |
| Certified ISMS with narrow scope (one product, one data centre) | Widen the ISMS scope to DORA scope, or run a DORA control layer over the wider estate reusing ISMS processes | Widening raises certification cost; a layer avoids it but creates two evidence trails |
| No ISMS, DORA in scope | Build to DORA first, structured on clauses 4 to 10 so certification is possible later | Certification is optional; a market need for it decides the timing |
| Simplified framework entity under Article 16 | Apply RTS 2024/1774 Title III; a lean ISMS may exceed requirements | Avoid gold-plating; document proportionality |
| Group with NIS2 and DORA entities | One control set mapped to ISO, DORA and NIS2 per legal entity | Mapping effort up front; see the DORA and NIS2 Overlap Mapping Guide |
Small versus large: a small payment institution can run DORA from its ISMS register, a GRC tool and a well-kept register of information. A banking group needs consolidated registers, a TLPT programme and board reporting that the ISMS management review was never designed to carry.
Worked scenario: a certified payment institution
A mid-sized payment institution holds an ISO/IEC 27001 certificate scoped to its card processing platform. Its gap analysis runs as follows.
- Scope check: critical or important functions include payment initiation, customer onboarding and fraud monitoring. Onboarding runs on a SaaS platform outside the ISMS scope, so it has no risk assessment, no access review and no contract review. Action: bring the SaaS arrangement into the register and the risk process.
- Evidence reuse: the risk methodology, internal audit programme, incident process and logging controls pass with minor changes. Management review minutes are reformatted into the Article 27 report.
- Parameters: vulnerability scans run monthly. Action: weekly for the three critical function stacks; access reviews move from yearly to six-monthly, including 140 service accounts and API keys.
- Missing processes: no reporting clocks, no register in ITS format, 31 ICT contracts without Article 30 clauses. Action: incident reporting runbook, register build with LEIs, contract repapering starting with critical functions at renewal.
- TLPT: the competent authority has not identified the entity for TLPT, so the yearly Article 24 testing programme applies; this is recorded and rechecked yearly.
Roughly two thirds of the evidence carried over. The remaining third was the work that supervisors look at first.
How to run the gap analysis
- Fix the perimeter (weeks 1 to 2): list critical or important functions and the ICT systems and providers behind each; compare against the certificate scope.
- Map evidence (weeks 2 to 6): use the clause-to-article table above; for each DORA obligation record the ISMS artefact, its owner and a reuse verdict.
- Adjust parameters (weeks 4 to 8): change procedure frequencies for in-scope systems; update the SoA justifications.
- Build the missing processes (months 2 to 6): reporting runbook and tabletop exercise against both clocks, register of information, contract remediation plan, resilience strategy, TLPT readiness if identified.
- Test before relying on it: run a dry-run incident report, validate the register against the ITS templates, and sample five contracts against Article 30.
- Integrate assurance: add DORA obligations to the clause 9.2 internal audit programme and the management review inputs, so one cycle produces both ISO and DORA evidence.
- Roll back safely: keep previous ISMS procedure versions under clause 7.5 control; if a DORA change breaks a certified process, revert and log the DORA gap rather than run an uncontrolled exception.
Detection and measurement
- Scope coverage: percentage of critical or important function systems inside both the ISMS risk process and the DORA evidence log (target 100 percent).
- Parameter compliance: percentage of weekly scans, six-monthly firewall reviews and six-monthly access reviews completed on time for in-scope systems.
- Reporting timeliness: share of initial, intermediate and final reports filed within RTS 2025/301 limits, including exercises.
- Register quality: validation errors per submission and percentage of arrangements with LEI and function mapping complete.
- Contract remediation: percentage of critical or important function contracts carrying the full Article 30(3) clause set.
- Finding convergence: number of open findings that appear in the ISO trail but not in the DORA remediation log, or the reverse (target zero).
Common failure patterns
- Presenting the certificate as compliance: the supervisor asks for article-level evidence, and the team has only an SoA.
- Leaving the scope narrow: critical functions on SaaS or outsourced platforms sit outside the ISMS and have no evidence trail.
- Keeping risk-based frequencies: monthly scanning and yearly access reviews survive in the ISMS procedures for systems where the RTS fixes weekly and six-monthly.
- Starting the reporting clock at classification only: teams plan for four hours and miss that the one-day limit runs from awareness, so slow classification is the real exposure.
- Treating the supplier list as the register: no LEIs, no function identifiers, no subcontractor ranking, and the submission fails validation.
- Ignoring machine identities in access reviews: human accounts are reviewed every six months while service accounts and API keys behind payment flows are never reviewed; see the DORA ICT Risk Management Framework Guide for the identity articles.
Practitioner checklist
- List critical or important functions and compare their ICT systems and providers against the ISMS certificate scope.
- Record DORA and its RTS and ITS as legal requirements under clause 4.2 and Annex A 5.31.
- Complete an article-by-article evidence map with a reuse verdict and owner for each obligation.
- Change scanning, firewall review and access review frequencies for in-scope systems, and update SoA justifications.
- Write and exercise a major incident reporting runbook against both the four hour and one-day limits.
- Build the register of information in the ITS 2024/2956 templates with LEIs and function mapping.
- Plan Article 30 contract remediation, critical or important functions first.
- Confirm TLPT status with the competent authority and record the answer.
- Reformat management review outputs into the RTS Article 27 review report.
- Add DORA obligations to the internal audit programme so one cycle evidences both.
Standards and references
- EUR-Lex: Regulation (EU) 2022/2554 on digital operational resilience for the financial sector (DORA)
- EUR-Lex: Delegated Regulation (EU) 2024/1774, RTS on ICT risk management tools, methods, processes and policies
- EUR-Lex: Delegated Regulation (EU) 2024/1772, RTS on classification of ICT-related incidents and cyber threats
- EUR-Lex: Delegated Regulation (EU) 2025/301, RTS on content and time limits for major incident reports
- EUR-Lex: Implementing Regulation (EU) 2024/2956, ITS on register of information templates
- EUR-Lex: Delegated Regulation (EU) 2025/1190, RTS on threat-led penetration testing
- ISO: ISO/IEC 27001 Information security management systems
Related NHI Mgmt Group resources: DORA Guide, ISO 27001 Certification Guide, ISO 27001 to NIS2 and DORA Mapping Guide, DORA Readiness Checklist, ISO 27001 Statement of Applicability Template. This guide summarises how ISO/IEC 27001:2022 relates to Regulation (EU) 2022/2554 and its technical standards and is not legal advice.