Article Security September 26, 2019

Understanding the Shared Responsibility Model for Cloud Security

Shared Responsibility in the Cloud

 

Public cloud providers, like Amazon Web Services (AWS) and Microsoft Azure, have no choice but to take their security and compliance responsibilities very seriously. In the early days of cloud, enterprises had initial concerns about the data security in multi-tenant architectures. Security within infrastructures outside of the enterprise’s direct control was also a key consideration. Since then, however, Amazon and Microsoft have assured users that their environments are as secure as on-premises data centers, if not more so.

As a result, we’re seeing an uptick in highly-regulated sectors, such as financial services and healthcare, deepening their cloud profiles. Perhaps the strongest endorsement for the security capabilities of today’s leading cloud providers is the CIA’s strategic decision to go all-in on the cloud, using a private AWS cloud deployment.

However, Amazon has notably drawn a line in the sand over how far they’ll go to monitor and regulate security and compliance on behalf of their end-users. AWS did this by developing a shared responsibility model, structured in such a way that puts the onus on customers to close the data security loop in their own environments.

 

What is the Shared Responsibility Model?

So what is the shared responsibility model? Simply put, the cloud provider is responsible for the security of the cloud, while the customer is responsible for security in the cloud.

Essentially, your cloud provider is responsible for making sure your infrastructure built within its platform is inherently secure and reliable. On the flip-side, customizable cloud capabilities like application management, network configuration, and encryption are the responsibility of the end-user. This shared security model—illustrated in the chart below—has been adopted by other prominent cloud providers as well.

 

Cloud provider vs. End-user

To provide a secure cloud, the cloud vendor manages and controls the host Operating System (OS) and the virtualization layer. They also guarantee the physical security of their facilities. To ensure security within a given cloud environment, the customer configures and manages the security controls for the guest OS and other apps (including updates and security patches), as well as for the security group firewall. The customer is also responsible for encrypting data in-transit and at-rest.

 

Shared Responsibility Model
 

Gartner predicts that by 2025, 99% of cloud security failures will be the customer’s fault. Based on the European Union’s GDPR data privacy legislation that came into effect May 25, 2018, we can also say that regulators place the onus of securing personal data squarely on the shoulders of the data owner, i.e. the entity that collects the data. The data owners are liable for data security breaches. It’s their responsibility to ensure that the cloud providers they invest in support suitable security and compliance guardrails.

 

How to protect your cloud environment from security threats

Next-generation automated cloud monitoring and data security management tools are essential protection as organizations grow their cloud usage. Scaling often increases complexity and dilutes visibility into your cloud environments. A cloud governance platform, like CloudCheckr, offers a single dashboard to manage all data, analytics, and users in one place.

CloudCheckr’s cloud management platform delivers self-healing automation capabilities that can detect and remedy security misconfigurations. CloudCheckr CMx leverages “Fix Now” and “Always Fix” buttons to correct issues as they’re detected—without human intervention. For example, if a user makes an S3 bucket public, automated Best Practice Checks will detect any permissions issues, correct them, and the administrator will be alerted of the correction. Alerts can be enabled to notify appropriate personnel of any specific configuration change via email.

Cloud providers are constantly investing in innovative solutions to strengthen their security profiles. In order to hold up their end of the shared responsibility model, their customers must do the same.

Learn more about protecting your cloud environment: Download our Shared Responsibility white paper.

Todd Bernhard
Todd Bernhard is a Product Marketing Director at CloudCheckr. He has earned his AWS Solutions Architect Associate, AWS Certified Cloud Practitioner, Microsoft Azure Fundamentals, Google Cloud Certified Engineer and Google G-Suite certifications. He has been administering, teaching and developing on Unix systems since 1984 including 16 years at Sun Microsystems, now part of Oracle, and while a Teaching Assistant and Student at Carnegie Mellon University. In 2010, Todd founded the award-winning app development firm NoTie.com. This photo is the last known image of him wearing a tie!
Subscribe to our Newsletter
Get cloud insights delivered. Sign up for the newsletter.

CLOUD CHECK UP

Learn how to save 30% or more on your cloud computing bill immediately. Request a custom Cloud Check Up report, only from CloudCheckr.