DORA · European Union

DORA logging requirements, RTS Article 12, clause by clause.

What the Digital Operational Resilience Act and its ICT risk-management RTS ask of your logs, in plain English, and how a SIEM you run on infrastructure you choose covers each line, without your logs ever reaching nano.

Buy nano
Talk to sales
Who's in scope

Which rules apply to you.

DORA sets the obligations; Commission delegated and implementing regulations spell out the detail. Because DORA is a regulation, the text is the same in every Member State.

DORA · Art. 2

Twenty types of financial entity.

Credit institutions, payment and e-money institutions, investment firms, crypto-asset service providers, market infrastructures, fund managers, insurers, pension institutions, credit rating agencies and more. Some small entities are excluded (Art. 2(3)).

Regulation (EU) 2022/2554 ↗
RTS 2024/1774 · Titles II and III

Full framework, or the simplified one.

Most entities follow Title II, where Article 12 sets the logging rules. Smaller entities under DORA Article 16 follow the simplified framework in Title III, which still requires logging of access control, ICT operations, network traffic and change events (Art. 34(f)).

Delegated Regulation (EU) 2024/1774 ↗
DORA · Art. 46

Supervised nationally.

National competent authorities, usually your existing prudential or markets supervisor, check compliance. Critical ICT third-party providers are overseen by a Lead Overseer from the EBA, EIOPA or ESMA.

Regulation (EU) 2022/2554 ↗
What the rule requires

The DORA logging checklist.

Each line: what the text says, what it means in practice, and where nano fits.

Delegated Regulation (EU) 2024/1774, Article 12: logging

The RTS made under DORA Article 15. Applies to financial entities under DORA's full ICT risk-management framework. Entities on the simplified framework (DORA Article 16) have a shorter logging duty in Article 34(f) of the same RTS.

Ref The requirement In plain English How nano helps
Art. 12(1) Develop, document and implement logging procedures, protocols and tools, as part of the safeguards against intrusions and data misuse. EUR-Lex · 2024/1774 Logging is a written, operated control, not a default setting on each server.
nano collects, parses, stores and searches your logs and runs detections on them, inside your own environment.
Art. 12(2)(a) Identify the events to be logged, the retention period and the measures to secure and handle log data, considering the purpose of the logs. EUR-Lex · 2024/1774 Write down what you log, for how long, and how you protect it, and why.
Every install starts with zero log sources: you choose what to onboard. You set event retention (365 days by default) and can tier older data to S3-compatible storage you own.
Art. 12(2)(b) Align the level of detail of the logs with their purpose and usage, to enable effective detection of anomalous activities. EUR-Lex · 2024/1774 Logs must be detailed enough to detect things, not just to exist.
Events are parsed into OCSF fields so detection rules and searches can use them across sources.
Art. 12(2)(c) Log events related to access control and identity management, capacity management, change management, ICT operations and network traffic. EUR-Lex · 2024/1774 Five event families are mandatory. The grid below maps them to typical sources.
HTTP, HEC and OTLP ingest, syslog through a Vector collector, and pull connectors for identity and SaaS sources such as Entra ID and Okta.
Art. 12(2)(d) Protect logging systems and log information against tampering, deletion and unauthorized access at rest, in transit and, where relevant, in use. EUR-Lex · 2024/1774 Lock down who can read, change or delete logs, and the SIEM itself.
Logs sit on disks and object storage you own, behind your access controls. Role-based access control limits who can read; retention and settings changes go to the platform audit log.
Art. 12(2)(e) Measures to detect a failure of logging systems. EUR-Lex · 2024/1774 You must notice when logging stops, not discover it during an incident.
The bundled Prometheus monitoring can alert through your own Alertmanager when ingest or a component stops. Searching event counts by source shows sources that went quiet.
Art. 12(2)(f) Synchronize the clocks of each ICT system to a documented, reliable reference time source. EUR-Lex · 2024/1774 Clocks must agree so events from different systems line up.
Events are normalized to OCSF time fields, so correctly synchronized sources line up on one timeline. Time synchronization itself is configured on your systems.
Art. 12, last subpara. Set the retention period taking into account business and information security objectives, the reason for recording the event, and the results of the ICT risk assessment. EUR-Lex · 2024/1774 There is no fixed DORA log retention period. You justify yours.
Retention is a setting you control per install, on storage you pay for directly, so a longer period is a storage decision rather than a vendor price tier.

Delegated Regulation (EU) 2024/1774, Article 23: detecting anomalous activity

Article 23 builds on the logs collected under Article 12 to specify the detection mechanism required by DORA Article 10(1).

Ref The requirement In plain English How nano helps
Art. 23(2)(a) Collect, monitor and analyze internal and external factors, including at least the logs collected under Article 12, and potential cyber threats based on threat intelligence. EUR-Lex · 2024/1774 Your logs must actually be analyzed, together with threat intelligence.
Detection rules run on incoming events, with enrichment from threat-intelligence feeds you can switch on or off.
Art. 23(2)(b) Identify anomalous activities and implement tools that generate alerts, at least for assets supporting critical or important functions, including automated alerts on the completeness and integrity of data sources or log collection. EUR-Lex · 2024/1774 Alert on attacks, and also alert when log collection itself breaks.
Alerts with notifications to Slack, Microsoft Teams, PagerDuty or webhooks. The bundled monitoring can alert through your own Alertmanager when ingest stops.
Art. 23(2)(c) Prioritize alerts so detected incidents are managed within the expected resolution time, both during and outside working hours. EUR-Lex · 2024/1774 Severity and routing have to work at 3 a.m. too.
Severity on every rule, and risk-based alerting that rolls related weak signals into one higher-priority alert.
Art. 23(3)–(4) Protect records of anomalous activities against tampering and unauthorized access; log the date and time of occurrence, the date and time of detection, and the type of each anomalous activity. EUR-Lex · 2024/1774 Keep a protected record of each detection with its timestamps and type.
Alerts and cases keep the triggering events, detection time, rule and analyst notes, in your own database.

Regulation (EU) 2022/2554 (DORA): the obligations logging supports

Ref The requirement In plain English How nano helps
Art. 10(1)–(2) Mechanisms to promptly detect anomalous activities, with multiple layers of control, alert thresholds and automatic alerts to incident-response staff. EUR-Lex · DORA Detection is mandatory, and it must be tested regularly (Art. 25).
Detections, thresholds and alert routing are configured by your team and run in your environment.
Art. 17(2) Record all ICT-related incidents and significant cyber threats, and identify, document and address root causes. EUR-Lex · DORA Every incident is recorded, not only the major ones you report.
Cases hold the alert, evidence, timeline and notes, so the record and root-cause work live in one place.
Art. 19(4) Initial notification, intermediate report and final report on major ICT-related incidents to the competent authority. EUR-Lex · DORA The reporting clock below starts with classification, so you need the facts fast.
One place to search across sources for timeline, scope and affected systems while the clock runs.

RTS Article 12(2)(c): the five event families you must log

Mandatory for entities on the full framework. The typical sources are examples; the regulation does not name any.

  1. (i) Logical and physical access control, and identity management Entra ID, Okta, Active Directory, PAM, badge systems
  2. (ii) Capacity management Host and service metrics, OpenTelemetry, storage alerts
  3. (iii) Change management Cloud control-plane audit logs, CI/CD, configuration management
  4. (iv) ICT operations, including ICT system activities Windows and Linux system logs, EDR, database audit
  5. (v) Network traffic activities, including network performance Firewall, proxy, DNS, NetFlow, load balancers
Major-incident reporting

Three deadlines once an incident is major.

You classify ICT-related incidents against the criteria in Delegated Regulation (EU) 2024/1772. Once one is major, the reporting clock in Delegated Regulation (EU) 2025/301 runs, on the forms in Implementing Regulation (EU) 2025/302. Classification depends on facts your logs hold: clients affected, duration, data losses, geographic spread.

  1. 0 h

    Incident classified as major

    Classify quickly: the initial notification is due no later than 24 hours after you become aware of the incident.

  2. 4 h

    Initial notification

    Within 4 hours of classifying the incident as major, and no later than 24 hours after becoming aware of it.

  3. 72 h

    Intermediate report

    Within 72 hours of the initial notification, with an update once regular activities are recovered.

  4. 1 month

    Final report

    No later than one month after the latest intermediate report, including root cause and measures taken.

Delegated Regulation (EU) 2025/301, Article 5. Reports go to your competent authority under DORA Article 19.
Third-party and concentration risk

Where your detection layer runs is a DORA question.

DORA asks you to manage ICT third-party risk, plan your exit and look at concentration before you contract. In November 2025 the ESAs designated the first critical ICT third-party providers, the hyperscalers among them.

Your environment

Your data center, your account with the cloud provider you choose, or an air-gapped network

01 · Sources
  • core banking
  • Entra ID
  • EDR
  • firewall
  • DNS
  • cloud audit
02 · nano
  • Collect and parse
  • Detections and alerts
  • Search and cases
03 · Your storage
  • Disks you own
  • Optional object storage tier
  • Retention you set
Optional · AI pivt AI calls your model endpoint directly: any OpenAI-compatible API (including self-hosted models) or the Anthropic Messages API. Off by default; model calls never go through nano.
nano, the vendor

Never receives your logs.

Connected
  • Daily license check-in: deployment ID, install ID, version
  • Hourly content and enrichment-feed updates (no data sent; can be turned off)
  • One number per day: total GB ingested
  • Downloads: log-source catalog, detection rules and SOAR content, enrichment feeds, releases
Air-gapped
  • No connection to nano at all
  • Offline license file, renewed by hand
fig 01 · nano runs inside your environment. Log data is never sent to nano.
Concentration · Art. 29

Don't share a failure domain with what you watch.

The 19 designated providers include Amazon Web Services EMEA, Google Cloud EMEA and Microsoft Ireland Operations. If your workloads run on one of them, you can run your SIEM on different infrastructure, so an outage there doesn't take out your detection and incident evidence with it. High availability

Register and exit · Art. 28

nano is a supplier, not a data holder.

List nano in your register of information like any software supplier. Your logs stay in standard database formats on storage you control and can be exported at any time, which keeps an exit strategy concrete. With an online license, an install that can't reach nano keeps its last verified license for 14 days, then its licensed features lock until it checks in again. While locked, pushed ingest (HTTP, HEC, OTLP), search over stored data and scheduled detection rules keep running and local admins can still sign in; SSO sign-in, pull collectors, cases, SOAR and AI stop. No data is deleted or altered. An offline license file is checked locally, so it removes the check-in dependency. Data flows · Self-run Addendum

Protection · RTS Art. 12(2)(d)

Your storage, your access rules.

Logs sit on disks and object storage you own, behind your access controls and backups, for the retention period you justify. No vendor administrator has access to the deployment. Storage and retention

Key dates

Where DORA stands.

Status as of November 2026.

  1. 16 Jan 2023 In effect

    DORA in force

    Published in the Official Journal on 27 December 2022; in force twenty days later (Art. 64).

    EUR-Lex · DORA ↗
  2. 17 Jan 2025 In effect

    DORA applies

    Financial entities must meet DORA and its technical standards, including RTS 2024/1774 (Art. 64).

    EUR-Lex · DORA ↗
  3. 18 Nov 2025 In effect

    First CTPP list

    The ESAs designated 19 critical ICT third-party providers, including AWS, Google Cloud and Microsoft.

    EBA / EIOPA / ESMA ↗
  4. Yearly Next

    List updated

    The ESAs establish, publish and update the CTPP list every year (Art. 31(9)). Check for the current list.

    EUR-Lex · DORA ↗

The first designated critical ICT third-party providers

Published by the ESAs on 18 November 2025 under DORA Article 31(9):

  • Accenture plc
  • Amazon Web Services EMEA Sarl
  • Bloomberg L.P.
  • Capgemini SE
  • Colt Technology Services
  • Deutsche Telekom AG
  • Equinix (EMEA) B.V.
  • Fidelity National Information Services, Inc.
  • Google Cloud EMEA Limited
  • International Business Machine Corporation
  • InterXion HeadQuarters B.V.
  • Kyndryl Inc.
  • LSEG Data and Risk Limited
  • Microsoft Ireland Operations Limited
  • NTT DATA Inc.
  • Oracle Nederland B.V.
  • Orange SA
  • SAP SE
  • Tata Consultancy Services Limited
ESAs press release and list ↗
FAQ

Questions we get asked.

What is DORA, in simple terms?

DORA, the Digital Operational Resilience Act, is Regulation (EU) 2022/2554. It sets one EU rulebook for how banks, insurers, investment firms, payment institutions and other financial entities manage ICT risk: protecting and monitoring their systems, handling and reporting ICT incidents, testing resilience, and managing the risk of their ICT suppliers. As a regulation it applies directly in every Member State, from 17 January 2025.

Who does DORA apply to?

Article 2 lists 20 types of financial entity, including credit institutions, payment and e-money institutions, investment firms, crypto-asset service providers, central securities depositories, central counterparties, trading venues, fund managers, insurance and reinsurance undertakings, occupational pension institutions, credit rating agencies and crowdfunding providers, plus ICT third-party service providers in parts of the Regulation. Article 2(3) excludes some smaller entities, and Article 16 gives certain small ones a simplified ICT risk-management framework.

What are the five pillars of DORA?

DORA's substantive chapters cover five areas: ICT risk management (Chapter II), ICT-related incident management, classification and reporting (Chapter III), digital operational resilience testing (Chapter IV), managing ICT third-party risk (Chapter V), and information-sharing arrangements (Chapter VI). 'Five pillars' is a common shorthand, not a term the Regulation uses.

What logging does DORA require?

The detail is in Article 12 of Delegated Regulation (EU) 2024/1774, not in DORA Article 12, which covers backup and restoration. RTS Article 12 requires documented logging procedures, protocols and tools that identify the events to log, a justified retention period, log detail sufficient to detect anomalous activity, logging of access control and identity, capacity, change, ICT operations and network traffic events, protection of logs against tampering, deletion and unauthorized access, detection of logging failures, and clocks synchronized to a reliable reference time source.

What are the DORA major-incident reporting deadlines, and what must the reports include?

Under Delegated Regulation (EU) 2025/301, the initial notification is due within 4 hours of classifying an incident as major and no later than 24 hours after becoming aware of it; the intermediate report within 72 hours of the initial notification; and the final report no later than one month after the latest intermediate report. The initial notification includes, among other things, when and how the incident was detected, why it was classified as major under Delegated Regulation (EU) 2024/1772, the Member States affected and whether a business continuity plan was activated. Implementing Regulation (EU) 2025/302 sets the forms.

How does DORA treat ICT third-party service providers, and is a SIEM vendor one?

Financial entities must manage ICT third-party risk as part of ICT risk (Article 28), keep a register of information on all their ICT service contracts (Article 28(3)), have exit strategies for services supporting critical or important functions (Article 28(8)) and assess concentration risk before contracting (Article 29). Any SIEM vendor that supplies software, updates or support is an ICT third-party service provider for those purposes, nano included. What differs is that you run nano yourself: it does not hold, process or have access to your log data, so the SIEM's data and its availability stay with infrastructure you choose.

Who supervises DORA?

National competent authorities supervise financial entities, as set out in Article 46: for example the authority that already supervises a bank, insurer or investment firm in its Member State. For critical ICT third-party providers designated under Article 31, one of the European Supervisory Authorities (EBA, EIOPA or ESMA) acts as Lead Overseer.

Does DORA apply to UK firms?

DORA is EU law, so it does not apply to UK entities as such. It applies to financial entities established in the EU, including EU subsidiaries of UK groups. UK-based ICT providers serving EU financial entities are affected through those customers' contracts and third-party risk management.

What happens if you are not DORA compliant?

DORA leaves penalties for financial entities to Member States: competent authorities must have supervisory, investigatory and sanctioning powers, including administrative penalties and remedial measures (Article 50), and national law sets the amounts. Critical ICT third-party providers face periodic penalty payments of up to 1% of average daily worldwide turnover from their Lead Overseer (Article 35(8)).

Does a SIEM make you DORA compliant?

No. DORA obligations sit with the financial entity and its management body and cover governance, risk management, testing, third-party risk and reporting. A SIEM supplies the logging, detection and evidence that RTS Articles 12 and 23 describe. nano helps with that part and holds no DORA-related certification.

Primary sources

Read the rules yourself.

Start with nano.

From US$149/month at 5 GB/day, US$279/month at 10 GB/day (list price, billed monthly; 10% off billed annually). Every feature in one license, and one license covers two installs.

Buy nano
Talk to sales