Digital Operational Resilience Act
DORA Compliance Audit
Article 6(6) of DORA requires your ICT risk management framework to be audited regularly by auditors with sufficient knowledge, skills and expertise in ICT risk. We carry out that audit, and on request the other pillars, against DORA and its technical standards, so your internal audit plan and your supervisor have the evidence they expect.
WHY YOU NEED THE AUDIT
DORA expects the framework to be audited
Article 6(6) asks for regular internal audit of the ICT risk management framework, and Article 6(7) for a formal follow-up of the findings.
The problem
Internal audit may lack ICT depth
DORA asks for auditors with sufficient expertise in ICT risk; many audit functions need that expertise for the first cycles.
- Supervisors review DORA compliance in their inspections
- Technical standards add detail beyond the regulation
- Findings need a formal follow-up process
The solution
An audit against DORA and its standards
We audit the framework and, on request, the other pillars, mapping every test to the article or technical standard it covers.
- Scope matched to your entity and proportionality
- Every test mapped to DORA and its standards
- Findings ready for your follow-up process
The outcome
Evidence for the audit committee and the supervisor
Your audit plan is covered, and you can show the supervisor an independent audit with tracked follow-up.
- Report for the audit committee
- Findings tracked to closure
- Input for the next audit cycle
Does a requirement ask for it?
What asks for it in Romania
We scope the work to what your requirement asks for, so the result serves that audit or supervisor too.
What we check
What we audit
For each requirement we review the evidence and check that the control works, so you know exactly where you stand.
ICT risk management framework
Governance under Article 5, the framework of Articles 6 to 15 and RTS 2024/1774, or the simplified framework of Article 16 where it applies.
Incidents and testing
Classification and reporting under Articles 17 to 19 and the reporting standards, and your resilience testing programme.
ICT third-party risk
Your strategy, contracts and register of information against Articles 28 to 30 and the register standard.
Each finding with a recommendation
Every gap comes with its risk, the article or standard concerned and a practical recommendation.
HOW THE AUDIT RUNS
From scoping to audit report
The phases follow internal audit standards; their length follows the entities and pillars in scope, and your proposal gives the dates.
-
Scoping
Scoping
Entities, pillars and proportionality in scope, agreed with your head of internal audit.
-
Evidence
Documents
The framework, policies, registers, incident and test records.
-
Testing
Interviews and testing
Sessions with the first and second line and tests of the controls on evidence.
-
Findings
Draft findings
You see every conclusion before it is final and can add evidence.
-
Report
Audit report
The report for your audit committee and supervisor.
A guide, not a fixed promise: the length of each phase depends on your scope and on how quickly evidence and people are available.
WHEN TO START
Plan the audit into DORA's yearly cycle
Your ICT risk management framework is reviewed every year and audited on your audit plan, and the register of information goes to your authority once a year.
-
Every year
Review the framework
The ICT risk management framework is reviewed at least once a year and after major incidents or supervisory findings.
-
Q1 each year
Submit the register of information
In 2026 national authorities collected registers between February and March and passed them to the ESAs in April; your authority sets the date.
-
Audit plan
Audit the framework
Internal audit on the cycle of your audit plan, with a formal follow-up of the findings.
-
Every 3 years
Threat-led penetration testing
For entities your authority identifies: a TLPT at least every three years.
Based on DORA Articles 6(5), 6(6), 26 and 28(3), and the 2026 register notices of national authorities. Confirm your dates with your authority.
YOUR DORA AUDIT
Cover DORA in this year's audit plan
Tell us your entity type and the pillars in scope. We send a written proposal with scope, dates and a fixed fee within two working days.
WORKING WITH US
What it takes from your side
Your team's time, how quickly we start, and how the work is organised.
From your go-ahead to kick-off
We start within days, timed to your audit plan.
No travel costs
Interviews and evidence by video call; on-site days only when you want them.
With your internal audit
We can work under your audit methodology and alongside your own auditors.
Delivered Work on the Same Topic
Clients are described, never named.
What you receive
The audit report
Scope, method and a conclusion for each area, mapped to DORA and its technical standards.
Findings and recommendations
Each gap with its risk, the article concerned and a practical recommendation, ready for follow-up.
Excel finding list
A DORA control mapping
Every test linked to its article or standard, for your next audit cycles.
Excel mapping
A briefing for the audit committee
The result and the decisions needed.
Presentation and a closing call
Why financial entities choose GRC+ for DORA
ICT risk expertise, as Article 6(6) asks
Audits are led by an auditor who holds CISA, CRISC and CISSP.
Regulation and standards together
Every test covers the article and its technical standards, so nothing is audited against the regulation alone.
Proportionate
We scope the audit to your size and risk profile, including the simplified framework where it applies.
One audit, more frameworks
Our mappings link DORA to ISO 27001, NIS2 and Swift CSP, so the evidence serves those audits too.
Credentials
Who does the work
Certified practitioners
Every engagement is led by a senior, certified practitioner.
25+
years in regulated sectors
Banks, insurers, payments, healthcare and the public sector across the globe.
Insured
Professional indemnity cover on every engagement.
FAQ
DORA compliance audit: frequently asked questions
Something else? Ask us in a 30-minute call.
What does the audit cost?
A fixed fee, set in your written proposal before any work starts. It follows the entities, systems and sections in scope.
Who may audit the ICT risk management framework?
Article 6(6) asks for auditors with sufficient knowledge, skills and expertise in ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. and appropriate independence. Your internal audit function can carry out the audit itself or bring in external auditors who meet that standard.
Do you audit the register of information?
Yes. We check your register against the implementing standard on the register of informationThe register that financial entities must maintain and update under DORA Article 28(3), covering all contractual arrangements for ICT services provided by ICT third-party service providers. Competent authorities collect the registers, and the ESAs use them to designate critical providers. and your contracts against Article 30.
Want to know more about DORA?
Our guide to DORA explains who it applies to, what it requires, the deadlines and what happens if you do not comply. Digital Operational Resilience Act (DORA) →
Plan your DORA audit
Tell us your entity type, the pillars in scope and your audit plan dates. We send a written proposal with scope, dates and a fixed fee. sales@grc.plus +31 20 241 66 00
Related: DORA Gap RemediationRed TeamingVendor Risk Management
