When attackers gain access to the channels used to coordinate a cyber response, the company’s familiar tools can become part of the incident. Email, Slack, Teams and video calls may keep working, while responders lose confidence that their messages are private or that the people on the other end are who they claim to be. That makes a trusted backup communications plan a core response capability, not just a fallback for an outage.
The distinction matters. Many organizations prepare for email or collaboration tools to become unavailable: they keep phone trees, personal contact details and backup conference lines. The harder case is when services remain online but may be under an attacker’s control. A response plan needs to tell teams how to recognize that condition, move out of the affected environment and continue coordinating while investigators establish what was compromised.
Functional tools can still be compromised
During a ransomware attack, disrupted systems make the need for alternate communications obvious. A compromised collaboration environment creates a less visible risk. Messages arrive, meetings proceed and employees may see no sign that their communications are exposed.
Consider a security team that discovers an attacker has accessed accounts used by incident responders. The team must scope the intrusion and plan containment, but sharing those plans in the usual channel could warn the attacker. Legal needs reliable facts to assess notification requirements. Communications staff are preparing for customer questions, and executives expect updates. If the attacker can observe those discussions, each one may reveal information that complicates the response.
The first question becomes simple: who can see what the team is saying? A company that keeps using its normal channels before answering it may hand the intruder a view into the response. The author says they’re aware of several cases in which attackers joined or recorded Zoom and Teams bridges used for incident meetings.
That possibility changes how teams should treat a channel that appears to work. Its availability says nothing about whether its participants, messages or meeting controls can be trusted. Until responders establish otherwise, an account or service under investigation should not be the sole route for sensitive coordination.
Separate response work from legal analysis
Exposure can continue after the attacker is removed. If the intruder read the response channel, teams should assume that containment plans, candid assessments of the intrusion and draft customer statements may have left the company. Some material could appear in an extortion demand; it may also become part of later discovery.
Putting a lawyer in a large incident channel doesn’t make every discussion privileged. Operational coordination and legal advice have different purposes, and sensitive conversations still need clear limits on who participates. An out-of-band plan should give the organization a way to control those discussions and document what was decided, by whom, based on which facts and for what reasons.
Legal should help design that structure before an incident begins. Trying to define participation and recordkeeping while the attacker may still be reading the current channel adds pressure at exactly the wrong time. Planning ahead gives the response team a prepared way to separate operational updates from legal analysis when the usual environment can’t be trusted.
Build around dependencies, identities and devices
Choosing a backup app is an incomplete starting point. The more useful exercise is to map the dependencies shared by primary and emergency communications. Identity services, managed devices, mobile device management, administrator credentials and employee directories can all connect the two environments. If both channels rely on the same compromised component, the backup may fail for the same reason as the primary one.
Identity checks need equal attention. An attacker with access to corporate email or calendars may know that an emergency meeting is planned and have enough context to imitate a responder or executive. Participants need a way to confirm one another without relying on the accounts under investigation.
The plan should cover outside counsel, forensic investigators, insurers and communications advisers as well as employees. Keep their contact details current, define who can approve their participation and decide in advance how the response team will verify them. A trusted channel is only useful if the people who need to join can be authenticated.
Devices can also undermine the plan. Responders may be told to disconnect corporate laptops, so an alternate channel that works only on those machines won’t help. Specify which devices people may use during the response and what information they can access from them. The right design will vary by company size, risk profile and existing systems; the practical test is whether the response can continue without depending on the environment under investigation.
Rehearse the decision to move
Testing whether a backup channel works is only part of the job. Teams also need practice recognizing when to activate it, alerting participants without exposing the move and continuing the response after they switch. The decision can be difficult precisely because the compromised environment may look normal.
A tabletop exercise can start with evidence that an attacker has accessed the email and collaboration accounts of several responders, while both services remain available. Participants then decide what evidence is enough to trigger a move, who has authority to call it and how the team will verify identities in the alternate channel.
Bring security, legal, executives and essential outside partners into the exercise. Add complications that test the plan under pressure: an executive sends conflicting instructions through corporate email, someone joins from an unfamiliar account, an emergency contact is out of date or a third party can’t authenticate.
These details show whether the organization can carry out the move or has only documented it. Useful measures include how long it takes to recognize the need to switch, reach key participants, establish a verified response group and brief leadership. Each fallback to the affected environment points to a dependency or decision the plan hasn’t resolved.
Make the destination familiar before an incident
Response plans often assume the company will have a safe place to coordinate. That assumption deserves the same scrutiny as backup systems, recovery steps and containment playbooks. Teams need defined triggers for leaving familiar tools, a clear owner for that decision and an alternate channel they’ve already practiced using.
When the communication environment is part of a breach, business decisions and questions from customers and employees continue. Rehearsal can help the response team move quickly while protecting the integrity of its coordination. The essential outcome is a prepared route from an uncertain channel to a verified group that can keep the response moving.