DORA for financial entities
Keep your operations running, and show the supervisor how
For credit institutions, payment and electronic money institutions, investment firms and insurers. Pritect holds your business impact assessments, continuity plans and tests, ICT incidents and the register of information on one record, so an outage reads the continuity work you already did and every regulatory clock starts from the same facts.
Payment gateway outage
Incident Centre · reported 09:12
DORA initial notification clock
24 h left
Ready
Step 1 of 6
DraftICT incident logged
Card payments are failing for retail clients. The payment gateway is named as the affected service.
Jonas Berg, IT operations
Log
Nothing logged yet
Six steps inside the clock. Maja Lindqvist, Head of ICT Risk, confirms the classification, reviews the draft and records the submission, and the plan owner approves the activation. Nothing is filed until Maja decides.
Demo data. The Incident Centre carries a Preview marker in the app while its notification content is reviewed. Pritect proposes the major incident classification and a named person confirms it; the classification thresholds are still under expert review. Today the DORA initial notification clock runs from awareness.
- In scope
- Art. 2 financial entities, DORA applies from 17 Jan 2025
- One record
- BIA, continuity, incidents and the register read the same services
- Sign-off
- Drafts wait for a named person; nothing is filed for you
01 · Beyond governance
Four DORA jobs, each with a mechanism you can inspect
Most DORA work is not writing policy. It is knowing what an outage costs, having a tested plan for it, running the incident against the clock, and filing what the supervisor asks for. Each of these is a working surface in Pritect.
Business impact
Business impact assessments
One BIA per business service, with configurable impact categories. RTO, RPO and MTPD are required before submission, RTO can never exceed MTPD, and a second person approves each revision.
Continuity
Continuity plans and their tests
Plans with scenarios for loss of site, people and ICT, linked to the BIA they answer. Exercises record the result and planned against actual recovery times, and a failed test opens a remediation action.
Incident clocks
ICT incidents, classified and on the clock
One incident record carries every regulation you adopted. Pritect proposes the DORA major incident classification for a named person to confirm, and the obligation engine runs each notification clock side by side.
- DORA initial notification, from awareness
- 24h
Filing
The reports you file
Notification drafts per obligation, and a recorded submission with its method, reference and the person who filed it. The register of information exports as the xBRL-CSV filing package.
02 · Business impact and continuity
The incident reads the continuity work you already did
A BIA in Pritect belongs to a business service, and so does the continuity plan that answers it. When an incident names that service, the plan is suggested from it, so the recovery targets in front of the responder are the ones the business approved.
Critical or important functions
Each service records whether it supports a critical or important function, with who reviewed that and when.
A plan looser than the BIA is a finding
If an approved plan promises a slower RTO or RPO than the BIA tolerates, or an asset on the critical path recovers too slowly or has not been verified in 12 months, Pritect raises a remediation action.
Activation needs an approver
Activating a plan from an incident is a request. A named approver accepts or declines it, and both are on the record.
An annual testing programme
What must be tested, how often and whether an independent tester is needed, with last tested, next due and overdue items.
Exercises with results
Tabletop, walkthrough, simulation and full tests, each with findings, actions and planned against actual RTO and RPO.
Exit plans that are tested
Supplier exit plans are approved and tested as exit simulations, and a supplier behind a critical function cannot be offboarded without one.
03 · Incidents and reporting
Every clock on one incident, and a person on every filing
DORA asks you to classify ICT-related incidents and to report the major ones in an initial notification, an intermediate report and a final report. Pritect records the classification on the incident and keeps the reports as obligations, beside the GDPR and contractual clocks the same outage starts.
Major incident classification
Pritect scores the incident against the major incident criteria and proposes a verdict. A named person confirms it, the decision stays on an append-only record, and reversing a major verdict needs a second person. The thresholds are still under expert review.
Recurring incidents
Incidents that share an apparent root cause are grouped, their impact is combined, and the assessment against the major incident criteria is recorded.
Clocks side by side
Each adopted regulation's notification duty becomes an obligation with its own anchor. Where a duty has two limbs, the earlier deadline binds.
Drafts, never sends
A notification draft is grounded on what the obligation requires, abstains when facts are missing, and must be reviewed before use.
A recorded submission
Who submitted, when, by which channel and with which authority reference, then the acknowledgement. Each framework's reporting contacts, including outsourced reporting, are kept in one place. Filing stays with your people.
A post-incident review
One structured review per incident. Each action you choose to track becomes a remediation action, linked to the service, plan, risk or supplier it concerns.
A crisis team ready to call
Declare a crisis from the incident and the team is filled from your standing roster, with deputies, a call order and an after-action report.
An incident dossier
The incident, its timeline and its obligations as a versioned PDF, generated from the record rather than assembled by hand.
Contractual clocks too
Notification commitments in client contracts run as obligations on the same incident as the regulatory ones.
04 · Register of information
The register of information, kept live and filed as a package
Your ICT third-party arrangements sit with the suppliers, contracts and services they describe. The register is checked against Pritect and EBA rules, findings are listed record by record, and the filing package is built on the server and refused while a blocking finding stands.
- Templates
- B_01.01
- B_01.02
- B_01.03
- B_02.01
- B_02.02
- B_02.03
- B_03.01
- B_03.02
- B_03.03
- B_04.01
- B_05.01
- B_05.02
- B_06.01
- B_07.01
- B_99.01
- Format
- EBA DORA module 4.0, taxonomy 4.0 errata 5, severity 4.0.0.3
- Exports
- XLSX working copy and the xBRL-CSV filing package, each recorded in an export ledger with its digest
- Contract of record
- Each arrangement points at its contract in Legal, and every re-point is audited
- Identifiers
- The LEI check-digit test, a GLEIF check of each LEI's legal name, country and registration status, and an EUID, registration, VAT or passport number for a provider without an LEI
Fill-in rules from the implementing standard are shown as advice until their review is signed off, and the package then says which rules were not checked.
05 · The governance layer
Governance that points at the working records
The framework, the board and the supplier policy still matter. In Pritect they sit on top of the operational records above, so evidence is a link rather than a statement.
DORA workspace
Scope, register and filing gaps, exit plans, the testing programme, supervisory orders and board resolutions in one read-only view. It shows gaps; it does not grade you.
Resilience strategy
The digital operational resilience strategy as a governed policy, with each required element linked to its evidence.
Obligations and controls
DORA articles as obligations you adopt, own and evidence, mapped to the Pritect Cybersecurity Framework.
Management body
Management body, internal auditor and external reviewer roles with time-limited access, and board resolutions on record.
Third-party risk
Supplier due diligence, ICT concentration risk across functions and locations, and contract clause checks.
Supervisory orders
An order becomes actions with owners and evidence, with a status report on progress.
06 · Overlaps
One outage, several laws, one record
Where DORA applies, its ICT risk and incident reporting rules take the place of the NIS2 equivalents, and NIS2 still governs group companies DORA does not reach. A personal data breach starts the GDPR clock as well. Pritect runs the clock of every regulation you adopted on the same incident.
| Duty | DORA | NIS2 | GDPR |
|---|---|---|---|
| ICT and security risk management | Art. 6 | Art. 21 | Art. 32 |
| Incident reporting | Art. 17, Art. 18, Art. 19 | Art. 23 | Art. 33, Art. 34 |
| Third-party and processor contracts | Art. 30 | Not tracked | Art. 28 |
07 · Coming next
What we are building next for DORA reporting
These are in design or being built. None of them is available today, and we will not show them as available until they are.
Chained reporting clocks
The law times the initial notification at 4 hours from classification and at most 24 hours from awareness, the intermediate report at 72 hours after it, and the final report one month after the intermediate one. Pritect will run each clock from the event before it.
Generated reports
Initial, intermediate and final reports in the shape of the reporting template, exported as PDF and JSON and recorded as filed by a person.
Client notices from the classification
A major classification will open the notice to affected clients, to be approved and released to the right stakeholder groups with fallback guidance.
08 · Residency and price
Hosted in the EU, priced in public
Your DORA records stay in the EU. Every tier is published, so you can size the programme before you talk to us.
- Database
- Ireland, EU
- AI drafting
- Mistral AI, France, EU
- Sub-processors
- Published, with location and purpose
- Pricing
- Every tier priced on the pricing page
