Determine the legal basis for an audit
Essential entities may face proactive supervisory measures under Article 32. For important entities, Article 33 generally provides for ex post measures after indications or evidence of non-compliance.
A supervisory audit should be distinguished from an internal audit, commercial certification assessment or routine customer assurance review. They have different purposes and legal authority.
Identify scope and competent authority
Confirm the legal entity, services, jurisdiction, supervisory notice and relevant statutory powers. Establish an internal point of contact and a process for handling requests for records or access.
Do not presume that every cybersecurity regulator has jurisdiction over every group member or that one inspection covers all affiliates.
Prepare traceable evidence
Useful records may include asset and service inventories, Article 21 risk-management decisions, policies, implementation tests, supplier assessments, incident reporting assessments and unresolved remediation.
Organise documents by control and accountable owner. Mark sensitive material appropriately and maintain reliable version history.
Coordinate technical and management interviews
Ensure factual explanations of who approved controls, how changes operate and what was tested. Where evidence is incomplete, describe the limitation and improvement plan instead of inventing conclusions.
Preparedness does not require rehearsed claims. It requires responsible staff to understand their processes and the relevant records.
Handle findings and corrective directions
Record the precise finding, applicable requirement, deadline, remediation owner and method of verifying closure. Escalate orders and requests that may carry legal consequences.
Under the Directive, supervisory and enforcement powers are exercised subject to proportionality and the national legal framework. Procedural rights and appeals require jurisdiction-specific assessment.
Use audit outcomes to improve effectiveness
Examine systemic causes such as gaps in asset ownership, unsupported technology or unclear incident responsibilities. Track improvements and retests rather than merely closing an audit spreadsheet.
No universal regulator-run annual audit cadence exists for all NIS2 entities. Check national rules and the actual classification before describing audit frequency as mandatory.
Questions on the text
Does every covered entity have identical requirements?
No. The applicable duties depend on the entity, relevant provisions and national implementation.
Can internal policies alone establish compliance?
No. They should be supported by evidence of implementation, effectiveness and appropriate oversight.