The denial of service attack on Twitter should remind organizations that are automating their emergency call trees and crisis communications that a single end point isn’t good enough. Given the growth in social networking, more and more organizations are starting to think about leveraging these sites for emergency/crisis communications. But if it becomes your only end point, you risk not getting your message out when it is most needed – during a disaster. In addition, no national telcom network has been tested for a regional disaster, so your phone messages might not get delivered either. Hence, build for emergency notification around multiple channels for best coverage. What is your organization doing to support best coverage?
Read Complimentary Relevant Research
Top Strategic Predictions for 2019 and Beyond: Practicality Exists Within Instability
Technology-based change is happening continuously, and most organizations struggle to see the change in advance. Continuous change can...
View Relevant Webinars
Tags: availability-risk backup-and-recovery bcm bcp bia business-continuity-management business-continuity-planning business-impact-analysis business-resiliency contingency-planning continuity-of-operations coop crisis-management data-protection disaster-recovery emergency-notification emergency-preparedness incident-management it-disaster-recovery mass-notification operational-risk-management pandemic-planning recovery-planning recovery-plans resiliency risk-assessment workforce-continuity
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.