Consulting Module

Module 14 โ€” Sovereign Communications

Your incident response plan assumes your communication platform is available. Your incident response plan is wrong. When ransomware takes down corporate IT, Teams goes down too. When Active Directory is compromised, the attacker can monitor your response in real time. This module builds the alternative.

What It Delivers

๐Ÿ’ฌ

Delta Chat โ€” Crisis Out-of-Band Channel

Delta Chat deployed on independent chatmail relay infrastructure in under 10 minutes per user. Encrypted, works on mobile, requires no corporate account or corporate network to operate. When the corporate identity provider is down or compromised, your incident response team still has a secure, verified channel. Used as the crisis fallback that is always independent from whatever is failing.

๐Ÿ 

Matrix/Element โ€” Sovereign Primary Platform (Optional)

For organisations that want to own their primary communications entirely: a self-hosted Matrix homeserver with Element client. No vendor dependency, no Microsoft or Google account required for access, fully federated if needed. Your communication infrastructure becomes sovereign in the same way your authentication infrastructure should be.

๐Ÿ“‹

Crisis Communication Runbook

A documented, tested out-of-band communication protocol โ€” who contacts whom, on which channel, in which sequence, for which incident types. The runbook exists on paper and on every responder's personal device, independent of corporate infrastructure. Tested in the tabletop exercise so the first time it is used under pressure is not the first time it is used at all.

๐Ÿ”‘

Key Verification and Trust Establishment

Encryption keys verified out-of-band before the incident, so responders know they are talking to each other and not to an attacker who has compromised the corporate directory. Trust established in advance is the only trust that holds under incident pressure.

Why Communications Infrastructure Is a Security Control

An incident response that depends on the infrastructure the incident might destroy is not a response capability โ€” it is a hope. For OT environments and critical infrastructure, the dependency is even more direct: control room operators cannot rely on a communication tool that depends on corporate IT when the incident is in the corporate IT.

Scope and Prerequisites

Duration15โ€“30 days
EnvironmentAny
PrerequisitesNone โ€” this module can be delivered standalone as crisis preparedness
Natural follow-onModule 7 (Recovery & Resilience) โ€” sovereign communications integrates with the full incident response capability

Keep talking when everything else is down

The crisis communication channel must be independent from the infrastructure that might fail during the crisis. Module 14 builds it.