By Yupeng Ji, VP of Compliance at New Relic
The Digital Operational Resilience Act (DORA) represents a shift in how regulators expect financial institutions to manage and evidence technology risk. Where firms were previously assessed on whether they had adequate incident response plans, DORA introduces a stricter standard, measuring how quickly and confidently they can assess and communicate impact when something goes wrong.
Central to that standard is a four-hour window within which to report an incident. Once an incident is classified as “major,” firms have a mere four hours to notify their regulatory supervisor. It is one of the most stringent reporting timelines in financial regulation, which, in turn, creates a massive burden on financial institutions to meet. Delayed classification or missed reporting leaves firms facing automatic regulatory breach, potential fines of up to 2 percent of annual global turnover, and reputational damage lasting years. At the same time, firms are managing high‑impact outages that cost an average of $1.8 million per hour, making operational visibility and impact assessment a direct financial priority.
Meeting such a demanding deadline requires continuous visibility across the technology estate, enabling teams to quickly identify operational risks and assess incidents against DORA’s major event thresholds.
How intelligent observability helps support financial institutions’ DORA journey
Modern observability platforms are positioned to provide financial institutions with the tools needed to achieve broad and continuous visibility across their stack.
By structuring telemetry around DORA’s specific criteria, such as affected clients and service disruption duration, teams can immediately map technical system health against DORA’s major event thresholds.
Financial organisations should consider tools for digital operational resilience testing, including synthetic monitoring for critical ICT infrastructure and alerting/insights for anomalous behavior, satisfying requirements for both ongoing monitoring and testing.
The ability for an observability platform to connect technical performance signals to specific business functions and customer groups is also key. This allows senior leaders to make confident, informed decisions without waiting for technical data to be manually interpreted.
When manual reporting is not enough
Traditional monitoring relies on teams piecing together data from multiple systems over time, an approach that works when there is sufficient time available.
However, when classification has to happen before this full picture has emerged, the instinct is to wait. Teams hold off, wanting to be certain before they escalate, but under DORA that caution has become a compliance risk in its own right. Intelligent observability can eliminate this hesitation by consolidating all telemetry data into a single, real-time platform, allowing teams to automatically detect, classify, and resolve incidents instantly, ensuring continuous DORA compliance without the wait.
Better understanding is needed within a faster timeframe
To maintain operational resilience, teams need to understand the scope of impact across services, how performance is degrading in real time, and whether the thresholds that define a “major” incident have been crossed before the situation has fully resolved itself.
Under DORA’s regulatory technical standards, an incident is classified as major when critical services are affected or when it breaches at least two of six defined criteria, including the number of clients affected and the duration of disruption. To address this, organisations should structure telemetry around these criteria in advance so disruption data can immediately be assessed against DORA’s thresholds, allowing faster and more accurate classification decisions.
Organisations can use intelligent observability to map telemetry directly, utilising real-time dashboards and automatic correlation to instantly measure service impact and classify incidents the moment they occur.
The difference between engineering visibility and clarity in the boardroom
Beyond technical visibility, DORA introduces a second layer of complexity. The technical signals engineers use to monitor system health do not automatically translate into the language that board members need in order to act.
Boards need to know which business functions are down and where the exposure sits across different regions and entities. Teams that have invested in observability tools that connect technical performance with business functions and customer groups find that leaders can act on the information directly rather than waiting for it to be interpreted.
In an environment where every hour of uncertainty carries a seven‑figure cost, and 29 percent of firms face high-impact incidents weekly, translating technical failure into real-time business impact is fast becoming a regulatory and financial necessity. Observability can bridge this gap by mapping raw telemetry directly to business-level KPIs, translating complex engineering data into clear, real-time dashboards that give boardroom executives the exact customer and financial impact context they need to make rapid compliance decisions.
A compliance challenge that starts before the incident
For years, monitoring infrastructure was considered an engineering concern, valuable for operational reliability, but largely separate from compliance and regulatory risk. Firms must ensure their systems can support classification decisions directly from data and produce accurate reports for regulators.
The firms most likely to struggle are those still relying on traditional monitoring, or using observability purely as a post-incident recovery tool, rather than as a foundation for resilience and the operational insights that DORA now demands. Observability helps firms assess risk, understand impact and meet DORA’s reporting requirements more effectively.