Distinguish commissioned assurance from supervision
Organisations may engage a specialist firm to examine security controls, evaluate a particular system or challenge an internal assessment. That commissioned work is different from an inspection or audit ordered by a competent authority under national NIS2 law.
The Directive gives authorities different supervision and enforcement powers for essential and important entities under Articles 32 and 33. Before describing an external review as mandatory, identify the legal provision, competent authority instruction or contractual condition that creates the obligation.
Select the right scope and expertise
Define which services, facilities, cloud resources, suppliers and control areas are in scope. A governance reviewer might examine risk decisions, management oversight and incident exercises. A technical firm might inspect network segregation or run an authorised penetration test. No single speciality substitutes for both.
Assess the provider's competence, independence, handling of confidential information and potential conflicts of interest. Ensure the engagement specifies approval requirements, testing windows, access restrictions, evidence retention and communication routes for urgent findings.
Specify the evidence needed
A clear engagement letter should identify the audit criteria, examination period, sampling approach, systems excluded and expected deliverables. Ask for findings linked to identifiable risks and observed evidence, not just a numerical grade or badge.
An external certification may be useful evidence for part of a programme but cannot by itself establish full compliance with every NIS2 duty. Auditors should document limits caused by unavailable logs, inaccessible third-party environments or unfinished remediation.
Review findings against actual risk
Prioritise audit findings according to the services affected, likelihood of exploitation and potential impact. A missing control on a public-facing administration interface can merit faster attention than an equally labelled issue on an isolated test asset.
Resolve disagreements using evidence and explicit risk decisions. Management should understand residual risk after any proposed compensating measure, rather than treating acceptance of an audit report as acceptance of every unresolved issue.
Verify remediation and preserve records
Assign owners, target dates and retest methods when findings are accepted. Retests should address the failure mode originally observed; a statement that a new policy was published cannot verify that an exposed service is no longer vulnerable.
Keep reports, test permissions, corrective-action decisions and verification evidence under controlled access. Reassess the audit programme after significant incidents or technology changes, and check national or sector-specific guidance before setting binding review intervals.
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.