Recognition
BreachRx is the pioneer of Cybersecurity Incident Response Management (CIRM), helping organizations manage cyber incidents as the enterprise-wide risk events they are.
When the systems you trust are compromised,
your response cannot be.
Out-of-Band Comms gives your enterprise a trusted communications environment when corporate systems are unavailable, compromised, or cannot be trusted.
Cyberattacks Can Take Down Your Communication Systems
Ransomware, identity takeover, and business email compromise can disrupt the same email, chat, and conferencing your team uses to run the response, exactly when coordination matters most.
Communication Continuity
Is Not Response Continuity
Keeping people connected is only the beginning. The enterprise still needs to assign work, make decisions, coordinate handoffs, manage obligations, brief leadership, protect sensitive discussions, and document what happened.
Don’t just move the conversation out-of-band. Move the entire response.
Coordinate the Entire Response in One Secure Environment
Supports ownership, decisions, handoffs, and documentation so your team can focus on the response, not the tools.
Out-of-Band Communication
01Meetings
Secure out-of-band video and audio conferencing for live incident coordination, with support for privileged meetings, recording, and transcription.
02Chat
Dedicated incident, leadership, and action chats that keep fast-moving coordination tied to the active response instead of scattered across text threads.
03Mail
An out-of-band alternative to corporate email for critical incident correspondence when normal inboxes are unavailable or cannot be trusted.
04Scratch Pad
A protected, real-time collaborative workspace for findings, handoffs, decisions, remediation detail, and draft communications, built into the incident.
05Mobile Command™
Secure mobile access for executives to live incident status, what changed, and decision-ready context, without responders rebuilding the update by hand.
Protect Sensitive Discussions Without Fragmenting the Response
Protected workstreams separate sensitive legal discussions from routine operational coordination, while role-based access gives counsel the context they need without exposing the entire incident.
Backup Communications or Response Continuity
BreachRx Out-of-Band Comms
Keep the cyber response operating
Mail, Chat, Meetings, Scratch Pad, Mobile Command
Communications stay tied to the active incident and its procedures
Privileged workstreams connected to broader response context
Real-time access to current status, material changes, and decision-ready incident context
Communications, decisions, ownership, and evidence stay connected to the governed record as the incident unfolds
Standalone or Backup Comms
Keep people communicating
Chat, messaging, conferencing, or email
Often managed separately from the communications layer
Manual control by restricting access
Status communicated through messages and meetings
Manually recreate the incident through messages and meeting notes that must be reconciled with the incident record afterward
Why We Built It
“An out-of-band war room is not an incident response capability. Neither is a backup chat app. Both give you somewhere to talk, not a way to run the response.”
Frequently Asked Questions
We already have an out-of-band chat tool. Why do we need this?
A chat tool only solves one part of the problem. The question is what happens to the rest of the response. Out-of-Band Comms keeps mail, chat, meetings, executive visibility, privileged workstreams, decisions, and the incident record in one governed environment.
What do I get beyond a backup communications channel?
You get the coordination, obligations, and documentation layers in the same environment as the conversation. Out-of-Band Comms is one capability of the Rex Platform, which BreachRx builds for cybersecurity incident response management. Response capacity depends on response continuity.
Can we just use personal phones and personal email during an incident?
Improvised channels restore communication quickly, but they scatter sensitive information, fragment context, and make the response record much harder to assemble afterward. In the event of litigation, personal devices and email messages could be subject to discovery if used for business purposes.
Doesn’t Microsoft, Slack, or Zoom already give us secure communications?
Those tools may be excellent for normal operations. The cyber incident use case is different. Threat actors often join Zoom calls in compromised environments to follow the response team’s every move and stay steps ahead. You need a trusted alternative for the scenario where parts of the corporate communications or identity environment are affected or under investigation.
How is this different from our crisis communications platform?
Employee and mass-notification systems solve a different problem: reaching a large population quickly. Out-of-Band Comms is built for the response team and the cross-functional work of managing the incident itself.
Does BreachRx protect sensitive discussions without fragmenting the response?
Protected workstreams separate sensitive legal discussions from routine operational coordination, while role-based access gives attorneys the context they need without exposing the entire incident.
Technology does not create privilege on its own. Rex supports how legal team members manage privileged response activity while keeping the broader response coordinated.
Why does out-of-band communication need to be part of an incident response platform?
Because the messages, meetings, decisions, approvals, and legal discussions are part of the response. Keeping them in the same governed environment reduces the risk that the emergency communications layer becomes one more disconnected silo.
Keep the Response Running
A cyberattack should not take your incident response down with it. Watch your team move out-of-band and keep coordinating from there.
Book a Demo