Diagram
A layered stack diagram comparing responsibility splits for IaaS, PaaS, and SaaS on Google Cloud. Blue layers are Google Cloud responsibilities such as hardware, storage, network, runtime, and platform; orange layers are customer responsibilities, with data and its access and usage always owned by the customer.
Shared Responsibility Boundary Across Service Models
The shared responsibility boundary divides security duties so each side knows which controls it must provide. In general, the customer secures what it brings to the cloud and Google protects the cloud itself. The exact split changes by service type because Google manages more of the stack as services become more complete. When workloads span multiple service types, the customer must apply the correct split to each part.
| Service model | Google Cloud responsibility | Customer responsibility |
|---|---|---|
| Infrastructure as a service (IaaS) | Hardware, storage, and network | Everything else, including data and workloads |
| Platform as a service (PaaS) | More controls than in IaaS, including runtime and platform layers | Application controls, IAM management, data security, and client protection |
| Software as a service (SaaS) | Security of everything except data and its access and usage | Data and its access and usage |
Domain 3 of 3
137 practice questions
Practice this DomainLast updated