Join our Newsletter — 33% off our NHI Course
Home› Guides› Out-of-Band Communications Plan Template: Pre-Agreed Channels for When…
Template Incident Response & Forensics

Out-of-Band Communications Plan Template: Pre-Agreed Channels for When Email and Teams Fail

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 10 min read
On this page

If an attacker controls your email, chat or identity provider, every incident call scheduled through them is a briefing for the attacker, and if ransomware takes them down, responders may not even have each other's phone numbers. This template gives [Organisation] a ready-to-complete out-of-band (OOB) communications plan: when to switch, which pre-agreed channels to use, who is allowed in, how members prove who they are, and how to return to normal channels safely. It is the fill-in companion to the Out-of-Band Communications for Incident Response Guide, which explains the design choices, and it sits alongside the Incident Communication Plan Template, which covers what to say to whom. It is for incident response leads, security operations, IT, legal, communications and executives. Replace every [bracketed] placeholder before adoption.

How to use this template

  • Complete it before you need it: an OOB plan written during an incident is written on compromised systems. Finish channel set-up, enrolment and printed copies in peacetime.
  • Keep it off the production estate: store the approved plan and contact sheet as printed copies and in an offline or separately hosted location, as CISA's #StopRansomware Guide advises for incident response plans ("Ensure a hard copy of the plan and an offline version is available").
  • Treat the plan as sensitive: it names the channels and people an attacker would most like to watch. Mark it [TLP:AMBER+STRICT or internal classification] and limit distribution to members.
  • Exercise it: the plan only works if members have actually installed, enrolled in and used the channels.

1. Scope and triggers

1.1 This plan covers communications between incident responders, decision makers and essential external parties (incident response retainer, legal counsel, insurer, key suppliers) when normal corporate channels cannot be trusted or are unavailable.

1.2 Switch to OOB immediately when any of the following is confirmed or suspected:

  • Compromise of the identity provider, a Global Administrator or equivalent tenant-level account, or the email or collaboration platform.
  • Access to mailboxes or chat of executives, security, IT or legal staff by an unauthorised party.
  • Ransomware or destructive activity affecting email, chat, telephony, directory or documentation systems.
  • An intruder known to monitor responses: CISA advisory AA23-320A reports that Scattered Spider actors often search victims' Slack, Microsoft Teams and Exchange Online for conversations about the intrusion and the security response, and frequently join incident remediation calls.
  • Insider involvement in the incident by someone with administrative access to communication systems.

1.3 Consider OOB for any high-severity incident where the scope is not yet known. The incident lead may invoke OOB at any time; invocation does not require prior approval.

2. Roles and contacts

RoleOOB responsibilityPrimaryDeputy
Incident leadInvokes OOB, owns membership decisions, chairs calls[Name][Name]
OOB administratorCreates and closes rooms, adds and removes members, manages devices and accounts[Name][Name]
Executive sponsorBusiness decisions, spending approval, board liaison[Name][Name]
Legal counselPrivilege, regulator and law enforcement contact, record retention[Name][Name]
Communications leadStaff, customer and media messaging using approved channels[Name][Name]
IT and identity leadRecovery actions on production systems[Name][Name]
External IR providerInvestigation and containment support[Firm, hotline, retainer number][Contact]

2.1 The contact sheet lists for each member: name, role, personal and work mobile numbers, OOB account identifier, and a verification phrase held only on the printed sheet. Keep it in [sealed envelopes at named locations, password manager outside the corporate tenant, offline encrypted storage]. Microsoft's incident response planning guidance makes the same point: plan for email and collaboration impairment and the unavailability of personnel phone numbers, and store phone numbers, topologies, build documents and restoration procedures immutably offline. See the Incident Response Contact and Call Tree Template.

Approved channels

PurposePrimary channelFallbackIndependence from production
Core responder chat[Separate collaboration tenant, or end-to-end encrypted messenger on managed devices][Second messenger or SMS group]Separate identity provider, no federation or synchronisation with the production directory
Voice and video calls[Conference bridge in separate tenant, unique PIN per incident][Mobile phone conference]Meeting links never sent through production email or chat
Executive decisions[Dedicated room in the OOB tenant][Phone call with verification phrase]Separate membership from the technical room
Document sharing[OOB file storage][Encrypted removable media]No sync clients on compromised endpoints
External parties[Guest access to OOB tenant, or provider's own secure channel][Phone]Invites sent by phone, not by production email
Total outage[Satellite phones, physical war room at named location][Named meeting point and time]No dependency on corporate network or power

3. Detection and triage

  1. Decide: the incident lead checks the triggers in section 1 and records the decision and time.
  2. Do not announce on production channels: do not post "moving to Signal" or similar on email or chat. Silence the production channel, or keep low-value routine traffic going if alerting the attacker would cause harm, as decided by the incident lead.
  3. Activate by phone: the OOB administrator calls each core member using the printed contact sheet, verifies identity with the verification phrase and directs them to the OOB channel.
  4. Verify every joiner: no one is admitted on the strength of a display name. Confirm by voice call to a known number or in person before adding.
  5. Check device trust: members join only from devices designated in section 4. A laptop that may be compromised is not used for OOB.
  6. Record: start an incident log in the OOB channel, with times, decisions and owners.

4. Containment

Containment here means keeping the response itself out of the attacker's view.

  • Membership: keep the core room small; create separate rooms for technical, executive and legal discussion. Remove members who no longer need access.
  • Devices: use [dedicated OOB mobile devices, or personal mobiles enrolled in advance]; never use endpoints in scope of the incident.
  • Accounts: OOB accounts are not federated with the production identity provider, use phishing-resistant MFA where the platform supports it, and are recoverable without production email. See the Phishing-Resistant MFA Guide.
  • Meeting hygiene: new bridge PIN per incident, lobby enabled, roll call at the start of every call, and challenge of any unrecognised participant. Attackers joining calls is a documented behaviour, not a hypothetical.
  • Information discipline: do not paste credentials, recovery keys or full indicator lists into chat; share them through [vault outside the production tenant] or by voice.
  • Privilege: legal counsel marks privileged rooms and advises on what should be discussed only by voice. See the Legal Privilege in Incident Response Guide.

5. Eradication

5.1 While production channels remain untrusted, eradication actions on email, chat and identity systems (for example resetting administrator accounts or revoking sessions) are coordinated only in OOB, so the attacker does not see the timing in advance.

5.2 Before any production channel is used again, the IT and identity lead confirms in OOB that: attacker access to the identity provider and administrative roles is removed; malicious mailbox rules, forwarding, OAuth grants and app registrations are removed; administrator credentials and service account secrets have been rotated; and audit logging is active. See the Identity Incident Response Playbook.

5.3 Where the OOB environment itself may have been exposed (a member device lost or compromised, an unknown participant joined), the OOB administrator rotates the room, revokes affected accounts and re-verifies all members.

6. Recovery

  1. Restore in stages: return first to one production channel for low-sensitivity coordination, keeping sensitive discussion in OOB until the incident lead declares production trusted.
  2. Announce return by phone or OOB: never by an email that could be spoofed.
  3. Preserve records: export the OOB log, decisions and files into the incident record under legal counsel's instructions, then archive the rooms.
  4. Reset the OOB environment: close incident rooms, rotate bridge PINs and verification phrases, and confirm every member's device is still trusted.
  5. Return equipment: recover and reset loaned devices and satellite phones.

7. Communication and notification

7.1 Staff: when production email is untrusted, brief staff through [managers by phone, SMS broadcast service, intranet hosted outside the tenant, physical notices], with a clear instruction not to discuss the incident on corporate chat.

7.2 Customers, regulators and partners: follow the Incident Communication Plan Template for content and approval. Draft and approve messages in OOB; send them only through channels confirmed clean. Regulatory deadlines continue to run during an outage, so the legal lead tracks them in the OOB log.

7.3 Executives and board: brief them in the executive room or by phone. Executive mailboxes are high-value targets: in the Microsoft Midnight Blizzard breach, the actor accessed mailboxes of senior leadership, cybersecurity and legal staff and initially searched them for information related to Midnight Blizzard itself.

7.4 Impersonation risk: attackers may imitate executives or the IT team to staff during an incident. Remind staff that genuine instructions will come through [named channel] and can be verified by [method]. See the Deepfake CEO Fraud Response Playbook.

8. Post-incident review

  • Time from trigger to OOB invocation, and from invocation to all core members verified and present.
  • Members who could not join (no device, not enrolled, lost credentials) and why.
  • Any production-channel leakage of response information, and any unverified participant.
  • Whether external parties (IR provider, counsel, insurer) could join quickly.
  • Changes needed to channels, membership, contact sheet or storage of the plan.

Implementation guidance

  1. Select channels: choose a primary and fallback for each purpose in section 2, checking that none depends on the production identity provider, email domain, network or endpoint management. Large organisations often stand up a separate minimal collaboration tenant; smaller ones commonly rely on an end-to-end encrypted messenger plus a phone bridge.
  2. Enrol members: create accounts, register MFA, install apps on designated devices and record identifiers on the contact sheet. Include deputies and external parties.
  3. Protect the OOB administrator identity: it is a high-value account. Hold its recovery details offline and treat it like break-glass access. See the Break-Glass Account Guide.
  4. Print and distribute: plan, contact sheet and verification phrases to named holders; record who holds which copy.
  5. Test quarterly: an unannounced activation drill (call tree, join, roll call) within [30 minutes], and an annual tabletop in which email and chat are declared compromised. See the Tabletop Exercise Guide.
  6. Review: update after every activation, every change of role holders and at least every [6 months].
FrameworkReferenceHow this plan supports it
NIST CSF 2.0RS.CO-02 stakeholders notified; RS.CO-03 information shared with designated stakeholders; RC.CO-03 recovery progress communicatedTrusted channels for response and recovery communication
NIST CSF 2.0PR.IR-03 resilience mechanisms in normal and adverse situationsChannels independent of production failure
NIST SP 800-53 Rev. 5IR-8 Incident Response Plan; IR-3 Incident Response Testing; IR-7 Incident Response AssistanceDocumented, tested plan including external assistance
NIST SP 800-53 Rev. 5CP-2 Contingency Plan; CP-8 Telecommunications ServicesAlternate communications when primary services fail
MITRE ATT&CK v20T1114.002 Remote Email Collection; T1213.005 Messaging ApplicationsAttacker collection from email and chat that OOB is designed to defeat

Measure readiness with: share of core members enrolled and able to join in the last drill (target 100 per cent); median time to full verified attendance; age of the contact sheet; and number of drills per year.

Standards and references

Related NHI Mgmt Group resources: Out-of-Band Communications for Incident Response Guide · Incident Communication Plan Template · Crisis Management Guide · Scattered Spider Threat Actor Profile

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.