Prompt Details
Model
(claude-5-opus)
Token size
2,704
Example input
[BREACH_DESCRIPTION]: An unsecured S3 bucket exposed customer records for approximately 3 weeks before discovery via a security researcher's responsible-disclosure email; access logs show 4 distinct external IPs accessed the bucket during that window
[AFFECTED_JURISDICTIONS]: California, European Union
[ORG_CONTEXT]: 80-person e-commerce company, no dedicated incident-response function, outside counsel retained after discovery
[DATA_TYPES_INVOLVED]: Full names, email addresses, hashed passwords, last-4 payment card digits
Example output
# Data Breach Regulatory Response Runbook
## 80-Person E-Commerce Company — S3 Bucket Exposure (Date Not Specified)
---
## CARD 1 — EXECUTIVE SITUATION SUMMARY
**What's known:** An unsecured Amazon S3 bucket exposed customer records — full names, email addresses, hashed passwords, and last-4 payment card digits — for approximately three weeks before discovery. Discovery occurred via a security researcher's responsible-disclosure email, and access logs show four distinct external IP addresses accessed the bucket during the exposure window. Outside counsel has been retained; the organization (an 80-person e-commerce company) has no dedicated incident-response function.
**Most time-critical action:** Confirm, in writing, that the bucket's public access has been fully revoked and that no further unauthorized access is possible — this is a foundational fact the rest of the runbook depends on and is **not confirmed** in the information provided. `TIME-CRITICAL`.
**Evidence-quality warning:** Several facts material to notification scope are currently `UNKNOWN` and must be treated as open, per Rule 9:
- **Containment status is not confirmed** — the description states the bucket was unsecured and exposed for ~3 weeks, but does not state that remediation (revoking public access, closing the exposure) has occurred. Until confirmed, all population and scope figures below must be read as provisional, not final.
- **Population affected is not provided** — no count has been given and none is invented here.
- **Whether the security researcher's own IP is among the "4 distinct external IPs" is unknown** — this affects whether the access pattern reflects one benign discoverer plus up to three unknown parties, or four unknown parties. This is a technical/forensic determination, out of scope for this tool (see Card 13).
- **Password hash algorithm/strength is unknown** — materially affects the realistic risk of credential compromise.
- **Whether the organization has an EU establishment, or only serves EU customers remotely, is unknown** — affects which GDPR territorial-scope mechanism and lead supervisory authority analysis applies.
---
## CARD 2 — IMMEDIATE ACTIONS (0–24H)
1. **Confirm and document bucket containment** — verify public access has been revoked, bucket policy corrected, and no further external access is possible. Owner: Engineering/IT lead. `TIME-CRITICAL`.
2. **Preserve all available evidence before any rotation or retention expiry** — S3 access logs, CloudTrail logs, bucket policy/configuration change history, IAM policy history. Owner: Engineering/IT, under counsel direction. `TIME-CRITICAL`.
3. **Preserve the researcher's original disclosure email and all related correspondence** — do not forward-and-delete; preserve headers and full thread. Owner: Whoever received the disclosure (IT/Security/Support). `TIME-CRITICAL`.
4. **Brief outside counsel on jurisdictional facts and confirm engagement scope** covers breach-notification analysis and communications review, not just general advisory. Owner: Executive sponsor. `TIME-CRITICAL`.
5. **Establish and document the "date of awareness"** — the date the responsible-disclosure email was received — since GDPR's notification clock is commonly understood to run from awareness. Owner: Legal/Compliance liaison. `TIME-CRITICAL`.
6. **Engage a third-party forensics firm** to determine root cause, confirm the true scope of access, and validate containment. This is where the "how did this happen" question belongs — not this runbook. Owner: Outside counsel/IT. `TIME-CRITICAL`.
7. **Stand up an internal incident coordination point of contact** (single-threaded owner) even in the absence of a formal IR function. Owner: COO/CEO or designated executive. `STANDARD`.
8. **Hold all external statements pending classification** — no public or customer-facing communication until Card 7's plan is approved. Owner: Communications lead. `CONDITIONAL`.
9. **Inventory which customer records were actually stored in the affected bucket** versus other data stores, to bound the classification work in Card 3. Owner: Data/Engineering. `STANDARD`.
10. **Prepare an acknowledgment to the security researcher** consistent with responsible-disclosure norms (do not disclose case specifics beyond appropriate scope). Owner: Security/Communications liaison. `STANDARD`.
---
## CARD 3 — BREACH CLASSIFICATION REGISTER
| Data Type | Jurisdiction | Population Scale (if known) | Sensitivity | Classification Status |
|---|---|---|---|---|
| Full names | California | UNKNOWN | Low-Moderate (identifier) | PRELIMINARY — likely relevant only in combination with other elements below |
| Full names | European Union | UNKNOWN | Low-Moderate (identifier) | PRELIMINARY — personal data under GDPR Art. 4(1) on its face |
| Email addresses | California | UNKNOWN | Low-Moderate (identifier; phishing/credential risk when paired with password) | PRELIMINARY |
| Email addresses | European Union | UNKNOWN | Low-Moderate | PRELIMINARY — personal data on its face |
| Hashed passwords | California | UNKNOWN | Moderate-High — sensitivity ceiling `UNKNOWN` pending hash-algorithm confirmation | PRELIMINARY — commonly a triggering element when paired with a unique identifier |
| Hashed passwords | European Union | UNKNOWN | Moderate-High — same caveat | PRELIMINARY |
| Last-4 payment card digits | California | UNKNOWN | Low standalone (truncated PAN); Moderate in combination with other elements | PRELIMINARY — not a full card/account number on its face |
| Last-4 payment card digits | European Union | UNKNOWN | Low-Moderate | PRELIMINARY |
*Containment caveat (Rule 9): every row above is provisional. Because bucket remediation is not confirmed as complete, both the population scale and the final data-type scope may widen. None of these classifications should be treated as final until containment is confirmed and forensics has validated scope.*
---
## CARD 4 — NOTIFICATION TIMELINE MAP
| ID | Jurisdiction | Typical Window | Who Must Be Notified | Trigger Condition |
|---|---|---|---|---|
| N1 | California | `GENERAL PRACTICE — NOT VERIFIED`: commonly described as "the most expedient time possible and without unreasonable delay"; no fixed day-count for this fact pattern | Affected California residents; California Attorney General if more than 500 CA residents are affected | Unauthorized acquisition of personal information — here, potentially an identifier (name/email) in combination with a password. `TIME-CRITICAL` given unconfirmed containment and elapsed exposure window. |
| N2 | European Union | `GENERAL PRACTICE — NOT VERIFIED`: commonly cited as 72 hours from awareness for supervisory-authority notification "where feasible" (Art. 33); "without undue delay" to individuals if high risk (Art. 34) | Competent supervisory authority (lead authority determination depends on establishment, which is `UNKNOWN`); affected individuals if risk is assessed as high | Personal data breach likely to result in a risk to the rights and freedoms of natural persons. `TIME-CRITICAL` — if awareness is dated to the researcher's email, any 72-hour framing may already be running or elapsed. |
*Both N1 and N2 are assessed independently per Rule 4 — neither's timeline or trigger is assumed to apply to the other jurisdiction.*
---
## CARD 5 — NOTIFICATION OBLIGATION DIAGNOSTIC
### N1 — California
| Factor | Score | Status | Rationale |
|---|---|---|---|
| Regulatory Trigger Clarity | HIGH | `GENERAL PRACTICE — NOT VERIFIED` | Email/username exposed in combination with a hashed password matches the fact pattern commonly treated as triggering California's breach-notification statute; exact statutory language requires counsel confirmation. |
| Population Affected Scale | UNKNOWN | UNKNOWN | Not provided; directly determines whether the CA AG 500-resident notification threshold is met. |
| Data Sensitivity | MEDIUM-HIGH | `GENERAL PRACTICE — NOT VERIFIED` | Credential-pair exposure creates credential-stuffing/account-takeover risk; ceiling depends on hash strength, which is unknown. |
| Existing Safeguard Mitigation | UNKNOWN | UNKNOWN | Hash algorithm and salting practice not stated; this materially changes the realistic risk-of-harm analysis. |
| Regulatory Exposure Cascade *(OPERATIONAL EXTENSION — NOT A LEGAL DETERMINATION)* | LOW-MEDIUM | `SEMANTIC INFERENCE` | No stated cross-jurisdiction trigger (e.g., no named data-sharing agreement); inference only from the likelihood that a single e-commerce customer base overlaps CA and EU residents. |
**Core Obligation Reading (N1):** Preliminary indication is that a California notification obligation is **likely implicated** by the identifier+password combination, but the population count and exact statutory match must be confirmed with counsel before this becomes a final determination.
### N2 — European Union
| Factor | Score | Status | Rationale |
|---|---|---|---|
| Regulatory Trigger Clarity | HIGH | `GENERAL PRACTICE — NOT VERIFIED` | Unauthorized third-party access to names, emails, hashed passwords, and partial payment data facially meets the "personal data breach" definition; precise article-by-article application needs counsel confirmation. |
| Population Affected Scale | UNKNOWN | UNKNOWN | Not provided; affects the Art. 34 "high risk" threshold for individual notification. |
| Data Sensitivity | MEDIUM-HIGH | `GENERAL PRACTICE — NOT VERIFIED` | Same rationale as N1. |
| Existing Safeguard Mitigation | UNKNOWN | UNKNOWN | Hash strength and whether payment data is otherwise tokenized/PCI-scoped are not stated. |
| Regulatory Exposure Cascade *(OPERATIONAL EXTENSION — NOT A LEGAL DETERMINATION)* | LOW-MEDIUM | `SEMANTIC INFERENCE` | No stated cross-jurisdiction trigger; inference only from overlapping customer base. |
**Core Obligation Reading (N2):** Preliminary indication is that an EU notification obligation is **likely implicated**, but is contingent on two unresolved facts: (1) population/risk scale, and (2) whether the company has an EU establishment (affecting lead-authority mechanics) or is in scope solely via GDPR's extraterritorial reach — neither of which is stated in the organizational context provided.
---
## CARD 6 — INTERNAL STAKEHOLDER COMMUNICATION PLAN
| Audience | Objective | Channel | Timing |
|---|---|---|---|
| Executive leadership | Situational awareness, resourcing decisions, approval authority | Direct briefing (call/in-person) | Within hours of confirmed engagement |
| Engineering/IT | Containment confirmation, evidence preservation instructions, forensics coordination | Direct briefing + written instructions | Immediate |
| Customer support team | Prepare for inbound inquiries; scripted holding language only — no speculation | Written briefing document, live Q&A session | Before any external notice goes out |
| Legal/Compliance liaison | Central coordination point with outside counsel | Ongoing working channel | Immediate, continuous |
| All employees (need-to-know basis) | Confidentiality expectations; no public/social commentary on the incident | Internal memo | Within 24–48 hours, after leadership alignment |
| Payment processor / acquiring bank relationship owner | Flag potential PCI-adjacent exposure (last-4 digits) for their own assessment | Direct contact | Within 24–48 hours |
---
## CARD 7 — EXTERNAL COMMUNICATION PLAN
| Audience | Message Objective | Channel | Timing | Approval Needed From |
|---|---|---|---|---|
| Affected individuals — California | Statutory notice of breach and protective steps (per counsel-finalized language) | Direct notice (email/mail per counsel guidance) | Per N1 timeline (Card 4), pending scope confirmation | Outside counsel + executive sponsor |
| Affected individuals — European Union | Notice per Art. 34 if risk assessed as high | Direct notice | Per N2 timeline (Card 4), pending risk assessment | Outside counsel + executive sponsor |
| California Attorney General | Regulatory notification if population threshold met | Formal filing per AG process | Per N1 timeline, once population confirmed | Outside counsel |
| EU supervisory authority(ies) | Regulatory notification per Art. 33 | Formal filing per DPA process | Per N2 timeline, once lead authority determined | Outside counsel |
| Press/media | Holding statement only — factual, non-speculative, no root-cause claims | Prepared statement, reactive only | Only if inquiry received or notice becomes public | Communications lead + outside counsel |
| Business/payment partners | Notice of potential exposure relevant to shared data | Direct contact | Within 24–72 hours | Executive sponsor + counsel |
| Security researcher | Acknowledgment and thanks for responsible disclosure | Direct email reply | Within 24–48 hours | Security/Communications liaison |
---
## CARD 8 — EVIDENCE PRESERVATION CHECKLIST
*This checklist supports preservation only — it is not a substitute for a forensics firm's guidance, and forensics should be engaged before further remediation steps that could alter system state.*
- Preserve S3 access logs and CloudTrail logs covering the full exposure window and discovery period; do not allow default log-rotation/retention policies to purge them.
- Preserve the bucket's policy and configuration change history (including any recent changes prior to discovery).
- Preserve IAM policy and role-assignment history relevant to the bucket.
- Preserve the security researcher's original disclosure email, full headers, and any follow-up correspondence.
- Avoid modifying, deleting, or "cleaning up" the affected bucket's contents or configuration until forensics has imaged/documented current state — remediation (e.g., revoking public access) is still appropriate and should not be delayed, but should be logged with timestamps.
- Document every containment action taken, with timestamp and actor, to preserve a clear timeline.
- Issue a legal hold notice to relevant custodians (engineering, IT, support) covering all incident-related records.
- Maintain a chain-of-custody log for any exported logs or artifacts handed to forensics or counsel.
---
## CARD 9 — CROSS-JURISDICTION CASCADE MAP
| Trigger Jurisdiction | Linked Jurisdiction | Cascade Confidence | Operational Consequence |
|---|---|---|---|
| European Union | California | `SEMANTIC INFERENCE` | If an EU notification proceeds, it may be operationally sensible to revisit the California notification decision on a similar timeline for consistency — but this is not a legal trigger and is **insufficient on its own to justify unilaterally notifying California regulators or individuals**. |
| California | European Union | `SEMANTIC INFERENCE` | Same reasoning in reverse — a California notification decision does not establish or waive any EU obligation. |
*No `EXPLICIT` cascade was identified. Nothing in the breach description or organizational context states an actual cross-jurisdiction trigger (e.g., a data-sharing agreement requiring joint notice), so both entries remain at `SEMANTIC INFERENCE` and neither should drive a notification decision by itself.*
---
## CARD 10 — REMEDIATION & RECOVERY PLAN
- Confirm (if not already done) that the bucket is fully non-public and access is restricted to authorized principals only. *(Detection & Containment)*
- Audit the broader cloud environment for similarly configured buckets or storage resources — this single bucket may not be the only exposure. *(Assessment & Classification)*
- Force a password reset for affected accounts as a precaution, regardless of hash strength, given the credential-pair exposure. *(Remediation & Recovery)*
- Monitor for credential-stuffing or account-takeover activity on affected accounts in the weeks following. *(Remediation & Recovery)*
- Coordinate with the payment processor/acquiring bank regarding the last-4 digit exposure and any obligations under the merchant agreement. *(Remediation & Recovery)*
- Consider offering credit monitoring or identity-protection services to affected individuals — this is a common voluntary practice, not confirmed as legally mandated here (`GENERAL PRACTICE — NOT VERIFIED`), and is a business/counsel decision. *(Remediation & Recovery)*
- Hand off the technical root-cause question (how the bucket became unsecured, and why it went undetected for three weeks) to the forensics firm and engineering — **this runbook does not diagnose that question.** *(Remediation & Recovery → feeds Post-Incident Review)*
- Stand up a dedicated support channel (phone/email) for affected-customer inquiries once notice goes out. *(Remediation & Recovery)*
---
## CARD 11 — POST-INCIDENT FOLLOW-UP
- Conduct a full review of cloud storage access-control practices and provisioning defaults across the environment, informed by forensics' root-cause findings. *(Post-Incident Review)*
- Formalize an incident-response function or a retained IR/forensics arrangement — the organization currently has none. *(Post-Incident Review)*
- Define and document the duration of any affected-user support offering (e.g., credit monitoring period) as a business decision, once made. *(Post-Incident Review)*
- Track any regulator follow-up correspondence or requests for additional information (CA AG, EU supervisory authority) through to close-out. *(Post-Incident Review)*
- Conduct a lessons-learned review covering detection gap (3-week undetected exposure) and the role of the responsible-disclosure channel in surfacing it. *(Post-Incident Review)*
- Review or establish a formal responsible-disclosure/bug-bounty policy, given that this incident was surfaced by an external researcher rather than internal monitoring. *(Post-Incident Review)*
---
## CARD 12 — VERIFICATION MAP
| Named Regulation | Cited Obligation | Verification Status | Note |
|---|---|---|---|
| California data breach notification law (Cal. Civ. Code §1798.82 et seq.) | Notice to affected CA residents; CA AG notice if >500 CA residents affected | `REQUIREMENT UNVERIFIED against external statutory text` | Confirm current statutory text, applicable thresholds, and "without unreasonable delay" standard with counsel. |
| California Consumer Privacy Act / CPRA private-right-of-action provisions | Potential separate exposure given the identifier+password combination | `REQUIREMENT UNVERIFIED against external statutory text` | Confirm applicability and interaction with the breach-notification statute with counsel. |
| EU General Data Protection Regulation (Regulation (EU) 2016/679), Arts. 33–34 | Notification to supervisory authority; notification to data subjects if high risk | `REQUIREMENT UNVERIFIED against external statutory text` | Confirm the 72-hour framing, lead-authority mechanics, and high-risk threshold with counsel; also confirm territorial-scope basis (establishment vs. Art. 3(2)). |
| PCI DSS (contractual/industry standard, not a statute) | Reporting obligations to acquiring bank/card brands regarding payment-data exposure | `REQUIREMENT UNVERIFIED against external statutory text/contract` | Confirm actual merchant-agreement obligations with counsel and the payment processor; last-4-only exposure may or may not trigger contractual reporting. |
---
## CARD 13 — SCOPE BOUNDARY & OPEN QUESTIONS FOR COUNSEL
**What this tool does not do:**
- It does not perform technical forensics or determine how or why the bucket became unsecured or went undetected for three weeks — that belongs to the forensics firm and technical incident-response process referenced in Cards 2 and 10.
- It does not provide legal certification of any notification deadline, threshold, or obligation — every timeline and trigger above is tagged `GENERAL PRACTICE — NOT VERIFIED` and requires counsel confirmation against current statutory text.
- It does not provide a complete PR strategy — Cards 6–7 are a bounded messaging skeleton, not a full communications/reputation-management plan.
**Open questions for counsel and forensics:**
- Has bucket containment been confirmed complete, and when exactly?
- What is the confirmed count of affected California residents and EU data subjects?
- Of the four external IPs, which (if any) correspond to the disclosing researcher versus unknown parties?
- What hashing algorithm and salting method was used for the exposed passwords?
- Does the organization have an EU establishment, or is EU exposure based solely on offering goods/services to EU residents?
- Does the last-4 payment-card exposure trigger any PCI-DSS or card-network contractual reporting obligation?
- What is the confirmed "date of awareness" for GDPR clock purposes, and does it match the date of the researcher's email?
---
## CARD 14 — METHOD NOTE
This runbook is a coordination aid for use during an active incident — it is not a legal determination, a forensic finding, or a substitute for either. California and EU obligations were assessed independently, consistent with the rule that no jurisdiction's notification triggers or timelines were assumed to transfer from the other simply because both were named in the same request. The Incident Response Governance Framework (Detection & Containment → Assessment & Classification → Notification Obligations → Internal Governance & Communication → Remediation & Recovery → Post-Incident Review) structures the action items throughout, and the Regulatory Exposure Cascade analysis in Cards 5 and 9 is explicitly an operational planning lens, not a legal determination of cross-jurisdiction obligation. The organization's context — an 80-person e-commerce company with no dedicated incident-response function but outside counsel already retained — shaped the feasibility notes above (e.g., recommending a retained forensics arrangement and a single-threaded internal coordinator rather than assuming an in-house IR team) without dropping or softening any notification obligation that would otherwise apply. **This runbook does not replace, and must be followed up with: (1) confirmation from retained outside counsel on every deadline, threshold, and obligation tagged `GENERAL PRACTICE — NOT VERIFIED` above; (2) a qualified forensics firm to determine root cause and validate the true scope of access; and (3) a technical incident-response process to close the underlying exposure.**
---
**VERDICT: ESCALATE TO COUNSEL IMMEDIATELY — the most time-critical open item is confirming bucket containment and the population/scope figures needed to finalize the California (N1) and EU (N2) notification decisions; outside counsel is already retained and should receive Cards 1, 4, 5, and 13 first.**
Get this prompt + 9 more with Select$14 your first month, then $19/mo$14 first month, then $19/mo
View SelectBy purchasing this prompt, you agree to our terms of service
CLAUDE-5-OPUS
🚨 During an active data breach, get an instant 14-card regulatory-notification, communications, and evidence-preservation runbook — never a technical root-cause guess. Assesses each affected jurisdiction independently, flags time-critical actions clearly, and never states a statutory deadline as settled fact. Built to stay usable under real time pressure: the most urgent material sits right up front. This is the coordination aid your incident response team wishes existed at 2am. 🕐
...more
Added over 1 month ago
