An independent information publicationDirective (EU) 2022/2555 · The NIS2 DirectiveNot an official publication
The Independent NIS2 Desk
NIS2 Compliance
Independent information on the NIS2 Directive, for the organisations it covers.
HomeArticlesNIS2 Cybersecurity Audits: Scope, Evidence and Findings
Security Testing Audit / 2026-10-09

NIS2 Cybersecurity Audits: Scope, Evidence and Findings

A NIS2 cybersecurity audit reviews whether relevant security measures are appropriately designed, implemented and working. Audits can support the effectiveness assessment required by Article 21(2)(f), but the Directive does not establish one identical annual audit or certification obligation for all covered entities. National law, sector-specific requirements and supervisory powers must be checked separately.

First determine what kind of audit is being discussed

An internal assurance audit performed for management differs from a competent authority's supervisory audit or inspection. NIS2 Articles 32 and 33 establish different supervisory regimes for essential and important entities, and the circumstances in which authorities can intervene are not identical.

Organisations should not confuse a voluntary audit schedule with a universal requirement to obtain a particular certification. A national law, regulatory decision or sector-specific measure may impose additional obligations, so the audit brief should state its actual basis.

Define scope around services and risks

An audit should identify the legal entity, services, sites, relevant systems, control areas and review period. Include significant outsourced functions where they affect the service's security, while making clear what evidence is accessible from suppliers and what remains outside the auditor's scope.

Start from the risk assessment and previous findings. A newly outsourced incident-monitoring function or a repeatedly failing backup restore process may warrant more scrutiny than a control with stable performance and strong recent evidence.

Look for operational evidence, not only documents

Policies, risk registers and meeting minutes demonstrate governance decisions. System configurations, access logs, change records, restore-test outputs and incident exercises help show whether measures operate. Inspect samples covering normal and exceptional conditions, recording the sampling method and any limitations.

For example, a vendor security questionnaire may show that due diligence was requested. An audit may still need to establish whether material exceptions were assessed, supplier access was limited and contractually agreed safeguards were implemented.

Distinguish weaknesses by consequence

Findings should describe the observed condition, the expected control, supporting evidence and the affected risk. Classify severity using a documented method that considers exploitability, business criticality and possible service disruption. Avoid labels that imply a legally defined NIS2 violation unless the legal basis has been established.

Audit reports should separate confirmed nonconformities from improvement opportunities and evidence gaps. A missing record may prevent the auditor from reaching a conclusion even when there is no proof that the technical control failed.

Close the audit loop

Agree remediation owners, due dates and objective completion criteria. A corrective action might involve reducing excessive privileged accounts, testing a revised restoration process or improving incident escalation. Request evidence of completion and repeat the relevant assessment when warranted.

Management should see material findings, unresolved risks and overdue actions. Retain a versioned audit trail so a later reviewer can tell what was tested, what changed and why a finding was closed.

Keep regulatory references accurate

Article 21(2)(f) supports effectiveness assessment policies and procedures. Articles 32 and 33 address supervision and enforcement powers, with differences between entity classifications. These provisions do not mean that every entity must follow one identical internal audit timetable.

Commission Implementing Regulation (EU) 2024/2690 and ENISA's related technical guidance provide additional detail for specified digital and ICT provider categories. Confirm applicability before using those materials as a binding audit criterion.

Points of clarification

Does NIS2 require every organisation to obtain ISO 27001 certification?

No universal ISO 27001 certification requirement appears in Article 21. Certification may be useful or separately required in a particular context, but it is not a substitute for assessing the applicable NIS2 duties.

Can internal audits provide useful evidence?

Yes. Documented internal reviews can support assurance when they have appropriate scope, competent assessors, reliable evidence and follow-up.

Should findings be deleted after remediation?

No. Retain a suitable audit history and evidence of verified correction under the organisation's retention and security rules.

Further entries on this subject

The texts relied on

General editorial guidance only: it does not determine your organisation's legal obligations. See our editorial policy for how this site works and corrects errors.