Amazon's Cloud Is Full of Holes
itwbennett writes "Amazon's Web Services is so easy to use that customers create virtual machines without following Amazon's 'very detailed' security guidelines, says Thomas Schneider, a postdoctoral researcher in the System Security Lab of Technische Universität Darmstadt. Most notably, Schneider and his fellow researchers found that the private keys used to authenticate with services such as the Elastic Compute Cloud (EC2) or the Simple Storage Service (S3) were publicly published in Amazon Machine Images (AMIs), which are pre-configured operating systems and application software used to create virtual machines. '[Customers] just forgot to remove their API keys from machines before publishing,' Schneider said."
I don't get it. It's more like sending a letter to someone with your housekeys in the envelope.
But some users are sloppy and thus are.
they will suck.
- Love, Every Technology Vendor Ever
Thomas Schneider, Bruce Schneier - it's all too confusing for us morals. One of you needs to change his name to Mr. Security McSmartypants.
with many cloud providers try buying a large chunk of disk space with ur VM and see what standard data recovery tools can do ....and what previous customers leave behind.
This is a known issue and when Amazon.com finds out that certain AMIs have preinstalled root ssh keys, they send you an email letting you know, along with instructions on how to remove the root ssh key. Non-issue.
Linux O Muerte!
I don't know, the cloud looks like a safe to me..... or a pad lock.
Oh, and that cloud looks like a shark.... and that one next to it looks like a worm....
Previewing comments are for sissies!
If it allows you to do something incorrectly then it isn't very easy to use.
This is people bundling their own AMIs and publishing them publicly without reading security docs. Has nothing to do with Amazon's greater cloud infrastructure or what 99% of the people use it for. In fact, is the article arguing that allowing people to publish their own AMIs is a bad thing?
Article title is very misleading and irresponsible...
Full of holes? I think the title of the article should be "People don't always read instructions." Duh.
It's actually like a building company selling prefab bank buildings, and then selling it to your local bank, and the bank forgot to lock the back door they used to get into the building all the while inviting you to come into their new fangled ultra safe and secure bank where you can store personal stuff.
The problem is that Amazon gave someone a super easy way to set up a site... so easy, even idiots can set it up. And idiots will set it up and forget to close the back door, and those idiot will sell services and what not with users who log in using a customer ID and password, and then someone can come in and steal it using a very basic back door. The problem is that it's too easy to forget to do or completely ignore this last part. That's what needs to be fixed.
This is a process problem that makes it too easy for users to shoot themselves in the foot. Sure, those who bought web services should know better, but that doesn't mean Amazon bears no responsibility to make it easier to secure the site. In terms of managing risk, it's too likely that people will forget to secure this. Amazon, logically, has a responsibility to minimize this risk through any number of means, like an education program to it's hosted companies, a redesigned tool, or something similar. But by putting this 100% on the customer fails to acknowledge that the problem is not necessarily people, but the process.
"All great wisdom is contained in .signature files"
This seems like basically the same issue as "forgot to remove my SQL password from the config file in the code I uploaded to github", which is also quite common. If you upload a working version of some of your infrastructure somewhere, you need to be careful about whether it contains any sort of authentication tokens.
10 PRINT CHR$(205.5+RND(1)); : GOTO 10
It's not too difficult to plug a LAMP stack (or a windows/BSD/Solaris equiv.) into the net but the average lamer isn't going to know about hardening, updating, monitoring and troubleshooting. Amazon apparently could care less as well.
Join the Slashcott! Feb 10 thru Feb 17!
Yay cloud!
Worst Sig Ever
Like, this guy got his Amazon EC2 server owned, and was arrested for distributing child porn... (hackers put it on his server)
If there were no holes, how could it have a silver lining?
Amazon wants you to store all your videos and music on their servers but with ISPs capping traffic and lowering limits that idea may be short lived. "I have that movie but we can't watch it until the 18th when my limit resets for the month"
Blame the person who uses the tool incorrectly.
Take some personal responsibility for goodness sakes.
Sure... blame the users... /sarcasm
amazon's cloud is full of holes? come on..
As an IaaS it is YOUR responsibility to design security etc into YOUR servers on EC2. I think the title of this thread is misleading in that it makes it sound like AWS is at fault for implementation of someone's poor practices. "Amazon's Cloud is Full of Holes" That's like saying Intel's processor's are Full of Holes because people do stupid things using machines that have them.
It has been reported that certain ford mustangs allow the owner to leave the doors unlocked and the keys in the ignition..
a large recall is expected once the ford motor company finishes studying the problem.