Resilience you can show, not just describe.

The Digital Operational Resilience Act has applied since 17 January 2025 to financial entities in the EU, authorised CASPs included. It asks for a working ICT risk framework, fast incident reporting, regular testing and firm control of the technology providers you depend on.

17 Jan 2025

the date DORA began to apply, CASPs included

4h

to notify a major incident once it is classified, and no later than 24 hours after detection

0

pillars: risk, incidents, testing, third parties and information sharing

0 yrs

between threat-led penetration tests, for the firms selected

What DORA asks, and what Avus records.

DORA is about how your systems hold up. Avus is one of those systems, and it keeps the evidence for the rest.

Art. 5 to 16

ICT risk management

The management body owns a documented framework to identify, protect, detect, respond and recover, reviewed at least once a year.

Access, roles and MFA are checked all the time, with gaps surfaced as they appear.

Governance and audit
Art. 9

Protection and prevention

Strong authentication, access limited to what each role needs, and logging of what happens on your systems.

Single sign-on and MFA, role-based access and an append-only log of every action.

Governance and audit
Art. 17 to 23

Incident reporting

Major ICT incidents are classified against set criteria and reported on a fixed clock: an initial notification, an intermediate report and a final report.

Provider outages are logged with their timeline, ready for the report.

Integrations and API
Art. 24 to 27

Resilience testing

A testing programme covers critical systems, with threat-led penetration testing every three years for the firms selected for it.

Failover to a second provider is set up and exercised, and every switch is recorded.

Integrations and API
Art. 28 to 30

ICT third-party risk

Contracts with ICT providers need specific terms, and a register of information on every arrangement is kept and shared with the regulator.

An ICT third-party register with criticality, exit plans and review dates.

Governance and audit
Art. 28(8)

Exit strategies

Where a provider supports a critical or important function, a documented and tested exit plan must exist.

A provider-neutral data model, so a switch leaves your rules and history untouched.

Integrations and API

Key dates.

DORA is fully in force. What remains is doing it well, every year.

  1. DORA enters into forceA two-year run-in begins for firms and supervisors.
  2. DORA appliesICT risk, incidents, testing and third-party rules take effect.
  3. First registers of informationEvery ICT third-party arrangement recorded and submitted.
  4. Critical providers designatedThe first critical ICT third-party providers come under EU oversight.

Resilience with the receipts.

Supervisors want to see that controls ran, when they ran and who looked.

Engine

Watches every connection

Latency, errors and failures on every provider are recorded as they happen.

Agent

Assembles the timeline

When something breaks, the events are pulled into one timeline for the report.

Person

Classifies and signs off

People decide whether an incident is major, and approve what goes to the regulator.

Show us your register.

We will map your providers into an ICT third-party register and show what an incident timeline looks like in Avus.

Sources

A summary to help you find your way, not legal advice. The official texts are the reference, and your own counsel should confirm how they apply to you.