NIS2 Directive Compliance

NIS2 Article 21 Linux Identity Assessment

NIS2 Article 21 requires identity and access controls. We assess your Linux estate.

Years of sudo rules, SSH keys and service accounts have built paths to root across the Linux systems behind your essential or important services. Those paths live on the host, outside what SIEM, EDR and cloud IAM were designed to inspect. Automation and AI agents now find and use them persistently, in the gaps between reviews. Article 21 asks for demonstrable control over exactly that access. Our pilot maps every path and delivers the evidence.

Why Linux identity is a NIS2 question

  • Undocumented sudo rules build up quietly over time, and each one makes the continuous control that NIS2 Article 21(2)(a) risk analysis expects harder to show.
  • Former employees’ accounts that still hold sudo fall squarely under NIS2’s access-management requirements.
  • Automation and AI agents authenticate as service accounts on those systems and inherit whatever reach the accounts have built up, so an unmapped path to root is used persistently, in the gaps between review cycles. Demonstrating control under Article 21 means knowing what each of those accounts can do on each host, continuously.
  • NIS2 Article 21(2)(i) makes access control a required cybersecurity measure for essential and important entities. Linux servers are a key surface where it applies.
  • NIS2 Article 20 makes the management body approve and oversee your cybersecurity risk-management measures.
  • NIS2 (Directive (EU) 2022/2555) had to be transposed into national law by 17 October 2024. National laws have taken effect on staggered dates since, and supervisory authorities in most member states are now assessing compliance.

How the pilot maps to NIS2 Article 21

Every pilot finding is mapped to specific NIS2 Article 21 controls, so the evidence supports your NIS2 supervisory reporting.

Article / RequirementWhat it requiresHow the pilot covers it
Article 21(2)(i)Human resources security, access control policies and asset managementFull inventory of users, groups, sudo rules, SSH keys, PAM configuration, and service accounts with privilege path mapping
Article 21(2)(a)Risk analysis and information system security policiesRisk-scored findings mapped to exploit patterns, prioritised by likelihood and impact on essential services
Article 21(2)(d)Supply chain securityThird-party and service account privilege assessment identifying vendor accounts with excessive access
Article 21(2)(j)Multi-factor or continuous authentication and secured communicationsAssessment of authentication controls on privileged accounts including sudo and SSH key management gaps

The two documents that define NIS2 evidence in practice

Article 21 says what must be managed. Commission Implementing Regulation (EU) 2024/2690 and ENISA’s Technical Implementation Guidance say what the evidence looks like, and neither is about servers. Both are covered in our guide to Linux access control evidence under NIS2, DORA and the EU AI Act.

Where the pilot’s evidence lands in the Annex

  • 11.2

    Requirement
    Management of access rights
    What the pilot hands over
    Every account and group membership on each host, with the sudo rules and SSH keys attached; dormant and orphaned accounts flagged.
  • 11.3

    Requirement
    Privileged accounts and system administration accounts
    What the pilot hands over
    Which identities can reach root on which host, ranked by risk; NOPASSWD and standing sudo grants surfaced.
  • 11.5 and 11.6

    Requirement
    Identification and authentication
    What the pilot hands over
    Shared accounts and keys reused across hosts flagged; SSH keys graded for algorithm strength, reuse and whether they still belong to anyone.
  • 12.4 and 12.5

    Requirement
    Asset inventory; return or deletion of assets on termination of employment
    What the pilot hands over
    The identity inventory per host, continuously updated; a leaver’s residual access — local accounts, keys, sudo — surfaced and removable behind an approval.
  • 3.2

    Requirement
    Monitoring and logging
    What the pilot hands over
    Sudo, SSH and PAM changes detected in near-real-time and attributed to the identity that made them, recorded in a chain-hashed audit log.
  • 6.3 and 6.4

    Requirement
    Configuration management; change management
    What the pilot hands over
    Sudoers, SSH and PAM configuration tracked against an approved baseline, so an undocumented change is a finding the same day.

Where LinuxGuard sits among the Linux compliance tools you already run

Most estates in scope already run one or more of these for hardening and logging. Each closes part of the picture; none of them answers who can reach root on which host, or keeps that answer current. Read them as complements, which is how we deploy alongside them.

Open-source options

Lynis

A host-based security audit for Linux and Unix systems. It runs on the host itself, tests hundreds of hardening controls drawn from CIS, NIST and NSA guidance, and reports a hardening index with warnings and suggestions.

Closes
A point-in-time hardening audit of an individual host.
Leaves open
It does not inventory accounts, sudo rules or SSH keys across an estate, does not attribute a change to an identity, and does not watch between runs.
Documentation

OpenSCAP with Ansible

SCAP content from the SCAP Security Guide, with CIS, DISA STIG and PCI DSS profiles. It evaluates a host’s configuration against a profile, produces HTML and ARF reports, and ships remediation content, including Ansible, to bring the host back to the baseline.

Closes
Configuration-baseline conformance and remediation at scale.
Leaves open
Who holds privilege on the host is not a benchmark rule: sudoers topology, SSH key ownership and service accounts sit outside the profile, and each scan describes one moment.
Documentation

auditd

The userspace component of the Linux Auditing System. It writes audit records to disk according to the rules loaded from audit.rules, which is the event record that monitoring and logging requirements draw on.

Closes
A record of what happened on the host — logins, privileged commands, file access — as configured.
Leaves open
It records events; it does not assess configuration, inventory accounts or rank privilege. Rulesets drift between hosts, and the logs still need central collection and interpretation.
Documentation

Ubuntu Pro (Ubuntu Security Guide)

Canonical’s subscription tooling for Ubuntu LTS. The Ubuntu Security Guide hardens a host to CIS or DISA-STIG profiles and generates audit reports; CIS profiles cover 20.04, 22.04 and 24.04 LTS, DISA-STIG 20.04 and 22.04.

Closes
Benchmark hardening and audit reporting on Ubuntu hosts.
Leaves open
Ubuntu only, by design. It reports benchmark conformance, not who can reach root or which keys and service accounts hold privilege, and it does not attribute change to an identity.
Documentation

Alongside them: LinuxGuard

LinuxGuard

A Linux-native control plane for identity and access. A continuous inventory of every account, group, sudo rule, SSH key and service account across the distributions you run, risk-scored, with sudo, SSH and PAM changes detected in near-real-time and attributed to the identity behind them, response actions behind an approval gate, and evidence exported per framework.

Closes
The access-rights, privileged-account and inventory evidence that the access-control and asset-management requirements ask for — continuously, rather than per scan.
Leaves open
It does not harden the operating system to a benchmark and does not replace auditd’s event record. It runs alongside both.
What LinuxGuard does

Ubuntu Pro is listed with the open-source tools because the Ubuntu Security Guide is the hardening route most Ubuntu estates already have; it is a Canonical subscription. LinuxGuard is Validated with Ubuntu under Canonical’s Software Partner Programme and is certified with Red Hat and SUSE.

What you get

  • Identity & Privilege Inventory — Every user, group, sudo rule, SSH key, and service account across your Linux estate, showing who can do what
  • Risk-Scored Findings Report — Prioritised findings based on real exploit patterns, highlighting the privilege paths attackers would use first
  • Compliance Evidence Package — Identity governance gaps mapped to NIS2 Article 21 controls with remediation guidance
  • Prioritised Remediation Plan — Phased plan to reduce privilege drift and move toward least-privilege, ordered by the paths to root each change closes
  • Board-Ready Executive Summary — Executive summary for boards and a technical deep-dive for your security team

How the Founding Pilot works

The Founding Pilot runs in five phases over 60 days. It starts with discovery and scoping, then maps identity and privilege with lightweight, read-only collectors. A security and compliance assessment maps the findings to NIS2 Article 21 controls. Reporting closes it, with a prioritised least-privilege remediation roadmap. A dedicated Linux identity specialist supports the pilot throughout. Collection is read-only. Only a response action alters a host: one someone has approved or, once an administrator has switched on active response, one that runs in real time. See the Founding Pilot for the full five-phase process, timeline, and deliverables.

Frequently Asked Questions

Does NIS2 apply to our Linux servers specifically?
Yes. NIS2 Article 21(2)(i) mandates identity and access management controls as a baseline cybersecurity measure. Linux servers running essential services — healthcare systems, energy management — are within scope. The directive does not distinguish by operating system. It requires demonstrable control over all systems supporting essential services. Operators of essential services will find the sector view under essential-function Linux estates.
What does Article 21 require for identity and access management?
Article 21(2)(i) requires entities to implement and maintain appropriate measures for identity and access management. This means being able to demonstrate who has access to which systems, what privileges they hold, and that access is granted on a least-privilege basis with regular review. On Linux estates, this includes sudo rules, SSH key management, service account governance, and group membership oversight.
How does LinuxGuard produce NIS2 compliance evidence?
The pilot delivers a structured compliance evidence pack mapped directly to NIS2 Article 21 controls. For each control, we document the current state of your Linux identity infrastructure, identify gaps against the NIS2 requirements, and provide remediation guidance with a prioritised action plan. The evidence pack is structured for review by your national supervisory authority and for internal board reporting.
What are the non-compliance penalties under NIS2?
For essential entities, NIS2 penalties reach €10M or 2% of global annual turnover, whichever is higher. For important entities, the ceiling is €7M or 1.4% of global turnover. Article 20 also allows members of the management body to be held liable for infringements.
How long does the NIS2 pilot take?
It is a fixed-scope engagement that runs in five phases over 60 days: scoping and data collection, analysis that maps findings to NIS2 Article 21 controls, then delivery of the evidence package, executive summary and remediation roadmap with a readout for your team, and dedicated expert support throughout. The Founding Pilot page has the full timeline.

Ready to evidence NIS2 on your Linux estate?

Start the pilot on your Linux estate: every path to root mapped, and the evidence pack for Article 21 produced from the same map.