You can't rely on cloud providers for data security.
Slideshow: Cloud Security Pros And Cons
(click image for larger view and for full slideshow)
This column was written by the editor-in-chief of Dr. Dobbs.
A theme that appears anytime the cloud is discussed in the context of IT is security. The general direction of this concern is the prevention of unauthorized access to cloud-hosted data and apps. If the topic is pursued, rather than just acknowledged as an issue, it generally forks into two main threads: preventing access by outside parties (hackers, crackers, protesters, and the like) and preventing access by inside parties, such as unauthorized employees.
Both issues are problems and in both cases the cloud platform vendors offer an assurance that is, at first blush, comforting. Namely, that providers deliver better security of the hosted data than most data centers can provide. The primary reason for this is that they have many full-time, dedicated resources watching security, monitoring threats, and enforcing access control. Moreover, the staff members know what to do in the event of a violation. It is true that this pool of expertise--especially at large cloud providers--is likely to significantly exceed the capabilities of most small-to-medium IT organizations and even some of the larger IT shops. And the few reports of any break-ins at cloud providers tend to support the view of good security.
What is not clear from the cloud providers' contention, however, is that there is a third possible source of access, which the providers will not protect against: Access by the provider itself either on its own initiative or at the request of government agencies. Let's look at these.
Cloud providers vary widely with respect to the access they grant themselves to your data. However, none forswears all access. Many of the companies, such as Dropbox, use encryption, but have a backdoor to decrypt anything they've encrypted. (To quote, "Dropbox cooperates with United States law enforcement when it receives valid legal process, which may require Dropbox to provide the contents of your private Dropbox. In these cases, Dropbox will remove Dropbox's encryption from the files before providing them to law enforcement.")
A reaction I see frequently to this common policy is, "If I'm doing nothing wrong, I shouldn't mind the scrutiny." This view is, of course, intensely naive. Even if you have done nothing wrong, the government agencies examining your files have no contractual obligation to you to keep them safe, nor even to get rid of all their copies once they've determined you're not guilty or that they pulled the wrong party's data. In other words, by a simple bureaucratic error of accessing the wrong account, government agencies can disseminate your information more or less freely.
Some hosts, such as Box.Net, do not even encrypt your data unless you purchase a plan that specifically includes encryption. Right now, that's only their most expensive plan, despite the company's advertisements that seem to imply all data is encrypted--it is not.
Earlier this week, Microsoft announced that foreign customers were not immune from similar provisions. Namely, that the U.S. Patriot Act forces it to provide access to any data hosted anywhere by a U.S. company--even if that data resides outside the United States.
This is a major concern. Two parties--the government and the cloud provider--have access to the data, even if it's encrypted. In the former case, the access is unfettered. The cloud provider will not defend your data on your behalf, but will turn over whatever is asked for by government request (no posted policy I've seen requires a subpoena). In the latter case, the access is nearly as unfettered. The provider is free to change the terms of their privacy policies at any time and your only choice is to remove your data--a possibly enormous cost if your infrastructure depends on the cloud application.
At the 2011 InformationWeek 500 Conference, C-level executives from leading global companies will gather to discuss how their organizations are turbo-charging business execution and growth--how their accelerated enterprises manage cash more effectively, invest more wisely, delight customers more consistently, manage risk more profitably. The conference will feature a range of keynote, panel, and workshop sessions. St. Regis Monarch Beach, Calif., Sept. 11-13. Find out more and register.
New Best Practices for Secure App DevelopmentThe transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Published: 2015-10-15 The Direct Rendering Manager (DRM) subsystem in the Linux kernel through 4.x mishandles requests for Graphics Execution Manager (GEM) objects, which allows context-dependent attackers to cause a denial of service (memory consumption) via an application that processes graphics data, as demonstrated b...
Published: 2015-10-15 Cross-site request forgery (CSRF) vulnerability in eXtplorer before 2.1.8 allows remote attackers to hijack the authentication of arbitrary users for requests that execute PHP code.
Published: 2015-10-15 Directory traversal vulnerability in QNAP QTS before 4.1.4 build 0910 and 4.2.x before 4.2.0 RC2 build 0910, when AFP is enabled, allows remote attackers to read or write to arbitrary files by leveraging access to an OS X (1) user or (2) guest account.
In past years, security researchers have discovered ways to hack cars, medical devices, automated teller machines, and many other targets. Dark Reading Executive Editor Kelly Jackson Higgins hosts researcher Samy Kamkar and Levi Gundert, vice president of threat intelligence at Recorded Future, to discuss some of 2016's most unusual and creative hacks by white hats, and what these new vulnerabilities might mean for the coming year.