Cloud computing — and by extension, cloud security — can be traced back to Amazon. In the early 2000s, the online retailer faced a common problem among e-commerce sites: it needed server capacity to handle peaks in holiday shopping.
As the story goes, Amazon bought the faster servers and began renting unused capacity during off-peak times as a way to generate revenue during periods when they did not need the compute capacity. Flash forward to today, and Amazon Web Services (AWS) has grown into the largest and most successful cloud infrastructure in the world.
Just as robbers rob banks because that’s where the money is, cyber criminals now look to the cloud to steal information because that is where data resides. Yet, unlike on-premise security, where you have the comfort of implementing security controls on your company’s network and devices that you own to keep people out of systems, information in the cloud feels both everywhere and nowhere, adding a layer of abstraction to how you should protect your enterprise.
But in reality, the concept of securing the cloud isn’t much different from securing internal IT environments. The same guidelines apply: You must be able to determine who’s coming in, who can go where, and whether users are doing what they’re supposed to be doing.
For a compelling deep dive of this Amazon effect, see
“Amazon Enters the Cloud Computing Business” from Stanford University in 2008.