OrganizationPractitioner2 min read
Are you ready for a NIS2 audit?
The ten measures of NIS2 Article 21, the evidence logs, metrics and traces can provide for each, your status and a prioritized action plan.
For: finance, risk and compliance · executives and CIOsPrerequisites: Basic notions of the NIS2 directive. The page recaps what it asks for.
An illustrative scenario: an auditor settles into the meeting room and opens a checklist. “Do you have an incident handling procedure?” Yes, it is in a binder. “Show me how you applied it during your last three incidents.” Silence. The procedure exists, but nobody can prove it is used.
That is the whole difference between having a measure and being able to demonstrate it. At a vehicle inspection, saying the brakes work is not enough: the inspector measures them and the result goes on the report. The European NIS2 directive, which sets cybersecurity rules for many organizations, works in the same spirit. Its Article 21 lists ten risk-management measures. The question an auditor will ask is not “does the measure exist?” but “can you prove it?”.
This tool separates the two. For each measure, it suggests the evidence observability can produce: a metric, a log or a dashboard showing that the measure works over time. It helps settle a simple question: where do we really stand and where do we start?
| Measure | Evidence logs, metrics and traces can provide | Status |
|---|---|---|
| aPolicies on risk analysis and information system security | asset inventory kept up to date by automatic discovery, dated review | |
| bIncident handling | alerts, timestamped timelines, tickets linked to traces and logs | |
| cBusiness continuity, backup management, disaster recovery, crisis management | backup success, timed restore tests, logged exercises | |
| dSupply chain security | measured availability and errors of supplier services, logged supplier access | |
| eSecurity in acquisition, development and maintenance, including vulnerability handling and disclosure | tracked deployed versions, software bill of materials (SBOM), measured patch delays | |
| fAssessing the effectiveness of risk-management measures | security indicators tracked over time, archived reviews | |
| gBasic cyber hygiene and cybersecurity training | patch and configuration status, training rate tracked | |
| hCryptography and encryption | certificate inventory and expiry, logged key rotation | |
| iHuman resources security, access control, asset management | access logs, privileged account review, leavers processed | |
| jMulti-factor or continuous authentication, secured and emergency communications | share of access with MFA, authentication logs, emergency channel tests |
Result
- Demonstrable
- In place, no evidence
- Partial
- Missing
Action plan, by priority
Reference: Article 21(2), points (a) to (j), of Directive (EU) 2022/2555. This tool helps prepare the discussion with the CISO and legal; it is not legal advice. How it applies to your organization depends on your classification and on the national transposition law. Nothing is sent: your answers stay in this browser.
Things to try
Section titled “Things to try”- Start from the starting situation. It is Helinord’s in June 2025, the company in the journal of the CIO path: three partial measures, seven missing. The action plan starts with the missing ones.
- Set incident handling (b) to “In place, no evidence”. It drops to priority 3, but stays in the plan. That is the scenario above: a process nobody can demonstrate does not count in front of an auditor.
- Declare a measure not applicable. It leaves the calculation and the tool reminds you that the justification must be written down.
- Aim for eight out of ten, like Helinord a year later. The remaining two often depend on suppliers and go through a contractual plan.
The rule to remember
Section titled “The rule to remember”A measure without evidence is a paper measure. Every line of the table should be backed by a metric, a log or a dashboard that shows it works over time. I recommend doing the exercise as a trio, with the CIO, the CISO and legal, then keeping the evidence in the same place as the grid.
This tool is not legal advice: your organization’s classification and the national rules should be checked with your lawyer. This matters all the more since the French transposition law has not yet been enacted as of 2 October 2026.
Going further: the compliance lesson of the CIO path, a signed log is not an auditable log and the evidence matrix of the GenAI method.