DORA in 2022: Measuring operational resilience in financial technology
A retrospective on the 2022 operational resilience regulation and its practical implications for service maps, suppliers and recovery tests.
Archive retrospective · Topic year 2022
Start from the business outcome
EU Regulation 2022/2554 set out an operational resilience framework for the financial sector. Its adoption and application dates are distinct. Identify the service that must continue during an incident. A balance screen may still work while payment reconciliation is unavailable. Describe who is affected, how an interruption is detected and what business result constitutes recovery. Track those along with infrastructure health.
An inventory needs to explain dependencies
A process can rely on infrastructure, identity and a payment processor. For each dependency identify the service, failure signal, owner and fallback. Several suppliers can rely on the same upstream component. Keep records in line with what is actually used in production. An inventory that lists only names and renewal dates leaves a resilience exercise working from incomplete assumptions.
Measure the journey after traffic returns
In a controlled exercise, make a test dependency unavailable. Measure which steps in customer payment and reconciliation recover. A healthy endpoint does not establish that queued transactions have been processed. Record recovery of customer-facing service, clearance of accumulated work and data reconciliation as distinct checkpoints. Set acceptance criteria before the exercise. Use a controlled environment when interrupting production is unnecessary.
Turn the evidence into a management decision
A repeatedly missed recovery objective should have an owner and an explicit decision. Improve monitoring, establish an alternate process or change the architecture, depending on the evidence. Identify what the next exercise should verify and when. This retrospective does not determine an organization’s legal obligations. It shows how operational evidence, business effects and responsibilities can be linked in a useful management record.
Separate a claim from its evidence
A demo or experiment does not prove that an approach works in every context. Record measurement conditions, versions, data samples and assumptions. Compare a new method with the current one under the same workload before claiming a performance or quality improvement. Explicit uncertainty is more useful than false precision.
Keep tests and evidence for long-term value
Investigate root causes rather than symptoms. Check downstream components, stored records and user actions affected by a change. Test both successful and failed paths. Record dates, versions, measurements and references so later decisions can be reviewed without reconstructing the entire history.
Comments
No comments yet. Be the first to contribute.
Reading “DORA in 2022: Measuring operational resilience in financial technology” raised this question for me: the business decision needs traceable evidence.
Editor note: Security and failure modes require evidence beyond a launch post. We will revisit the assessment as the source is updated.
Features are only part of the story: security and privacy deserve their own review.
I would compare the announcement against independent benchmarks before making a decision.
✎ Write a comment