-
Website
http://flipbitsnotburgers.blogspot.com -
Original page
http://flipbitsnotburgers.blogspot.com/2008/08/computer-forensics-cloud-computing.html -
Subscribe
All Comments -
Community
-
Top Commenters
-
Chris Miller
1 comment · 1 points
-
jokeyxero
1 comment · 1 points
-
Tyler
2 comments · 4 points
-
krishnan
3 comments · 3 points
-
MikeDriehorst
1 comment · 1 points
-
-
Popular Threads
-
Every now and then ...
3 days ago · 2 comments
-
Well, it happened ...
1 week ago · 9 comments
-
PowerShell: Remove-SVN: Stripping .svn folders within a target directory tree
3 weeks ago · 16 comments
-
Every now and then ...
If you break into a system, one of the things you're going to try to do is erase your tracks. There are several interesting attack vectors here, namely:
1: You can wipe your tracks by simply bringing the system down. No system logs. No hard drives to wipe. Just pop the instance and you're done. Forensics is significantly more difficult if there's no physical system to analyze.
2: I'm personally a little concerned with all the pre-built images out there. How many of them have old SSH versions on them that make them vulnerable on bootup? What procedures do people have in place to update the AMI's? Yes, this needs to be addressed on physical servers as well, but are people forgetting about security with the set and forget nature of EC2?
3: Let's say I find a box is vulnerable to something, but the admin bounces it every x hours for whatever reason. Then I have a reliable host that my tracks will be wiped from every x hours.
Definitely some interesting points here.