Vulnerabilities / Threats
11/23/2010
12:29 PM
50%
50%

Enterprises Overlook Virtualization, Cloud In Disaster Recovery

Symantec study finds 44% of data on virtualized systems is rarely backed up, and 60% of virtualized servers are not included in disaster recovery plans.

Slideshow: Cloud Security Pros And Cons
Slideshow: Cloud Security Pros And Cons
(click image for larger view and for full slideshow)

When making disaster recovery plans, don't forget virtualized and cloud computing environments. That's the warning from research which found that 44% of enterprise data stored on virtualized systems is rarely backed up, and 60% of virtualized servers aren't included in corporate disaster recovery plans -- up from 45% of servers in 2009.

Those results come from a survey of 1,700 enterprise employees, conducted by Applied Research, for Symantec's sixth-annual study of corporate disaster recovery trends.

Today, 26% of the total annual IT budget goes to disaster recovery-related initiatives. But despite that level of spending, there's still room for improvement. For example, the survey found that only one in five organizations use replication or failover technologies for safeguarding virtualized environments.

When it comes to cloud computing, survey respondents said that approximately 50% of mission-critical applications run in the cloud. Still, 66% of respondents report having security concerns relating to storing data in the cloud, and 55% said that controlling failovers and ensuring high levels of availability continue to be cloud-related challenges.

Without a doubt, one disaster recovery challenge is that data now lives in an ever-increasing number of locations. "While organizations are adopting new technologies such as virtualization and the cloud to reduce costs and enhance disaster recovery efforts, they are currently adding more complexity to their environments and leaving mission critical applications and data unprotected," said Dan Lamorena, director of the storage and availability management group at Symantec, in a statement.

Indeed, the typical data backup -- at 82% of organizations -- doesn't occur daily, but weekly, at most.

The survey also found that when it comes to recovering from downtime, predictions and reality aren't in sync. While respondents expect to be back up and running just two hours after an outage, the average downtime over the past year was 5 hours, with organizations experiencing an average of four "downtime incidents" in the past 12 months.

Symantec said organizations tend to get swamped by outages -- more than they should -- related to "basic causes such as system upgrades, power outages, and cyberattacks."

Over the past five years, for example, organizations said they'd experienced downtime principally due to system upgrades (for 72% of respondents), followed by power outages (70%), fire (69%), configuration issues (64%), plus cyber attacks, malicious employees, and data leakage or loss (all 63%). Meanwhile, almost half of organizations also experienced downtime due to floods, hurricanes, earthquakes, tornados, terrorism, tsunamis, volcanoes, and war.

Given that power outages are a not-uncommon source of downtime, another surprising finding is that only 26% of organizations assess, in advance, what impact a power outage or failure might have on IT availability.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Tech Digest, Dec. 19, 2014
Software-defined networking can be a net plus for security. The key: Work with the network team to implement gradually, test as you go, and take the opportunity to overhaul your security strategy.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-3971
Published: 2014-12-25
The CmdAuthenticate::_authenticateX509 function in db/commands/authentication_commands.cpp in mongod in MongoDB 2.6.x before 2.6.2 allows remote attackers to cause a denial of service (daemon crash) by attempting authentication with an invalid X.509 client certificate.

CVE-2014-7193
Published: 2014-12-25
The Crumb plugin before 3.0.0 for Node.js does not properly restrict token access in situations where a hapi route handler has CORS enabled, which allows remote attackers to obtain sensitive information, and potentially obtain the ability to spoof requests to non-CORS routes, via a crafted web site ...

CVE-2004-2771
Published: 2014-12-24
The expand function in fio.c in Heirloom mailx 12.5 and earlier and BSD mailx 8.1.2 and earlier allows remote attackers to execute arbitrary commands via shell metacharacters in an email address.

CVE-2014-3569
Published: 2014-12-24
The ssl23_get_client_hello function in s23_srvr.c in OpenSSL 1.0.1j does not properly handle attempts to use unsupported protocols, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via an unexpected handshake, as demonstrated by an SSLv3 handshak...

CVE-2014-4322
Published: 2014-12-24
drivers/misc/qseecom.c in the QSEECOM driver for the Linux kernel 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, does not validate certain offset, length, and base values within an ioctl call, which allows attackers to gain privileges or c...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Join us Wednesday, Dec. 17 at 1 p.m. Eastern Time to hear what employers are really looking for in a chief information security officer -- it may not be what you think.