Crisis communication during a cyberattack: the secure second channel
During an attack, e-mail and internal chat are often compromised. Why the crisis team needs an independent, encrypted channel.

- During an attack, attackers may read e-mail and internal chat — exactly when the crisis team needs them most.
- For entities covered by NIS2, a 24-hour deadline for the early warning starts once a significant incident becomes known.
- An independent crisis channel set up in advance belongs in every emergency plan and must be practised.
Sunday, 6:40 am. The control room reports encrypted file servers, and unknown administrator accounts appear in the directory service. The head of IT wants to call the crisis team together — and asks the obvious question: over which channel? If attackers have been in the network for days, they are reading the e-mails. Crisis communication during a cyberattack therefore starts long before the attack.
The problem: the attacker is at the table
In many serious incidents, attackers first gained access to accounts with far-reaching rights. The usual collaboration tools are therefore potentially compromised: the mail system, internal chat, video conferencing and the file server. Whoever discusses countermeasures there may be revealing them.
Then there is the practical outage: if servers are encrypted or shut down as a precaution, login and mailboxes stop working. Teams then turn to private messengers and phone trees — unstructured, without a record and with the risk that confidential details end up in private chat histories.
Time pressure from the reporting obligation
Since 6 December 2025 Germany's NIS2 implementation act has applied. Essential and important entities must report a significant security incident to the BSI without undue delay, and at the latest within 24 hours of becoming aware of it, in an early warning, followed by an incident notification and a final report (Section 32 BSIG). For these reports, management, IT, data protection, legal and communications must work together quickly and confidentially — often while their own network cannot be trusted.
Crisis communication during a cyberattack: what the channel must do
A crisis channel is more than "yet another messenger". It should:
- Be independent: own accounts, own login, no single sign-on via the possibly compromised directory. Operated outside your own infrastructure or on separate hardware.
- Be end-to-end encrypted: not even the operator may read along, nor an attacker who has taken over a server.
- Cover all forms: chat for situation reports, calls and video for coordination, file storage for situation pictures, draft reports and forensic reports.
- Include outsiders: forensic service providers, law firm, insurer, authorities — as guests without access to internal systems.
- Be traceable: who decided what and when? The final report needs it, and so will the insurer later.
Rule of thumb: The crisis channel is a fire extinguisher, not an everyday tool. It must be there before the fire, and everyone must know where it hangs.
When it has to be fast: sealed messages
Not everyone in the crisis team is in the new channel straight away. For the first minutes a sealed message helps: the text is encrypted and sent as a link over any messenger or by SMS. Only the intended recipient can read it, with an expiry date and read receipt. Access details for the crisis room, meeting points or first instructions can thus be distributed without writing them in plain text into third-party chat histories.
What you can do now
- Set up the crisis channel in advance: with fixed members, own accounts and two-factor login, separate from the company directory.
- Keep the contact list offline: phone numbers and responsibilities on paper, in the safe and with emergency management.
- Register external partners: forensics, law firm, insurer as prepared guests.
- Prepare report templates: for the 24-hour, 72-hour and final reports, stored in the crisis room.
- Practise: at least once a year — ideally on a Sunday morning.
PQVault as a crisis channel
PQVault Collaboration offers chat, calls and video, end-to-end encrypted and additionally protected with NIST-standardised post-quantum algorithms, as SaaS in the EU or separately self-hosted. Outsiders join as guests. Distribute the first messages with PQVault Seal over any messenger; situation pictures and draft reports sit in a data room of PQVault Spaces. More scenarios for operators under Digital infrastructure & data centres.
PQVault is a product of QuantiCor Security GmbH, Darmstadt — specialists in post-quantum cryptography. More about QuantiCor Security
