Enterprise Connect Schedule Viewer

If your enterprise suffers a security breach, your incident response team will need to communicate securely with one another, at a time when the attack may still be ongoing—which means this team’s communications may be vulnerable if run over the enterprise's system. To deal with this reality, some enterprises are building separate communications systems, completely unconnected to the main enterprise communications system and dedicated to security incident response. In this session, you'll learn why such standalone incident response systems are being adopted, the factors that should be taken into account when designing such a system, and how such systems are implemented. A leading expert will explain the security, compliance, and financial implications around securing incident response communications, and will suggest steps you can take to prepare for the potential need to implement such a solution in your enterprise. You’ll come away with practical advice and insights on a problem your enterprise might not have considered yet—but may need to soon.

Takeaways

• How are communications over the normal communications system impacted when the enterprise suffers a security breach? How does this in turn affect the team charged with responding to the security breach?
• If your enterprise implements a separate, standalone communications system for incident response, what should that system look like? Who should design, support, and fund it — the Security or IT/Telecom department?
• What are the security and compliance considerations when building such a standalone system?
• What are the risks of not implementing a standalone incident response communications system?