Prepare for and Respond to a Business Disruption After an Aggressive Cyberattack
Global boardroom awareness of the rapid increase in the scale and sophistication of cyberattacks, as well as their financial and reputational impact, is skyrocketing. To ensure effective enterprisewide risk containment, cybersecurity and BCM leaders must align their response and recovery processes.
- A successful cyberattack can shut down operations — not just for a few hours, but rather for multiple days and weeks. The collateral damage, such as information leaks, reputational damage and so on, can continue for much longer.
- Backup systems, applications and data may also be infected and, therefore, of little usable value during response and recovery operations in the short term — they may need to be cleansed before they can be used for recovery.
- Cyberattacks can easily derail your documented and tested RTOs and recovery point objectives because production and recovery IT assets are likely to be infected.
- Computer security incident response teams may not be aware of BCM automation solutions that can be leveraged for faster and more comprehensive response and recovery actions after a cyberattack.
Here’s the full article: you might need Gartner credentials to access it: Prepare for and Respond to a Business Disruption After an Aggressive Cyberattack .
Category: advisory bcm-process business-continuity disaster-recovery it-disaster-recovery-management it-service-continuity-management john-morency roberta-witty security security-of-applications-and-data
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.