DORA compliance
Your DORA compliance gap will not close itself.
First result within 24 hours.
If you are a financial entity, or a critical ICT provider to one, you need operational resilience you can show: ICT risk, incident handling, testing, and third-party oversight.
Recognize your situation?
- The register of ICT providers is incomplete or stale
- Testing of resilience is irregular or only theoretical
- Incident classification and reporting would be invented under pressure
One free session per client: the first 4 hours with a specialist, plus unlimited AI as a tool.
The problem
What DORA compliance looks like, how you can tell, and what is at stake if it stays.
Signs you have a DORA compliance gap, not only a pending workshop
These are concrete signals that operational resilience is not yet something you can show.
The register of ICT providers is incomplete or stale
You cannot honestly say who is critical, or how you would replace them.
Testing of resilience is irregular or only theoretical
A desktop comment is not a test of a path the business needs.
Incident classification and reporting would be invented under pressure
Informal stories will not survive a supervisory or client clock.
Contracts do not match how the service actually runs
The paper describes a world the operators do not live in.
A client due-diligence questionnaire already exposed the thin spots
You delayed, or you answered more confidently than the estate allows.
What DORA compliance looks like
What a DORA gap looks like in ICT risk and third parties, how it feels to stitch screenshots for evidence, and why paper that does not match the estate is not resilience.
A DORA compliance gap is an operational-resilience problem for financial entities and critical ICT providers: incomplete provider registers, irregular testing, informal incident classification, and contracts that do not match how the service actually runs.
DORA arrived as a dense text while teams were already busy keeping systems up. Being late to a structured gap analysis is common, and it is still urgent. The first serious test should not be a real outage or a supervisor's letter.
Registers, testing and incident paths are informal
Registers of ICT providers are incomplete, testing is irregular, incident classification is informal, and contracts do not match how the service actually runs.
You are stitching evidence you do not trust
You are being asked for DORA evidence and you are stitching screenshots. You do not want the first serious test to be a real outage or a supervisor's letter.
Resilience is whether you can still serve clients when ICT fails
Operational resilience is whether you can still serve clients when ICT fails. Paper that does not match the estate is not resilience.
If you leave it, and if we close the urgent gaps
If you leave it
If the gap stays, you can fail a customer due-diligence, miss a reporting duty, or find during an incident that a critical provider was never really overseen.
If we close it
You get a plain map of the DORA-shaped gaps that matter in your setup, and the first practical fixes that fit the session.
Recognize your situation?Message us, we will sort it out.
Why it happens
Where this usually comes from, why it shows up in fast or AI-assisted work, and how to check it yourself.
Why DORA work stays on the to-do list
The text is dense, and the estate is busy. The gap still has a clock.
- 01
The duty was treated as legal reading, not as operations
A memo circulated. ICT risk, testing, and providers did not change.
- 02
Provider inventories lived in procurement, not in resilience
The two lists never met.
- 03
Testing was postponed because it is disruptive
So the first serious test remains the next real outage.
- 04
Incident processes were built for IT tickets, not for DORA-shaped clocks
Classification and reporting were never designed.
- 05
A programme was planned at a scale that never started
While a smaller, honest gap map could have begun.
Why DORA gaps are being felt now
The regulation made operational resilience a duty you have to show, not a slogan. Lean teams cannot invent registers, tests and reporting in a weekend, even with an assistant drafting text. The honest work is a human map of ICT risk, incidents, testing and third parties as they really are, then the first fixes that change the estate.
How to start a DORA gap picture yourself
These checks do not replace a specialist, but they make the first conversation sharper.
List ICT providers you would struggle to replace in a week
If the list is hard to write, that is a finding.
Find the last resilience test that actually ran
Date, scope, and whether a real path was exercised.
Read one critical contract against how the service runs
Mismatches are in-scope findings.
Ask who would classify and report a serious ICT incident
Names, times, and templates — or the lack of them.
Gather the last client due-diligence you found uncomfortable
Those questions are a preview.
0/ 5
Recognize your situation?Message us, we will sort it out.
How Contentum fixes it
A senior specialist leads. AI is a tool. A human checks the result.
DORA arrived as a dense text while teams were already busy keeping systems up. Being late to a structured gap analysis is common, and it is still urgent.
Contentum is Human First. A specialist leads DORA-gap work. AI may help us organise inventories. A human writes what actually applies. We do not sell a supervisory approval, and a session is not an official examination.
You need a plain picture of ICT risk, incident handling, testing and third-party oversight as they really are, then the first practical fixes. We do not sell a supervisory approval, and a session is not an official examination.
How a typical weekday case moves
- 01Message received
- 02Specialist named
- 03Diagnosis
- 04Fix
- 05Human check
- 06Handover
How to get a human onto a DORA gap
No web form, no web chat. We do not sell a supervisory approval, and a session is not an official examination.
Write about the duty and the thin spots
Write on WhatsApp or Telegram. Say whether you are an entity or a provider, who is asking, and which of registers, testing, incidents or contracts already worry you.
You get a specialist's name
Within a minute you should see the name of the person who will lead. That specialist is alerted, and can be called if they do not respond.
A weekday case in scope is the 24-hour aim
A plain gap map and first practical fixes is the aim on a typical weekday. A full DORA programme is a complex project, and we will say so.
How a Contentum specialist works a DORA gap
We start with ICT risk, incidents, testing and third parties as they really are, then close what we can in scope.
We start with ICT risk, incidents, testing and third parties as they really are, then close what we can in scope. A full DORA programme is a complex project; the 24-hour aim is a typical weekday case.
- 01
Build an honest picture of role and scope
Entity or provider, and what that means for you, including remaining doubt.
- 02
Map registers, testing, incidents and contracts against reality
The mismatches are the work.
- 03
Close a first practical gap the session can reach
A missing owner, a stale register, a test that can be scheduled, a reporting path.
- 04
Write evidence so it can be found again
Not a one-off screenshot pile.
- 05
Leave the full programme as a programme
We will not pretend a session is a supervisory examination.
What to send so the first session is sharp
You do not need a finished legal memo. Honest fragments help.
Whether you are a financial entity, a provider, or still unsure
Say so.
Any existing register, policy, or consultant note
Even a draft.
Recent incidents or tests
Dates and short descriptions.
Important ICT providers and contracts you already worry about
A short list is enough.
Who is asking — supervisor, client, or board
That context changes the first output.
Quick and urgent fixes
First 4 hours with a specialist + unlimited AI: free, once per client. Further work is paid, on request. A human leads and checks the result.
Free (first session)
Complex projects
Larger work uses a different rate, on request. We say so before we continue.
On request
Weekdays, then weekends
The base plan is weekdays only. Weekend work is a separate product. Any surcharge is stated up front, before any call, and depends on complexity. Amount: on request.
On request
The first session is free: the first 4 hours with a specialist, plus unlimited AI, once per client. Work beyond that, the complex-project rate, and the weekend rate are paid, on request.
One free session per client: the first 4 hours with a specialist, plus unlimited AI as a tool.
Stay fixed
What not to do next, the stacks we see in this kind of work, and how to keep the fix in place.
Mistakes that waste a DORA programme
These are common when the text is treated as a reading list.
Drafting policies and skipping tests
Resilience you have not exercised is a claim.
Keeping provider lists only in procurement
Resilience has to own the same list.
Answering client questionnaires more confidently than the estate allows
The next incident will make that sentence expensive.
Waiting for a huge programme before fixing an obvious gap
A stale register can start now.
Asking us to certify you to a supervisor
We will not. We will tell you what official routes involve.
How to keep DORA work alive after the first map
A gap analysis that does not change operations will rot.
Keep the provider register living, with an owner
A yearly export is not a register.
Put tests on a calendar you protect
Cancelled tests are a postponed outage.
Classify and record incidents in the same rhythm you would need to report
Do not invent the muscle in a real event.
Review contracts when the service changes, not only at renewal
Drift is a finding.
Use client due-diligence as a health check
Uncomfortable questions are useful.
Budget the full programme honestly
The first session is a start, not the end of the duty.
Where DORA-shaped gaps usually land
The duty is organisational. The holes still sit in ICT you can name.
Critical business applications and their hosting
Including cloud.
Identity, payments-adjacent and messaging paths
Where an ICT failure becomes a client failure.
ICT third parties and outsourcing
The register, the contract, and the real service.
Incident and testing evidence
Classification, clocks, and what was actually run.
Reporting paths
Who would write, who would send, and how fast.
Recognize your situation?Message us, we will sort it out.
Questions about a DORA compliance gap
Straight answers about this problem, the session, and what happens next.
Do you approve us for DORA?
No. We help you see and close practical gaps. We do not sell a supervisory approval, and a session is not an official examination.
We are a provider, not a bank. Is this still relevant?
It can be, if you are a critical or important ICT provider to a financial entity. Tell us how you sit in the chain. We will not invent a scope.
Is DORA the same as NIS2 or ISO 27001?
No. They can support each other. They are not the same duty. See those pages if they also apply.
Will you invent a legal opinion?
No. We may say you should involve counsel. We will not pretend a session is legal advice.
What do I get within 24 hours?
A first result: a gap assessment and a plan you can act on, on a typical weekday in agreed scope. A finished programme — a full SOC, a certificate, or a rebuilt estate — is later work, and we will say so. The first 4 hours with a specialist, plus unlimited AI as a tool, are free, once per client.
Do I fill in a form?
No. There is no web form and no web chat. Write on WhatsApp or Telegram. Within a minute you should see the specialist's name.
Will you publish findings?
No. This is a private service conversation, not a public write-up.
What is free?
You get one free session per client: the first 4 hours with a specialist, plus unlimited AI as a tool. Further work is paid, on request.
Do you take emergency work during an active attack?
Yes. If you are under an active attack, write now on WhatsApp or Telegram and say so in the first message. A specialist is alerted, and can be called. Keep your own incident plan running in parallel — two paths are safer than waiting. We start as soon as we can on a typical weekday case in scope. We do not promise to stop every attack in a day, but we do take this work.
What is free, and what does “within 24 hours” mean?
You get one free session per client: the first 4 hours with a specialist, plus unlimited AI as a tool. On a typical weekday, for a case in agreed scope, we aim to give you a first result within 24 hours: a gap assessment and a plan. On urgent, in-scope fixes we often close the job itself in that window. That 24-hour line is a speed aim, not 24 hours of unpaid work, and not a promise to finish a large programme in a day.
Related security problems we also take on.
See all 20 problems. Each page is written for one pain, not as a copy of this one.
Need urgent help, fast?
If you have a deadline or an incident in motion, these Help Hub topics are a closer match.
Your DORA compliance gap will not close itself. First result within 24 hours.
Write on WhatsApp or Telegram. You will talk to a person. We aim to give you a first result within 24 hours — a gap assessment and a plan — a gap map and first fixes, not a supervisory approval in a day.
One free session per client: the first 4 hours with a specialist, plus unlimited AI as a tool.