P3: Insufficient Data Breach Response
You cannot notify the right people if you never logged reads.
What Is P3: Insufficient Data Breach Response?
When an API never logs who read which record, a misused credential leaves one honest answer to whose data was taken: everyone. You'll hit that wall with the regulator's 72-hour clock running, add read-access audit logging so the next incident can be answered, and scope this one from a log that already recorded every request. You'll finish able to size a breach notice to the people actually affected.
What You'll Learn in P3: Insufficient Data Breach Response
- Without a record of reads, the only defensible breach scope is everything the credential could reach.
- Every read of personal data should be logged with the client, the record and the time.
- A log deployed during an incident covers only what happens after it, so know in advance which systems already record reads and for how long.
- The 72 hours to report a breach run from awareness, and the notice should go to the people actually affected.
P3: Insufficient Data Breach Response — Training Steps
-
A Key Used From Outside
Security Operations has found that the API key of an internal reporting service was copied out of a build log and has been used from an unknown address for six days. They revoked it this morning. The key could read any customer record through Pellora's customer API. Whether this is a personal data breach is not in doubt. What nobody knows yet is whose records were read.
-
Ask the Audit Log
The customer API writes an audit log. Alice searches it for every event by the reporting service's client since the first misuse.
-
Connect to the Replica
With no read log, Alice turns to the data itself. She connects to the read-only incident replica of the production database to see what the key could reach.
-
Everyone It Could Reach
The key had no per-customer limit. Every customer in the table was one request away.
-
The Clock Is Running
The Data Protection Office has been told about INC-2291. Pellora became aware of the breach at 09:10 today, and that is when the clock started. The Data Protection Office has to tell the supervisory authority, the regulator for data protection, without undue delay and within 72 hours where feasible. Health data puts customers at high risk, so they have to be told too.
-
Knowledge Check
-
Open the Read Handler
Every one of those calls went through one handler. Alice opens it beside the terminal to see why it leaves no trace.
-
Spot the Gap
The handler finds the record and returns it. Look for what it does not do.
-
Log Every Read
The fix writes an audit event for every read before the record is returned: which client asked, which customer it was, and when. The event holds ids and a time, never the record itself.
-
Read the Fixed Handler
Before shipping it, walk through what the new line records, and what it cannot.
Security Framework Coverage
OWASP Privacy Top 10
- P3 Insufficient Data Breach Response
OWASP ASVS
- V16.3.2 Security Events
- V16.2.1 General Logging
CWE
- CWE-778 Insufficient Logging
CIS Controls
- CIS 3 Data Protection
NIST CSF
- PR.AT-02 Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind
- PR.DS Data Security
NICE Framework
- DD-WRL-003 Secure Software Development
- OG-WRL-008 Privacy Compliance
GDPR
- Art. 33 Notification of a personal data breach to the supervisory authority
- Art. 34 Communication of a personal data breach to the data subject
CCPA/CPRA
- 1798.150 Personal information security breaches
HIPAA
- 164.404 Notification to individuals