EVIDENCE ARTEFACTS
- Approved message version
- Audience and delivery record
- Fact-source review
BREACH-04v1.0
CONTROL RECORD · REVIEWED 2026-08-30
Affected-person communication
Make affected-person communication an inspectable system decision with a named owner, defined trigger and retrievable evidence.
Engineering control
Catalogue status
not legal status
RECORD ANATOMY
What this control needs to be reviewable.
- Objective
- Make affected-person communication an inspectable system decision with a named owner, defined trigger and retrievable evidence.
- Rationale
- Connect safeguards, access, observability, recoverability and incident facts to decision-ready evidence.
- Owner model
- Incident lead · Privacy decision owner · Communications reviewer
- Review frequency
- Per incident and after every exercise
- Architecture layer
- Security and breach response
- Version
- 1.0 · 2026-08-30
IMPLEMENTATION SEQUENCE
Move from scope to retrievable evidence.
- 01
Scope the decision: separate confirmed facts from hypotheses and preserve the decision and communication trail.
- 02
Record the approved design and its source-status verification boundary.
- 03
Connect implementation events to evidence that a reviewer can retrieve without broad production access.
CONTROL TEST
- Select a recent, in-scope sample for affected-person communication and record why it was chosen.
- Trace the sample from its trigger and owner through the implemented system to the retained evidence.
- Record exceptions, confidence and remediation without converting an unknown into a pass.
ANTI-PATTERNS
Completion labels can hide an evidence gap.
- Treating “affected-person communication” as a policy sentence without an operating owner
- Marking the control complete from self-attestation alone
- Hiding missing, stale or inaccessible evidence behind a pass label
ARCHITECTURE → EVIDENCE DECISION JOURNEY
Follow the dependency, then inspect the proof.
Each connection uses existing catalogue records. Source IDs remain verification pointers—not provision mappings.
Add to a review route- Control pathwayBREACH-04: Affected-person communication
- 01 · PrerequisiteNotification owner
Review BREACH-03 before testing this dependent record.
Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023 - 02 · Implementation patternBreach fact ledger and communication package
Separate confirmed facts from hypotheses and generate consistent decision and communication evidence.
Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023, dpdp-rules-2025, act-commencement-2025 - 03 · Validation / testSelect a recent, in-scope sample for affected-person communication and record why it was chosen.
Trace the sample from its trigger and owner through the implemented system to the retained evidence. Record exceptions, confidence and remediation without converting an unknown into a pass.
Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023 - 04 · Evidence artefactApproved message version
Audience and delivery record · Fact-source review
Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023 - 05 · Failure modeTreating “affected-person communication” as a policy sentence without an operating owner
Marking the control complete from self-attestation alone · Hiding missing, stale or inaccessible evidence behind a pass label
Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023 - 06 · Research noteFrom obligation to evidence: the DPDP implementation stack
Implementation teams benefit from separating legal interpretation from the engineering artefacts used to execute and test a decision. Radar context: Automated legal-text monitoring is Assess.
Editorial analysis · reviewed 2026-08-30 · sources act-commencement-2025, pib-status-2026 - 07 · Specialist propertyNews and discourse signals
Monitor external developments separately from the organisation’s own incident evidence. This route remains optional if the destination is unavailable.
Contextual external property · no affiliation or availability implied
- 01 · PrerequisiteNotification owner
Open semantic relationship table (1pathway)
| Record | Phase | Relationship | Status / boundary | Source pointers |
|---|---|---|---|---|
| BREACH-04: Affected-person communication | 01 · Prerequisite | Notification owner Review BREACH-03 before testing this dependent record. | Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023 | dpdp-act-2023 |
| BREACH-04: Affected-person communication | 02 · Implementation pattern | Breach fact ledger and communication package Separate confirmed facts from hypotheses and generate consistent decision and communication evidence. | Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023, dpdp-rules-2025, act-commencement-2025 | dpdp-act-2023 · dpdp-rules-2025 · act-commencement-2025 |
| BREACH-04: Affected-person communication | 03 · Validation / test | Select a recent, in-scope sample for affected-person communication and record why it was chosen. Trace the sample from its trigger and owner through the implemented system to the retained evidence. Record exceptions, confidence and remediation without converting an unknown into a pass. | Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023 | dpdp-act-2023 |
| BREACH-04: Affected-person communication | 04 · Evidence artefact | Approved message version Audience and delivery record · Fact-source review | Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023 | dpdp-act-2023 |
| BREACH-04: Affected-person communication | 05 · Failure mode | Treating “affected-person communication” as a policy sentence without an operating owner Marking the control complete from self-attestation alone · Hiding missing, stale or inaccessible evidence behind a pass label | Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023 | dpdp-act-2023 |
| BREACH-04: Affected-person communication | 06 · Research note | From obligation to evidence: the DPDP implementation stack Implementation teams benefit from separating legal interpretation from the engineering artefacts used to execute and test a decision. Radar context: Automated legal-text monitoring is Assess. | Editorial analysis · reviewed 2026-08-30 · sources act-commencement-2025, pib-status-2026 | act-commencement-2025 · pib-status-2026 |
| BREACH-04: Affected-person communication | 07 · Specialist property | News and discourse signals Monitor external developments separately from the organisation’s own incident evidence. This route remains optional if the destination is unavailable. | Contextual external property · no affiliation or availability implied | None · contextual external route |
VERIFY BEFORE MAPPING
GENERIC VERIFICATION POINTER · NOT A PROVISION MAPPING
dpdp-act-2023
Provision-specific applicability must be verified against the primary-text ledger.
Boundary: Operational control pattern; not a standalone legal conclusion.
Open the source ledgerCONNECTED SYSTEM PATTERN
Breach fact ledger and communication package
Separate confirmed facts from hypotheses and generate consistent decision and communication evidence.
LOCAL WORKSPACE NOTE
Give this work a next owner.
Nothing is sent anywhere. Avoid names, personal data or confidential incident details.
CHANGE LOG
Version 1.3 — Architecture-to-evidence journey and non-personal review-route relationship added; verification-pointer boundary retained.
Version 1.2 — Official-source status rechecked; command-centre indexing and the non-mapping boundary retained.
Version 1.1 — Engineering fields, source verification pointers and acceptance evidence reviewed.
Version 1.0 — Stable catalogue ID, objective, evidence model, test sequence and verification boundary established.