Who DORA applies to
The Digital Operational Resilience Act, Regulation (EU) 2022/2554, has applied since 17 January 2025. It covers 20 types of financial entity, including banks, insurers, payment and e-money institutions, investment firms, crypto-asset service providers and occupational pension funds. ICT third-party service providers are also named in its scope, and the critical ones fall under an EU oversight framework. In Germany, BaFin supervises DORA and summarises the rules on its DORA page.
The obligations scale with the entity. DORA applies its ICT risk management rules in proportion to size, risk profile and the complexity of the business (Art. 4). Some small entities, such as small and non-interconnected investment firms, follow a simplified framework, but they too must develop awareness programmes and resilience training "according to needs and ICT risk profile" (Art. 16(1)(h)).
What DORA requires for security awareness
DORA's awareness duties come down to three things: compulsory training for everyone, regular training for the management body, and staff who know how to report suspicious activity. Around these sit rules on budget, third-party providers, detection and learning from incidents.
The requirements are spread across the regulation and one of its delegated regulations. The table brings them together and translates each one into what it means for an awareness programme.
ReferenceWhat it requiresWhat it means in practiceArt. 13(6) DORAICT security awareness programmes and digital operational resilience training are compulsory modules for all employees and senior management, with complexity matched to each function; ICT third-party service providers are included where appropriateRole-based content, full coverage and a plan for contractors with access to your systemsArt. 5(4) DORAManagement body members keep their knowledge up to date, "including by following specific training on a regular basis"The board and executive committee need their own training, matched to the ICT risk they overseeArt. 19(b)(ii) Delegated Regulation (EU) 2024/1774Staff and ICT service provider staff must be aware of the reporting channels for detecting anomalous behaviourPeople need to know how to report a suspicious email, call or message; DORA does not prescribe a metric for checking thisArt. 5(2)(g) DORAThe management body allocates and reviews the budget for digital operational resilience, including awareness and trainingAwareness funding is a board decision; document approval and reviewsArt. 30(2)(i) DORAContracts with ICT third-party service providers set the conditions for their participation in your awareness programmesCheck that supplier contracts cover trainingArt. 10(1) and 17(3)(a) DORAPrompt detection of anomalous activity; incident management with early warning indicatorsEmployee reports can feed detection and incident handlingArt. 13(3) and 13(5) DORALessons from tests and real incidents feed the ICT risk assessment; senior ICT staff report to the management body at least yearlyUse incident patterns to choose training topics and include results in the yearly reportArt. 25(1) DORAThe resilience testing programme includes appropriate tests, for example "scenario-based tests"Simulations can be documented as part of the testing programme if your testing policy defines them that way
Mandatory, recommended or optional?
A frequent mistake with DORA and phishing is treating a method as an obligation. The distinction matters when you write your policy and talk to your auditor.
CategoryWhat falls into itRequired by DORA and its delegated regulationCompulsory awareness programmes and resilience training for all staff and senior management; regular training for the management body; staff awareness of reporting channels; contract terms on supplier participation in trainingRecommended practice (our view)Role-based scenarios for people with payment, credential or data authority; measuring reporting rates and time to report, not just clicks; feeding incident lessons into training; aggregated resultsOptional methodPhishing simulations by email, voice, SMS or messenger; gamified or micro-learning formats
DORA sets the outcome (trained staff, a trained management body, known reporting channels) and leaves the method to you. Phishing simulations are optional, but they let you check all three in practice.
Why phishing simulations still help with DORA
Phishing simulations are optional under DORA, but they make the mandatory parts easier to deliver and to prove. Each benefit below links to a requirement from the table above; none of them replaces the training itself.
BenefitWhat it gives youRelated requirementDocumentationDated records of who received which scenario and follow-up training, per role and entityArt. 13(6), Art. 5(4)Tested reporting channelsEvidence that staff actually use the report button or phone channel, not only that a policy existsDelegated Regulation 2024/1774, Art. 19Awareness in contextTraining tied to a realistic situation from the employee's own role, such as a changed supplier bank accountArt. 13(6)Management reportingTrends per role and channel for the yearly report by senior ICT staffArt. 13(5)Lessons learnedA practical check on whether changes made after an incident or test workArt. 13(3)
Whether simulation results count as evidence in a supervisory review depends on how your policy defines them. Treat them as supporting evidence for the required training, not as proof of compliance.
How to design phishing simulations around DORA
If you use simulations, design them around the three core requirements: training matched to the role, involvement of the management body and a working reporting channel. Five choices make the link to DORA visible.
Match difficulty to the role. DORA asks for training whose complexity fits each function. Payment operations, treasury, IT helpdesk, customer service and executive assistants face different attacks from the average employee, so test their actual authority: a changed bank account for a supplier payment, a password reset request by phone, an urgent transfer approval from an "executive". Our article on CEO fraud losses in Germany shows how these attacks play out.
Include the board. Board members and executives are targets of CEO fraud and impersonation, and they approve the ICT risk framework. Short, role-specific training and simulations show that they train regularly, as DORA requires.
Measure reporting, not only clicks. A simulation that counts clicks says little about detection. The delegated regulation requires staff to know the reporting channels; measuring whether people actually use them, and how quickly, is a recommended way to check that, not a stated requirement. Regular reports also turn employees into an early warning source for incident handling.
Go beyond email. Attacks on financial entities also arrive by phone, SMS and messenger. Add voice scenarios for roles that verify callers, such as helpdesk and contact centre agents.
Feed lessons back. When a real incident or a test reveals a pattern, for example supplier impersonation by phone, add it to the next simulation cycle and record the change.
Example scenario: A payment operations clerk receives an email from a known supplier announcing new bank details. An hour later, a caller claiming to be the supplier's accountant asks for the change to be processed before the payment run. The desired behaviour: the clerk calls the supplier back on the number stored in the vendor master data, reports the email through the report button and does not change the bank details. The security team sees the report, checks whether colleagues received the same email and records the case.
Social engineering testing under DORA: phishing simulations vs. TLPT
Awareness simulations and threat-led penetration testing (TLPT) are different exercises, and DORA governs them differently.
- TLPT is an intelligence-led red team test on live production systems. Under Art. 26 DORA, financial entities identified by their competent authority must run one at least every three years. The technical standard on TLPT, Delegated Regulation (EU) 2025/1190, expects red teams to use tactics that can include exploiting staff through social engineering (recital 21), and the test plan must set "ethical boundaries for social engineering" (Annex IV).
- Awareness simulations are not regulated as such by DORA. Where you use them, they can run regularly across the employee groups you choose and aim at learning and measurement, not at reaching a target system.
The two inform each other. TLPT findings on which pretexts worked are good material for simulations, and simulation data shows which roles a red team might target. Keep them separate in your documentation.
Which evidence to keep for your supervisor
DORA does not provide one fixed evidence checklist for awareness programmes. Some underlying obligations are explicit, such as training for all staff and the management body, the contract terms on supplier participation and staff awareness of reporting channels. How you document them is up to you; the records below are our recommendation.
EvidenceLinked requirementApproved awareness plan and budget, with review datesArt. 5(2)(g)Training records for management body membersArt. 5(4)Completion rates per role, including senior managementArt. 13(6)Contract clauses on supplier participation in training (the clauses themselves are required)Art. 30(2)(i)Policy describing reporting channels; reporting rates from simulations as a recommended checkDelegated Regulation 2024/1774, Art. 19Simulation results over time: reporting rate, time to report, interaction rate per roleArt. 13(4), 13(6)Changes made after incidents or tests, and the yearly report to the management bodyArt. 13(3), 13(5)
Define your metrics with clear denominators. The reporting rate is reported simulations divided by delivered simulations. Time to report can mean the time to the first report in a campaign (a detection measure) or the median across all reports (a habit measure), so state which one you use.
Data protection and works councils still apply
DORA does not replace data protection or employment law. Simulations process data about how employees behave, so you need a legal basis under the GDPR, a defined retention period and, depending on the processing, a data protection impact assessment. Our GDPR checklist for phishing simulations covers these steps.
In Germany, where a works council exists, co-determination under § 87(1) no. 6 BetrVG is likely to be relevant, because simulation tools record individual behaviour. Agree on reporting levels, retention and the handling of individual results before the first campaign; our works agreement template lists the usual clauses. DORA's awareness provisions do not call for individual results, so evidence aggregated by role or department is a sensible default that also limits the privacy impact.
This is not legal advice. How DORA, the GDPR and national employment law apply to your entity depends on your set-up; your counsel, compliance function and data protection officer should assess it.
Where to start: three practical steps
Whether or not you use phishing simulations, DORA asks you to prove that everyone is trained and knows how to report. Three steps get you there:
- Map your current training against the requirements table. Check coverage for the management body, senior management and supplier staff with access to your systems, and close the gaps first.
- Identify the roles with authority over payments, credentials or customer data. Give them targeted, multi-channel scenarios and measure whether they report, not only whether they click.
- Agree the rules before the first campaign. Settle the reporting level and retention with your data protection officer and, where one exists, the works council, then set up the evidence records from the table above.
How revel8 helps financial entities meet DORA's awareness requirements
revel8 supports the training, simulation and evidence parts of these requirements. It does not make an entity DORA compliant on its own, because compliance depends on the whole ICT risk management framework. The capabilities below are taken from revel8's public product pages.
Role-based training, including DORA modules. revel8's Interactive Trainings include ready-made modules for DORA, NIS-2, GDPR, ISO 27001 and phishing, maintained and updated as regulations change. Learning paths adapt by role, so finance gets invoice fraud and executives get deepfake awareness, and modules can be localised in more than 40 languages.
Multi-channel simulations. The Awareness Playlist runs simulations by email, voice call, SMS, WhatsApp, Telegram, Teams and deepfake video, matched to role, team and tooling, with difficulty adjusted to each person's awareness level. Simulations can start in the inbox and escalate to a call, as in the supplier example above. Contact centre teams can be trained with dedicated voice simulations.
Reporting channels and metrics. Employees report suspicious emails with one click in Outlook or Gmail, and a phone reporting app covers suspicious calls, SMS and WhatsApp messages on managed devices. Risk Monitoring & Mitigation shows reporting rate, interaction rate and time to report, with drill-downs by cohort, channel and campaign.
Audit-ready records. Completion records and reporting logs are mapped to NIS-2, DORA and ISO 27001 and can be exported via API, PDF or CSV. revel8 describes its monitoring as works-council conform with no individual surveillance, and hosts data in Germany on STACKIT. When you assess revel8 itself as an ICT third-party service provider, note that it lists itself as DORA aligned and certified to ISO/IEC 27001:2022.
To see how revel8 fits your DORA documentation, book a demo.




