How do we…
How do we get ready for a NIS2 supervisor's request for evidence?
Add to board memoOpen the memo
The short answer
- Recommendation
- List every record a NIS2 supervisor may ask for, across scope and registration, the management body, the ten measures, incident reporting and supervision. Check each one exists, is complete and current, and could be handed over in time, and raise a gap in your own tracker for every item that is not fully ready.
- Reasoning
- A competent authority may ask for your documented cybersecurity policies, access to data and documents, and evidence that the policies are implemented. So be ready with both the policies and the records that show them working. An essential entity can be asked at any time; an important entity is supervised after the event, when there is evidence or an indication that it does not comply. A request can come while you are still handling an incident, so the set has to be current all year (NR-11). Every gap that is known has an owner and a due date (NR-09).
- Considerations
- The 5 working days to produce any item and the six-monthly check are the pack's defaults (NR-11, NR-08). Set them to suit your authority; national law may add documents to the list.
- For a financial entity, the pack says DORA applies instead of NIS2's risk-management and reporting duties. Confirm with counsel which NIS2 items give way, and keep every item until they do.
- A record can be ready while its measure still has an open gap. Using a template, or an ISO/IEC 27001 control, does not by itself show that a NIS2 measure is met.
- Where a service provider holds a record, it counts only if you can obtain it in time. Put that right in the contract.
The decision, step by step
Select any step for the reasoning behind it and where the pack covers it.
- Start
- Step
- Decision
- Outcome
Keyboard: Tab to a step, arrow keys move along the flow, Enter pins its explanation, + and − zoom, 0 fits the diagram, Esc closes. The text version below has the same content.
Where a step quotes a number, it is the default in the CISO Times pack. Your own standard may set a different one.
Read as text
The same flow written out: each step, its reasoning and where the pack covers it. 18 steps.
Start
A NIS2 supervisor may ask us for evidence
NIS2 lets a competent authority inspect, audit, scan and request information, including your documented cybersecurity policies, access to data and documents, and evidence that the policies are implemented. So be ready with both: the policies, and the records that show them working. National law may add to what the authority can ask for.
In the pack
- P12-A07 NIS2 Documentation & Evidence ChecklistSupervisor Requests
- P12-A07 NIS2 Documentation & Evidence ChecklistInstructions
Decision
Is your scope and classification decided in writing?
Everything that follows depends on whether you are essential or important, and the scope assessment is itself the first record a supervisor asks for. It counts when it gives each answer with its source and reasoning, was confirmed with counsel, approved by the management body, and reviewed within the last 12 months or since the last trigger.
- Yes: Does DORA apply instead of some NIS2 duties?
- No, or not known: Settle scope and classification first
In the pack
- P12-A04 NIS2 Readiness Self-AssessmentInstructions
- P12-A04 NIS2 Readiness Self-AssessmentAssessment (rule NR-01)
Outcome
Settle scope and classification first
Run the scope assessment, have counsel confirm it, and take it to the management body before you build the evidence set. Without it you cannot say how a supervisor would approach you, and the first item on the checklist is missing.
In the pack
- P12-A02 NIS2 Scope & Entity Classification AssessmentInstructions (rule NR-01)
Decision
Does DORA apply instead of some NIS2 duties?
For a financial entity, the pack says DORA applies instead of NIS2's risk-management and reporting duties, and to confirm that with counsel. If you are not sure, keep every NIS2 item on the list until counsel confirms which ones give way.
- Yes: a financial entity: Use your DORA register for the items DORA covers
- No, or not known: Are you an essential or an important entity?
In the pack
- P12-A07 NIS2 Documentation & Evidence ChecklistInstructions
- P12-A03 NIS2 Article 21 Measure-to-Control Mapping LibraryInstructions
Step
Use your DORA register for the items DORA covers
Where DORA applies instead of NIS2's risk-management and reporting duties, the pack says to use your DORA register of documents for them. With counsel, mark those NIS2 items not applicable, with that reason, and assess them against DORA. Keep the rest of the list.
In the pack
- P12-A07 NIS2 Documentation & Evidence ChecklistInstructions
- P12-A04 NIS2 Readiness Self-AssessmentInstructions
Decision
Are you an essential or an important entity?
The same documents answer both. What differs is when a supervisor is likely to ask. An essential entity is supervised before and after the event: on-site inspections, regular, targeted and ad hoc audits, scans and requests for information. An important entity is supervised after the event, when the authority has evidence or an indication that it does not comply.
- Essential: Be ready at any time, not only after an incident
- Important: Expect the request after a complaint, incident or indication
In the pack
- P12-A07 NIS2 Documentation & Evidence ChecklistSupervisor Requests
- P12-A07 NIS2 Documentation & Evidence ChecklistDefinitions
Step
Be ready at any time, not only after an incident
A request can come without warning, so the evidence set has to be current all year, not assembled when a letter arrives. The pack also tells an essential entity to treat gaps where a measure is in place but not yet operating as urgent, because a supervisor would find them as soon as it asks.
In the pack
- P12-A07 NIS2 Documentation & Evidence ChecklistSupervisor Requests
- P12-A04 NIS2 Readiness Self-AssessmentInstructions
Step
Expect the request after a complaint, incident or indication
Supervision of an important entity follows evidence or an indication that it does not comply, such as a complaint or an incident. A request could come while you are still handling that incident, so prepare the set in advance in the same way.
In the pack
- P12-A07 NIS2 Documentation & Evidence ChecklistSupervisor Requests
Step
List the records a supervisor may ask for
The pack's checklist has 18 items in five areas: scope and registration; the management body's approval, oversight and training; one item for each of the ten risk-management measures; incident reporting; and supervision, such as your self-assessment and the results of any security audit. Add anything your national law asks for. A small organisation may answer several items with one document; name it against each. A group may rely on a parent's record if it says where its copy is.
In the pack
- P12-A07 NIS2 Documentation & Evidence ChecklistChecklist
- P12-A07 NIS2 Documentation & Evidence ChecklistInstructions
Step
For each measure, name what you could show
For each of the ten measures, name the policies, procedures and records that put it in place for you, and one owner. The test is what you could hand over today. The pack does not say that any ISO/IEC 27001 control or NIST CSF outcome meets a NIS2 measure, and using a template does not by itself show that a measure is met. Size each measure to the risks your risk assessment shows.
In the pack
- P12-A03 NIS2 Article 21 Measure-to-Control Mapping LibraryMeasure Library (rule NR-06)
- P12-A03 NIS2 Article 21 Measure-to-Control Mapping LibraryInstructions
- P12-A03 NIS2 Article 21 Measure-to-Control Mapping LibraryArticle 21
Decision
Can this item apply to you?
Take each item in turn. Answer no only where it cannot apply, for example audit results when no security audit has been carried out or asked for, and write down the reason. When you are unsure, treat the item as applying.
- No: it cannot apply: Mark it not applicable, with the reason
- Yes, or not sure: Does the record itself exist?
In the pack
- P12-A07 NIS2 Documentation & Evidence ChecklistInstructions
Step
Mark it not applicable, with the reason
The reason is part of the evidence: a supervisor who sees an item marked not applicable will ask why. Check it again at the next review, because it can start to apply, for example once an audit is ordered.
In the pack
- P12-A07 NIS2 Documentation & Evidence ChecklistChecklist
Decision
Does the record itself exist?
Open the record and look; do not rely on what people say. A draft, or only part of the record, is a partial answer. Nothing at all makes the item not ready.
- Yes: Is it complete and current?
- Partly, no, or not known: Not fully ready: raise a gap in your tracker
In the pack
- P12-A07 NIS2 Documentation & Evidence ChecklistInstructions
- P12-A04 NIS2 Readiness Self-AssessmentInstructions
Decision
Is it complete and current?
Complete and current means it covers the whole item and is up to date: approved, within its review date, with records kept to date. Anything missing or out of date makes it partly ready.
- Yes: Could its owner hand it over within 5 working days?
- Partly, no, or not known: Not fully ready: raise a gap in your tracker
In the pack
- P12-A07 NIS2 Documentation & Evidence ChecklistInstructions
Decision
Could its owner hand it over within 5 working days?
The 5 working days is the pack's default, to set to suit your authority's usual deadlines. The owner must know where the record is. Where a service provider holds it, it counts only if you can obtain it in time, so put that right in the contract.
- Yes: Ready: keep it current, with one named owner
- Partly, no, or not known: Not fully ready: raise a gap in your tracker
In the pack
- P12-A07 NIS2 Documentation & Evidence ChecklistSupervisor Requests (rule NR-11)
- P12-A07 NIS2 Documentation & Evidence ChecklistInstructions
Step
Ready: keep it current, with one named owner
Name one owner who keeps the record current and would hand it over, and say where it is kept. A record can be ready while its measure still has an open gap: the checklist asks whether a supervisor could be handed the record, and the self-assessment asks whether the measure works in full.
In the pack
- P12-A07 NIS2 Documentation & Evidence ChecklistInstructions
- P12-A07 NIS2 Documentation & Evidence ChecklistChecklist
Step
Not fully ready: raise a gap in your tracker
Every item partly ready or not ready goes into your gap tracker with one owner, a priority, a due date and the change that closes it, and is corrected without undue delay. Put the gap's ID against the item, so the evidence set shows the gap is known and owned.
In the pack
- P12-A07 NIS2 Documentation & Evidence ChecklistInstructions (rule NR-09)
- P12-A08 NIS2 Gap & Remediation TrackerInstructions
Outcome
Sign off, and repeat with each self-assessment
The evidence set is in order when every item that applies has an owner and is ready, or has its gap in the tracker. The NIS2 lead checks it and an executive sponsor accepts it. Repeat the check with each readiness self-assessment, at least every 6 months by the pack's default, and after a significant incident or a change in scope.
In the pack
- P12-A07 NIS2 Documentation & Evidence ChecklistResults
- P12-A04 NIS2 Readiness Self-AssessmentInstructions (rule NR-08)
Practical checklist
- Confirm the scope and classification decision is written, confirmed with counsel and approved by the management body.
- With counsel, mark the items DORA covers instead, if you are a financial entity, and keep the rest.
- List the records a supervisor may ask for in the five areas, adding anything your national law asks for.
- For each of the ten measures, name the policies, procedures and records you could hand over today, with one owner.
- Mark an item not applicable only where it cannot apply, and write down the reason.
- Open each record and check it exists, is complete and current, and could be handed over in time.
- Raise a gap in your tracker for every item partly ready or not ready, and put its ID against the item.
- Have the NIS2 lead check it and an executive sponsor accept it, and repeat with each readiness self-assessment.
Evidence to have ready
- The approved scope and classification assessment.
- The evidence checklist: each item with its owner, where the record is kept, the date checked and its status.
- The records themselves: policies, management body approvals and oversight, training records, incident reports and audit results.
- The gap tracker entries for every item not fully ready.
- The sign-off by the NIS2 lead and the executive sponsor, and the reason for each item marked not applicable.
Assumptions
- You know whether you are an essential or an important entity, from a written scope decision.
- The 5 working days and the six-monthly check are the CISO Times NIS2 pack's defaults. Your own rules may set others, and national law may add documents to the list.
- The national law, the competent authority and what it usually asks for are yours to confirm with counsel. The pack leaves them as placeholders. This is not legal advice.
Not covered here
- Whether you are in scope, and as essential or important. That is “Is our organisation in scope of NIS2, and as essential or important?”.
- Which gaps are blocking and who must hear about them. That is “When is a NIS2 readiness gap blocking, and who must hear about it?”.
- How to show the management body approved and oversees the measures. That is “How do we show that our management body has approved and oversees our NIS2 measures?”.
Related questions
- Is our organisation in scope of NIS2, and as essential or important?
- When is a NIS2 readiness gap blocking, and who must hear about it?
- How do we show that our management body has approved and oversees our NIS2 measures?
- If we are not sure whether we must register with our NIS2 authority, then what do we do?
- How do we find the minimum control set when DORA, NIS2 and ISO 27001 all apply to us?