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.
HomeArticlesCreating Evidence for Technical Security Controls Under NIS2
Cryptography Access Assets Physical Security / 2026-10-10

Creating Evidence for Technical Security Controls Under NIS2

Evidence for NIS2 technical security controls should connect a documented cybersecurity risk to the selected safeguard, its implementation, an assessment of its effectiveness and any necessary corrective action. A collection of policy files alone does not prove that controls function in operation.

Start with a traceable risk-to-control relationship

Identify the legal entity and regulated services, the systems supporting them and the risks being managed. For each material control, record its objective, responsible owner and the NIS2 measure area it supports.

Article 21(2)(f) refers to policies and procedures assessing the effectiveness of cybersecurity risk-management measures. Other relevant parts of Article 21 include cryptography, access control and asset management. National measures may add evidence expectations.

Keep implementation records that can be checked

Useful examples include approved access requests, current configuration baselines, encryption coverage, key ownership and asset inventories. Each artefact should indicate its system, relevant period, source and responsible custodian.

A screenshot without a date, asset identifier or surrounding context may not demonstrate the intended control. Use controlled references to source systems where possible and avoid duplicating sensitive infrastructure details in widely shared audit packs.

Collect operating and test evidence separately

A control's design may be appropriate while its operation is inconsistent. Check actual account removal, selected encryption settings, certificate renewals, backup restoration and environmental alert escalation, using methods suited to the risk.

Document scope, sample selection, test procedure, result and limitations. Record any systems excluded because of safety, provider restrictions or unavailable data, and explain how those gaps affect assurance.

Follow findings through to verified correction

Record observed weaknesses, affected services, significance, mitigation, owner and target date. Preserve the original evidence as well as proof of remediation, because a completed change ticket does not necessarily establish that the weakness is resolved.

Use repeat testing or other suitable verification to close findings. Escalate recurring issues and unresolved material exposure to management with context about residual risk.

Organise records securely for review

Maintain an index linking obligations, risks, controls, supporting records and last assessment dates. Apply appropriate access restrictions, retention periods and integrity protections, since evidence may expose privileged configurations or vulnerability details.

Review the index when services, technology or legal requirements change. Where an external provider controls records, document the contractual evidence route and any limitations. The objective is clear and reproducible assurance, not the greatest possible volume of documentation.

Points of clarification

Does NIS2 prescribe the same technical configuration for every covered organisation?

No. Appropriate measures depend on identified risk, relevant services, Member State law and any applicable sector-specific requirements.

Can a policy alone prove that a technical control works?

No. Relevant implementation records and effectiveness assessments provide stronger assurance.

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.