Agentic compliance for DORA

DORA, from the ICT risk framework to a complete register of information.

GetTeddy's agents check every ICT contract against Art. 30, keep the register of information current and map the rest onto your controls. A compliance engineer helps you prepare for supervisory audits.

  • Every ICT contract checked against Art. 30
  • Register of information from your contracts
  • Hosting in the EU, Germany or US

Reviewed by Sven Moritz, former CISO · October 2026

Backed byAntlerHosting in the EU, Germany or USShaped with our CISO Panel

What DORA asks for

DORA is an EU regulation and applies directly to banks, insurers, investment firms, payment and e-money institutions, crypto-asset service providers and other financial entities, with proportionate rules for smaller ones.

Show the six obligations
Art. 5 to 16ICT risk management framework

Strategies, policies and tools to protect ICT systems, detect anomalies, respond, recover and learn. Some smaller entities can apply a simplified framework under Art. 16.

In GetTeddyMapped onto your existing ISMS controls
Art. 5(2) and 5(4)Management body

The management body defines, approves and oversees the ICT risk framework, bears ultimate responsibility and keeps its knowledge current through regular training.

In GetTeddyDecisions and training records for management
Art. 17 to 23Incident classification and reporting

Classify ICT-related incidents with the EU criteria. For major incidents: an initial notification within 4 hours of classification and no later than 24 hours after becoming aware, then an intermediate and a final report.

In GetTeddyClassification checklist and report templates
Art. 24 to 27Resilience testing

A testing programme in which systems that support critical or important functions are tested at least yearly. Entities identified by the authority also run threat-led penetration testing at least every three years.

In GetTeddyTest plan and results linked to controls
Art. 28 and 30ICT third-party risk and contracts

A third-party risk strategy and ICT contracts with the provisions of Art. 30, with stricter ones where a service supports critical or important functions.

In GetTeddyContract Agent checks every ICT contract
Art. 28(3)Register of information

A register of all contractual arrangements for ICT services, at entity and group level, in the EU templates and available to the competent authority on request.

In GetTeddyBuilt from your contracts and kept current
At least yearlyFramework reviewICT risk management framework
Per major incidentReportingInitial, intermediate, final
At least yearlyTestingSystems for critical or important functions
Every three yearsThreat-led testingFor identified entities

Map once. Comply everywhere.
Run easy.

DORA's ICT risk framework overlaps with what you already run for ISO 27001 or NIS2. GetTeddy keeps one control set for all of them and shows only what DORA adds.

How it works

A DORA program you
can show the supervisor

GetTeddy's agents map the requirements, read the contracts and keep the register current. Legal and management decide, and a compliance engineer helps you prepare for supervisory audits.

01
Gap Audit Agent

Scope and proportionality per entity

GetTeddy works out which DORA rules apply to each entity in your group and whether the simplified framework under Art. 16 is an option.

DORA scope · Acme GroupDraft
Acme Payments · payment institutionIn scope
Simplified framework (Art. 16)Not applicable
Threat-led testing (Art. 26)Not identified
Teddy: The competent authority decides on threat-led testing. I will flag it if that changes.
02
Gap Audit Agent

ICT risk framework on your existing controls

Requirements from Art. 5 to 16 are mapped onto the controls you already run for ISO 27001 or NIS2. You see what is covered and what DORA adds.

Chapter IIICT risk management
Requirements covered by existing controls78%
Art. 11 · Response and recovery plansPartial
Art. 12 · Backup and restorationCovered
03
Contract Agent

Every ICT contract against Art. 30

The Contract Agent reads each contract, marks whether the service supports a critical or important function and checks the provisions that apply.

Granite Data ServicesPayment gateway
Supports a critical functionYes
Data locations · Art. 30(2)(b)Stated
Exit strategy · Art. 30(3)(f)Missing
Teddy: I drafted an exit clause from your template. Legal decides what goes to Granite.
04
Contract Agent

A register that stays current

The register of information is filled from the contracts themselves. New or changed contracts update the draft, and nothing is final before you approve it.

Register of informationEU templates
Contractual arrangements412
Linked to functionsComplete
Fields still missing23
Teddy: A new contract was signed yesterday. I added it to the register draft for your approval.
05
Policy Agent

Incident classification and reporting

The Policy Agent drafts the classification checklist and the report templates, linked to your incident response, so the clock never surprises you.

Major incident reportingArt. 19
Classification checklistApproved
Initial notification · 4 hoursTemplate ready
Intermediate report · 72 hoursTemplate ready
Final report · one monthTemplate ready

How long DORA takes

TypicalTwo years, and counting

Institutions had a two-year window, and many still did not finish. Before the deadline, fewer than half were confident they would make it, and over a third planned full compliance only for 2026.

With GetTeddyAgents do the groundwork

Register of information built from your contracts, every ICT contract checked against Art. 30 and the gaps listed with owners. After that, GetTeddy keeps the register current all year.

  • Register of information: submitted every year in March. In Germany, the 2026 window ran from 9 to 30 March.
  • What BaFin saw in year one: more than 600 major ICT incidents reported. Most institutions using critical providers said those services would be hard to bring back in-house.
  • Supervisory focus 2026: ICT third-party risk management and incident reporting, the part of DORA practitioners rate as hardest.
The problem

Where DORA projects
get stuck

DORA turned supplier management into a regulatory duty. Every ICT contract needs specific provisions, and the register of information has to be complete and current.

01
Older IT contracts

The Contract Agent lists missing clauses and suggests wording.

02
The register of IT providers

GetTeddy fills it in the official EU format from your contracts and supplier list.

03
Is this a major incident

Clear criteria and owners decide quickly whether an incident must be reported.

04
400 contracts, a register in Excel and a supervisor asking. Still no answer.

Legal holds the contracts, procurement holds the supplier list, and the register lives in a workbook with broken links. GetTeddy's Contract Agent reads every ICT contract, flags missing provisions and fills the register from the source.

SMSven MoritzCo-founder of GetTeddy, former CISOLast reviewed: October 2026
From the audit room

Where DORA programs fall short

  1. The contracts are older than DORA.

    Many existing ICT contracts still lack the Art. 30 minimum clauses, and many agreements have no exit plan at all.

  2. The exit plan exists on paper only.

    Supervisors ask for credible, tested exit strategies for critical or important functions. With critical cloud providers that is hard, and most institutions know it.

  3. The register is filled once a year, in March.

    It has to reflect every contract signed or ended during the year, including tools teams bought on their own. Treat it as a living inventory you update all year.

Why teams start with GetTeddy

The same result, without months of spreadsheets and consultant hours.

Consultants and spreadsheetsGetTeddy
Contract reviewClause by clause by handChecked by the Contract Agent
Register of informationSpreadsheet maintained by handBuilt from your contracts
EvidenceCollected by handCollected continuously
ISO 27001 or NIS2Separate projectsBuilt on the same controls
OngoingYearly reviewGap audits every week

GetTeddy at a glance

GetTeddy is a compliance platform by Teddy Technologies GmbH, based in Berlin, built for start-ups and mid-sized companies. The platform runs in the region you choose: EU, Germany or US, in line with GDPR. Start-ups and Antler portfolio companies get special terms.

FAQ

Questions about DORA

Does DORA apply to ICT providers too?

DORA applies directly to financial entities. ICT providers feel it through their contracts, because financial entities must include the Art. 30 provisions. Providers designated as critical are also overseen directly by the European Supervisory Authorities.

We have ISO 27001. How much counts?

Much of the ICT risk management framework. DORA adds incident classification and reporting deadlines, resilience testing, specific contract provisions and the register of information.

Do you support us with supervisory requests?

Yes. A compliance engineer helps with supervisory requests, register submissions and audits, and prepares the evidence with you.

What is the difference between Art. 30(2) and 30(3)?

Art. 30(2) lists provisions every ICT contract needs, such as data locations, service levels and termination rights. Art. 30(3) adds stricter ones for services that support critical or important functions, such as exit strategies and full audit rights.

Do we need threat-led penetration testing?

Only if your competent authority identifies you for it. Every entity needs a testing programme, and systems that support critical or important functions are tested at least yearly.

Where is our data hosted?

In the region you choose: the EU, Germany or the US. Each customer's data is kept separate and encrypted. GetTeddy connects read-only by default and does not train on customer data. Details are on our security page.

By industry DORA for banks and financial firms · DORA for FinTechs · DORA and AI pricing for insurers · Rules by industry

Your DORA program,
built from your contracts and your controls.

See it on your own contracts in a 30-minute demo.

  • Backed by Antler
  • Hosting in the EU, Germany or US
  • Compliance engineer included