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.

Free online assessment

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

The services

What AtWorkStudio delivers for each DORA pillar

Your compliance adviser tells you what the regulation requires. AtWorkStudio turns it into systems that work, proportionate to the size and risk profile of the entity, on-prem or in the cloud, and keeps them running over time.

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.

Digital identity management →

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.

Backup and disaster recovery →

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.

Incident response and recovery →

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.

Vulnerability assessment and penetration testing →

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.

European data centres →

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.

Security awareness →

Simplified framework · Article 16

For smaller entities: the simplified framework, done properly

Small and non-interconnected investment firms, exempted payment and e-money institutions and small occupational pension funds do not apply Articles 5 to 15, but a simplified ICT risk management framework (Article 16 and Title III of Delegated Regulation (EU) 2024/1774). Simplified does not mean optional: the measures must still be documented, applied and verified.

What remains mandatory

A documented ICT risk management framework, continuous security monitoring, identification of ICT risk sources, tested business continuity plans. Incident reporting, the register of information and contractual provisions with providers stay the same as for other entities.

Proportionate measures, managed

A small entity often has no in-house IT department. AtWorkStudio runs the measures that are actually needed as a managed service: tested backup and disaster recovery, identity and MFA, endpoint protection, updates, log collection. No big-bank tooling that nobody would have time to look after.

Documentation that stands up to review

The documented framework, the asset inventory, the continuity test reports and the periodic review are prepared by AtWorkStudio based on the systems it manages. One single contact for systems and evidence.
AtWorkStudio as your ICT provider

A provider that passes your due diligence

If you entrust AtWorkStudio with cloud services, backup or systems management, AtWorkStudio becomes one of your ICT third-party service providers under DORA. The information you need to assess us and to fill in your register is already public or documented.

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.

Subcontractor list →

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.

Certifications →

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. 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. 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. 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.

The path

From gap analysis to evidence

A four-step path built on the entity’s priorities: critical or important functions first, then everything else.

1. Technical gap analysis

NIST CSF 2.0 assessment and review of controls against the requirements of DORA and Delegated Regulation (EU) 2024/1774. Outcome: a list of gaps ranked by priority and impact.

2. Remediation plan

For each gap: technical solution, alternatives, impact on processes and budget. The plan is shared with the compliance function and with the management body, which approves it.

3. Implementation and management

AtWorkStudio implements the measures, on-prem or in the cloud, and runs them as a managed service. Alternatively, it hands them over fully documented to your IT department.

4. Tests and evidence

Recovery tests, vulnerability assessments and reviews at an agreed frequency, with reports and logs ready for internal audit and for the supervisory authority.

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.

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.