How to manage GDPR, NIS2 and DORA at once — without hiring a compliance team

Yes, you can cover GDPR, NIS2 and DORA without a compliance department — but only if you stop treating them as three projects. The three laws ask for largely the same things: know your data and systems, control access, log what happens, manage suppliers, and prove it all works. Run them as one control set with one evidence chain, and the workload is closer to one regulation than three. Euraika builds tools for exactly this: one platform that maps requirements across 30 frameworks, so a control you implement once satisfies every law it covers.
What do the three laws actually ask for?
Start from the texts, not from vendor marketing. Regulation (EU) 2016/679 (GDPR) has applied since 25 May 2018 and governs personal data: a lawful basis, records of processing, security of processing, breach notification. Directive (EU) 2022/2555 (NIS2) sets a cybersecurity baseline for essential and important entities — risk management measures, incident reporting, management accountability. Regulation (EU) 2022/2554 (DORA) has applied to EU financial entities since 17 January 2025 and adds operational resilience: ICT risk management, incident reporting, third-party risk, and digital operational resilience testing.
Put their requirement lists side by side and the overlap is obvious. Access control, asset inventory, supplier oversight, incident handling and audit logging appear in all three. The differences are mostly of emphasis and threshold — GDPR asks why you process personal data, NIS2 asks how you secure it, DORA asks whether your ICT can survive an incident.
Which controls satisfy more than one law?
Map each control to every framework it serves before you implement anything. A single access-control policy — least privilege, MFA, joiner-mover-leaver process — serves GDPR Art. 32, NIS2 Art. 21 and DORA Art. 9 at once. An ICT asset inventory serves NIS2's risk-management measures and DORA's ICT risk-management framework, and it is where GDPR's records of processing start. Supplier due diligence is one process under three names: GDPR Art. 28 processor agreements, NIS2 supply-chain security, DORA Arts. 28–30 third-party risk.
The same goes for evidence. An access review, a penetration-test report, a supplier register entry: each artefact feeds all three regimes. The mistake to avoid is collecting it three times in three formats — once for the DPO, once for the NIS2 auditor, once for the financial regulator. Collect once, tag by control, and every audience gets its own view of the same evidence.
How do you run it with a small team?
Practically, the sequence that works without a dedicated compliance department:
- One owner, not three. Someone owns "compliance" as a whole — even at 20% of their time — so GDPR, NIS2 and DORA aren't three silos reporting to three people.
- One control framework as the spine. A recognised baseline such as ISO 27001 or, in Belgium, the CyberFundamentals Framework (CyFun) covers most technical measures; each regulation then maps onto that spine instead of getting its own checklist.
- Evidence collection in the daily workflow. Reviews, approvals and test results land in one place as they happen, not reconstructed the week before an audit. Continuous evidence is what makes three regimes tractable for a small team.
- One incident process. GDPR gives you 72 hours to notify a personal-data breach; NIS2 and DORA have their own reporting clocks. One detection-to-notification runbook with the shortest clock as the default keeps you inside all of them.
What falls over when teams try to do it manually?
Spreadsheets. Not because spreadsheets are bad at holding information, but because they are bad at proving it is current. Every regime above asks you to demonstrate that controls work at any moment — the Belgian NIS2 law, for instance, subjects essential entities to a regular conformity assessment (Art. 39) and lets inspectors demand evidence that the measures are implemented, including through ad hoc audits (Art. 48). A static file cannot do that; it only shows a snapshot that may already be stale.
The second failure mode is duplicated effort: the same control implemented once per regulation, because nobody did the mapping. That is where the "without a compliance team" ambition dies — not in the difficulty of any single law, but in doing the same work three times.
How does tooling change the equation?
Tooling earns its keep at exactly two points: the mapping and the evidence. A platform that keeps the cross-framework mappings for you — control X satisfies GDPR Art. 32, NIS2 Art. 21 and DORA Art. 9 — removes the work that only compliance specialists can do. And a platform that collects evidence continuously, with a tamper-proof trail and an auditor-facing view, replaces the spreadsheet scramble. Euraika GRC was built for European organisations in exactly this situation: 30 frameworks with cross-framework mappings, EU-hosted, single-tenant, and an auditor portal so the regulator's questions never turn into a fire drill.
Frequently asked questions
Do all three laws apply to my organisation?
Check each scope separately — they differ. GDPR applies to any organisation processing personal data of EU residents. NIS2 applies to essential and important entities listed by each member state; in Belgium, the NIS2 law of 26 April 2024 defines the scope. DORA applies to financial entities such as banks, insurers and investment firms, and reaches their critical ICT providers through its oversight framework; for a financial entity in its scope, DORA's ICT rules replace NIS2's risk-management and reporting duties (NIS2 Art. 4, DORA Art. 1(2)). All three therefore meet mostly in groups that combine financial and non-financial entities.
Is a DPO a compliance team?
No. A DPO advises and monitors (GDPR Art. 39); they do not implement controls. Many organisations covered by all three regimes run on one compliance owner plus tooling, and designate or outsource the DPO role as required.
Where do I start if I have done nothing yet?
With the shared spine: asset inventory, access control, supplier register, incident runbook. Those four cover the largest share of overlapping requirements across GDPR, NIS2 and DORA and are useful even if one of the three turns out not to apply to you.


