> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/trust-center/legal/dora-compliance.md).

# DORA Compliance Package

{% hint style="info" %}
🇩🇪 [Diese Seite auf Deutsch lesen (DORA Compliance‑Paket)](https://docs.ilert.com/trust-center/deutsche-versionen/dora-compliance-paket.md)
{% endhint %}

{% hint style="info" %}
**Version 1.2 · valid from 9 November 2026** · [Versions and changes](https://docs.ilert.com/trust-center/legal/versions/dora-compliance.md)
{% endhint %}

**Last updated: 2026‑11‑09**

## 1 Introduction

**ilert GmbH** is a B2B SaaS provider of incident management and alerting solutions. This document is a self‑contained dossier demonstrating ilert GmbH’s alignment with **Regulation (EU) 2022/2554 on Digital Operational Resilience for the Financial Sector ("DORA"**). It is intended for EU financial entities (banks, insurers, investment firms, PSPs, etc.) and their ICT third‑party service providers that rely on ilert’s SaaS platform. ilert reviews and, where necessary, revises this package at least annually and whenever new regulatory guidance is issued.

### Key Facts

| Topic                  | Statement                                                                                                               |
| ---------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| Legal status           | GmbH (German **private limited‑liability company**)                                                                     |
| Senior accountability  | **CEO** is executive owner of digital resilience; **CTO** leads the ISO 27001 ISMS and reports quarterly to management. |
| Data hosting           | **Active/active AWS eu‑central‑1 (Frankfurt)** & **eu‑north‑1 (Stockholm)**                                             |
| Certifications         | ISO/IEC 27001:2022 (scope: SaaS platform + support scope)                                                               |
| DORA “critical” status | Not designated as critical ICT third‑party                                                                              |
| GDPR                   | Data Processor under Art. 28; [DPA](https://docs.ilert.com/trust-center/legal/data-processing-agreement.md)             |
| Continuous improvement | This package is reviewed at least annually; regulatory monitoring performed monthly                                     |

This package concisely maps ilert’s controls to the **core obligations for third‑party ICT service providers** under DORA. It is **uniform** for all customers and suitable for inclusion in due‑diligence files.

## 2 Compliance with Core DORA Requirements

| DORA Theme                                               | ilert Control Summaries                                                                                                                                                                                                                                                                                                                       |
| -------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **ICT risk management & governance** (Arts. 5‑6)         | ISO 27001 ISMS; quarterly KPI review by management; annual risk assessment.                                                                                                                                                                                                                                                                   |
| **Incident detection & reporting** (Arts. 10‑11)         | 24×7 monitoring & on‑call SRE; “Major ICT Incident” = Art. 3(10) DORA. Customer notice ≤ 4 h after confirming a Major ICT Incident, with nature, impact, mitigation. Updates at least every 4 h until resolved, also on <https://status.ilert.com>; preliminary report within 5 and final report within 20 business days of incident closure. |
| **Digital operational‑resilience testing** (Arts. 24‑27) | Annual external penetration test; quarterly vulnerability scans; full cooperation in client‑led TLPT & cyber exercises.                                                                                                                                                                                                                       |
| **Information sharing** (Art. 45)                        | Critical threat advisories forwarded to customers within 24 h.                                                                                                                                                                                                                                                                                |
| **Third‑party contractual clauses** (Art. 30)            | Standard **DORA Addendum**: audit & access; subcontractor conditions; security & training participation; TLPT cooperation; material‑developments notice; exit & transition.                                                                                                                                                                   |
| **Business continuity & DR** (Arts. 11‑12)               | **Active/active Frankfurt + Stockholm**; RPO ≤ 15 min & RTO ≤ 60 min; quarterly fail‑over tests.                                                                                                                                                                                                                                              |

## 3 Allocation of Responsibilities

| Area              | ilert (Vendor)                                                                                                                                                                                                                                                                                      | Financial‑entity Customer                   |
| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------- |
| Risk management   | Operate ISO 27001 ISMS                                                                                                                                                                                                                                                                              | Assess ilert via vendor‑risk programme      |
| Incident handling | Detect → contain → notify ≤ 4 h after confirming a Major ICT Incident; assist with RCA & regulator queries                                                                                                                                                                                          | Classify impact, file DORA incident reports |
| Audits            | Provide ISO certificate & pen‑test summary; 1 audit per contract year: remote free of charge (10 business days’ notice), on‑site at agreed cost (30 days’ notice)                                                                                                                                   | Initiate & evaluate audits                  |
| Exit plan         | Transition period under clause 18.3 of the ToS: up to 30 days, extendable once, charged pro rata; full export (JSON) within 5 business days; then 30 days to retrieve data; erasure incl. backups within 90 days after the end of the contract or of the transition period (ToS clauses 18.4, 18.5) | Maintain contingency / migration plan       |

## 4 Key Measures Ensuring Ongoing Compliance

1. **Security & Governance**
   * MFA enforced; encryption in transit (TLS 1.2+) & at rest (AWS KMS).
   * Quarterly security awareness training for all staff.
2. **Incident Response & Notification**
   * Dedicated on‑call team with automatic escalation; **initial notification by email/API/SMS** within 4 h of confirming a Major ICT Incident and continuing updates via <https://status.ilert.com> (public status page). A live conference bridge is opened for priority‑1 incidents upon customer request.
   * Assistance during incidents (forensic data, logs, statements).
3. **Business Continuity & Disaster Recovery**
   * **Active/active architecture across AWS eu‑central‑1 (Frankfurt) and eu‑north‑1 (Stockholm)**; automated multi‑region replication; quarterly fail‑over tests.
4. **Risk Assessments & Audits**
   * Annual ISO surveillance audit.
   * Customer audits: one per contract year, plus after a Major ICT Incident, on a regulator’s demand or on a reasonable suspicion of a material breach of the Addendum; remote audits with 10 business days’ notice, free of charge; on‑site audits with 30 days’ notice.
   * Audits by competent authorities: no limits on frequency or notice.

## 5 Supporting Documentation (Available on Request)

| Document                    | Purpose                              |
| --------------------------- | ------------------------------------ |
| ISO 27001 Certificate       | Independent verification of ISMS     |
| Information‑Security Policy | Detailed control descriptions        |
| Incident‑Response Plan      | Process, roles, templates            |
| BCP/DR Plan                 | Recovery architecture & test results |
| Pen‑Test Executive Summary  | Latest external test outcomes        |
| Sub‑processor List          | Names, roles, data‑location          |

***

> **Contact:** <compliance@ilert.com> © 2026 ilert GmbH – All rights reserved


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ilert.com/trust-center/legal/dora-compliance.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
