← GLBA · Safeguards Rule (16 CFR 314)
314.4(j) — Notify the FTC of notification events affecting 500 or more consumers
Requirement
When the institution discovers a notification event — unauthorised acquisition of unencrypted customer information — involving the information of at least 500 consumers, it notifies the FTC through its online form as soon as possible and no later than 30 days after discovery, including the types of information involved, the date or range of the event, the number of consumers affected and a general description.
What the engine looks for
Every group below must be satisfied — by an affirmative statement, not a plan, a hedge or a denial — for the control to count as covered. A term ending in … matches any word it begins. Supporting terms do not change the verdict — they raise confidence and distinguish a policy that names a mechanism from one that gestures at a category.
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| GDPR | Art.34 | Communication of a breach to data subjects | breach-notification |
| GDPR | Art.33 | Notification of a breach to the supervisory authority | breach-notification |
| SOC 2 | CC7.4 | Incident response programme | breach-notification |
| PCI DSS 4.0.1 | 12.10 | Incident response plan for suspected compromise of account data | breach-notification |
| HIPAA | 164.308(a)(6)(ii) | Response and reporting (R) | breach-notification |
| HIPAA | 164.404-410 | Breach notification to individuals, HHS and the media | breach-notification |
| NIST CSF 2.0 | RS.CO-02 | Internal and external stakeholders are notified | breach-notification |
| NDPA 2023 | s.40 | Personal data breaches: notification and breach records | breach-notification |