This is the third in a series of posts that will drill deeper into cloud security and some of the key questions it sparks. In the second installment, I highlighted the spheres of responsibility and looked at which security components are Rackspace’s responsibility, and which are the customer’s. In this installment, I will discuss the physical security measures Rackspace has in place to protect its cloud customers’ data.
This is the second in a series of posts that will drill deeper into cloud security and some of the key questions it sparks. The first post examined the many faces of cloud security. In this second installment, I will highlight the spheres of responsibility and look at which security components are Rackspace’s responsibility, and which are the customer’s.
This is the first in a series of posts that will drill deeper into cloud security and some of the key questions it sparks. In this first installment, I will highlight some of the different facets of cloud security.
As cloud computing continues to evolve, I’ve noticed one major difference in the IT executive thought process. When I was meeting with Fortune 500 IT executives a few years back — around 2008 — they had a lot of concerns about cloud computing. They were particularly concerned with security. Inevitably, security would become a main point in any cloud computing conversation.
It’s a common misconception that on-premise infrastructure is inherently more secure than infrastructure managed by a service provider in the cloud. And while security remains among the top concerns that some users have about cloud computing, recent research from cloud security player Alert Logic found that security threats faced by infrastructure in the cloud is on par, or in many cases less prevalent than those for on-premise system.
This week, our Anatomy Of An Attack infographic showcased steps hackers may take to crack into your systems. The goal was to show the discovery process that an attacker goes through when looking to do something nasty. We’re not looking to spark fear, but instead to instill some common sense goals to lock down systems before attackers have a chance to penetrate them.
How does access to web properties end up in the hands of a hacker? In this interactive piece, we’ll take you through the steps on how an attacker goes about targeting an organization. The primary goal of such an attack could be to gain access to competitive intelligence, to interfere with business by modifying or defacing a web site or to otherwise disrupt normal business activities – which can all affect you.