"The cloud provider handles security" is one of the most expensive misunderstandings in IT. Cloud providers secure the cloud itself, but customers remain responsible for much of what they build and store in it. Most cloud breaches trace back to the customer's side of the line: misconfigured storage, exposed credentials, excessive permissions.
The basic split
The provider is responsible for security of the cloud: physical data centres, hardware, the global network, and the virtualisation layer.
The customer is responsible for security in the cloud: what they deploy, how they configure it, who can access it, and their data.
Where exactly the line falls depends on the service model.
Service by service
| Layer | On-premises | IaaS | PaaS | SaaS |
|---|---|---|---|---|
| Data and its classification | Customer | Customer | Customer | Customer |
| Identities and access | Customer | Customer | Customer | Customer |
| Endpoints and devices | Customer | Customer | Customer | Customer |
| Application | Customer | Customer | Customer | Provider (customer configures) |
| Runtime, middleware | Customer | Customer | Provider | Provider |
| Operating system | Customer | Customer | Provider | Provider |
| Virtualisation | Customer | Provider | Provider | Provider |
| Network infrastructure | Customer | Shared | Provider | Provider |
| Physical facilities | Customer | Provider | Provider | Provider |
Three rows never move: data, identities and endpoints stay with the customer in every model. So does accountability. You can outsource tasks, but if customer data leaks, the regulator and your customers will hold you responsible.
IaaS: you run almost everything above the hypervisor
Virtual machines, networks and storage are yours to configure: OS patching, hardening, host firewalls, security groups, encryption choices, backups, logging and monitoring. The provider gives you the tools; you have to use them.
PaaS: you own the code, configuration and data
Managed databases, serverless functions and container platforms remove OS patching, but you still own application security, secrets management, identity and access configuration, network exposure (is that database public?), data encryption options and logging.
SaaS: you own configuration, access and data
Even with SaaS you are responsible for: who has accounts, MFA and single sign-on, sharing settings, data retention, third-party app integrations, admin roles and audit logging. Many SaaS breaches are simply account takeover of users without MFA, or over-permissive sharing.
Where the gaps appear
- Default settings that favour ease over security, such as public sharing or broad network access.
- Assumed backups. Many SaaS providers protect against their own failures, not your accidental or malicious deletion. Check whether you need your own backups.
- Logging not enabled or retained too briefly to investigate. CERT-In expects 180 days of logs in India. See the six-hour rule.
- Unclear internal ownership. Cloud, security and application teams each assume another team handles a control.
- Third-party integrations granted broad API access and never reviewed.
Make responsibilities explicit
- Read the provider's shared responsibility documentation for each service you use. It differs between services, even from the same provider.
- Build a responsibility matrix (RACI) per service: each control, who is responsible (provider, platform team, application team), and how it's verified.
- Use the provider's assurance reports (SOC 2, ISO 27001 certificates and their scopes) for the provider's side.
- Verify your side continuously with cloud security posture management (CSPM) and SaaS security posture management (SSPM) tools that check configurations against benchmarks.
- Write it into contracts for SaaS and managed services: security obligations, breach notification, data location and deletion.
Learn more
Shared responsibility, cloud architecture and cloud data security are core topics of the free CCSP track. See also seven cloud identity mistakes and cloud encryption and key management.
Written and reviewed by the DigiTrust Asia editorial team. How we research, review and correct articles.