Shared Responsibility Model

The shared responsibility model divides cloud security duties between the provider and the customer. The provider secures the underlying infrastructure; the customer is always responsible for its data, accounts, access and devices.

BeginnerCategory: Cloud and software supply chain

Also called: cloud shared responsibility, shared security model

What is the shared responsibility model?

When you move to the cloud, you hand some security work to the provider, but not all of it. The shared responsibility model spells out the split. Every major provider, including Microsoft, AWS and Google, publishes its own version.

A common misunderstanding is that "it's in the cloud, so Microsoft (or Amazon) protects it." Providers protect their infrastructure. If an employee's password is phished or a storage bucket is made public, that's on the customer.

How it changes by service type

NIST defines three main cloud service models, and the split shifts with each:

  • Software as a service (SaaS), such as Microsoft 365, Google Workspace or Salesforce. The provider runs almost everything. You manage users, access, settings, sharing and your data.
  • Platform as a service (PaaS), such as managed databases or app hosting. The provider handles the operating system and runtime; you secure your application code, its configuration and data.
  • Infrastructure as a service (IaaS), such as virtual machines in AWS or Azure. The provider secures physical hardware, networks and the virtualization layer. You're responsible for the operating system, patching, firewalls, applications and data.

What you're always responsible for

Microsoft's guidance is clear that whatever the deployment type, the customer always keeps responsibility for:

  • Data: what you store, how it's classified and shared, and backups
  • Endpoints: the laptops and phones used to access the cloud
  • Accounts: user identities, passwords and MFA
  • Access management: who can see and change what

What this means in practice

  • Turn on the security features you have; many are off by default.
  • Back up SaaS data separately. Providers protect against their own outages, not your deletions or ransomware.
  • Read the provider's documentation to see exactly where its responsibility ends.
  • Check contracts for breach notification and data handling terms, as part of third-party risk management.

See cloud security for a practical checklist.

Related terms

Sources

  1. Shared responsibility in the cloud (Microsoft)
  2. SP 800-145: The NIST Definition of Cloud Computing (NIST)

Drafted with AI assistance, then edited and fact-checked by a person. How we use AI.