DPO Radio

A breach response is a clock-driven event. Notifications to the supervisory authority, to affected data subjects, and to a sector CSIRT each run on their own clock, and those clocks are set by different instruments that do not agree with one another. Getting them wrong is a regulatory finding in its own right. Reconstructing them correctly under pressure is exactly the work that fails when the incident response team is already stretched.
The breach notification timeline workflow takes the incident record and reads, in one pass, every personal-data breach and security-incident notification duty declared by the frameworks your organisation has installed. There is no fixed list in the product: a framework you have not installed contributes no row, and one you installed in reference mode contributes none either. The output is a structured timeline — one row per duty, each with the recipient and article its record names, a deadline counted from the event that record declares, the record's own note, and a drafted notification body. The DPO and the incident response lead review and acknowledge it; the workflow does not file anything.
The workflow runs against an incident whose breach assessment marks it notifiable, and refuses one that is not. The jurisdictions recorded in that assessment decide which duties come first.
Each row is a personal-data breach notification or security-incident notification duty set out in one of your installed frameworks. Where GDPR is installed, that is the notification to the supervisory authority and the communication to affected data subjects; where NIS2 is installed, the early warning within 24 hours, the incident notification within 72 hours, the intermediate report on request and the final report; where the Vietnamese personal data protection law and its decree are installed, their breach notifications. Every installed duty becomes a row. Those whose jurisdiction the incident records — or every duty, when the incident records no jurisdiction — are listed first, and only those raise follow-up tasks; the rest stay visible, because hiding a duty is worse than showing one that may not bind.
Each row counts from the event its installed record declares — discovery, awareness, or containment — using the matching time recorded on the incident. GDPR and NIS2 count from awareness; the Vietnamese duties count from discovery. If the incident does not record that time, the row stays undated rather than borrowing another; if the record states no period, as for GDPR's communication to data subjects, the row says so rather than showing an invented one.
Each row carries a notification draft built from what its installed record states — the recipient, the citation, the due time and the record's note. Forseti drafts the body for up to five rows; the others keep the plain draft. The DPO reviews and adapts.
Each duty the incident's jurisdiction reaches becomes a follow-up task due at its deadline, raised at the highest priority for a window of a day or less and at high priority up to three days. Once the notifications are handled, the DPO acknowledges the timeline, and the acknowledgement is recorded against the run.
The audit trail records the start of the run, the draft it produced, and the acknowledgement. Multiple runs against the same incident are tracked separately so revisions remain walkable.



Every row cites the article its installed record names. Drafts are built from what that record states; where it names no recipient or states no period, the draft says so rather than filling the gap.

The workflow does not file autonomously. The DPO and the incident response lead review and acknowledge the timeline; filings route through the standard regulator notification workflow with operator confirmation per filing.

The audit trail walks the timeline back through the originating incident and the workflow run.
| Framework | How Breach Timeline Supports It |
|---|---|
| EU GDPR | Two rows where installed — notification to the supervisory authority within 72 hours of awareness, and communication to affected data subjects, for which the regulation states no fixed period. |
| Vietnam Personal Data Protection Law and its implementing decree | The breach notifications their installed records declare, counted from discovery. |
| EU NIS2 | Four rows where installed — the early warning within 24 hours and the incident notification within 72 hours of awareness, the intermediate report on request, and the final report — addressed to the competent CSIRT or authority. |
| EU ePrivacy Directive | The personal data breach notifications its installed records declare for providers of publicly available electronic communications services. |

The timeline records the platform's installed deadlines. The incident practitioner workflow compares notification duties against those recorded dates. See Incident and Continuity Workflows.
Ready to see a structured breach timeline drafted in three minutes, with a live countdown against every applicable obligation? Request a personalised demo.


Run breach notification timeline against your incident response exercises so the team is familiar before a real breach.

Talk to our team about how the breach timeline workflow fits your incident response programme.
The ones your organisation has installed. The workflow reads every personal-data breach and security-incident notification duty their records declare, so the recipients follow the records: a supervisory authority, affected data subjects, or a CSIRT. A framework you have not installed adds nothing. Duties whose jurisdiction the incident records are listed first and raise tasks; the others stay on the timeline, clearly after them, for a person to rule out.
No. The workflow drafts the timeline and the notification templates; filings route through the standard regulator notification workflow with operator confirmation per filing.
Yes. Re-runs against revised breach assessments are tracked separately in the audit trail. The DPO can re-run as the breach scope evolves.
From the event each duty's own record names — discovery, awareness or containment — using the time the incident records for that event. Each row shows the hours remaining, or how far past the deadline the duty already is; a row whose event time is not recorded, or whose record states no period, is shown undated. Tasks for duties with a window of 24 hours or less are raised at a higher priority than those up to 72 hours. Re-running the workflow after a time is corrected recomputes the whole timeline.
Yes. Each run sends requests to the AI provider your organisation has configured, and your provider bills your organisation for them directly. A run is never refused because a Forseti allowance ran out, and the Usage page reports what each feature consumed.