Cloud Shared Responsibility Model

A security framework defining the division of security responsibilities between a cloud service provider and the customer based on the service model (IaaS, PaaS, SaaS).

On this page

What is Cloud Shared Responsibility Model?

In the shared responsibility model, cloud providers secure the underlying infrastructure ("security of the cloud") while customers are responsible for securing their data, configurations, and access ("security in the cloud"). Responsibility boundaries shift by service model: in IaaS, customers manage OS, applications, and data; in PaaS, the provider manages the platform; in SaaS, the provider manages nearly everything except user access and data classification. Misunderstanding these boundaries is a leading cause of cloud security incidents. Each major provider (AWS, Azure, GCP) publishes their specific model.

Application to Vendor Screening

When vendors use cloud infrastructure, understand which cloud provider they use and how responsibilities are divided. Misconfigurations in the vendor's portion of shared responsibility create risk for your data. Assess vendor cloud security posture management (CSPM), IAM practices, and data encryption within their cloud environments.

Practical Examples

  • Mapping security responsibilities for a vendor hosting on AWS IaaS
  • Assessing a SaaS vendor's understanding of their shared responsibility obligations
  • Reviewing a vendor's cloud security posture management practices

Frequently Asked Questions

What is the customer responsible for in SaaS?

In SaaS, customers are typically responsible for user access management, data classification, authentication configuration (enabling MFA), and ensuring appropriate use policies. The provider handles infrastructure, application security, patching, and physical security.

Why does the shared responsibility model matter for vendor assessment?

If a vendor misunderstands their cloud security responsibilities, gaps emerge. Common failures include misconfigured storage buckets, overly permissive IAM roles, and unencrypted data. Understanding the model helps you ask the right assessment questions.

Check the vendor. Keep the evidence.

Start free