NIS2 · European Union

NIS2 logging requirements, line by line.

What the NIS2 Directive and Implementing Regulation 2024/2690 ask of your logs, in plain English, and how a SIEM you run in your own environment covers each line, without your logs ever reaching nano.

Buy nano
Talk to sales
Who's in scope

Which rules apply to you.

NIS2 sets the obligations; national laws apply them; a Commission implementing regulation spells out the technical detail for some digital providers.

NIS2 Directive

Medium and large entities in the listed sectors.

Organizations of the types in Annexes I and II that are medium-sized enterprises or larger, plus some entities regardless of size. Broadly, large Annex I entities are essential and most other in-scope entities are important; Article 3 lists the exceptions. (Art. 2 and 3)

Directive (EU) 2022/2555 ↗
Implementing Regulation 2024/2690

Digital infrastructure and ICT service providers.

DNS providers, TLD registries, cloud, data center and CDN providers, managed service and managed security service providers, online marketplaces, search engines, social networks and trust service providers. Its Annex sets the technical measures, including section 3.2 on logging.

Implementing Regulation (EU) 2024/2690 ↗
Management bodies

Accountability sits at the top.

Management bodies of essential and important entities must approve the cybersecurity risk-management measures, oversee their implementation, and can be held liable for infringements. (Art. 20)

Directive (EU) 2022/2555 ↗
What the rule requires

The NIS2 logging checklist.

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

Implementing Regulation (EU) 2024/2690, Annex, section 3.2: monitoring and logging

Binds the digital-infrastructure and ICT-service providers listed in its Article 1 directly. For everyone else it is the most concrete published description of what NIS2 logging looks like.

Ref The requirement In plain English How nano helps
3.2.1 Lay down procedures and use tools to monitor and log activities on network and information systems to detect events that could be incidents. EUR-Lex · 2024/2690 You need a logging and monitoring capability, not just logs sitting on each server.
nano collects, parses, stores and searches your logs and runs detections on them, inside your own environment.
3.2.2 Monitoring automated to the extent feasible, continuous or periodic, minimizing false positives and false negatives. EUR-Lex · 2024/2690 Machines watch, people tune. Noise counts against you as much as gaps.
Detection rules run automatically on incoming events. Risk-based alerting rolls related weak signals into one alert so analysts see fewer, better alerts.
3.2.3 Maintain, document and review logs; logs include, where appropriate, the twelve categories (a) to (l) listed in the checklist below. EUR-Lex · 2024/2690 Decide what you log from your risk assessment, write it down, and cover the listed event types.
HTTP, HEC and OTLP ingest, syslog through a Vector collector, and pull connectors for identity and SaaS sources. Every install starts with zero log sources: you choose what to onboard.
3.2.4 Review logs regularly; set alarm thresholds where appropriate; trigger alarms automatically; start a qualified response in a timely manner. EUR-Lex · 2024/2690 Someone has to look, thresholds have to fire, and a response has to follow.
Alerts with notifications to Slack, Microsoft Teams, PagerDuty or webhooks, and cases that hold the alert, evidence, timeline and notes of the response.
3.2.5 Maintain and back up logs for a predefined period and protect them from unauthorized access or changes. EUR-Lex · 2024/2690 Pick a retention period, keep backups, and lock down who can read or alter logs.
You set event retention (365 days by default) and can tier older data to S3-compatible storage you own, still searchable. Role-based access control limits who can read; retention and settings changes go to the platform audit log.
3.2.6 Rely on synchronized time sources to correlate logs between systems; keep a list of all assets being logged. EUR-Lex · 2024/2690 Clocks must agree, and you must know which assets feed the logs.
Events are normalized to OCSF time fields so sources line up on one timeline. A stats search by source and host lists everything that sent events in a period, to reconcile against your asset list.
3.2.6 Monitoring and logging systems are redundant; their availability is monitored independently of the systems they monitor. EUR-Lex · 2024/2690 The SIEM must survive a failure, and something outside it must notice if it goes down.
Run nano on three or more servers or on Kubernetes so storage, search and ingest survive losing a server. The bundled Prometheus monitoring can alert through your own Alertmanager on separate infrastructure.
3.2.7 Review and update the procedures and the asset list at regular intervals and after significant incidents. EUR-Lex · 2024/2690 Revisit what you log, and how, on a schedule and after every major incident.
The platform audit log records rule, user and settings changes, so a review can show what changed and when.

Directive (EU) 2022/2555: the obligations logging supports

Apply to essential and important entities through each Member State's national law.

Ref The requirement In plain English How nano helps
Art. 21(2)(b) Cybersecurity risk-management measures shall include incident handling. EUR-Lex · NIS2 You need a working process to detect, analyze and respond to incidents.
Detections feed alert queues; alerts group into cases where analysts investigate with search, entity context and playbooks.
Art. 21(2)(c) Business continuity, such as backup management and disaster recovery, and crisis management. EUR-Lex · NIS2 Security tooling has to keep working, or come back, when things go wrong.
A nano license covers two installs, so production plus a second install for DR or backup is included.
Art. 21(2)(f) Policies and procedures to assess the effectiveness of cybersecurity risk-management measures. EUR-Lex · NIS2 Show that your controls work, with evidence.
Search and dashboards over your own retained logs give the evidence; nothing has to be exported from a vendor first.
Art. 23(4) Early warning within 24 hours, incident notification within 72 hours, final report within one month. EUR-Lex · NIS2 Reporting clocks start when you become aware of a significant incident.
One place to search across sources for timeline, scope and affected systems; the case keeps the record you need for the final report.

Annex 3.2.3: what the logs should include

"Where appropriate", based on your risk assessment. The typical sources are examples; the regulation does not name any.

  1. (a) Relevant outbound and inbound network traffic Firewall, proxy, NetFlow, DNS
  2. (b) Creation, modification or deletion of users and extension of permissions Active Directory, Entra ID, Okta, Google Workspace
  3. (c) Access to systems and applications VPN, SSO, application access logs
  4. (d) Authentication-related events Identity provider sign-ins, MFA, Windows logons
  5. (e) All privileged access and activity by administrative accounts PAM, sudo, cloud admin and control-plane logs
  6. (f) Access or changes to critical configuration and backup files File integrity, configuration management, backup software
  7. (g) Event logs and logs from security tools such as antivirus, IDS and firewalls EDR/AV, IDS/IPS, firewall
  8. (h) Use of system resources and their performance Host metrics, OpenTelemetry
  9. (i) Physical access to facilities Badge and door-control systems
  10. (j) Access to and use of network equipment and devices Switch, router and wireless controller syslog
  11. (k) Activation, stopping and pausing of the various logs Audit-policy changes, log-cleared events, agent status
  12. (l) Environmental events Building management, UPS, environmental sensors
Article 23 reporting

Three deadlines from the moment you know.

For a significant incident, essential and important entities report to their CSIRT or competent authority on a fixed clock. You can only meet it if the logs are already collected and searchable when the incident starts.

  1. 0 h

    Aware of a significant incident

    The clock starts when you become aware, not when the incident began.

  2. 24 h

    Early warning

    Flag whether the incident is suspected to be malicious or could have cross-border impact.

  3. 72 h

    Incident notification

    Update the early warning with an initial assessment, severity, impact and indicators of compromise where available.

  4. 1 month

    Final report

    Detailed description, root cause, mitigations and any cross-border impact, one month after the notification.

Directive (EU) 2022/2555, Article 23(4). National laws set the recipient and the form.
Why where your logs live matters

A SIEM that doesn't share fate with what it watches.

Annex 3.2.6 asks for logging systems that are redundant and monitored independently of the systems they monitor. Where your SIEM runs, and who holds the data, is part of the answer.

Your environment

Your data center, your account with an EU cloud provider, or an air-gapped network

01 · Sources
  • firewall
  • Entra ID
  • EDR
  • DNS
  • servers
  • OT
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.
Independence · 3.2.6

Separate from what it monitors.

You choose the infrastructure, so you can keep the SIEM out of the failure domain of the systems it watches, and run it on three or more servers for redundancy. High availability

Protection · 3.2.5

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 set. Storage and retention

Supply chain · Art. 21(2)(d)

One less party holding your security data.

nano never receives your logs, so your SIEM vendor is not another place your security data lives. A connected install exchanges only license and content traffic with nano; an air-gapped one exchanges nothing. Monitor your install

National transposition

Where NIS2 stands, country by country.

NIS2 obligations reach you through national law, and Member States moved at different speeds. Status as of November 2026.

  1. 17 Oct 2024 In effect

    Transposition deadline

    Member States had to adopt national measures by this date and apply them from 18 October 2024 (Art. 41).

    EUR-Lex · NIS2 ↗
  2. 28 Nov 2024 In effect

    Infringement letters

    The Commission sent letters of formal notice to 23 Member States.

    European Commission ↗
  3. 7 May 2025 In effect

    Reasoned opinions

    Reasoned opinions to 19 Member States that still had not fully transposed.

    European Commission ↗
  4. 6 Dec 2025 In effect

    Germany in force

    Germany's NIS2 implementation act entered into force.

    BSI ↗
  5. 8 Jul 2026 In effect

    Court referrals

    Ireland, Spain, France and the Netherlands referred to the Court of Justice.

    European Commission ↗
  6. 15 Aug 2026 In effect

    Netherlands in force

    The Cyberbeveiligingswet and its decree entered into force.

    wetten.overheid.nl ↗
  7. As of Nov 2026 Pending

    France: bill not yet law

    The Senate adopted the bill in March 2025; the National Assembly's plenary debate began on 9 November 2026.

    Assemblée nationale ↗
Germany · in force

NIS2UmsuCG and the new BSIG

Germany's implementation act, known in draft as the NIS2UmsuCG and enacted as the Gesetz zur Umsetzung der NIS-2-Richtlinie und zur Regelung wesentlicher Grundzüge des Informationssicherheitsmanagements in der Bundesverwaltung, was promulgated on 5 December 2025 and entered into force on 6 December 2025. Entities register with the BSI within three months of first falling in scope (§ 33 BSIG).

Operators of critical facilities (KRITIS) must also run attack-detection systems that "continuously and automatically capture and evaluate" suitable parameters from ongoing operations (§ 31(2) BSIG, previously § 8a(1a)).

Netherlands · in force

Cyberbeveiligingswet (Cbw)

The Senate (Eerste Kamer) adopted the Cyberbeveiligingswet on 7 July 2026. The act and its implementing decree, the Cyberbeveiligingsbesluit, entered into force on 15 August 2026. The Commission had referred the Netherlands to the Court of Justice on 8 July 2026 for late transposition.

France · pending, as of Nov 2026

Resilience and cybersecurity bill

France's transposition bill (projet de loi relatif à la résilience des infrastructures critiques et au renforcement de la cybersécurité) was adopted by the Senate on 12 March 2025. Its plenary debate in the National Assembly began on 9 November 2026; it had not been promulgated as of November 2026. The Commission referred France to the Court of Justice on 8 July 2026.

FAQ

Questions we get asked.

What is NIS2?

NIS2 is Directive (EU) 2022/2555, the EU law on a high common level of cybersecurity. It replaced the original NIS Directive from 18 October 2024, covers more sectors, and requires essential and important entities to take cybersecurity risk-management measures (Article 21) and to report significant incidents (Article 23). As a directive, it applies through each Member State's national law.

Who needs to be NIS2 compliant?

Medium-sized and larger organizations in the sectors listed in Annexes I and II of the Directive. Annex I covers energy, transport, banking, financial market infrastructures, health, drinking water, waste water, digital infrastructure, ICT service management, public administration and space. Annex II covers postal and courier services, waste management, chemicals, food, manufacturing, digital providers and research. Some entities are in scope regardless of size, such as trust service providers, TLD name registries and DNS service providers. Broadly, large Annex I entities are essential and most others are important.

Is NIS2 implemented in Germany, the Netherlands and Ireland?

As of November 2026: Germany's implementation act entered into force on 6 December 2025. The Netherlands' Cyberbeveiligingswet entered into force on 15 August 2026. The European Commission referred Ireland, Spain, France and the Netherlands to the Court of Justice on 8 July 2026 for failing to transpose NIS2 in time. For Ireland's current position, see its National Cyber Security Centre.

What logging does NIS2 require?

Article 21 of NIS2 requires risk-management measures including incident handling, without listing log types. Implementing Regulation (EU) 2024/2690, Annex section 3.2, gives the detail for the digital providers it covers: tools to monitor and log activity, a documented list of what is logged (network traffic, account and permission changes, authentication, privileged activity, security-tool logs and more), alarm thresholds, retention and backup for a predefined period, protection from unauthorized access or changes, synchronized time, and redundant logging systems whose availability is monitored independently.

What are the NIS2 incident reporting deadlines?

For a significant incident: an early warning within 24 hours of becoming aware of it, an incident notification within 72 hours, and a final report no later than one month after the incident notification (Article 23(4)). The CSIRT or competent authority can also ask for an intermediate report. National laws set who receives the reports.

What is the difference between ISO 27001 and NIS2?

ISO/IEC 27001 is a voluntary international standard for an information security management system, and organizations can be certified against it. NIS2 is EU law: in-scope entities must meet it, under supervision, with fines for infringements. An ISO 27001 management system can help organize NIS2 measures, but a certificate does not by itself show that NIS2 obligations are met.

What is the difference between NIS2 and DORA?

DORA, Regulation (EU) 2022/2554, is the sector-specific law for financial entities. NIS2 treats it as such: for financial entities covered by DORA, DORA's rules on ICT risk management and incident reporting apply instead of the NIS2 ones (NIS2 Article 4 and recital 28). Other organizations in NIS2 sectors follow NIS2 through national law.

Does NIS2 apply to UK companies?

The UK is not in the EU, so NIS2 does not apply to UK operations as such. A UK group's subsidiaries established in an EU Member State fall under that state's NIS2 law. Certain digital providers, such as cloud, data center and managed security service providers, that are not established in the EU but offer services there must designate a representative in the EU (Article 26(3)).

Does a SIEM make you NIS2 compliant?

No. NIS2 obligations sit with the organization and cover governance, risk management, supply chain, training, incident handling and reporting. A SIEM supplies the monitoring, alerting and log evidence those measures depend on. nano helps with that part and holds no NIS2 or related certification.

How long do NIS2 logs have to be kept?

There is no single EU retention period. Annex 3.2.5 of Implementing Regulation 2024/2690 requires logs to be kept and backed up for a predefined period that you set, and national laws or sector rules can add their own. In nano you set the event retention window yourself (365 days by default) and can tier older data to object storage you own.

What does a connected install send to nano?

A daily license check-in with the deployment ID, install ID and version, and one number per day: the total GB ingested. It downloads the log-source catalog, detection rules, SOAR content, enrichment feeds and releases. Default enrichment feeds (IPinfo Lite, ThreatFox, Tor exit nodes) are served by nano and can be turned off. No log content is sent. In air-gapped mode there is no connection to nano at all, and the license is an offline file you renew by hand. AI features call your own model endpoint directly.

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