Build evidence around specific obligations and risks
Begin with the services and legal entities within the NIS2 scope assessment. Connect each relevant risk-management measure to an owner, the affected network and information systems, a procedure and evidence that it operates. Article 21(2)(f) specifically addresses policies and procedures for evaluating the effectiveness of cybersecurity risk-management measures.
Separate the underlying legal obligation from an internal framework mapping. ISO 27001 records and other security certifications may help, but cannot automatically establish compliance with every NIS2 provision. Check Member State implementing law and any applicable sector-specific measures before defining a mandatory record set.
Keep evidence that shows controls operating
Policies, approvals and risk registers explain intended controls. Operating records can show whether measures worked: completed access reviews, incident response timelines, restoration tests, vulnerability remediation records and supplier due diligence decisions. An auditor should be able to distinguish a prescribed process from proof it was followed.
For each artefact, record the date, relevant service, responsible team, control objective, source system and retention location. Include samples from the review period rather than relying entirely on screenshots taken immediately before an audit.
Make conclusions traceable and reproducible
Assessment records should specify methodology, scope, sampling criteria, test results, limitations, findings and follow-up. An evidence index can connect the assessment to authoritative source documents without circulating multiple outdated copies.
Preserve versions where decisions have changed. If a finding was closed following a configuration update, retain the original failure and subsequent verification. Avoid replacing failed test evidence with only a favourable retest result, which obscures the corrective history.
Protect sensitive records and control retention
Security audit artefacts may contain internal topology, vulnerability details, system configurations or personal information. Restrict access, minimise unnecessary copies and establish proportionate retention according to applicable law and organisational policy. An evidence pack should not become a new repository of exposed credentials.
Where a supplier holds records, agree how they can be requested or inspected without breaching contractual or data-protection requirements. Document gaps where evidence could not be obtained, together with the risk decision and action owner.
Prepare for questions about effectiveness
Reviewers may ask how critical systems were selected, how tests represent normal operating conditions, who accepted residual risk and whether remediation was verified. Prepare a clear chain from risk to measure, test, result, corrective action and management oversight.
Periodically confirm that links and records still exist and that the evidence inventory reflects new infrastructure, incidents or organisational changes. The objective is reliable assurance, not the maximum number of files.
Points of clarification
Does NIS2 require every entity to use the same audit evidence checklist?
No. The Directive provides the common framework, while applicable national and sector-specific rules and the organisation's risks affect the evidence required.
Can policies alone demonstrate that controls work?
No. Operating records and relevant assessments help establish whether measures function as intended.
Should unsuccessful tests be retained?
Yes, subject to applicable retention and security rules. Keep findings and the evidence used to verify corrective actions.