← Back to Insights
November 18, 2026 · 6 min read · NIS2 Evidence
What Counts as Evidence for NIS2 Compliance?
When a NIS2 regulator asks "show us you're compliant," most companies hand over a compliance document. A policy. A risk register. An ISO 27001 certificate. The regulator puts it back on the table and asks again: "show us the evidence." The difference between those two moments is where most NIS2 compliance falls apart.
Documentation vs evidence
Documentation says what you do. Evidence proves that it works. The difference:
- Documentation: "We have an access control policy." (A document that says you control access.)
- Evidence: "Here are the IAM permissions, the automated review that flags over-permissioned roles, the access logs reconciled with approved access, and the test results from last quarter." (Proof the control works.)
Every NIS2 measure needs evidence, not documentation. The regulator wants to see that risks are managed, not just described.
What NIS2 regulators actually ask for
When regulators examine your compliance, they're looking for:
- Article 21 measures: Not "we have risk management" but "here's our threat model, here's how each risk is mitigated, here's the test that proves the mitigation works."
- Incident handling: Not "we have an incident response plan" but "here's our last tabletop exercise, here's the detection-to-reporting timeline, here's how we met the 24h/72h deadline."
- Supply chain: Not "we assess our suppliers" but "here's the security verification for each supplier, here's what we tested, here's what we found."
The evidence hierarchy
Not all evidence is equal. Here's what regulators consider strong vs weak:
- Strong: Test results (detection rules fired against simulated attacks), audit logs (actual access reviews with findings), configuration exports (actual IAM rules, firewall policies), metrics (mean time to detect, mean time to respond)
- Medium: Internal audit reports, penetration test reports, vulnerability scan results, supplier security assessments with findings
- Weak: Policy documents, risk registers, training records, meeting minutes. These show intent, not effectiveness.
A policy document is not evidence of compliance. It's evidence of intent. Regulators want evidence of effectiveness — that the control actually reduced the risk. No test result means no evidence.
How to build an evidence file
For each NIS2 measure in your compliance:
- Map it to a technical verification. "We have access control" → "here's the IAM review that proves it."
- Run the verification on a schedule. Not once during audit. Monthly or quarterly. Log each result.
- Record failures and remediation. If the test found a gap, document the fix. Regulators want to see you found and fixed things, not that everything was always perfect.
- Keep timestamps. Evidence without dates is just documentation. "We tested this" is weak. "We tested this on 12 November and here's the result" is evidence.
The evidence file is what you hand the regulator when they ask. It's also what protects management from personal liability if something goes wrong. "Here's what we did and when" is the defence. "We had a policy" isn't.
Questions about NIS2 evidence?
Get in touch. 15-minute call, no obligation.
Get in touch
Aethel Guard is a Netherlands-based security architecture firm serving EU companies of all sizes. Your architect, not your vendor.