DORA · Regulation (EU) 2022/2554
DORA compliance, from regulation to systems
DORA (Digital Operational Resilience Act) requires financial entities to prove that their ICT systems withstand incidents, that incidents are detected and reported on time and that services can be restored. AtWorkStudio delivers the technical side: it designs, implements and runs the measures and produces the evidence for audits, alongside your compliance function and your advisers. Backed by a management system certified to ISO/IEC 27001, 27017, 27018 and ISO 9001.
Where to start? With a snapshot of your controls
The free assessment based on the NIST Cybersecurity Framework 2.0 measures the maturity of your security controls. It is the first step of the technical gap analysis against DORA requirements.
106 questions · Online result · No commitment
What AtWorkStudio delivers for each DORA pillar
ICT risk management
Inventory of assets, functions and dependencies, risk analysis, hardening, identity and privileged access management, phishing-resistant MFA, endpoint and server protection. Chapter II of DORA and Delegated Regulation (EU) 2024/1774.
Backup, continuity and recovery
Immutable backups kept separate from production, disaster recovery with RTO and RPO defined for every critical function, periodic recovery tests with written reports. The continuity policies of Articles 11 and 12, made verifiable.
Incident detection and handling
Log collection, EDR/XDR detection, response and recovery procedure, technical data ready to classify the incident and complete the initial notification, the intermediate and the final report. Reporting stays with the entity: AtWorkStudio prepares the technical facts.
Operational resilience testing
Continuous vulnerability assessment, penetration tests on exposed and internal systems, recovery and continuity tests, with fixes tracked through to closure. For entities required to run TLPT, preparation of the environment and implementation of the fixes.
ICT and cloud providers
Hosting choice with data in the European Union or in Italy only, architectures that reduce dependence on a single provider, a tested exit strategy, technical data on ICT services for the register of information.
Training and awareness
Awareness programmes for all staff and dedicated sessions for the management body, which under Article 5 must keep sufficient knowledge of ICT risk. Phishing simulations and measured results.
For smaller entities: the simplified framework, done properly
What remains mandatory
Proportionate measures, managed
Documentation that stands up to review
A provider that passes your due diligence
Data and subcontractors on record
Four hosting options, each stating where the data is stored and which jurisdiction the provider falls under. The subcontractor list is public and versioned: the subcontracting chain for your register is already written down.
Contracts that speak DORA
Service levels, assistance during incidents, audit rights, termination and exit strategy with data return: the Article 30 provisions are discussed and put in writing before the work starts, not after.
Controls verified by third parties
A management system certified to ISO/IEC 27001, 27017, 27018 and ISO 9001 and three services qualified by the Italian National Cybersecurity Agency (ACN) at level QC1. Certificates and records available for review.
From the field
An exit strategy from the public cloud, designed down to the last cable.
DORA requires financial entities to have an exit strategy for ICT services supporting critical or important functions (Article 28). Long before the regulation, a bank in Rome asked AtWorkStudio to design exactly that: bring every application running on the public cloud back on-premises, keeping the cloud for disaster recovery only.
The full story, with every step of the project, is on the cloud IT services page.
413
virtual machines
1,288
vCPUs
537 TB
usable storage
18
vSAN nodes
40 GbE
spine-leaf network
76 kW
power draw
- 1
The inventory
Networks, firewall rules, 413 virtual machines with resources and dependencies, around forty applications classified by criticality: the same mapping of functions and dependencies that DORA requires today.
- 2
The detailed design
Two vSAN clusters on 18 nodes, a 40 GbE spine-leaf network, power, cooling, a disaster recovery link and a bill of materials ready for tender. An executable plan, not a statement of intent.
- 3
The decision
With every cost on the table, including the people needed to run an in-house datacentre, the bank independently chose to stay on the public cloud. Knowing exactly how to leave it.
An exit strategy has to be proven on the numbers, not just written into the contract.
From gap analysis to evidence
1. Technical gap analysis
2. Remediation plan
3. Implementation and management
4. Tests and evidence
Frequently asked questions about our DORA services
The questions financial entities and the IT companies working for them ask us most often. For the obligations of companies subject to NIS2, see the NIS2 compliance page.
No, and nobody can: there is no DORA certification. Compliance remains the responsibility of the financial entity and its management body, and is verified by the supervisory authority. AtWorkStudio implements and runs the technical measures and produces the evidence (configurations, logs, test results) that the entity brings to audits and inspections.
Regulation (EU) 2022/2554 has applied since 17 January 2025 to the financial entities listed in Article 2: credit institutions, investment firms, management companies, payment and e-money institutions, insurance and reinsurance undertakings, pension funds, crypto-asset service providers and others. For some smaller entities, Article 16 provides a simplified ICT risk management framework. IT companies serving these entities are not directly subject to DORA, but receive its requirements through their contracts.
The contractual provisions of Article 30 (service description, data processing locations, service levels, assistance during incidents, audit rights, termination and exit strategy) and the information the entity must enter in its register of information, including the subcontracting chain. Direct oversight by the European authorities only applies to providers designated as critical: the first list, published by the ESAs on 18 November 2025, has 19 providers. AtWorkStudio also helps IT companies prepare credible answers and technical measures.
Under Delegated Regulation (EU) 2025/301: initial notification within 4 hours of classifying the incident as major and in any case within 24 hours of becoming aware of it, intermediate report within 72 hours of the initial notification, final report within one month of the latest intermediate report. Reporting is the entity’s duty; AtWorkStudio provides the technical data needed to classify the incident and complete the reports.
Alerts are analysed by the AtWorkStudio team during business hours. Out of hours, automation takes over: it isolates the device, blocks the compromised account, stops malicious processes and notifies the contacts designated by the entity. For entities that need to be able to classify an incident out of hours, on-call availability and extended coverage are defined in the contract, together with the escalation procedure to whoever decides on classification and reporting.
Threat-led penetration testing (TLPT, Article 26) is only required of entities identified by the authority, at least every three years, and must be carried out by testers meeting the requirements of Article 27. AtWorkStudio runs vulnerability assessments, penetration tests and recovery tests, prepares the environment for TLPT and implements the fixes that come out of it.
For the financial sector, DORA is the sector-specific law and takes precedence over NIS2 for ICT risk management and incident reporting. Many technical measures are shared (backup, identity management, detection, supplier management), so a group with companies in both scopes can run a single technical programme.
No. ISO/IEC 27001 covers much of ICT risk management, but DORA adds its own obligations: incident classification and reporting with fixed deadlines, a resilience testing programme, a register of information on ICT providers, mandatory contractual provisions. AtWorkStudio’s management system, certified to ISO/IEC 27001, 27017, 27018 and ISO 9001, is a solid basis for the due diligence the entity carries out on us.
DORA asks for evidence, not statements
Tell us how your entity is organised, which functions are critical and who runs your systems today. AtWorkStudio will suggest where to start.