Diagram
A three-column comparison showing IaaS leaves bulk security to the customer, PaaS shares app and IAM controls, and SaaS leaves bulk security to Google while data and access stay with the customer.
How Responsibility Shifts by Service Model
How responsibility shifts by service model determines how many controls appear in the customer's audit scope. The split depends on whether the workload uses Infrastructure as a Service (IaaS), Platform as a Service (PaaS), or Software as a Service (SaaS), and a single enterprise often uses all three at once:
| Service model | Example services | Responsibility split |
|---|---|---|
| Infrastructure as a Service (IaaS) | Compute Engine, Cloud Storage, Cloud VPN, Cloud Load Balancing, Cloud DNS | The bulk of security responsibility belongs to the customer; Google Cloud is responsible for underlying infrastructure and physical security |
| Platform as a Service (PaaS) | App Engine, Google Kubernetes Engine (GKE), BigQuery | Google Cloud owns more controls, varying by service and feature; responsibility is shared for application-level controls and IAM, while the customer remains responsible for data security and client protection |
| Software as a Service (SaaS) | Google Workspace, Google Security Operations, Marketplace SaaS applications | Google Cloud owns the bulk of security responsibility; the customer remains responsible for access controls and the data placed in the application |
Domain 3 of 4
23 practice questions
Practice this DomainLast updated