SEF-07 Security Breach Notification
Notify affected parties of security breaches, including breaches reaching the organisation through its supply chain, within the timeframes set by service agreements, law and regulation.
4
artefacts
0
held by a system
2
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Notification records for actual breaches with timestamps · Document repository
- Evidence supply chain breaches are captured and assessed for notification · Document repository
governing documentDocuments that govern the control
- The breach notification procedure with the timeframes from each obligation · Policy repository / GRC workspace
- The obligations register showing notification requirements per jurisdiction and contract · Vendor register / contract repository
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Regulatory timeframes documented while contractual ones are not
- Supplier breach not treated as a notifiable event for the organisation's own customers
- Notification decision made without legal input and recorded only informally
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetSEF-06 Event Triage Processes · SEF-08 Points of Contact Maintenance