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.
HomeArticlesBuilding a 2024/2690 Compliance Matrix
Implementing Regulation 2024 2690 / 2026-10-11

Building a 2024/2690 Compliance Matrix

A Regulation (EU) 2024/2690 compliance matrix links the applicable Annex's cybersecurity measures to responsible owners, operational controls, evidence and remediation tasks. The matrix should also record service scope and the separate incident-significance tests in Articles 3 to 14. It supports assessment and oversight but does not itself establish compliance.

Define the entity and service scope

Record the regulated legal entity and the Article 1 provider category, including any multiple services supplied. Name the relevant competent authority and confirm where national NIS2 procedures apply. If a corporate group uses shared controls, identify which entity is legally accountable and which provider operates the underlying systems. Do not copy the same applicability conclusion across subsidiaries without checking their activities.

Use one row per relevant provision

Capture the Annex section and subparagraph, its requirement in concise language, qualifiers such as where appropriate and the service or system it affects. Add fields for implementation approach, mapped security framework, accountable owner, evidence location, test date, gap rating and follow-up. Keep the official citation in the record so revisions can be assessed without losing the connection to the binding wording.

Distinguish implemented, tested and not applicable

A control's existence, successful operation and applicability are different judgements. Use clear assessment statuses with supporting evidence rather than a single unexplained compliance percentage. Where a qualified provision is not applied, document the comprehensible justification required by Article 2(2). An unresolved requirement should produce an action owner, risk consequence and due date, not an optimistic completed mark.

Add a separate incident-threshold worksheet

Record the provider-specific article in Regulation 2024/2690, the Article 3 common conditions and Article 4 recurring-incident rule where relevant. Identify data required to apply each test, such as affected users, disruption duration, losses or integrity consequences. Assign responsibilities for evaluating evidence, escalating events and completing Article 23 notifications under national processes. Keep threshold mapping current when services change.

Make the matrix part of governance

Have operational teams update evidence and remediation results, with periodic independent review where appropriate. Summarise material gaps, deadlines and exceptions for the management body to meet its Article 20 oversight responsibilities. Retain version history, source dates and decisions. Treat the matrix as a living control register, not a certificate or replacement for tests of real security outcomes.

Points of clarification

Is a spreadsheet itself evidence of NIS2 compliance?

No. It organises obligations and points to evidence that controls operate.

Should incident thresholds appear in the matrix?

Yes, preferably in a separate worksheet connected to provider-specific tests and response procedures.

How often should the matrix be reviewed?

Review it when requirements, services or controls change and at a risk-appropriate regular interval.

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.