Notifying the users of your service
Compared across 6 jurisdictions
In European Union (NIS2 baseline)
Tell the recipients of your services when an incident affects them
Where appropriate, an entity must notify without undue delay the recipients of its services who are potentially affected by a significant incident. Separately, where a significant cyber threat — not an incident — could affect them, it must tell those recipients about any measures or remedies they can take in response, and about the threat itself. The two duties have different triggers and different content: the first is about something that happened to you, the second about something that might happen to them.
When: Without undue delay. There is no fixed clock, and deliberately so — it runs from when notification becomes appropriate, which for a widely used service is usually earlier than the 72-hour regulatory notification, not later.
What evidence looks like
- A customer-communication procedure naming who decides that notification is appropriate
- Pre-drafted notification templates for incidents and for cyber threats, kept separate
- A recipient contact list that is maintained outside the systems an incident would take down
- Records of past notifications with the time the decision to notify was taken
In Germany
Tell the recipients of your services when an incident affects them
Where appropriate, an entity must notify without undue delay the recipients of its services who are potentially affected by a significant incident. Separately, where a significant cyber threat — not an incident — could affect them, it must tell those recipients about any measures or remedies they can take in response, and about the threat itself. The two duties have different triggers and different content: the first is about something that happened to you, the second about something that might happen to them.
When: Without undue delay. There is no fixed clock, and deliberately so — it runs from when notification becomes appropriate, which for a widely used service is usually earlier than the 72-hour regulatory notification, not later.
What evidence looks like
- A customer-communication procedure naming who decides that notification is appropriate
- Pre-drafted notification templates for incidents and for cyber threats, kept separate
- A recipient contact list that is maintained outside the systems an incident would take down
- Records of past notifications with the time the decision to notify was taken
In Poland
Tell the recipients of your services when an incident affects them
Where appropriate, an entity must notify without undue delay the recipients of its services who are potentially affected by a significant incident. Separately, where a significant cyber threat — not an incident — could affect them, it must tell those recipients about any measures or remedies they can take in response, and about the threat itself. The two duties have different triggers and different content: the first is about something that happened to you, the second about something that might happen to them.
When: Without undue delay. There is no fixed clock, and deliberately so — it runs from when notification becomes appropriate, which for a widely used service is usually earlier than the 72-hour regulatory notification, not later.
What evidence looks like
- A customer-communication procedure naming who decides that notification is appropriate
- Pre-drafted notification templates for incidents and for cyber threats, kept separate
- A recipient contact list that is maintained outside the systems an incident would take down
- Records of past notifications with the time the decision to notify was taken
In Czechia
Tell the recipients of your services when an incident affects them
Where appropriate, an entity must notify without undue delay the recipients of its services who are potentially affected by a significant incident. Separately, where a significant cyber threat — not an incident — could affect them, it must tell those recipients about any measures or remedies they can take in response, and about the threat itself. The two duties have different triggers and different content: the first is about something that happened to you, the second about something that might happen to them.
When: Without undue delay. There is no fixed clock, and deliberately so — it runs from when notification becomes appropriate, which for a widely used service is usually earlier than the 72-hour regulatory notification, not later.
What evidence looks like
- A customer-communication procedure naming who decides that notification is appropriate
- Pre-drafted notification templates for incidents and for cyber threats, kept separate
- A recipient contact list that is maintained outside the systems an incident would take down
- Records of past notifications with the time the decision to notify was taken
In Estonia
Tell the recipients of your services when an incident affects them
Where appropriate, an entity must notify without undue delay the recipients of its services who are potentially affected by a significant incident. Separately, where a significant cyber threat — not an incident — could affect them, it must tell those recipients about any measures or remedies they can take in response, and about the threat itself. The two duties have different triggers and different content: the first is about something that happened to you, the second about something that might happen to them.
When: Without undue delay. There is no fixed clock, and deliberately so — it runs from when notification becomes appropriate, which for a widely used service is usually earlier than the 72-hour regulatory notification, not later.
What evidence looks like
- A customer-communication procedure naming who decides that notification is appropriate
- Pre-drafted notification templates for incidents and for cyber threats, kept separate
- A recipient contact list that is maintained outside the systems an incident would take down
- Records of past notifications with the time the decision to notify was taken
In Italy
Tell the recipients of your services when an incident affects them
Where appropriate, an entity must notify without undue delay the recipients of its services who are potentially affected by a significant incident. Separately, where a significant cyber threat — not an incident — could affect them, it must tell those recipients about any measures or remedies they can take in response, and about the threat itself. The two duties have different triggers and different content: the first is about something that happened to you, the second about something that might happen to them.
When: Without undue delay. There is no fixed clock, and deliberately so — it runs from when notification becomes appropriate, which for a widely used service is usually earlier than the 72-hour regulatory notification, not later.
What evidence looks like
- A customer-communication procedure naming who decides that notification is appropriate
- Pre-drafted notification templates for incidents and for cyber threats, kept separate
- A recipient contact list that is maintained outside the systems an incident would take down
- Records of past notifications with the time the decision to notify was taken