Skip to content
Tutorials Center
My learning

Topics

Lesson 5 of 38 ยท Shared Responsibility and Threats

The Shared Responsibility Model

Learn what the cloud provider secures and what you secure in IaaS, PaaS and SaaS, the common misunderstandings that cause breaches, and how to map controls to owners.

Every major cloud provider publishes a shared responsibility model. The idea is simple: the provider is responsible for the security of the cloud, and you are responsible for security in the cloud. The hard part is knowing exactly where the line falls, because it moves depending on the service you use, and the gaps between "I thought they did that" and "they thought I did that" cause real incidents.

Security of the cloud versus security in the cloud

The provider is responsible for:

  • Physical data centers: buildings, power, cooling, guards, hardware disposal.
  • The hardware, network backbone and the virtualization layer that isolates customers from each other.
  • The managed services themselves (for example the database engine of a managed database service) and their patching, as documented for that service.
  • Certifications and audits of that infrastructure.

You are responsible for:

  • Your data: what you store, how it is classified and encrypted, who can see it.
  • Identity and access: users, roles, keys, MFA, permission policies.
  • Configuration of each service: sharing settings, public access, logging, network rules.
  • Everything you install: operating systems, containers, application code and its dependencies, in the models where you control them.
  • Compliance obligations for your own data and processes.

Provider secures the cloud

Facilities Buildings, power, guards
Hardware Servers and network
Virtualization Tenant isolation

Documented and audited by the provider.

1 / 2

How the line moves

flowchart LR
    subgraph IaaS
      I1["You: OS, runtime, app, data, identity"]
    end
    subgraph PaaS
      P1["You: app, data, identity"]
    end
    subgraph SaaS
      S1["You: data, identity, settings"]
    end
    IaaS --> PaaS --> SaaS

Moving right, the provider takes over more layers. The last box never becomes empty.

A few concrete cases:

  • Virtual machine (IaaS). The provider keeps the hypervisor safe. You must patch the guest operating system, configure its firewall and manage who can log in.
  • Managed database (PaaS). The provider patches the database engine and handles backups if you enable them. You decide who can connect, whether it is reachable from the internet, whether it is encrypted with your keys, and what is in it.
  • Object storage. The provider guarantees durability of the service. You decide whether a bucket is public. Many headline breaches were a public bucket.
  • Hosted email (SaaS). The provider runs the app. You enable MFA, set sharing rules and decide who is an administrator.

Common misunderstandings

  1. "The provider encrypts everything, so I am safe." Encryption at rest is often on by default, but it does not stop someone with valid permissions from reading data. Access control is yours.
  2. "My data is in a secure data center." The data center is secure; your configuration may still make the data public.
  3. "The provider will back it up." Many services replicate for durability but do not protect against you deleting or encrypting your own data. Backups are usually a setting you must enable and test.
  4. "Compliance certificates cover me." A provider's audit report covers the provider's part. You still have to show that your part meets the standard.
  5. "Serverless means no security work." There are no servers to patch, but function permissions, event inputs and secrets are still yours.

Read the provider's documentation for each service. The exact split differs between services and changes over time. Treat the published responsibility documents as the source of truth, and record which ones you rely on.

Runnable example: a responsibility matrix

Teams often keep a table of every control with an owner. The program below builds one from data and finds controls that have no owner, the classic gap in shared responsibility.

Python Find unowned controls

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The two NOBODY rows are the dangerous ones. Assign each to a team or process, and the matrix stays useful.

Practical steps

  1. List the services you use and read each one's responsibility statement.
  2. For every control that matters (patching, backups, logging, encryption, access reviews), write down an owner and where the evidence lives.
  3. Turn on the settings that the provider leaves optional: logging, backups, public-access blocks, MFA.
  4. Review the matrix whenever you adopt a new service or move up or down a service model.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Who is responsible for deciding whether an object storage bucket is public?

    Configuration of sharing and access is the customer's responsibility in every service model.
  2. 2. In a managed database service, who typically patches the database engine?

    Managed services shift engine patching to the provider, while access, network exposure and data remain with you.
  3. 3. Which statement about provider compliance certificates is true?

    Certifications describe controls the provider operates; customer-side controls need their own evidence.
  4. 4. What is a gap in the shared responsibility model?

    Gaps appear when both parties assume the other owns a control, such as backups or application logging.

Summary

  • The provider secures the cloud itself; you secure what you put in it and how you configure it.
  • The boundary shifts with IaaS, PaaS, FaaS and SaaS, but data, identity and configuration always stay with you.
  • Typical misunderstandings: assuming encryption, backups or certificates cover your side.
  • Maintain a responsibility matrix with an owner for every control, and look for controls nobody owns.

Next: The Cloud Threat Landscape