News Room

Suspected Breach: Early-Response Messaging, Routing, and Approvals | Code Blue

>_ 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.

00:00–00:30 — Freeze improvisation
  • 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)
00:30–01:00 — Escalate in order
  1. Cyber insurer (policy notice + panel options)
  2. Outside breach counsel (privilege + notification analysis)
  3. DFIR (scoping, containment, exfil analysis)
  4. Crisis PR (holding statements + inquiry routing)
01:00–02:00 — Approve holding statements
  • 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
02:00–04:00 — Legal and regulatory triage
  • 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

TriggerImmediate actionOwnerEscalation 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.

Note: Avoid definitive terms such as "breach" or "no data was accessed" until forensics and counsel confirm.

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.

Note: No speculation, no impact counts, no attribution while facts are unconfirmed.

Routing and Guardrails

>_Inquiry matrix: approved answers, forbidden topics, and escalations

AudienceApproved response (short)Forbidden topicsOwnerEscalation 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

Directive (send now): We are investigating a potential cybersecurity incident. Do not comment publicly or on social media, do not reply to press, and do not speculate in Slack, Teams, email, or WhatsApp. Route all media inquiries to the Spokesperson, all customer questions to Support, and all legal questions to Legal. Preserve all potentially relevant files, messages, and logs. Further updates will come from the Incident Lead.
  • 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

StageOwnerWhat they approveSLA
Fact checkIncident LeadVerifies facts, unknowns, and confidence notes20 minutes
Legal review (parallel)Breach CounselRisk language, notification triggers, regulator constraints20 minutes
Comms review (parallel)Crisis PR / Comms LeadTone, clarity, channel suitability, Q&A alignment20 minutes
Executive releaseSpokesperson / CEO designeeFinal approval to publish10 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

Email template
Subject: Update on a potential security incident [Customer Name], We are investigating a potential security incident affecting [Affected Service]. We have engaged cybersecurity experts and taken steps to secure our environment. At this time, we have not confirmed whether your information was involved. If we determine that personal information was involved, we will notify affected individuals and regulators as required and provide guidance on any protective steps. Our next update is planned by [Next Update Time/Date]. Thank you, [Company Name] | [Official Channel/Status URL]

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.

Status page update
Incident: Potential security incident under investigation Start: [UTC Timestamp] Impact: Under assessment Summary: We have activated our incident response process and engaged cybersecurity experts. We are working to determine what happened and whether any personal information was affected. We will share verified updates here. Next update: [Time/Date] Contact: [Support Link]
Support macro
Thanks for reaching out. We are investigating a potential security incident related to [Affected Service]. Our team has engaged cybersecurity experts and taken steps to secure our environment. We do not yet know whether your information was involved. If we determine your information was affected, we will notify you directly with guidance. For official updates, please check [Status URL].

Support

>_Customer FAQ

1. What happened?
We are investigating a potential security incident and have activated our incident response process.
2. Was my data affected?
We have not confirmed the full scope. If we determine that your personal information was involved, we will notify you directly as required.
3. Why can't you share more details?
We want to provide accurate, verified information. Premature details can be wrong and unhelpful.
4. What should I do now?
Be cautious of suspicious emails, texts, or calls. Use only our official channels and monitor accounts for unusual activity.
5. When will you update us?
We will provide updates through official channels by [Next Update Time/Date] or sooner if we confirm material facts.
6. Will you notify regulators?
If required by law or regulation, we will notify affected regulators and parties.
7. Will you offer identity protection?
If personal information is confirmed affected, we will evaluate appropriate remedies and communicate them directly.
8. Was this ransomware?
We are evaluating the nature of the incident and will not speculate while the investigation is active.
9. How many customers are affected?
We do not want to provide numbers until they are verified.
10. Should I change my password?
If we determine that passwords were affected, we will provide specific guidance. As a best practice, enable MFA and use unique passwords.
11. How did you detect the issue?
We are reviewing our detection and response signals with cybersecurity experts.
12. Where can I get ongoing updates?
Follow [Status URL] and [Official Support Channel].

Activation Roster

>_Call-first contacts and after-hours ownership

RolePrimaryBackupAfter-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

"We have evidence your company was breached last night. Comment?"
  1. Front desk routes to Spokesperson (no-comment directive enforced)
  2. Spokesperson selects Reporter holding statement
  3. Legal + Comms same-time review (SLA met?)
  4. Publish via press inbox auto-reply + media line
  5. Log inquiry and response in Blue Castle fact log

Customer escalation

"Was my data stolen? Should I cancel my card?"
  1. Agent uses Support macro; avoids speculation
  2. Escalates unknowns to Incident Lead via Blue Castle
  3. Confirms next update time and official channel
  4. Records themes for daily risk brief

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.

Skip to content