Cloud

1/21/2011
10:43 AM
George Crump
George Crump
Commentary
50%
50%

How Careful Do You Need To Be With Cloud Storage? - Security

Developing a cloud storage strategy is moving to the top of many IT managers project lists. How to use cloud storage and what applications or processes could benefit the most from the use of cloud storage are key questions to answer. One mantra that keeps coming up is "you have to be careful" with cloud storage rollouts. Really? What makes cloud storage so risky that it requires this extra caution?

Developing a cloud storage strategy is moving to the top of many IT managers project lists. How to use cloud storage and what applications or processes could benefit the most from the use of cloud storage are key questions to answer. One mantra that keeps coming up is "you have to be careful" with cloud storage rollouts. Really? What makes cloud storage so risky that it requires this extra caution?First, let's assume that you are going to apply the same level of diligence to a cloud storage rollout that you will apply to any other IT project you are going to undertake this year. I doubt there is a single project that you will read about in the morning and then later that same afternoon begin deploying it in production. Cloud storage is no different, clearly as we discuss in our recent webinar "Developing a Cloud Storage Strategy", you'll want to plan when and how you will use cloud storage.

I think part of the extra level of concern with cloud storage is, if you are using a public cloud for storage, the assumption is that your data is now leaving your direct control. In other words it is that age old concern about security in the cloud, for the most part, much of that concern has been addressed. I don't know of a single business level cloud storage solution that does not encrypt data before it goes across the internet and almost all store that data in an encrypted format. That means you are still in control of your data. In almost every case the cloud storage provider can't see or do anything with that data (unless you give them the encryption keys).

It also means it is secure. While in theory it is possible that someone crack your encryption it is more likely that someone will be able to get to your encryption keys. If you protect those like you do any other password type of data then your data should be secure from almost every situation. Also most cloud storage providers use some sort of clustered storage system, which means that your data is spread across dozens if not hundreds of drives. So not only is the data encrypted but it is not all on one drive. Even if, for example, a failed drive is improperly disposed of, the data on that drive is just bits of the overall data set and again it is still encrypted.

I would argue that the chance of you having encrypted data that is stored in the cloud being compromised is less likely than having data within your data center compromised where most data is not encrypted. As we discuss in our recent article "What Can You Really Do With Cloud Storage in 2011?" most business grade cloud storage offerings leverage a hybrid model where an appliance is installed locally to act as a cache to the cloud. The means that most of your data can be stored securely in the cloud which limits the amount of un-encrypted data that people interacting with your data center can access.

This hybrid approach also addresses the next area that causes experts to warn of caution, the bandwidth required to interact with cloud storage. We'll address this in an upcoming entry.

Track us on Twitter: http://twitter.com/storageswiss

Subscribe to our RSS feed.

George Crump is lead analyst of Storage Switzerland, an IT analyst firm focused on the storage and virtualization segments. Find Storage Switzerland's disclosure statement here.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Crowdsourced vs. Traditional Pen Testing
Alex Haynes, Chief Information Security Officer, CDL,  3/19/2019
BEC Scammer Pleads Guilty
Dark Reading Staff 3/20/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Well, at least it isn't Mobby Dick!
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
The State of Cyber Security Incident Response
The State of Cyber Security Incident Response
Organizations are responding to new threats with new processes for detecting and mitigating them. Here's a look at how the discipline of incident response is evolving.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-3965
PUBLISHED: 2019-03-23
Hospira Symbiq Infusion System 3.13 and earlier allows remote authenticated users to trigger "unanticipated operations" by leveraging "elevated privileges" for an unspecified call to an incorrectly exposed function.
CVE-2016-10743
PUBLISHED: 2019-03-23
hostapd before 2.6 does not prevent use of the low-quality PRNG that is reached by an os_random() function call.
CVE-2019-9947
PUBLISHED: 2019-03-23
An issue was discovered in urllib2 in Python 2.x through 2.7.16 and urllib in Python 3.x through 3.7.2. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the first argument to urllib.request.urlopen with \r\n (specifically in the query string or PATH_INFO) follo...
CVE-2019-9948
PUBLISHED: 2019-03-23
urllib in Python 2.x through 2.7.16 supports the local_file: scheme, which makes it easier for remote attackers to bypass protection mechanisms that blacklist file: URIs, as demonstrated by triggering a urllib.urlopen('local_file:///etc/passwd') call.
CVE-2019-9945
PUBLISHED: 2019-03-23
SoftNAS Cloud 4.2.0 and 4.2.1 allows remote command execution. The NGINX default configuration file has a check to verify the status of a user cookie. If not set, a user is redirected to the login page. An arbitrary value can be provided for this cookie to access the web interface without valid user...