Cloud Fundamentals

The Shared Responsibility Model in Cloud Computing: Who Secures What?

Learn who secures what in the cloud under the shared responsibility model, from IaaS to SaaS, with examples of customer duties and common misconfigurations.

On this page
  1. What the model means
  2. What the provider is responsible for
  3. What the customer is responsible for
  4. How the split changes across IaaS, PaaS and SaaS
  5. A worked example: a web application
  6. Why customer-side mistakes cause so many incidents
  7. Compliance reports cover the provider’s part
  8. Common misconceptions
  9. Frequently asked questions

In cloud computing, the shared responsibility model divides security tasks between the cloud provider and the customer. In short, the provider secures the cloud itself: the facilities, hardware and underlying platform. The customer secures what it puts in the cloud: its data, who can access it, and how its resources are configured.

AWS describes this as security of the cloud (the provider’s job) and security in the cloud (the customer’s job). Microsoft Azure describes the same split in its guidance.

What the model means

Moving to the cloud does not move every security task to the provider. Responsibility is shared, and the exact boundary depends on the service you use. A provider can run a secure data center and still have customers whose data is exposed because a storage setting was wrong.

What the provider is responsible for

Across all service types, the provider generally owns:

  • Physical data centers, including access control and environmental protection
  • Physical servers, storage and network hardware
  • The virtualization layer (the hypervisor) that separates customers’ workloads

The provider also runs the core network and, in managed services, patches the platform beneath your application.

What the customer is responsible for

Microsoft’s guidance lists three things the customer owns whatever the service:

  • Data: what is stored, how it is classified, whether it is encrypted, and who can read it
  • Devices: the laptops, phones and other endpoints used to access the service
  • Accounts and identities: users, roles, permissions and multi-factor authentication

Configuration is also the customer’s job in most services, such as storage access, firewall rules and logging. Application code is the customer’s job when the customer writes it, and depends on the service model.

How the split changes across IaaS, PaaS and SaaS

The customer’s share shrinks as you move toward managed services. The table below shows a general pattern. Check each service’s documentation, because the split can differ even within one provider.

Responsibility IaaS (e.g., Amazon EC2) PaaS (e.g., managed app hosting or databases) SaaS (e.g., Microsoft 365, Salesforce)
Physical facilities, servers and network Provider Provider Provider
Virtualization layer Provider Provider Provider
Operating system patching Customer Provider Provider
Application code Customer Customer Provider
Data and its access controls Customer Customer Customer
Identities and user permissions Customer Customer Customer
Endpoints (devices used to connect) Customer Customer Customer

In IaaS, you manage the most. In SaaS, you still own your data, the people who can access it and the devices they use.

A worked example: a web application

Consider a company that runs a customer-facing web application.

  • On a virtual machine (IaaS): The provider keeps the data center and hardware secure. The company patches the operating system, configures firewall rules, restricts administrator access and encrypts its data.
  • On a managed platform (PaaS): The provider patches the operating system and runtime. The company still writes secure code, controls who can deploy it, and protects the data it stores.
  • As a SaaS tool: The provider runs the application. The company still manages who has accounts, enables multi-factor authentication and protects the data it uploads.

In each case, the customer may still need a web application firewall or equivalent controls to protect the application layer, unless the service already supplies them.

Why customer-side mistakes cause so many incidents

Many cloud data exposures come from customer configuration rather than from the provider’s infrastructure. A common cause is access that is set too broadly, such as a public storage bucket or an overly permissive identity.

One well-known case is the 2019 Capital One breach. An attacker exploited a misconfigured web application firewall to reach credentials and then data held in the cloud. About 100 million people in the United States and about 6 million in Canada were affected, and the company paid an $80 million civil penalty to a US regulator.

Provider defaults are improving. For example, new Amazon S3 buckets have blocked public access by default since April 2023. Defaults do not cover every setting, though, so customers still need to check their own configuration.

Compliance reports cover the provider’s part

Providers publish audit reports and certifications such as SOC 2, ISO 27001 and PCI DSS. These usually cover the provider’s share of the model. They do not make your workload compliant. You still need your own controls, evidence and audits for the parts you own.

Common misconceptions

  • The provider secures my configuration. It secures its platform. You configure your resources.
  • Encryption at rest means my data is protected. Default encryption helps, but it does not stop stolen credentials or a public access setting.
  • SaaS means no security work. You still manage accounts, access, devices and the data you put in the application.
  • The split is the same everywhere. The boundary varies by service, so read each service’s shared responsibility documentation.

Frequently asked questions

What is the shared responsibility model in simple terms?

The provider is responsible for security of the cloud, which means the physical infrastructure and the platform. You are responsible for security in the cloud, which means your data, your access controls and your configuration.

Who is responsible for patching in the cloud?

It depends on the service. In IaaS, you patch the operating system and your applications. In PaaS and SaaS, the provider usually patches the operating system and platform, while you still handle your application code and configuration.

Who is responsible for data security in the cloud?

The customer is responsible for its data in every service model. This covers classifying data, deciding how it is encrypted, and controlling who can access it.

For a broader introduction to how these services are organized, see how cloud computing works. The customer’s share also depends on the deployment model you choose.

The complete guide to cloud fundamentals

How Cloud Computing Works (With Diagram)
Read the guide

Keep exploring

Guides from other topics

All topics →