The Digital Operational Resilience Act (DORA), Regulation (EU) 2022/2554, has applied since 17 January 2025 [1]. Most of the early work went into registers of information, incident reporting and third-party contracts. Training got less attention, though DORA makes it mandatory and supervisors are now looking at how firms have embedded the rules, not just whether they wrote them down.
This guide covers the DORA training requirements in plain terms: who must be trained, on what, how often, what evidence to keep, and how DORA fits with NIS2 and the EU AI Act's AI literacy duty. It reflects the texts as of 12 November 2026 and is general information, not legal advice.
Who DORA applies to
DORA covers 20 types of financial entity. They include credit institutions, payment and e-money institutions, investment firms, crypto-asset service providers, central securities depositories, central counterparties, trading venues, managers of alternative investment funds, UCITS management companies, insurers and insurance intermediaries, occupational pension funds, credit rating agencies and crowdfunding providers. It also covers ICT third-party service providers [1, Art. 2].
If you run a US-headquartered group with EU-authorised investment firms, fund managers or banks, those EU entities are in scope. The training duty sits with each in-scope financial entity.
The two core DORA training requirements

Photo: Benjamin Child / Unsplash
Article 13(6): staff awareness and resilience training
"Financial entities shall develop ICT security awareness programmes and digital operational resilience training as compulsory modules in their staff training schemes. Those programmes and training shall be applicable to all employees and to senior management staff, and shall have a level of complexity commensurate to the remit of their functions." [1, Art. 13(6)]
In practice, this means:
- Compulsory, not optional. These must be mandatory modules in your training scheme. Optional e-learning doesn't meet the requirement.
- Everyone, including senior management. There's no carve-out for non-technical staff.
- Role-based depth. "Commensurate to the remit of their functions" means a customer-service agent, a developer with production access and a head of operations shouldn't all get the same course.
- Two subjects. ICT security awareness covers phishing, credentials, data handling and reporting anomalies. Digital operational resilience covers business continuity, incident escalation, the firm's response and recovery plans, and each person's role in them.
Article 5(4): management body training
"Members of the management body of the financial entity shall actively keep up to date with sufficient knowledge and skills to understand and assess ICT risk and its impact on the operations of the financial entity, including by following specific training on a regular basis, commensurate to the ICT risk being managed." [1, Art. 5(4)]
This sits inside Article 5, which makes the management body responsible for the ICT risk management framework. Article 5(2)(g) also requires the management body to allocate and periodically review the budget for "ICT security awareness programmes and digital operational resilience training referred to in Article 13(6), and ICT skills for all staff" [1, Art. 5(2)]. So the board has to be trained, and it also has to fund and oversee training for everyone else.
Board training should be specific: the firm's ICT risk profile, its critical or important functions, third-party concentration, incident reporting duties, resilience testing results, and what the board must approve.
Smaller entities: the simplified framework
Certain smaller entities, such as small and non-interconnected investment firms, exempted payment and e-money institutions and small occupational pension funds, follow a simplified ICT risk management framework under Article 16. They must still develop ICT security awareness programmes and digital operational resilience training for staff and management "according to needs and ICT risk profile" [1, Art. 16(1)(h)]. The supporting technical standard requires their management body to review the training budget at least once a year [2, Art. 28].
Including ICT third-party service provider staff

Photo: Taylor Vick / Unsplash
Article 13(6) continues: "Where appropriate, financial entities shall also include ICT third-party service providers in their relevant training schemes in accordance with Article 30(2), point (i)" [1].
Article 30(2)(i) makes this contractual. Every contract for ICT services must set out "the conditions for the participation of ICT third-party service providers in the financial entities' ICT security awareness programmes and digital operational resilience training" [1, Art. 30(2)(i)]. That applies to all ICT services contracts, not only those supporting critical or important functions.
The ICT risk management technical standard, Delegated Regulation (EU) 2024/1774, adds an HR-policy requirement. Staff of the financial entity and of ICT third-party providers who use or access the entity's ICT assets must be informed about, and adhere to, its ICT security policies, and must know the reporting channels for anomalous behaviour [2, Art. 19].
Practical approach: decide, provider by provider, which provider staff need to be included. Typical cases are managed service desks, outsourced SOC analysts and contractors with privileged access. Write the conditions into the contract: which modules, by when, how completion is evidenced and who pays. Then track completion the same way you track your own staff.
How often: what DORA says and doesn't say
DORA does not set a fixed training frequency. What it does say:
- Management body training must be followed "on a regular basis" [1, Art. 5(4)].
- The ICT risk management framework must be documented and reviewed at least once a year (periodically for microenterprises), after major ICT-related incidents, and following supervisory instructions or findings from resilience testing or audits [1, Art. 6(5)].
- Lessons from resilience testing and real incidents must be "duly incorporated on a continuous basis" into ICT risk assessment and reviews of the framework [1, Art. 13(3)].
A defensible cadence for most firms combines an annual baseline for all staff and the board with event-driven updates after a major incident, a significant test finding, a new critical provider or a material change in the threat picture. That's a practice recommendation that follows from the review duties above, not a stated DORA rule.
What evidence supervisors expect
DORA doesn't prescribe a training-record format. It does give supervisors broad powers. Competent authorities can access "any document or data held in any form" relevant to their duties [1, Art. 50(2)], and firms must submit a report on the review of their ICT risk management framework on request [1, Art. 6(5)].
Older guidance has been scaled back to make room for DORA. In February 2025 the EBA narrowed its Guidelines on ICT and security risk management because DORA now sets harmonised ICT risk requirements [9]. What supervisors have said since points to embedding and board ownership:
- BaFin noted that DORA "places a considerably stronger emphasis" on training obligations than Germany's previous BAIT/VAIT circulars. It highlighted Articles 13(6) and 5(4) and the contractual training conditions in Article 30(2)(i) [3].
- The ECB reports that operational and ICT risk continue to receive the worst average scores in its supervisory review (SREP). It found recurring weaknesses in cybersecurity strategies, incident management and third-party risk, and says it will assess DORA compliance [4].
- The Central Bank of Ireland found that most firms have documented DORA frameworks but that "end-to-end embedding in practice is still a work in progress". It reported gaps in senior management ownership and management body oversight of ICT [5].
An evidence pack that answers those concerns would usually include:
- A training policy that maps Articles 5(4), 13(6) and 30(2)(i) to audiences, content and cadence.
- Role-based curricula showing different depth for different functions.
- Per-person completion records with dates, content version and assessment results.
- Board training records: dates, topics, attendees and materials.
- Management body approval of the training budget [1, Art. 5(2)(g)].
- A list of in-scope third-party provider staff and their completion status.
- A change log showing how incidents, test results and audit findings updated the content.
DORA training vs NIS2 training
DORA describes itself as lex specialis to the NIS2 Directive for financial entities [1, recital 16]. For in-scope financial entities, DORA's ICT risk rules take precedence where they overlap. The two still differ in how they treat training:
| NIS2 (Directive (EU) 2022/2555) | DORA (Regulation (EU) 2022/2554) | |
|---|---|---|
| Legal form | Directive, transposed nationally | Regulation, directly applicable |
| Management body | Members are required to follow training [6, Art. 20(2)] | Must keep knowledge up to date, including specific training on a regular basis [1, Art. 5(4)] |
| Employees | Entities are encouraged to offer similar training regularly; "basic cyber hygiene practices and cybersecurity training" is a required risk-management measure [6, Arts. 20(2), 21(2)(g)] | Compulsory awareness and resilience modules for all employees and senior management [1, Art. 13(6)] |
| Third parties | Supply-chain security measures [6, Art. 21] | Include ICT third-party providers in training where appropriate, with contractual conditions [1, Arts. 13(6), 30(2)(i)] |
| Budget | Not specified | Management body allocates and reviews the training budget [1, Art. 5(2)(g)] |
Groups with both financial entities and non-financial essential or important entities, for example a bank with a separate data-centre subsidiary, may need both regimes. A shared core curriculum with DORA- and NIS2-specific modules keeps the work manageable. For NIS2 background, see our NIS2 guide.
How DORA interacts with the EU AI Act's AI literacy duty
Article 4 of the AI Act has applied since 2 February 2025. The Digital Omnibus on AI, Regulation (EU) 2026/1744, which entered into force in July 2026, rewrote it [7][8]. As amended, providers and deployers of AI systems "shall take measures to support the development of AI literacy of their staff and other persons dealing with the operation and use of AI systems on their behalf". The obligation "does not require providers or deployers to guarantee any specific level of AI literacy of any individual" [7]. The Commission says national market surveillance authorities supervise and enforce the rules from 2 August 2026, and that no certificate is needed: organisations can keep internal records of training [8].
For financial entities, the two duties are legally separate:
- DORA covers ICT security and operational resilience for everyone.
- AI Act Article 4 covers staff and others who operate or use AI systems on the firm's behalf, such as credit-scoring tools, fraud models, chatbots and coding assistants.
They overlap in practice. AI tools add ICT risk, such as data leakage, model supply chains and new third-party dependencies, which DORA training should address. AI literacy content should cover the firm's ICT security rules for those tools. Many firms run a shared module and record it against both obligations. See our overview of AI literacy requirements under the EU AI Act.
A practical 90-day plan
- Map the obligations. List every in-scope entity, its framework (full or simplified) and its audiences: board, senior management, staff by role and third-party provider staff.
- Build role-based content. Use one core awareness module, then resilience modules for each role, such as incident handlers, business-continuity owners, developers and front-office staff.
- Brief the board properly. Use firm-specific ICT risk sessions, not generic cyber talks, and minute them.
- Fix the contracts. Check that every ICT services contract sets the conditions for provider participation in training.
- Wire in triggers. Link incident reviews, test findings and audit actions to content updates.
- Assemble the evidence pack so you can produce it on request.
How NexeraOS can help
NexeraOS works as an AI-powered compliance training partner for financial firms. We help compliance, risk and L&D teams plan role-based DORA training, deliver it to staff, boards and third-party providers, and keep audit-ready records, with your team reviewing and approving content. Learn more about our work with banks and AML teams, broker-dealers and investment advisers, or our approach to AI-powered compliance training.
FAQ
What are the DORA training requirements? Article 13(6) requires compulsory ICT security awareness and digital operational resilience training for all employees and senior management, matched to each role. Article 5(4) requires management body members to keep their ICT risk knowledge current, including through specific training on a regular basis [1].
How often does DORA require training? DORA sets no fixed frequency. Board training must be "regular", and the ICT risk framework must be reviewed at least annually and after major incidents [1, Arts. 5(4), 6(5)]. An annual baseline with event-driven refreshers is common practice.
Do ICT third-party service providers have to take DORA training? Where appropriate. Contracts must set the conditions for their participation [1, Arts. 13(6), 30(2)(i)].
What evidence do supervisors expect? DORA doesn't prescribe a format, but supervisors can request framework documentation and any relevant records [1, Arts. 6(5), 50(2)]. Keep policies, role-based curricula, per-person completion and assessment records, board training minutes, budget approvals and a content change log.
How is DORA training different from NIS2 training? DORA is lex specialis for financial entities. It makes staff training compulsory where NIS2 only encourages it, and it adds third-party and budget requirements [1][6].
Does the AI Act's AI literacy duty overlap with DORA? They are separate duties, but they can share delivery and records. Article 4 now requires measures to support AI literacy without guaranteeing a specific level [7][8].
Sources
- Regulation (EU) 2022/2554 (DORA), EUR-Lex: https://eur-lex.europa.eu/eli/reg/2022/2554/oj/eng
- Commission Delegated Regulation (EU) 2024/1774 (RTS on ICT risk management framework), EUR-Lex: https://eur-lex.europa.eu/eli/reg_del/2024/1774/oj/eng
- BaFin, Supervisory statement: DORA implementation guidance (July 2024): https://www.bafin.de/SharedDocs/Downloads/EN/Anlage/dl_2024_07_08_Aufsichtsmitteilung_Umsetzungshinweise_DORA_en.pdf?__blob=publicationFile&v=3
- ECB Banking Supervision, Supervisory priorities 2026–28: https://www.bankingsupervision.europa.eu/framework/priorities/html/ssm.supervisory_priorities202511.en.html
- Central Bank of Ireland, Regulatory & Supervisory Outlook Report 2026: https://www.centralbank.ie/docs/default-source/publications/regulatory-and-supervisory-outlook-reports/regulatory-supervisory-outlook-report-2026.pdf
- Directive (EU) 2022/2555 (NIS2), EUR-Lex: https://eur-lex.europa.eu/eli/dir/2022/2555/oj/eng
- Regulation (EU) 2026/1744 (Digital Omnibus on AI), EUR-Lex: https://eur-lex.europa.eu/eli/reg/2026/1744/oj/eng
- European Commission, AI Literacy – Questions & Answers: https://digital-strategy.ec.europa.eu/en/faqs/ai-literacy-questions-answers
- European Banking Authority, EBA amends its Guidelines on ICT and security risk management measures in the context of DORA application (11 Feb 2025): https://www.eba.europa.eu/publications-and-media/press-releases/eba-amends-its-guidelines-ict-and-security-risk-management-measures-context-dora-application




