How to conduct a NIS2 audit? The 6-step method with maturity grid

How to conduct a NIS2 audit? The 6-step method with maturity grid

Step 1: qualify the entity and register

Everything starts with status: essential entity, important entity or outside direct scope (the 5-question test settles it in ten minutes, at group level and not just at subsidiary level). Status determines the supervision regime, the sanction ceiling and the personal exposure of the manager. It requires registration with the French cybersecurity agency (ANSSI) via MonEspaceNIS2. A supplier outside the scope but exposed by ricochet follows the same method, calibrated to its clients' requirements.

Step 2: define the scope of systems

NIS2 does not regulate 'the entire information system' but the network and information systems that support activities and services falling within the scope. The method: start with critical services, unfold the processes that carry them, then inventory the assets that support these processes (applications, infrastructure, remote access, service providers, flows). This work delivers two valuable by-products: the mapping required by the asset management in Article 21, and the list of critical suppliers for the supply chain component.

Step 3: measure gaps on the 10 measures in Article 21

Article 21(2) sets out the minimum baseline, which the French cybersecurity agency (ANSSI)'s Référentiel Cyber France breaks down into concrete requirements:

  1. Risk analysis and information system security policies.
  2. Incident management.
  3. Business continuity: backups, disaster recovery, crisis management.
  4. Supply chain security.
  5. Security of acquisition, development and maintenance, including vulnerability management.
  6. Policies and procedures for assessing the effectiveness of measures.
  7. Basic cyber hygiene and cybersecurity training.
  8. Cryptography and, where applicable, encryption.
  9. Human resources security, access control policies and asset management.
  10. Multi-factor or continuous authentication, secure communications, including for emergencies.

Each measure is assessed on the basis of evidence (document, configuration, test), never on declaration.

The four-level maturity grid

Rating each measure from 0 to 3 makes the gap readable and progress measurable:

LevelMeaningExample for backups
0 - Non-existentNothing formalised or practisedAd hoc backups, never tested
1 - InitiatedPartial practices, not documentedAutomated backups but no restoration test or offline copy
2 - DefinedWritten policy, applied, clear responsibilities3-2-1 policy, restoration tested annually, log maintained
3 - ManagedMeasured, improved, resilientQuarterly timed tests, immutable copies, indicators reviewed by committee

The target is not 3 everywhere: it is set per measure, according to risk and the entity's status. A radar chart of the 10 measures (current score vs target) fits on one page and speaks to a board of directors: this is the recommended reporting format.

Step 4: the risk analysis that justifies priorities

Gaps are not addressed in alphabetical order. A risk analysis, for example using the French cybersecurity agency (ANSSI)'s EBIOS Risk Manager method, cross-references feared scenarios, likelihood and impact on critical services. It meets the requirement of measure 1 and provides documented justification for trade-offs: why MFA on remote access takes priority over endpoint encryption, for example. It is also what makes the plan defensible before the authority.

Steps 5 and 6: the 12-36 month plan and the evidence file

The plan is structured around three timeframes: 90 days (quick wins with high risk impact: MFA, tested offline backups, incident and notification procedure), 12 months (policies, supply chain, training, logging) and 12 to 36 months (industrialisation, regular testing, continuous improvement), in line with the progressive compliance ramp-up announced by the French cybersecurity agency (ANSSI).

The evidence file documents the governance required by Article 20: management approval decision, quarterly dashboard, executive training certificates, CISO appointment letter, exercise reports. This is the document that personally protects the executive (see their liability).

Take action

Manage your compliance with Data Comply One: all-in-one software and outsourced DPO/CISO experts.

Discover the NIS2 software →Test my NIS2 compliance →

Sources

  • Directive (EU) 2022/2555 (NIS2), Articles 20, 21, 23 and 32 to 34, EUR-Lex.
  • The French cybersecurity agency (ANSSI), Référentiel Cyber France (ReCyF), MesServicesCyber and EBIOS Risk Manager method.
  • ISO/IEC 27001:2022, correspondences with the measures of Article 21.

Frequently asked questions

How long does a NIS2 audit take?

Between three and eight weeks depending on the size of the scope and the availability of teams: measuring gaps is quick, it is the collection of evidence that takes time. The online self-assessment provides an initial radar in 20 minutes.

Do you need to be ISO 27001 certified to be NIS2 compliant?

No, but the two frameworks overlap significantly: a certified organisation already has most of measures 1, 2, 6 and 9, and an existing ISMS is the best vehicle for carrying NIS2 compliance.

Who should conduct the audit: the CIO, a third party, the CISO?

Measure 6 requires the effectiveness of measures to be assessed: an independent evaluation of operations (internal audit, third party, outsourced CISO) is expected at least periodically. Self-assessment by the CIO alone is not sufficient in the long term.

How often should the exercise be repeated?

Maturity grid updated quarterly on measures being worked on, full annual audit, and review after any significant incident or major change to the information system.

What will the French cybersecurity agency (ANSSI) actually ask for in the event of an inspection?

Evidence: registration, risk analysis, policies, records of exercises and tests, management decisions, past notifications. A dated maturity radar with its plan in progress is exactly the format that demonstrates steering.