Edge Register
Incident alerts

When a site has an incident, tell the right people and show who knows

Log the incident at one or more sites from your register. Alert internal and external contacts with the template that fits them, see who acknowledged and who is still waiting, and read the reporting lines that attach from the published texts: NIS2 Art. 23, DORA Art. 19, GDPR Art. 33 and 34, ISO 22301 8.4.3. A time is shown only where the text fixes one and you recorded when the clock started.

01

Contacts and call tree per site

Internal contacts (site owner, IT or infrastructure lead, continuity lead, management) and external ones (provider, landlord, carrier, key customer, regulator or authority), each with email, phone, an out-of-hours number, a call order and a deputy. A contact covers one site or every site. The call list prints for when email is down.

02

An incident record that cannot be rewritten

What happened, when it started and when you became aware, in your time zone; the affected sites with what runs there and what a loss costs, taken from your register. Updates, decisions, phone calls, submissions to an authority and handovers go into an append-only timeline with who and when.

03

Alerts in three voices, acknowledged by link

An internal operational alert with every duty line, an external notice for a provider, landlord, carrier or customer that carries none of your internal clocks, and a regulator draft that is never sent. Initial, status update and all clear. Each recipient gets a private acknowledgement link.

The rules it keeps

The specimen, worked through

Northmoor Building Society is invented. The incident below is the one the incidents page shows a visitor without a plan: a ransomware alert on a vendor maintenance laptop stops a print and mail line, with the data centre link cut as a precaution and Irish members' statements held. The building society has not yet answered whether it is a NIS2 entity or a DORA financial entity, so those lines read "depends"; it has answered that personal data was affected and the risk, so the GDPR Art. 33 limit is shown.

Print and mail line 1 down after a ransomware alert on the vendor maintenance laptop. Started Tue 6 Oct 2026 08:40 GMT+1 (Europe/London); became aware Tue 6 Oct 2026 09:05 GMT+1 (Europe/London). Incident lead R. Ashworth. Status monitoring.

What is affected, from the register

SiteClassWhat runs thereIf it is lostWhere
Castleford print and mail, line 1Print and mail centrestatement printing and inserting for UK and Irish members, the line controller and the vendor maintenance laptopstatements and notices to members miss their posting dateUnited Kingdom
Leeds data centreData centre, if one is pastedcore banking, the branch network and the print file transferevery branch and channel stopsUnited Kingdom
Dublin officeRegional or satellite officemortgage servicing for Irish members, staff laptops and a file shareIrish members cannot be servedIreland

The lines that attach

2 answers open: Is the organisation an essential or important entity under the national law that transposes NIS2? Is the organisation a financial entity under DORA? Until answered, the lines that depend on them show no time.

Reporting lines for the incident

What the organisation is decides these, not where the site is. Times are outer limits from the instants recorded, in Europe/London; a duty the text sets as "without undue delay" or "on request" gets no time.

Depends on an answer NIS2 NIS2 incident reporting (Art. 23)

Depends on whether the organisation is an essential or important entity under the national law that transposes NIS2: not answered. If it is, a significant incident brings an early warning within 24 hours and a notification within 72 hours of becoming aware of it (24 hours for a trust service provider whose trust services are affected); no time is shown until this is answered.

Open answer Is the organisation an essential or important entity under the national law that transposes NIS2?
NIS2 Art. 23(4)(a) Submit an early warning within 24 hours of becoming aware of a significant incident

The first stage of the layered reporting regime falls due without undue delay and in any event within 24 hours of becoming aware of the significant incident. The early warning is deliberately light: where applicable it indicates whether the incident is suspected of being caused by unlawful or malicious acts, and whether it could have cross-border impact. It is not a full assessment and waiting for one is the classic way to miss the deadline. Two operational points decide whether an entity can meet this. First, becoming aware has to be defined and evidenced, because the clock starts there and an entity that cannot say when it knew cannot show it reported in time. Second, submission has to be possible at any hour, since a Friday night detection has the same 24 hours as a Tuesday morning one. The CSIRT or authority is expected to respond within 24 hours where possible, so the channel is two-way.

Our statement of the clause, read from the published text. NIS2 on compliance.theartofservice.com · the instrument

NIS2 Art. 23(4)(b) Submit an incident notification within 72 hours, with an initial assessment and indicators of compromise

Within 72 hours of becoming aware, the entity updates the early warning and provides an initial assessment of the significant incident covering its severity and impact, together with indicators of compromise where those are available. The 72 hours runs from awareness, not from the early warning, so the two clocks start together. Trust service providers are held to a shorter deadline: for significant incidents affecting the provision of their trust services they must notify within 24 hours. The practical demand here is investigative rather than administrative, since the entity needs enough forensic capability within three days to characterise severity and impact honestly and to extract indicators worth sharing. Producing indicators requires that the telemetry existed before the incident.

Our statement of the clause, read from the published text. NIS2 on compliance.theartofservice.com · the instrument

Depends on an answer DORA DORA major ICT-related incident reporting (Art. 19)

Depends on whether the organisation is a financial entity under DORA: not answered. If it is, an incident classified as major is reported to the competent authority on clocks that run from classification and from becoming aware; no time is shown until this is answered.

Open answer Is the organisation a financial entity under DORA?
DORA Art. 19 Reporting of major ICT-related incidents

Financial entities report major ICT-related incidents to their single designated competent authority (significant credit institutions report to the national authority, which passes the report to the ECB), using the Article 20 templates, with an alternative channel where a technical problem blocks the initial notification; Member States may also require copies to NIS2 authorities or CSIRTs. Under Commission Delegated Regulation (EU) 2025/301, Article 5, the clocks are: initial notification as early as possible and within 4 hours of classifying the incident as major, but no later than 24 hours after becoming aware of it (Art. 5(1)(a)); where the incident is classified as major only after that 24-hour point, within 4 hours of classification (Art. 5(2)); intermediate report within 72 hours of submitting the initial notification even if nothing has changed, plus a further updated intermediate report promptly, and at the latest once regular activities are recovered (Art. 5(1)(b)); final report at the latest one month after the intermediate report or, where updates were filed, the latest updated intermediate report (Art. 5(1)(c)). An entity that cannot meet a deadline must tell the authority and give reasons before it expires (Art. 5(3)). A deadline falling on a weekend or bank holiday may move to noon of the next working day (Art. 5(4)), except for initial and intermediate submissions by credit institutions, central counterparties, trading venue operators and NIS2 essential or important entities (Art. 5(5)), and competent authorities may withdraw that relief from other significant or systemic entities (Art. 5(6)). Where a major incident affects the financial interests of clients, they are told without undue delay about it and the mitigation taken (Art. 19(3)). Significant cyber threats may be notified voluntarily. Reporting may be outsourced, but the entity stays responsible (Art. 19(5)).

Our statement of the clause, read from the published text. DORA on compliance.theartofservice.com · the instrument

Not covered here UK GDPR UK GDPR Art. 33 and 34 (the Information Commissioner)

A separate law from the EU GDPR. Its text is not stated here, so the obligation is named and not stated, and no time is computed from the EU text. Prepare it separately.

the instrument

Attaches GDPR Notify the supervisory authority (Art. 33)
Where feasible, no later than Fri 9 Oct 2026 11:15 GMT+1 (Europe/London) 72 hours from the recorded awareness of the breach

Without undue delay and, where feasible, not later than 72 hours after becoming aware of the breach; a notification made later carries the reasons for the delay. Information may be given in phases. Document the breach either way.

GDPR Art. 33 Notification of a personal data breach to the supervisory authority

On becoming aware of a personal data breach, notify it to the competent supervisory authority without undue delay and, where feasible, not later than 72 hours after becoming aware, unless the breach is unlikely to result in a risk to the rights and freedoms of natural persons; a notification made later than 72 hours must be accompanied by the reasons for the delay. A processor must notify its controller without undue delay after becoming aware of a breach. The notification must at least describe the nature of the breach including, where possible, the categories and approximate number of data subjects and of personal data records concerned, give the name and contact details of the data protection officer or other contact point, describe the likely consequences, and describe the measures taken or proposed including any measures to mitigate adverse effects. Information may be provided in phases where it cannot all be given at once. Document every personal data breach, including the facts, its effects and the remedial action taken, so the supervisory authority can verify compliance with this Article.

Our statement of the clause, read from the published text. GDPR on compliance.theartofservice.com · the instrument

Per site

Castleford print and mail, line 1 Print and mail centre
Not covered here UK United Kingdom

UK GDPR Art. 33 and 34, the UK Network and Information Systems Regulations, and FCA and PRA incident notification rules are not stated here: each is named, its text is not stated, and no time is computed. Add your own line if you track one.

the instrument · the instrument · the instrument

Note Data Personal data at this site

The register reads personal and payment data here (payment data often includes personal data), so the personal data breach questions apply to this site.

Leeds data centre Data centre, if one is pasted
Not covered here UK United Kingdom

UK GDPR Art. 33 and 34, the UK Network and Information Systems Regulations, and FCA and PRA incident notification rules are not stated here: each is named, its text is not stated, and no time is computed. Add your own line if you track one.

the instrument · the instrument · the instrument

Note Data Personal data at this site

The register reads personal and payment data here (payment data often includes personal data), so the personal data breach questions apply to this site.

Dublin office Regional or satellite office
Note EU Ireland

An EU Member State: the NIS2, DORA and GDPR lines for the incident are the held EU texts; the Member State's own transposing law and authority are not stated here.

Note Data Personal data at this site

The register reads personal data here, so the personal data breach questions apply to this site.

Continuity communication

Attaches ISO 22301 Warning and communication (8.4.3)

Communicate with interested parties inside and outside the organisation by your documented procedure (what is said, when, to whom and how); keep the means of communication available while the disruption lasts; record the disruption, what was done and which decisions were taken; where relevant, warn parties who may be affected by a disruption that is happening or imminent.

ISO 22301 8.4.3 Warning and communication

Document and keep up procedures for: communicating with relevant interested parties inside and outside the organization, covering what is said, when, to whom and how; receiving, recording and answering communications, including those from national or regional risk advisory systems; keeping the means of communication available while a disruption lasts; structured communication with emergency responders; the organization's media response and communications strategy; and recording the disruption, what was done and which decisions were taken. Where relevant, also warn parties who may be affected by a disruption that is happening or imminent, and make sure several responding organizations work together; exercise these procedures as part of the exercise programme.

Our statement of the clause, read from the published text. ISO 22301 on compliance.theartofservice.com · the instrument

ISO 22301 8.4.1 General

Put in place and keep up a response structure that allows relevant interested parties to be warned and informed in good time. It needs plans and procedures for steering the organization through a disruption and for triggering the continuity solutions, identified and documented from the strategies and solutions that were selected, and procedures that are specific about the first steps to take, adaptable as internal and external conditions change, centred on the impact of incidents, effective at keeping that impact small, and clear about roles and responsibilities.

Our statement of the clause, read from the published text. ISO 22301 on compliance.theartofservice.com · the instrument

Your own lines

Your entry Your entry FCA and PRA notification
Your time Tue 6 Oct 2026 17:00 GMT+1 (Europe/London) entered by you

Our policy: tell our FCA and PRA supervisors the same working day (Your entry, not checked against any text.)

The alerts, as their recipients read them

Who has acknowledged

RecipientAlertStatusAcknowledgement
M. Doyle Site ownerIncident alert, internalheldWaiting (held, email is off), 280 minutes
Priya Shah IT or infrastructure leadIncident alert, internalheldAcknowledged Tue 6 Oct 2026 09:31 GMT+1
Chief operating officer ManagementIncident alert, internalheldAcknowledged Tue 6 Oct 2026 09:46 GMT+1
Service desk ProviderIncident alert, externalheldAcknowledged Tue 6 Oct 2026 09:57 GMT+1
Data protection authority (Ireland) (supervisory authority) Regulator or authorityIncident alert, regulatordraftDraft for review, not sent

The call list

#NameRoleSitePhoneOut of hoursDeputy
1R. AshworthContinuity leadevery site0113 496 000107700 900001K. Obi
2Priya ShahIT or infrastructure leadevery site0113 496 000207700 900002D. Hale
3Chief operating officerManagementevery site0113 496 000307700 900003Chief risk officer
1M. DoyleSite ownerCastleford print and mail, line 101977 496 01007700 900010S. Pike
1Service desk the print line maintainer (invented)ProviderCastleford print and mail, line 10800 496 01000800 496 0100
1Data protection authority (Ireland) supervisory authorityRegulator or authorityDublin office

The timeline

When (Europe/London)WhatWhoDetail
Tue 6 Oct 2026 09:05 GMT+1Loggedr.ashworth@northmoor.exampleIncident logged at Castleford print and mail, line 1; Leeds data centre; Dublin office
Tue 6 Oct 2026 09:25 GMT+1Alert heldr.ashworth@northmoor.exampleIncident alert, internal template, to Priya Shah, Chief operating officer, M. Doyle: held, the specimen sends no email
Tue 6 Oct 2026 09:29 GMT+1Told by phone or in personr.ashworth@northmoor.exampleM. Doyle told by phone, acknowledged
Tue 6 Oct 2026 09:31 GMT+1AcknowledgedPriya Shah by linkPriya Shah acknowledged the incident alert (internal template)
Tue 6 Oct 2026 09:40 GMT+1Alert heldr.ashworth@northmoor.exampleIncident alert, external template, to Service desk (the print line maintainer): held, the specimen sends no email
Tue 6 Oct 2026 09:46 GMT+1AcknowledgedChief operating officer by linkChief operating officer acknowledged the incident alert (internal template)
Tue 6 Oct 2026 09:57 GMT+1AcknowledgedService desk by linkService desk acknowledged the incident alert (external template)
Tue 6 Oct 2026 10:20 GMT+1Decisionr.ashworth@northmoor.exampleDecision by the chief operating officer: run the held statements on line 2 from 13:00; keep line 1 isolated until the forensic copy is taken. Why: line 2 is segregated and its controller was not reachable from the laptop.
Tue 6 Oct 2026 11:15 GMT+1Facts updatedr.ashworth@northmoor.exampleFacts updated: breach not answered to Yes; risk not answered to Likely to result in a risk
Tue 6 Oct 2026 11:55 GMT+1Updater.ashworth@northmoor.exampleLine 1 isolated; line 2 running the held statements from 13:00. Vendor laptop taken off the network for forensic copy.
Tue 6 Oct 2026 12:00 GMT+1Statusr.ashworth@northmoor.exampleStatus open to monitoring
Tue 6 Oct 2026 13:05 GMT+1Regulator draftr.ashworth@northmoor.exampleRegulator notification draft prepared for review (Data protection authority (Ireland)); not sent

Questions

Does Edge Register send anything to a regulator?

No. The regulator template is a draft for review, marked as not sent; the system refuses to email a regulator contact. You submit through the authority's own channel and record the time and reference.

Does it decide whether an incident is significant under NIS2 or major under DORA?

No. You answer those questions. Until you do, the lines that depend on them read "depends" and show no time.

Which times does it compute?

Only outer limits the published text fixes, counted from an instant you recorded: the NIS2 early warning (24 hours) and notification (72 hours, or 24 for a trust service provider), the DORA initial notification (4 hours from classification, no later than 24 hours from awareness) and intermediate report (72 hours from the initial notification), and the GDPR Art. 33 limit (72 hours, where feasible). A duty the text sets as without undue delay, on request or one month is stated without a computed date.

How do recipients acknowledge?

Each alert carries a private link for that recipient. Opening the page records nothing; pressing the button records the acknowledgement, once, in the incident timeline.

Not built: SMS or voice alerts (the phone numbers are kept for the call list), automatic escalation, and sending to an authority's portal. Exports: the incident log as CSV, each incident's timeline as CSV, the call list as CSV, a printable record and a one-page board summary.