Disaster recovery risk assessment for cyberterrorism attacks

Disaster recovery risk assessment for cyberterrorism attacks

Data center association AFCOM says companies aren't doing enough to prepare cyberterrorism disaster recovery plans, but how can a security organization make that justification to C-level executives? On the surface, it seems like a company is much more likely to deal with a security problem because of an unpatched system or a coding error in a Web application vs. a cyberterrorism attack.

    Requires Free Membership to View

    SearchSecurity.com members gain immediate and unlimited access to breaking industry news, virus alerts, new hacker threats, highly focused security newsletters, and more -- all at no cost. Join me on SearchSecurity.com today!

    Michael S. Mimoso, Editorial Director

    By submitting your registration information to SearchSecurity.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSecurity.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Whether cyberterrorism is a real threat is subject to ongoing debate. However, if the question were to be rephrased as: "Are denial-of-service (DoS) attacks (the most common form that cyberterrorist attacks would take) a viable threat?" then yes, this is something that should be addressed as part of a disaster recovery/business continuity (DR/BC) plan. This plan doesn't have to be anything fancy, but it's important to have contact information for the appropriate people at your ISPs and, if relevant, cloud service providers and application service providers (ASPs) as well.

However, it is my general opinion that while DoS and distributed DoS (DDoS) attacks are real threats, they should be categorized as a high impact/low probability threat; so, while it's important to have a plan to deal with them, they shouldn't be your biggest worry.

Instead, I'd worry about low- to medium-impact/medium- to high-probability threats, as they are the ones that can eat up resources quickly in the long run. Case in point: Small virus outbreaks, while relatively low-impact, can be highly disruptive and use up resources that could be focused on other issues. Likewise, patch management, configuration management and asset management all can be done with minimal effort, provided the organization has good change control and operational discipline. Doing this sort of planning right will free up resources to deal with more troublesome, less probable issues like DoS and DDoS attacks.

For more information:

This was first published in November 2009