Status: Companion note to TLCTC v2.7 — not part of the core taxonomy (the 10 clusters, 10 axioms, classification rules). It is a structural aid for the consequence-chain side of an incident. The edge types it relies on come from Layered Event Modelling (LEM) v1.0, of which TLCTC is the worked instance.
Audience: CISOs, IR designers, BCM/operational-risk owners, GRC architects.
The May 2026 original was written on v2.3. The mechanism is unchanged; what changed is how the chain around it is drawn:
- Two kinds of link. Events follow each other by a causal edge (with a Δt) or a duty arises by a normative edge (no Δt).
- Deadlines count from awareness. A statutory deadline is not a Δt; it bounds a separate response process whose clock starts when the organisation becomes aware.
- Spine and branches. The business layer starts with a process event (BRE₁); each duty branches off the event that meets the norm’s condition. The old NIS2 tree, which hung the NIS2 duty under the data event although the text placed it at the SRE, is corrected.
- A complete trigger map (§4): NIS2, GDPR, HIPAA, DORA, SEC 8-K, contracts, BCM and internal policy, each placed on the chain.
TL;DR
Where this fits in TLCTC: the core taxonomy classifies the cause side of an incident — which cluster, which attack path. This note is about the consequence side — where the controls and obligations that follow an incident have to run.
A single incident produces a chain of events — SRE → DRE → BRE₁ → … → BREₙ. Every event in it carries its own six control functions (GV, ID, PR, DE, RS, RC) and its own recovery objective: System Recovery for the SRE, Data Recovery for the DRE, business continuity for the BRE. These objectives are usually owned by different organisations with different clocks.
Many controls that protect a later event can only work if they run earlier. The control that prevents a missed GDPR deadline is the notification, and it has to start as soon as the personal-data breach is known. The control that prevents an outage beyond tolerance is the BCM handover, and it has to start while the IR team is still responding. TLCTC names this with one mechanism: the PR control of a downstream event is hosted in the RS (Respond) container of an upstream event.
RS(Eₙ) = { Response } ∪ { Propagated PR(Eₙ₊₁) } ∪ … ∪ { Propagated PR(Eₙ₊ₓ) }
The host is the earliest event that meets the control’s trigger. For a legal duty that is the event at which the duty arises: the significant incident for NIS2, the personal-data breach for GDPR, the major ICT-related incident for DORA. A propagated control is the upstream RS step that hands an obligation to whoever owns the downstream objective — a regulator, a contract counterparty, the BCM organisation, the board.
The name is kept from the glossary (Propagated PR, V2.0), but what moves is the placement of a control, not an effect. A hosted control is not an edge of the chain and carries no Δt. On a normative edge nothing propagates at all: an event meets a norm’s condition and a duty arises. Effects travel only along causal edges.
1. The mechanism
The consequence chain (core §3.4; glossary: Event Chain, Business Risk Event) runs one way: a System Risk Event may bring about a Data Risk Event, which may bring about one or more Business Risk Events. Controls in the NIST CSF sense are normally placed at the event they protect — PR(BRE: GDPR duty violated) would be “do what prevents a violation of the GDPR notification duty”.
But many of those PR controls only work as actions taken earlier in the chain:
- Notify the supervisory authority within 72 hours of awareness prevents the violation of the GDPR duty, but the action is part of responding to the data event.
- Hand over to the BCM organisation prevents the outage running beyond tolerance, but the action is part of responding to the data event, or to the SRE when its severity alone justifies it.
- Send the customer notice the SLA requires prevents the breach of contract, but the action is part of responding to the data event.
So the PR for the downstream event is hosted in the RS container of the upstream event. It is purely a placement rule — the control is still semantically a PR for Eₙ₊ₓ; it just executes during RS(Eₙ), run by a team that usually does not own the objective it serves.
1.1 Why this matters
Without naming the mechanism, IR playbooks degenerate into “reporting checklists” — flat lists of obligations bolted onto the response procedure with no causal grounding. With it, every propagated control has five properties:
- A protected event — the downstream BRE this PR belongs to.
- A host event — the upstream RS container in which it executes.
- A trigger — the condition the host event must meet: the norm’s condition, a contract clause, a BIA threshold, a policy severity.
- A clock start — almost always awareness of the host event (or a determination about it), not the moment it occurred.
- A bound — the deadline or tolerance: 72 hours, 4 business days, the RTO.
Two propagated controls can sit in the same RS container with completely different clocks, bounds and recipients (see §7).
2. What v2.7 adds: two kinds of link
Since v2.7 the consequence chain records two kinds of link between events (dictionary consequence_chain; LEM §6):
- Causal edge. One event brings about the next. The edge carries a Δt, the causal interval, which bounds the window in which detection and response can act. The chain can break only at a causal edge.
- Normative edge. An event meets the condition of a norm — a statute, regulation, contract or policy — so that a duty arises, or a norm stands violated. Nothing propagates and no Δt is defined.
This splits every reporting obligation into three distinct events. Take GDPR Art. 33:
DRE [C] personal-data breach
│
├┄┄ normative (no Δt) ┄┄▶ BRE notification duty arises
│
└── awareness ── response process (causal) ──▶ notification filed
│
filed ≤ 72 h after awareness? normative: fulfilment
filed later, no reasons? normative: BRE duty violated
The duty arising is a BRE reached by a normative edge. The filing is a causal act of a separate response process, and only that process has a duration. The 72 hours are not a Δt on the chain: they bound the response process, and its clock starts when the controller becomes aware of the breach, not when the breach occurred. Meeting the bound is necessary for fulfilment, not sufficient — the duty does not arise where a risk to individuals is unlikely, a late notification must give reasons, and information may be provided in phases (Art. 33(1), 33(4)).
The propagated control is the PR of the last event in that picture, BRE: duty violated, and it is hosted in RS(DRE), where the response process runs.
3. Sources of propagated controls
Compliance is the most visible source of propagation, but not the only one. Four sources cover the practical cases:
| Source | Examples | Typical host event | Clock and bound |
|---|---|---|---|
| Regulatory | NIS2 Art. 23, GDPR Art. 33/34, HIPAA breach notice, DORA Art. 19, SEC Form 8-K Item 1.05 | SRE, DRE or BRE₁, depending on the norm’s condition (§4) | From awareness or a determination; hours to days |
| Contractual | Customer SLA notification, partner-disclosure clauses, cyber-insurance notice conditions | DRE or SRE, as the contract defines | Minutes to hours |
| BCM / BIA | Handover to the enterprise BCM / crisis-management organisation; continuity-plan invocation; failover and alternate-site activation; crisis-comms playbook | DRE (standard), SRE (pre-emptive) | RTO, set by the BIA |
| Internal policy | Board notification thresholds, legal-hold triggers, ethics-committee referral | SRE, DRE or BRE | Per policy; hours |
All four behave identically: they are PR controls of a downstream BRE that execute as RS steps of an upstream event. The mechanism is source-agnostic; the source only changes who owns the obligation and what counts as its trigger.
4. The trigger map: where each obligation attaches
Each regime names its own trigger, and the trigger decides the host. Read against the chain, the common regimes fall on all three layers. The regimes, conditions and deadlines below are examples that illustrate the placement; they summarise the texts for orientation and are not legal advice.
| Obligation | Trigger (the norm’s condition) | Duty arises at | Hosted in | Bound (clock start) |
|---|---|---|---|---|
| NIS2 Art. 23 | Significant incident: has caused or is capable of causing severe operational disruption or financial loss, or considerable damage to others | SRE | RS(SRE) |
Early warning ≤ 24 h, notification ≤ 72 h (from awareness); final report ≤ 1 month after the notification |
| GDPR Art. 33 | Personal-data breach, unless unlikely to result in a risk to individuals | DRE | RS(DRE) |
Without undue delay, where feasible ≤ 72 h (from awareness) |
| GDPR Art. 34 | Personal-data breach likely to result in a high risk to individuals | DRE | RS(DRE) |
Without undue delay |
| HIPAA Breach Notification Rule | Breach of unsecured protected health information | DRE | RS(DRE) |
Without unreasonable delay, ≤ 60 days (from discovery) |
| DORA Art. 19 | Major ICT-related incident, classified by impact: clients affected, duration, spread, data losses, criticality of services, economic impact | BRE₁ | RS(BRE₁) |
Initial notification ≤ 4 h after classification as major and ≤ 24 h from awareness; intermediate ≤ 72 h; final ≤ 1 month |
| SEC Form 8-K Item 1.05 | Cybersecurity incident determined to be material | BRE₁ | RS(BRE₁) |
≤ 4 business days (from the materiality determination) |
| Contract / insurance | As the clause defines: data affected, service degraded, incident suspected | SRE or DRE | RS(SRE) or RS(DRE) |
Per contract |
| BCM handover | Local recovery insufficient; severity ≥ BIA threshold | — (no duty: an internal objective) | RS(DRE); RS(SRE) pre-emptively |
RTO |
| Board policy | Severity ≥ the policy threshold | Any event | The first RS that meets it | Per policy |
Three readings follow. NIS2 sits at the SRE because its condition is about the incident and what it could cause, whether or not any data moved. GDPR and HIPAA sit at the DRE because their condition is a property of data — personal data, protected health information — and the SRE alone does not establish it. DORA and SEC sit at the business layer because their condition is an impact judgement — major, material — that only a business event can carry. Regimes overlap: a financial entity under DORA reports major ICT-related incidents under DORA rather than NIS2, since DORA is the sector-specific act that NIS2 Art. 4 defers to.
The v2.7 dictionary and core §3.4 define a BRE as reached “from a Data Risk Event or a preceding Business Risk Event”. The NIS2 duty needs a normative edge from the SRE, which LEM §6 already admits (any occurrent can meet a norm’s condition). This note draws it that way; the dictionary wording is recorded for widening in the next version.
One entry point hosts nothing. A norm can be amended, so that an unchanged process becomes non-compliant: a BRE entered directly by a normative edge, with no SRE or DRE before it (dictionary consequence_chain, entry points). There is no upstream RS container to host a control. What acts instead is regulatory horizon scanning (ID) and the change to the process before the amendment takes effect.
5. Worked example A — NIS2 and GDPR on one incident
Companion blog: GDPR vs NIS2: Different Trigger Points for Compliance Events — full visual treatment of the two trigger points.
Ransomware hits a NIS2-scoped hospital. Patient data are exfiltrated and the scheduling system is encrypted.
SRE System Compromise (ransomware executes)
│ └┄┄ normative ┄▶ BRE NIS2 duty arises (significant incident)
│ causal, Δt
DRE [C] patient data exfiltrated · [Ac] scheduling data encrypted
│ └┄┄ normative ┄▶ BRE GDPR Art. 33 duty arises (risk to patients likely)
│ causal, Δt
BRE₁ Patient scheduling unavailable (process event)
│ causal, Δt
BRE₂ Appointments cancelled
The business layer starts with the process event; the duties hang off the events that meet their conditions. In the RS containers:
RS(SRE) = { containment, eradication, forensics }
∪ { Propagated PR(BRE: NIS2 duty violated):
early warning to the CSIRT ≤ 24 h, notification ≤ 72 h
from awareness; final report ≤ 1 month after the notification }
RS(DRE) = { breach assessment, evidence preservation }
∪ { Propagated PR(BRE: GDPR duty violated):
notify the DPA ≤ 72 h from awareness; inform patients
without undue delay if the risk is high (Art. 34) }
The two controls sit in different RS containers with different clocks. Putting GDPR in RS(SRE) or NIS2 in RS(DRE) is the standard failure of generic “incident reporting checklists”.
The second failure is starting the clock at the event instead of at awareness, or treating the 72 hours as the time the chain itself will take. The chain’s Δt to the next event is set by the attack and the system; the deadline is set by the norm.
6. Worked example B — BCM and DORA (business disruption)
Compliance is the visible propagation case. The same mechanism — with no regulator involved — is the BCM/BIA control set. A payment institution’s processing platform is encrypted by ransomware:
SRE System Compromise
│ causal, Δt
DRE [Ac] transaction data present but encrypted
│ causal, Δt
BRE₁ Payment processing outage (process event)
│ └┄┄ normative ┄▶ BRE DORA duty arises (major ICT-related incident)
│ causal, Δt
BRE₂ Settlements to merchants missed
│ └┄┄ normative ┄▶ BRE merchant contracts breached
│ causal, Δt
BRE₃ Revenue loss
BRE₁ has its own PR set — the business continuity controls: failover capability, alternate-site readiness, manual-process playbooks, customer-communication SLAs. Most of them do not execute at BRE time. They execute earlier, hosted upstream:
RS(SRE) = { containment, eradication, forensics }
∪ { Propagated PR(BRE₂): pre-emptive BCM handover if the
severity alone justifies it }
RS(DRE) = { restore from clean backup, validate integrity, verify state }
∪ { Propagated PR(BRE₂): HANDOVER to the BCM emergency
organisation, declare disaster, activate DR,
execute the customer-comms SLA }
RS(BRE₁) = { manual processing, crisis communication }
∪ { Propagated PR(BRE: DORA duty violated): initial notification
≤ 4 h after classification as major, ≤ 24 h from awareness;
intermediate ≤ 72 h; final ≤ 1 month }
The IR playbook for the data event is the BCM invocation point. This is why mature IR runbooks have BCM hand-off steps baked in: those steps are propagated PR controls in TLCTC terms. The BCM team’s RTO is the bound; the IR team’s SRE/DRE classification is the trigger.
6.1 Recovery objectives per event
The mechanism becomes most natural when you read it from the recovery side: each event in the chain owns its own recovery objective, and those objectives are typically held by different organisational units. Propagation is what happens at the seams between them. (Every event also carries the other five functions; the per-event control method is set out in Layered Event Modelling.)
Restore the technical system to a clean, known-good state — reimage, patch, rejoin, validate.
Restore data integrity, confidentiality where possible, or accessibility — clean-backup restore, integrity validation.
Restore the business process end-to-end — failover, alternate site, manual processing, crisis communication.
The DRE is where propagation becomes operationally visible. When data are encrypted by ransomware or known to be exfiltrated, the data-recovery team alone cannot complete the recovery objective — their RS plan must hand the baton over to the emergency organisation that owns the BCP/DR machinery. That handover is not a courtesy step; it is the moment where a PR control held by the BCM organisation executes as an RS step inside RS(DRE). Two organisations, two objectives, one container.
Read this way, propagation is the formal name for organisational handover. The question “which container does this control belong in?” becomes “which organisation owns the objective this control serves, and whose RS plan executes it?” — and those two answers do not have to match.
6.2 Two bounds, one window
Runbooks carry two kinds of time limit, and v2.7 adds a third quantity they are easily confused with:
- Duty deadlines (72 hours, 4 hours after classification, 4 business days) bound a response process — notifying, reporting. Their clock starts at awareness of the host event, or at a determination about it.
- The RTO bounds the recovery process of BRE₁. The BIA sets it as the tolerance for the outage.
- The Δt is neither: it is the causal interval to the next event — from the outage to the missed settlements. It is set by the business and the attack, not by anyone’s plan, and it bounds the window in which response can still break the chain.
A sound BIA chooses the RTO so that recovery completes inside that Δt. That is the same test TLCTC applies on the cause side with the Detection Coverage Score (DCS_c = TTC_P90 / Δt), and it is what stops an IR team from believing it is accountable for an RTO it does not own.
7. Two families of propagated controls
Read through the recovery lens, most real propagated controls fall into two families.
Family 1 — Reporting. A PR hosted upstream of the BRE duty violated: NIS2 Art. 23, GDPR Art. 33/34, HIPAA, DORA Art. 19, SEC 8-K Item 1.05, contractual disclosure clauses. The duty arises by a normative edge; the report is a causal act of the response process.
Family 2 — Organisational handover. A recovery objective owned by a downstream organisation, triggered by an upstream event: BCP/disaster-recovery invocation, crisis-comms activation, executive escalation. No duty arises; the edge it protects is causal.
Both families are mechanically identical — Propagated PR(downstream) hosted in RS(upstream). They differ in who owns the downstream objective:
| Family | Downstream owner | Control verb | Protects against | Bound |
|---|---|---|---|---|
| Reporting | External authority or counterparty | Notify / report | A normative BRE (duty violated) | Statutory or contractual deadline, from awareness |
| Organisational handover | Internal BCM / executive / legal | Escalate / hand over | A causal BRE (the next business event) | RTO / RPO |
A single IR playbook routinely contains both — a GDPR notification and a BCM handover sit in the same RS(DRE), with different clocks and different recipients.
7.1 Why the DRE is the natural BCM trigger point
The SRE is technical — something is wrong with the system. The BRE is business — the customer cannot transact. The DRE sits between them, and it is the first event in the chain where a business-relevant consequence is established rather than merely feared. That makes RS(DRE) the usual home for the IR → BCM handover:
- The clocks start here. Customer-comms SLAs, RPO commitments and the data-protection deadlines all run from awareness of the data event, not from the compromise.
- The classification is sufficient. A DRE, with its codes (
C,Ii/If,Av/Ac), carries enough to trigger BCM and disclosure. The SRE alone usually does not. - Uncertainty is acceptable but bounded. Acting at the SRE risks invoking obligations that may not apply; acting at the BRE is too late. The DRE is the earliest event where the risk of over-escalating is lower than the risk of waiting.
Pre-emptive SRE-level escalation is still valuable when severity alone justifies it — ransomware on a tier-0 system, a catastrophic outage — and NIS2 deliberately places its duty there. For BCM it is the exception, not the pattern.
8. Placement rule
Where does a propagated control belong?
Rule of Propagation: A PR control for eventEₙ₊ₓis hosted inRS(Eᵢ), whereEᵢis the earliest event in the chain that meets the control’s trigger. For a duty, that is the event at which the duty arises by a normative edge.
Practical consequences:
- NIS2-style obligations are hosted at the SRE, because the incident and what it could cause are the trigger — no data or business event is needed.
- GDPR- and HIPAA-style obligations are hosted at the DRE, because they need a data property (personal data, PHI) that the SRE alone does not establish.
- DORA- and SEC-style obligations are hosted at BRE₁, because their trigger is an impact judgement (major, material).
- BCM handover is hosted at the DRE as the rule and at the SRE pre-emptively.
Earlier placement means a longer reaction time but more uncertainty: you may invoke obligations that turn out not to apply. The quality of the classification at each event determines how far upstream a control can be hosted.
9. Relationship to TLCTC v2.7 and LEM
Already in the framework:
- Propagated PR (V2.0) — defined in the glossary for regulatory use. This note generalises the source to four categories without changing the definition.
- RS Container (Respond Container) (V2.0) —
RS(Eₙ) = { Response } ∪ { Propagated PR(Eₙ₊₁) } ∪ { Propagated PR(Eₙ₊ₓ) }is the canonical statement. - Regulatory Trigger Point and Eₙ Event Notation (Regulatory) (V2.0) — the subscripts (
E3a,E3b) extend naturally to non-regulatory branches. - Event Chain and core §3.4 —
SRE → DRE → BRE₁ → … → BREₙ, with causal and normative edges since v2.7 (dictionaryconsequence_chain). - Layered Event Modelling v1.0 — §6 (edge taxonomy; why a deadline is not a Δt) and §10 (compliance as a normative instantiation).
This note does not introduce new notation, axioms or classification rules. The recovery objective per event (system, data, business continuity) is a reading lens on the existing RC container, not a new construct.
10. Open questions
- JSON representation. Layer 3 attack paths model PR/DE/RS/RC controls indirectly. A future schema extension could carry an explicit
propagated_controls[]array on each event node:{ host_event, protected_bre, source_type (regulatory|contractual|bcm|policy), authority, trigger, clock_start (awareness|classification|determination), bound }. Not in scope here. - TLCTC+ codes. The TLCTC+ proposal (v0.9) records each BRE with its code and edge kind, e.g.
BRE-REG.11 Mandatory Notification Obligation Triggered(normative), and keeps deadlines on its Report entries, counted from awareness. A propagated control could name the code of the BRE it protects inprotected_bre. - Layer 2 registry — reporting side. A reference list of common propagated controls per regime (the trigger map of §4, extended) would let organisations stamp their IR playbooks without re-deriving the mapping each time.
- Layer 2 registry — handover side. Per-organisation BCM invocation procedures — who is the crisis-management duty officer, what is the activation channel, what counts as formal handover — are organisation-specific rather than standardisable.
- Dictionary wording. The BRE definition should admit a normative edge from an SRE, as the NIS2 case requires (§4).
References
- TLCTC v2.7 core — §3.4 (consequence chain, BRE, entry points); dictionary
consequence_chainintlctc-framework.v2.7.json(GitHub). - Layered Event Modelling v1.0 — §6 (edge taxonomy, deadlines), §10 (instantiation in cyber and operational risk).
- TLCTC glossary — entries Propagated PR, RS Container, Event Chain, Regulatory Trigger Point, Eₙ Event Notation, Business Risk Event (BRE).
integrations/cortex-xsoar-8/Playbooks/playbook-sub-rs-container.yml(GitHub) — reference implementation of the RS container concept (regulatory propagation).- Regulation (EU) 2016/679 (GDPR), Art. 33 and 34 — EUR-Lex.
- Directive (EU) 2022/2555 (NIS2), Art. 4 and 23 — EUR-Lex.
- Regulation (EU) 2022/2554 (DORA), Art. 18 and 19, with Commission Delegated Regulation (EU) 2025/301 on the content and time limits of the reports — EUR-Lex.
- SEC Form 8-K, Item 1.05 (Material Cybersecurity Incidents), adopted by Release No. 33-11216 (2023).
- HIPAA Breach Notification Rule, 45 CFR §§ 164.400–414.
- Companion blog: GDPR vs NIS2: Different Trigger Points for Compliance Events (2026-01-24) —
/tlctc-gdpr-nis2-triggers.html.
The mechanism described here is a V2.0 glossary concept (Propagated PR) lifted out of the regulatory context and generalised to four sources, now drawn on the v2.7 consequence chain: SRE → DRE → BRE* (System, Data and Business Risk Events), with causal edges that carry a Δt and normative edges that do not. NIST CSF function abbreviations (GV, ID, PR, DE, RS, RC) follow CSF 2.0. All regulatory data in this note (regimes, conditions, deadlines) are illustrative examples; the legal texts govern. For more on the framework, see tlctc.net.