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.
HomeArticlesInternal Cybersecurity Audits Under NIS2
Security Testing Audit / 2026-10-09

Internal Cybersecurity Audits Under NIS2

An internal cybersecurity audit can test whether an organisation's cybersecurity risk-management measures are properly designed and working. Article 21(2)(f) calls for policies and procedures to assess effectiveness, but does not prescribe a universal internal audit calendar.

Define the audit question

An internal review should begin with the risk or assurance question it needs to answer. For example, a review of privileged access should establish whether rights are approved, restricted, regularly checked and removed when no longer needed. Merely confirming that an access-control policy has been approved would not answer whether those controls operate.

Determine the services, legal entities, networks, information systems and review period in scope. Map the relevant NIS2 Article 21 control areas to the organisation's risk assessment. Include significant outsourced processes when they affect the security of covered services, but record any evidence or contractual access limitations.

Plan assurance with appropriate independence

An internal audit function needs sufficient competence and objectivity to challenge control owners. If a small organisation lacks a separate audit team, it can introduce safeguards such as peer review, external specialist support and management oversight. Describe those limitations openly rather than claiming complete independence.

Agree test methods before collecting evidence. Interviews establish how a process is intended to operate, while configuration snapshots, ticket records, incident timelines and access logs can show its actual performance. Different questions need different samples; a brief sample of routine activity cannot prove behaviour during an emergency.

Test design and operation separately

Design effectiveness asks whether a documented measure is capable of reducing the stated risk. Operating effectiveness asks whether it performed over the period examined. A vulnerability remediation process might assign owners and deadlines while leaving urgent findings unresolved in practice.

For a backup control, inspect retention and access restrictions, then review restoration results. For supplier risk, examine not just questionnaires but also the decisions made when vendors reported weaknesses. Record excluded systems, incomplete logs and other limits on the conclusion.

Write findings that lead to correction

Every material finding should state what was expected, what was observed, the supporting evidence and why the difference matters to the relevant service. Avoid calling every process weakness a legal breach without analysing the applicable national implementing law and any sector-specific requirements.

Assign a responsible owner and a realistic remediation date. Management reporting should distinguish high-impact exposure, overdue tasks and unresolved evidence gaps. Close findings on the basis of a follow-up assessment, not solely when the remediation ticket changes status.

Maintain a defensible audit trail

Retain the approved scope, methodology, samples, evidence references, assessor identity, report, management response and verification of remediation. Protect sensitive audit artefacts because configuration evidence and identified vulnerabilities may themselves create security risk.

Use audit results to update the effectiveness assessment programme. Repeated access failures might justify more frequent access reviews, while a major change in infrastructure may require testing beyond the normal schedule. National laws and supervisory guidance should be checked for any additional audit obligations.

Points of clarification

Is this exact testing method compulsory for every NIS2 entity?

No universal method or timetable follows from Article 21(2)(f) alone. Assess the risk and confirm national or sector-specific requirements.

Can an assessment report alone demonstrate compliance?

A report supports assurance only within its documented scope. Operational records, remediation and other legal obligations still need attention.

What should the organisation retain?

Retain the scope, authorisation, methods, evidence references, findings, responsible owners and verified corrective actions under appropriate security controls.

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.