Skip to content
Ransomware Readiness Assessment

TemplateChecked

A ransomware communications plan has holding statements approved before the attack and a channel that works without email

Take the assessmentSee the control mapping

What goes in a ransomware communications plan?

The #StopRansomware Guide asks that the communications plan include organizational communications procedures and templates for cyber incident holding statements, and that the organization reach consensus on the level of detail to share inside and outside and on how information will flow. CPG 5.A adds: identify stakeholders and mechanisms, update senior leadership regularly on major incidents, and follow media communications procedures.

NIST notes that ransomware attacks can disable common communication channels such as email, so planning must include a way to communicate with staff and partners.

Starting channel table. Fill in names in the plan template.
AudienceChannel if email is downOwnerApproved byWhen
Executives and boardPhone tree, then secure messaging set up in advanceIncident commanderIncident commanderWithin the first hours, then at set intervals
All staffText message and phone tree; notice at entrancesCommunications leadExecutive deciderAfter isolation is complete
CustomersAccount managers by phone; holding statement on the websiteCommunications leadBreach counselWhen counsel confirms what can be said
RegulatorsAs each clock requiresBreach counselExecutive deciderPer reporting clocks
Insurer and incident response firmPhone numbers on paperIncident commanderNot applicableAt once
MediaHolding statement onlyCommunications leadBreach counselIf asked or if public

What should a holding statement say?

A holding statement confirms facts that are known and promises updates without guessing. A neutral frame: "[Organization] has identified a cybersecurity incident affecting some of its systems. We took steps to contain it and have notified law enforcement. Some services may be unavailable. We will update [channel] by [time]."

Have counsel approve it before the event. If personal data may be involved, notification content follows the legal duties on the reporting duties page.

Why plan for pre-emptive messaging?

NIST lists pre-emptive messaging among the aims of immediate plan execution and information sharing, alongside stopping continuing exfiltration and the spread of infection. Agreeing wording beforehand removes drafting time from the first day.

Sources

Read 16 November 2026, the day this page was last reviewed, unless a line shows another date.

  1. CISA, MS-ISAC, FBI and NSA: #StopRansomware Guide (September 2023 edition, page read 16 November 2026)
  2. CISA: Cybersecurity Performance Goals 2.0 (CPG 2.0) goal list
  3. NIST IR 8374r1, full text (June 2026)

Last reviewed 16 November 2026.