Skip to main content
DORA Enforcement: 17 January 2025

4 DORA documents generated from your codebase

DORA covers ICT risk management, incident reporting, resilience testing and third-party risk. Generate draft documents for each from your codebase instead of building them manually.

Monthly monitoring — €499/month

Monthly DORA ICT-incident delta reports and refreshed compliance packs for EU/UK FinTechs, delivered every 30 days.

What the DORA Audit Pack delivers

1

ICT Risk Management

The problem

Regulated firms must show board-level accountability for ICT risk.

What we find

An ICT Risk Management Framework (Art 5-15) with a board accountability statement, an asset inventory taken from your scanned repositories, and controls grouped by severity.

2

Incident Reporting & Testing

The problem

Major incidents and resilience tests each have to follow a defined process.

What we find

A Major Incident Reporting Protocol (Art 17-23) and a Resilience Testing and TLPT Plan (Art 24-27).

3

Third-Party Risk

The problem

Regulators expect a record of every ICT service provider you depend on.

What we find

A Third-Party ICT Risk Register covering your providers and the risk each one carries.

17 Jan 2025

DORA full enforcement date across EU member states

Your national authority

Which authority supervises you depends on your licence. Confirm with counsel.

4h reporting window

Art 19 major incident initial notification to competent authority

What's in the DORA Pack

4 named documents. Evidence sourced from your GitHub repo scan, never fabricated.

1

ICT Risk Management Framework

Art 5-15

Board accountability statement (Art 5(2)), ICT asset inventory from scanned repos (Art 8), and risk controls bucketed by severity — HIGH/MEDIUM/LOW — with evidence and remediation actions per finding.

2

Major Incident Reporting Protocol

Art 17-23

DORA Art 19-20 mandatory reporting timeline (4h / 72h / 1 month), incident classification table (MAJOR / SIGNIFICANT / MINOR by severity), and incident response policy excerpts. Reporting ladder is always present — not inferred from scanner.

3

Resilience Testing & TLPT Plan

Art 24-27

TIBER-EU aligned TLPT scope (one entry per scanned ICT system), Red Team Charter stub (Art 26(3)), critical vulnerability findings with remediation roadmap, and significant findings for the testing governance record.

4

Third-Party ICT Risk Register

Art 28-44

Named ICT provider register per Art 28(3)(b), criticality assessment for high-severity providers, contractual arrangement excerpts, concentration risk analysis (Art 29), and a data-source note if repo audit is required to populate vendor entries.

No fabricated content

Evidence-sourced, not hallucinated

When evidence is missing — for example, no third-party vendor findings in your scan — the document renders an amber callout: “Evidence not available — questionnaire required.” We never invent ICT controls or risk indicators to fill a page. The DORA Art 19-20 reporting timeline is always present as static regulatory text — not inferred from scanner severity levels.

Cover + 4 DORA documents + Appendix A/B/C · Average 8-12 pages

Common objections

We already have a DORA consultant engaged.

Use the pack to cut their scoping time. Hand them a pre-populated evidence binder instead of a blank questionnaire. Most engagements charge by the hour.

Our CTO says we're not in scope.

If you hold an EMI licence, payment institution authorisation, or investment firm licence in the EU or UK, you are in scope. DORA Art 2 defines scope by licence type, not by company size or tech maturity.

€1,990 is expensive for a document generator.

The pack is not a replacement for a consultant or an assessment — it is the evidence layer you bring to that engagement, so the work starts from your scan findings instead of a blank questionnaire.

We need the TLPT to be TIBER-EU certified.

The pack generates the TLPT Plan and Red Team Charter stub (Art 26(3)). The actual TLPT exercise must be conducted by an accredited provider. The pack tells you what to give them on day one.

AI verifier: Claude Fable 5.1

Each generated document is checked by a second AI model, Anthropic's Claude Fable 5.1, for citation drift and hallucinated claims (Claude Opus 5.5 if Claude Fable 5.1 declines a request; the model that checked your pack is recorded with it). The verifier does not cross-reference against authoritative regulation text bytes and does not replace legal review. Have qualified counsel review before submitting to any regulator (OCR, FCA, BaFin, SEC). Regulatory Signals is an independent technical evaluation provider, not an accredited certification body under ISO/IEC 17065 or ISO/IEC 17021.

Frequently asked questions

When did DORA enforcement start?

DORA (Regulation EU 2022/2554) entered full enforcement on 17 January 2025 across all EU member states. UK equivalents under the FCA's operational resilience framework have been in force since March 2022, with full compliance required from March 2025.

Which regulators enforce DORA for FinTechs?

In the EU: EBA (banking), ESMA (investment firms), EIOPA (insurance), and national competent authorities — including BaFin (Germany), AMF (France), DNB (Netherlands), and CSSF (Luxembourg). In the UK: FCA under operational resilience rules (PS21/3). Most Series A-B FinTechs are in scope if they hold an EMI licence, payment institution authorisation, or investment firm licence.

What are the four DORA documents in this pack?

1. ICT Risk Management Framework (Art 5-15): board accountability, asset inventory, risk controls by severity. 2. Major Incident Reporting Protocol (Art 17-23): classification criteria, the 4h/72h/1-month reporting ladder, competent authority notification procedures. 3. Resilience Testing & TLPT Plan (Art 24-27): TIBER-EU aligned scope, Red Team Charter stub, vulnerability findings. 4. Third-Party ICT Risk Register (Art 28-44): named provider register per Art 28(3)(b), criticality assessment, contractual arrangement excerpts, concentration risk analysis.

How long does it take to generate the DORA pack?

Paste your GitHub repo URL, run the AI scan, then download the 4-document PDF. You complete the compliance questionnaire to fill any amber 'evidence not available' sections.

Is the €1,990 pack a replacement for a DORA consultant?

No — and we say so explicitly in the document. The pack generates documents structured by DORA article, with evidence from your codebase, so you spend less time on questionnaire prep. Most FinTechs use it to cut the scoping phase of a DORA engagement from weeks to days.

Your regulator isn't waiting

DORA enforcement started January 2025. €1,990 one-time · €499/month optional monitoring (subscribe above) · regulatory change alerts.

This document is an automated compliance analysis. It does not constitute legal advice. Review with qualified DORA counsel before regulatory submission.

Where to go next

EU AI Act Compliance

EU AI Act risk checks, reports, audit pack, and policies — one program.

Free to startStart Free Check
AI-built Code Audit

AI-generated codebase audit — Claude, Codex, Gemini, Cursor, Copilot, Lovable.

Free to startRun Free Scan
Website Privacy

Free website compliance scan, paid report, and daily regulatory feed.

Free to startStart Free Scan