Business guides – contracts, HR, AI & compliance

NIS2 supplier breach – incident exercise, 24/72h and restart evidence

Exercise a supplier cyber breach under Swedish NIS2 rules: assess significant impact, document 24/72-hour reporting, rehearse escalation and verify safe restart.
Published Mallbutiken
NIS2 supplier breach – incident exercise, 24/72h and restart evidence

Short answer: If a critical supplier is compromised, an entity covered by Sweden's Cybersecurity Act must promptly assess its own impact. A supplier's alert is not automatically a significant incident for the customer. Where the customer's incident meets the applicable criteria, an early warning is normally due within 24 hours of becoming aware, an incident notification within 72 hours, and a final report within one month after the notification. An exercise should test decisions, contacts and safe service recovery—not just how to fill in a form.

Editorial legal source review: 16 November 2026. Swedish Cybersecurity Act (2025:1506), Chapter 2 Sections 3 and 5–9, NIS2 Directive Articles 21 and 23, and Swedish NCSC guidance. Sector-specific and trust service provider requirements may differ. A training guide, not official reporting software, certification or instructions for cyber intrusion.

What does a supplier cyber breach mean for the customer?

A supplier may suffer ransomware, compromised remote administrators, stolen API credentials or an outage in its cloud platform. The customer must determine which of its own services, data, users, operations and downstream dependencies are at risk. A supplier security event and a customer's legally significant incident are not identical assessments.

Chapter 2 Section 3 of the Swedish Act requires appropriate, proportionate security measures, including incident response, business continuity and supply-chain security. Risk-based contractual arrangements can cover early warnings, escalation, logs, alternative operation and recovery. The law does not mandate a file called 'restart certificate' or a specific Excel workbook.

Decision matrix – six supplier incident situations

Document decisions using real evidence and relevant sector criteria. This matrix does not provide a legal determination or certify a particular service.

Supplier eventCustomer questionDecision or evidence
Intrusion into the supplier's internal office ITAre the customer's data, authentication or services actually affected?Ask for a factual scope and record why the case is or is not yet significant, with a review time
Critical SaaS platform unavailableCould customer services suffer severe disruption or significant damage?Relate the outage to a business impact analysis, actual consequences and reporting tests
Supplier API key or administrator account compromisedCan an attacker reach customer data or systems?Revoke or rotate credentials safely, preserve logs and test access and integrity
OT maintenance supplier's remote login compromisedCould production or physical safety be affected?Include OT and safety leads before controlled isolation; avoid creating new physical risks
Supplier says the service has recoveredIs the customer's environment safe to reconnect?Require test results, identity and integrity checks, log evidence and a recorded GO/NO-GO decision
Exercise uncovers a missing emergency contactCan the incident team act after hours?Log finding, owner and retest; a simulated issue is not itself an actual notifiable incident

24 hours, 72 hours and one month: which clock starts?

The Swedish Cybersecurity Act Chapter 2 Section 5 requires an early warning of a significant incident as soon as possible, no later than 24 hours after the entity becomes aware of it. Section 6 normally requires an incident notification within 72 hours of such awareness; trust service providers have a special 24-hour notification period. Section 8 requires a final report within one month of incident notification, or an interim situation report if the incident is ongoing, followed by a final report within one month of resolution.

Keep separate timestamps for supplier detection, customer awareness, significance assessment and actual submission. An internal classification approval does not automatically move the legal awareness clock forward. Check the applicable regulations and current NCSC reporting instructions, including sector-specific alternatives. Use the official cyber portal for real notifiable events; do not submit fictitious practice reports.

Eight-step incident simulation: alert to safe restart

  1. Define the tabletop exercise, participants, critical supplier, affected services and safety boundaries; clearly mark all simulated messages TEST.
  2. Inject a time-stamped supplier alert and confirm that on-call IT, OT, business owners and executives can be reached.
  3. Map customer impact: affected operations, data, dependencies, disruption, potential damage and exposure.
  4. Assess and reassess significance against the correct criteria; record yes/no/uncertain, evidence, owner and next review time.
  5. Rehearse the 24-hour warning, usually 72-hour notification, status updates and final report without submitting fake data to the live portal.
  6. Request supplier evidence: scope, timeline, logs, compromised access, mitigations, residual risks and tested recovery.
  7. Make an explicit GO/NO-GO decision after identity, integrity, backup, connection and safety testing; record risks and approvals.
  8. Capture exercise observations, corrective actions, owners, deadlines and a retest; update contracts and continuity procedures.

What belongs in a restart evidence record?

A restart evidence record is a recommended internal decision log, not a government-issued NIS2 certificate. Record system and service, configuration version, owner, supplier, timestamp, access/key resets, evidence of logging, integrity, backup restoration and service tests, remaining exceptions, risk acceptance and an attributable GO/NO-GO decision.

For operational technology, protect people and physical processes before reconnecting systems. Service-level credits cannot justify unsafe restart. A verbal statement from a supplier that everything is 'green' is not enough to demonstrate a tested recovery.

Scenario A – ransomware at a critical SaaS supplier

A Swedish logistics entity covered by the Act receives an alert at 09:20: its order-platform supplier suspects ransomware and has shut down an API. Participants assess the entity's own operational impact, possible harm to customers and significance. They test alternative ordering, preserve the supplier timeline and customer awareness time, decide whether an early warning is needed and verify restored order synchronisation before restart.

Scenario B – compromised remote access at an OT supplier

An industrial entity hears that an OT maintenance provider's administrator account may have been used by an attacker. The exercise brings together IT, OT, operations and safety personnel. Teams assess reachability, preserve logs, simulate safe isolation and fallback, determine any reporting duty, then require integrity and safety evidence before reconnecting remote access.

Supplier contracts, GDPR and DORA: separate duties

Contracts should enable timely information needed for the customer's independent incident assessment: contacts, severity escalation, log availability, subcontractors, tested recovery, evidence and practical exercise cooperation. These are risk-based arrangements under Chapter 2 Section 3 and NIS2 Article 21—not an identical mandatory contract clause for every supplier.

If personal data may be affected, conduct a separate GDPR personal data breach assessment and consider whether IMY notification is required. Financial entities within DORA's scope should apply their relevant sector-specific rules, rather than automatically layering the NIS2 deadlines over DORA. A supplier's own reporting duties do not replace the customer's responsibilities.

Related information: NIS2 supplier contract guide and NIS2 24/72-hour incident reporting guide.

Frequently asked questions

Does every supplier security alert start the customer's 24-hour clock?

No. Assess whether the customer becomes aware of its own significant incident covered by the law, keep timestamps and reassess quickly. A delayed internal signature is not necessarily a lawful postponement.

Must the supplier prepare the customer's NIS2 report?

Not as a general legal rule. Supplier evidence is valuable, but the covered entity needs to establish its own duties and reporting channel.

Is a restart certificate mandatory?

Not a file with that name. Risk-based incident, continuity and security measures are required; a traceable restart decision is a useful evidence method.

Can a simulated exercise be filed as a real incident?

A planned simulation is not itself a real significant incident. Label TEST and do not send fabricated events into a live reporting portal. Assess any genuine incident discovered during exercise separately.

Can GDPR, DORA and NIS2 share one 72-hour rule?

No. Reporting thresholds, actors, deadlines and sector-specific duties differ. Trust services and other sectors can have special NIS2 rules.

Before an incident exercise, map the critical processes that depend on the supplier and their recovery order. Start with our step-by-step Business Impact Analysis (BIA) guide. BIA, RTO and RPO guide internal priorities but do not replace an NIS2 reporting assessment or technical safety checks before restart.

A mock exercise, document template and restart log do not amount to an official cyber audit or security certification. Confirm legal scope, applicable regulations and actual technical proof. This guide is usable without purchasing a template.

Explore the topic

Back to blog
Customers rate us 4.6/5 based on 10261 reviews.