Distinguish supplier alerts from NIS2 reports
Article 23 regulates significant incident reporting by covered entities to the competent authority or CSIRT under the applicable framework. A supplier's contractually agreed alert to its customer serves a different purpose and does not itself satisfy that customer's legal reporting obligation.
Build a process to establish the affected service, time of awareness, available facts and decisions. A notification from a supplier is evidence to assess, not a universal starting point for every NIS2 reporting clock.
Set practical notification triggers
Agree which service disruptions, suspected compromises, unauthorised access or integrity failures require escalation under the supplier relationship. Match notice periods and contact arrangements to the speed at which the organisation must make informed response decisions.
Not every issue in a supplier's environment affects a covered customer. Define impact thresholds without excluding early warnings about material risks that are still being investigated.
Specify useful information
Request the affected services, known timing, potential data or system exposure, containment actions, workarounds and next update. Separate confirmed facts from preliminary estimates. Establish secure channels for sharing sensitive investigation evidence.
When the supplier initially lacks details, require a follow-up process instead of encouraging invented certainty. Maintain an auditable record of changes to key facts.
Coordinate internal incident decisions
Send relevant notifications to incident response, service owners, legal and continuity leads. Determine whether the covered service is affected and whether applicable Article 23 thresholds or other statutory duties are met.
Regulatory notifications may use the 24-hour early warning and 72-hour incident notification framework, followed by later reports where required. Check national procedures and any additional entity-specific EU rules.
Test, document and revise
Exercise notification contacts during supplier disruption scenarios, including weekends and loss of primary messaging. Record missed deadlines, unclear responsibilities and corrective actions.
Article 21(2)(d) addresses supplier relationships, but NIS2 does not impose one universal supplier-to-customer contractual deadline on all vendors. Contract terms should support the entity's own legal and operational needs.
Questions on the text
Does NIS2 require the same process for every supplier?
No. Measures should be proportionate to the supplier relationship, relevant risks and any additional applicable requirements.
Why retain records of the process?
Records support internal accountability, follow-up action and appropriate supervisory evidence.