>_ Preparedness • Response • Recovery
Suspected Breach: Early-Response Messaging, Routing, and Approvals
Move from chaos to control in the first hours. Use Code Blue's executive-ready holding statements, first-4-hours decision tree, inquiry matrix, and approval SLAs, supported by Blue Castle, the Autonomous AI Platform for Cyber Crises & Operational Resilience, and Code Blue's expert-led services. From first signal to recovery, autonomous agents and expert responders keep messaging disciplined and decisions documented.
First 4 Hours
>_Decision tree to stabilize suspected breaches
Trigger on any credible report of unauthorized access, extortion/ransomware claim, anomalous activity with potential data exposure, or regulator/reporters contacting you about a cyber incident.
- Designate Incident Lead and Spokesperson (default: CISO/GC names per plan)
- Issue internal no-comment directive and evidence-preservation notice
- Create single fact log (what/when/source/confidence/owner)
- Cyber insurer (policy notice + panel options)
- Outside breach counsel (privilege + notification analysis)
- DFIR (scoping, containment, exfil analysis)
- Crisis PR (holding statements + inquiry routing)
- Use non-speculative customer + reporter versions below
- Choose channels: website, support macro, press inbox auto-reply
- Set next-update timebox (e.g., 2–4 hours) and owner
- Breach counsel runs notification matrix (state/sector/SEC/contract)
- DFIR provides initial scoping facts, logs preserved
- Decide on law enforcement/CISA/FBI notifications as appropriate
Trigger criteria and routing
| Trigger | Immediate action | Owner | Escalation order |
|---|---|---|---|
| Credible claim of unauthorized access or data theft | Freeze comms; open war room; preserve evidence. | Incident Lead | Insurer → Breach Counsel → DFIR → Crisis PR |
| Ransomware/extortion note or dark web post | Do not engage attackers directly; capture artifacts; consult counsel. | CISO / GC | Insurer → Breach Counsel → DFIR → Crisis PR |
| Reporter asks about a "breach" rumor | Use reporter holding statement; route to Spokesperson. | Comms Lead | Spokesperson → Breach Counsel → Exec approver |
| Customer tickets spike about security | Enable support macro; prohibit speculation; log themes. | Support Lead | Support Lead → Comms → Incident Lead |
Approved Messaging
>_Holding statements with legal guardrails
Customer holding statement
We are investigating a potential security incident and have activated our incident response process. We have engaged cybersecurity experts, taken steps to secure our environment, and are working to determine what happened and whether any customer information was affected.
If we determine that personal information was involved, we will notify affected individuals and regulators as required and provide recommended steps. We will share updates through our official channels as soon as we can confirm facts.
Reporter holding statement
We are aware of reports regarding a potential security incident and are actively investigating. We have engaged cybersecurity experts, taken steps to secure our systems, and are working to understand the scope and impact. Because the investigation is ongoing, we are not going to speculate about the cause, the actor, or whether specific data was accessed. If notification is required, we will notify affected parties and regulators as appropriate.
Routing and Guardrails
>_Inquiry matrix: approved answers, forbidden topics, and escalations
| Audience | Approved response (short) | Forbidden topics | Owner | Escalation path |
|---|---|---|---|---|
| Reporters | "We are investigating; experts engaged; we will update with verified facts; no speculation." | Cause/actor attribution, unverified impact numbers, "no data taken" claims | Spokesperson | Spokesperson → Breach Counsel → Exec approver |
| Customers | "Investigation ongoing; if personal information was involved, we will notify you directly." | Account-specific assurances, promises on timing beyond law, over-reassurance | Support Lead | Support → Comms → Legal → Exec |
| Partners/Vendors | "Assessing potential impact; will inform if interfaces or shared data are implicated." | Blame statements, internal security details, network maps | Vendor Mgmt | Vendor Mgmt → Legal → Incident Lead |
| Investors/Board | "Status, known/unknowns, next milestones; materiality under assessment." | Public statements before SEC/securities counsel review | GC / CFO | GC → Securities Counsel → CEO/Board Chair |
Internal Control
>_Employee no-comment directive and channel rules
- Channels: Use only the designated incident channels in Blue Castle/war room.
- Evidence: Do not wipe or rebuild systems without DFIR guidance.
- Approval: No external message without Legal and Comms approval.
Governance
>_Named approval workflow with SLAs
| Stage | Owner | What they approve | SLA |
|---|---|---|---|
| Fact check | Incident Lead | Verifies facts, unknowns, and confidence notes | 20 minutes |
| Legal review (parallel) | Breach Counsel | Risk language, notification triggers, regulator constraints | 20 minutes |
| Comms review (parallel) | Crisis PR / Comms Lead | Tone, clarity, channel suitability, Q&A alignment | 20 minutes |
| Executive release | Spokesperson / CEO designee | Final approval to publish | 10 minutes |
Legal and Comms review run concurrently once fact check is complete, so the full cycle fits inside the 01:00–02:00 holding-statement window: roughly 20 minutes fact check, 20 minutes parallel Legal and Comms review, then 10 minutes for executive release.
Note: For public companies, involve securities counsel before any external statement; SEC Item 1.05 Form 8-K may be required within four business days after determining materiality.
Ready Templates
>_Customer holding statement as email, status page, and support macro
Do not publish a "date of first awareness" or any incident timeline in an early holding statement unless breach counsel has approved it. Stating a date before forensics are complete can lock the company into a timeline it cannot yet verify.
Support
>_Customer FAQ
Activation Roster
>_Call-first contacts and after-hours ownership
| Role | Primary | Backup | After-hours ownership |
|---|---|---|---|
| Incident Lead (internal) | [Name] • [Phone] • [Email] | [Name] • [Phone] | [Weeknights: Name A] • [Weekends: Name B] |
| Cyber insurer / broker | [Carrier/Broker] • Claim line: [Phone] | [Alt contact] | 24/7 claims: [Number] |
| Outside breach counsel | [Firm] • [Partner] • [Phone] | [Associate] • [Phone] | On-call: [Line] |
| DFIR (forensics) | [Firm] • Duty manager: [Phone] | [Alt] • [Phone] | Pager/Hotline: [Number] |
| Crisis PR | [Agency] • [Lead] • [Phone] | [Deputy] • [Phone] | After-hours: [Line] |
| Spokesperson | [Exec name] • [Phone] | [Deputy] • [Phone] | On-call: [Number] |
Note: Have counsel retain DFIR and PR where appropriate to structure work under legal direction; privilege is fact-specific and not automatic.
Verification
>_15-minute tabletop to test routing and approvals
Mock reporter inquiry
- Front desk routes to Spokesperson (no-comment directive enforced)
- Spokesperson selects Reporter holding statement
- Legal + Comms same-time review (SLA met?)
- Publish via press inbox auto-reply + media line
- Log inquiry and response in Blue Castle fact log
Customer escalation
- Agent uses Support macro; avoids speculation
- Escalates unknowns to Incident Lead via Blue Castle
- Confirms next update time and official channel
- Records themes for daily risk brief
Legal and Regulatory Guardrails
>_Say enough to show control — without legal overreach
- All U.S. states and territories have breach notification laws with differing triggers, timing, and content.
- FTC guidance: notify appropriate parties (law enforcement, affected businesses, individuals) as circumstances require; health-app/consumer health data may trigger FTC Health Breach Notification Rule timelines (often within 60 days).
- Public companies: SEC has distinguished voluntary incident discussions from mandatory Item 1.05 Form 8-K after a materiality determination; disclosure generally due within four business days of that determination.
- Consider sector rules (e.g., HIPAA, GLBA, education, critical infrastructure), contracts, and insurer obligations.
- Critical infrastructure entities: CIRCIA will require covered entities to report covered cyber incidents to CISA within 72 hours and ransom payments within 24 hours. As of October 2026 the CISA final rule has not been published and these reporting obligations are not yet in force; confirm current status with counsel.
- Coordinate with CISA/FBI/IC3 as appropriate; do not validate attacker claims publicly while facts are unconfirmed.
Blue Castle
>_How Code Blue and Blue Castle enable disciplined crisis communication
One operational view
Share a single, structured status across security, legal, privacy, communications, and business continuity planning (BCP) tracks, with Decision Tracking that keeps every call documented and audit-ready.
Role-based approvals
Route drafts to Incident Response (IR), Crisis Management Team (CMT), legal, and PR for fast, traceable sign-off through Cyber Crisis Communications workflows.
Autonomous support in the War Room
Autonomous agents draft, route, and track the first messages while expert responders coordinate decisions and keep leadership aligned, acting on the judgment of hundreds of real cyber crises.