DORA, kept current all year.
Register of information, ICT incidents and the resilience self-assessment in one place, ready for your supervisor.
Request a demoThe problem
The register of information lives in spreadsheets that drift away from the real contracts.
A major ICT incident starts a 4-hour clock, and nobody is sure who files what, when.
Exit plans, non-EU providers and concentration on one supplier are hard to see across many contracts.
How ActiveERM handles it
- 1Providers and functionsList ICT providers and the business functions they support, critical or important.
- 2Contracts and servicesLink contracts and services; record substitutability and the exit plan for critical ones.
- 3Excel on ESA templatesExport the register as one workbook laid out on the ESA template sheets.
- 4IncidentsFlag a major ICT incident on the event and the reporting clock starts.
- 5Self-assessmentScore 13 controls from 1 to 5; low scores become the gap list.
Dates that matter
The register is submitted through your supervisor's own channel; ActiveERM prepares the file, it does not file it for you.
Major ICT incident reporting clock
What you get
Dashboard
Providers, critical functions, concentration, non-EU critical providers, exit-plan gaps and contracts expiring within 90 days.
Register of information
Providers with LEI and parent, functions, contracts and services, kept as linked lists.
Export on ESA templates
One Excel workbook with the B_01.01, B_02.02, B_05.01, B_06.01 and B_07.01 sheets.
Incident deadlines
Initial, intermediate and final reports with due times, overdue alerts, e-mail reminders and a printable report.
One incident record
A DORA incident is the same event as in your operational-risk register, classified on six impact criteria.
Resilience self-assessment
13 controls scored 1 to 5, average maturity rated weak, developing or strong; scores of 1 or 2 become gaps.