Start hereIdentify applicable jurisdictions and entity class
~105 days leftOpen step
Guide library
Regulation Europe

NIS2

Network and Information Systems Directive · Directive (EU) 2022/2555

Identify your national implementation and prepare governance, security controls and incident reporting.

Who it applies to

Essential and important entities under national laws implementing NIS2, based on sector, size and specific designation or exceptions.

What you’ll produce

Documented security risk management and reporting, aligned to national transposition and authorities.

Use each applicable member state’s implementing law. Sector and national reporting rules can affect recipients, scope and timing.

Check official publications for this guide
TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

Which national implementation applies to each entity?
Document sectors, size, country-specific triggers, jurisdiction and any sector rules. Have local Legal confirm covered entities and registration or reporting instructions.
Who will approve the cybersecurity measures?
Put relevant management bodies on the approval and oversight schedule. Fund priority gaps in exposed systems, supply chain, backups and incident response, and make time for required management training.
Can local staff report a significant incident?
Name a local responder and backup per entity. Define how Security, Legal and Communications coordinate facts and deadlines for the relevant CSIRT or authority.

How to spend the first week

  1. Have local entity owners bring activities, size, jurisdictions, suppliers and dependencies. Validate each national law and competent authority.
  2. Choose a service disruption scenario and trace where it would be detected, who classifies it and which authorities could be involved.
  3. Present management with prioritized control gaps, accountable teams, staffing needs and the first exercise date.

What to review each week

Report covered entities with outstanding registration, gaps in priority controls, critical suppliers without a review and reporting exercises with overdue follow-up.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

NIS2 kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Identify applicable jurisdictions and entity class · Legal + management body [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Have local entity owners bring activities, size, jurisdictions, suppliers and dependencies. Validate each national law and competent authority.
2. Choose a service disruption scenario and trace where it would be detected, who classifies it and which authorities could be involved.
3. Present management with prioritized control gaps, accountable teams, staffing needs and the first exercise date.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
DATES AND TRIGGERS

Official milestones

See the deadline calendar
The whole journeyabout 105 days across 4 steps
  1. 01Identify applicable jurisdictions and entity classLegal + management body · ~21 days
  2. 02Implement governance and risk measuresManagement body + CISO · ~42 days
  3. 03Build significant incident workflowsIncident response + legal · ~21 days
  4. 04Exercise and maintain complianceSecurity operations + internal audit · ~21 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 11 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Identify applicable jurisdictions and entity classLegal + management bodyAt initiationSet a start dateCountry-by-country scope matrix; Authority registerOpen
Implement governance and risk measuresManagement body + CISOBefore applicable national deadlinesSet a start dateApproved risk program; Training evidence; Supplier controlsOpen
Build significant incident workflowsIncident response + legalAt incident and in exercisesSet a start dateEscalation tree; Incident classification; Reporting templatesOpen
Exercise and maintain complianceSecurity operations + internal auditOngoingSet a start dateTabletop evidence; Audit report; Corrective actionsOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Identify applicable jurisdictions and entity class

    Who Legal + management body When At initiation

    Map services and establishments, sector, size and national transposition. Determine competent authority and registration duties.

    How to do this step

    Before you start

    Entity chart, service locations, activities, size information and national implementing law.

    1. List activities by entity. Check sector, size and special inclusion criteria, then confirm applicable jurisdiction and classification with local Legal.
    2. Check sector-specific legislation and national deadlines. Record the authority, registration route, reporting channel and the basis for any scope decision.
    3. Obtain local approval of the decision and set a trigger to revisit it when services, legal entities, laws or geography change.

    What a reviewer should see

    A country row includes the entity, activity, current legal basis, authority, classification, registration owner and last verification.

    When to escalate

    Escalate conflicting jurisdiction interpretations or an entity whose registration and reporting requirements remain unclear.

    What to produce

    Country-by-country scope matrixSpreadsheet

    Gather first

    • Official rules or contract and version
    • Product, organization or processing facts
    • Jurisdiction and exception criteria

    How to prepare it

    1. Start with one row per rule, decision or authority. Record the citation, scope test and facts that determine whether it applies.
    2. Distinguish a confirmed decision from an open question. Record the obligation, any exception or approved route, owner and timing.
    3. Have technical and legal or program owners review the decision against the source. Revisit on a new market, product change or rule update.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement or decision
    REG-05, determine whether the new processing activity requires an assessment.
    Source and trigger
    Current regulator guidance, high-risk processing indicators
    Facts and evidence
    New dataset includes sensitive attributes. Data map P-024.
    Outcome and rationale
    Assessment required before release. Privacy lead to confirm scope.
    Owner and review
    Product privacy owner, reassess before launch and on new purposes.

    Check before handing it over

    A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.

    Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.

    Authority registerSpreadsheet

    Gather first

    • Official rules or contract and version
    • Product, organization or processing facts
    • Jurisdiction and exception criteria

    How to prepare it

    1. Start with one row per rule, decision or authority. Record the citation, scope test and facts that determine whether it applies.
    2. Distinguish a confirmed decision from an open question. Record the obligation, any exception or approved route, owner and timing.
    3. Have technical and legal or program owners review the decision against the source. Revisit on a new market, product change or rule update.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement or decision
    REG-05, determine whether the new processing activity requires an assessment.
    Source and trigger
    Current regulator guidance, high-risk processing indicators
    Facts and evidence
    New dataset includes sensitive attributes. Data map P-024.
    Outcome and rationale
    Assessment required before release. Privacy lead to confirm scope.
    Owner and review
    Product privacy owner, reassess before launch and on new purposes.

    Check before handing it over

    A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.

    Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.

  2. 02

    Implement governance and risk measures

    Who Management body + CISO When Before applicable national deadlines

    Approve controls for incidents, continuity, suppliers, vulnerability handling, access and encryption. Track proportionality and management training.

    How to do this step

    Before you start

    Approved entity scope, national requirements, control inventory, supplier contracts and management calendar.

    1. Link each applicable measure to a service owner, implementation and retained evidence. Rank gaps by business impact and exposure.
    2. Have local or group management approve the measures and resource decisions as applicable. Schedule training and retain agenda and participation records.
    3. Walk one critical supplier dependency, its security protections, notification obligations and fallback. Assign gaps and request evidence from the supplier.

    What a reviewer should see

    The approved risk program links a supplier outage risk to current tests, supplier terms, mitigation owners and management approval.

    When to escalate

    Raise a high-impact risk without a funded owner or a supplier that cannot meet your reporting or recovery needs.

    What to produce

    Approved risk programMemo

    Gather first

    • Approved scope
    • Governing requirements and risks
    • Teams, service dependencies and review gates

    How to prepare it

    1. State the objective, scope, accountable owner and conditions that trigger action. Translate commitments into tasks with periods, thresholds and evidence.
    2. For each task set the input, decision rule, output and handoff. Include escalation for failures and approvals for exceptions.
    3. Walk through one real case with owners and reviewers. Approve the version, schedule review, and check that promised tasks have operational records.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Purpose
    Identify failed production backup jobs and restore service data.
    Scope
    Production billing databases and backup vault
    Activity and timing
    On-call reviews daily job alerts and runs a quarterly restore test.
    Evidence and exception
    Keep job records and restore test output. Page the service owner if a job fails.
    Owner and approval
    Operations lead owns. Service owner approves.

    Check before handing it over

    A person who receives the plan can tell when to act, what to check and where to save the result.

    Give the approved plan to the people responsible for operation. Add dated checkpoints to the working calendar.

    Training evidenceSpreadsheet

    Gather first

    • Control descriptions and test request
    • Source system records
    • Defined period and evidence access rules

    How to prepare it

    1. Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
    2. Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
    3. Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Evidence ID
    EV-021
    Control or request
    AC-04, October administrator review
    Period and scope
    1 to 31 Oct 2026 UTC, production tenant
    Source and capture
    IAM export filtered to active elevated roles
    Link or record ID
    Restricted workpaper EV-021 plus ticket IAM-114
    Reviewer and status
    Security assurance, verified

    Check before handing it over

    A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.

    Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.

    Supplier controlsSpreadsheet

    Gather first

    • Applicable criteria, requirements or risk decisions
    • Current procedures and configurations
    • Names of people operating or reviewing each control

    How to prepare it

    1. Give each requirement and implemented control an ID. Write a short control statement naming who does what, when and in which system.
    2. Record the evidence the control produces and how it could be tested. For a shared or inherited control, state who owns each part.
    3. Walk through one control with its operator. Check a real recent run, record gaps and obtain approval for exclusions or alternate controls.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement
    Production access is reviewed periodically.
    Control ID
    AC-04
    Control activity
    IAM team exports administrator roles every quarter. System owners approve or revoke each assignment.
    Owner and frequency
    IAM lead, quarterly
    Evidence
    Export with filters, annotated review and removal tickets
    Test and status
    Reconcile export to current roles. Inspect approvals. Operating.

    Check before handing it over

    A different person can operate the control or test it using the matrix and its evidence links.

    Give the baseline to control owners and the assessor before walkthroughs or sampling.

  3. 03

    Build significant incident workflows

    Who Incident response + legal When At incident and in exercises

    Configure early-warning, notification, interim and final reporting with the local CSIRT or authority. Track when the entity became aware.

    How to do this step

    Before you start

    Incident criteria by entity and service, legal references, logging, on-call roster and current authority contacts.

    1. Capture when the team became aware of the incident, what it knew and which services and entities were affected. Apply the relevant significance criteria.
    2. Map early warnings, notifications and follow-up to national and sector requirements. Article 23 sets a 24-hour early warning and, generally, a 72-hour notification for significant incidents, with separate final report rules.
    3. Stage an after-hours drill. Prepare a first report with available facts, agree who files it and retain the receipt or exercise proof.

    What a reviewer should see

    The exercise shows a timestamped classification decision, qualified authority channel, prepared reports and a backup able to file.

    When to escalate

    Alert the appropriate incident and legal leads as soon as a potentially significant incident is identified. Track local deadlines while facts are still developing.

    What to produce

    Escalation treeMemo

    Gather first

    • Named roles, on-call contacts and authority
    • Realistic use cases and deadlines
    • Service and vendor dependencies

    How to prepare it

    1. Start with the event or decision and identify who acts first, who has approval authority and who covers absences.
    2. Write the sequence of handoffs and the information each recipient needs. Name the channel, timing and escalation if no one responds.
    3. Rehearse a case and record what broke. Fix missing contacts, duplicate ownership or gaps before approving the playbook or role map.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Event or activity
    Unusual activity detected in support export portal
    First action and owner
    On-call engineer opens a restricted incident case and preserves logs.
    Decision owner and backup
    Privacy lead or legal duty contact will determine reporting.
    Handoff and clock
    Send incident ID, UTC timestamp and known scope immediately.
    Validation
    Exercise completed and backup contact reached.

    Check before handing it over

    Every decision has one accountable person, a backup and a practical route to reach them.

    Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.

    Incident classificationSpreadsheet

    Gather first

    • Alert or breach report
    • Investigation facts and relevant thresholds
    • Escalation contacts and official reporting clocks

    How to prepare it

    1. Start a case with UTC timestamps for detection, awareness, assessment and containment. Keep known facts separate from estimates and update both as evidence changes.
    2. Identify affected systems, people, data and likely harms. Link your classification, notice decision and the rule that starts each clock.
    3. Record containment, preservation, escalation and notification actions. Capture who approved the decision and set a time to confirm outstanding facts.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Incident ID
    INC-041
    Awareness and facts
    2026-11-13 09:20 UTC. Export link exposed to an unauthorized account.
    Scope and uncertainty
    One confirmed access. Log review for further recipients in progress.
    Decision and reason
    Privacy lead to assess reporting threshold with counsel by 10:30 UTC.
    Actions and status
    Access revoked, logs preserved, next review at 12:00 UTC.

    Check before handing it over

    Timelines distinguish different events and a reviewer can reconstruct the reporting decision from the available facts.

    Give the incident lead and privacy decision maker a time-stamped update. Preserve working evidence separately.

    Reporting templatesMemo

    Gather first

    • Incident case facts and awareness timestamps
    • Current authority forms and applicable notification criteria
    • Approved recipients and counsel or incident lead

    How to prepare it

    1. Identify the recipient and required fields. Prepare a concise account of what happened, data and people affected, likely consequences, protective steps and an official contact.
    2. Mark unknown facts and state how they will be updated. Confirm recipients and secure delivery or required portal before sending.
    3. Obtain the prescribed approval. Keep the sent version, delivery receipt and any follow-up or supplement with the case.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Recipient and reference
    Approved authority or affected person, incident INC-041
    What happened
    An account viewed a link beyond its permissions. Investigation continues.
    Likely effect and protection
    Access was revoked. Review your recent account activity and contact support for help.
    Contact and update
    Approved incident contact, updated facts after log review
    Approval and record
    Privacy lead approved, receipt recorded in case file

    Check before handing it over

    Use the applicable authority’s language and official portal where required. Every material factual statement can be traced to the case.

    Have the authorized notifier submit through the official channel and add the receipt and follow-up date to the incident log.

  4. 04

    Exercise and maintain compliance

    Who Security operations + internal audit When Ongoing

    Test reporting and recovery, review third parties, close findings and adapt to local rule changes.

    How to do this step

    Before you start

    Last exercise and audit results, training records, management actions and service or law changes.

    1. Run different incident scenarios across covered entities, including a supplier that provides incomplete information.
    2. Record observed timelines and gaps, assign corrective actions and retest the failed handoff or control.
    3. Bring overdue actions and significant remaining risk to management. Recheck national registrations and authority details after structural changes.

    What a reviewer should see

    The corrective action links the original failed handoff to a dated retest and approval, with local roles and contacts updated.

    When to escalate

    Raise unresolved risks that threaten essential services or repeated missed escalation targets.

    What to produce

    Tabletop evidenceMemo

    Gather first

    • Approved scenario and participant roles
    • Goals and scoring criteria
    • Event timeline and expected records

    How to prepare it

    1. Prepare a scenario and timed new information that tests decisions, handoffs and evidence. Assign a facilitator and separate observer.
    2. During the exercise, note what participants actually did, the timestamps and where expected responses failed. Distinguish simulated actions from real ones.
    3. Write a short after-action summary with owners, deadlines and a retest plan. Attach the scenario, attendance and evidence references.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Scenario
    Simulated export leak found at 09:20 UTC
    Objective
    Reach operational and legal leads and classify the incident within the exercise target.
    Observed behavior
    Engineering preserved logs. Initial escalation went to an inactive mailbox.
    Action and owner
    Privacy operations updates the routing list before 2026-12-01.
    Retest
    Repeat the handoff in the next on-call drill.

    Check before handing it over

    An absent participant can see what was tested, what happened and why an action was assigned.

    Send approved findings to action owners and file the record for governance or assessment.

    Audit reportMemo

    Gather first

    • Approved test scope and criteria
    • Population and sample records
    • Test approach, results and reviewer requirements

    How to prepare it

    1. State objective, dates, scope and the method before describing results. Record the tester, any independence requirements, and how samples were selected.
    2. For each item, compare what should have happened with what the evidence shows. Describe impact and link the evidence or recorded exception.
    3. Add limitations, obtain review and give each finding an owner and a date. Retain the underlying samples and calculations with the signed version.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Test objective
    Check that production role removals happen within the internal deadline.
    Method and population
    All September departures. Test each privileged account.
    Expected result
    Remove access within one business day.
    Observed result
    11 on time. One late by two days, ticket IAM-114.
    Finding and follow-up
    F-008. Retest the next departure and verify alerting.

    Check before handing it over

    Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.

    Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.

    Corrective actionsSpreadsheet

    Gather first

    • Finding, risk or test exception
    • Root-cause analysis
    • Named owner, due date and expected evidence

    How to prepare it

    1. Record the observation and link the exact test or requirement. Describe the business effect and investigate why the issue was able to happen.
    2. Separate immediate containment from the permanent fix. Give each action an owner, date, verification method and any required approval for deferral.
    3. Retest against the original failure once the fix is live. Record who accepted the outcome and keep unresolved issues visible.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Finding or risk
    F-008, a departed contractor retained production access
    Cause and effect
    HR event never reached IAM. Admin access remained active.
    Action and owner
    Revoke access and alert on failed HR sync. IAM lead.
    Due and status
    2026-11-28, in progress
    Closure test
    Simulate departure and verify access disappears within policy
    Approver and evidence
    Risk owner, ticket IAM-114 and retest results

    Check before handing it over

    The closure test addresses the original problem and has a dated result from an independent reviewer where required.

    Send open items and decisions to governance, audit or the assessor on the applicable cadence.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes