The shared responsibility model is the foundation of cloud security. It says that the cloud provider secures some things and you secure the rest. Most cloud breaches come from customers misunderstanding where that line is.
What the Provider Secures
The provider secures the cloud itself: physical data centres, hardware, the core network and the virtualisation layer.
What You Secure
You secure what you put in the cloud: your identities, data, configurations, applications and, depending on the service, operating systems. The more control a service gives you, the more you are responsible for.
How It Changes by Service Model
- IaaS (virtual machines, networks, storage): you manage operating system, patches, network rules, applications and data.
- PaaS (managed databases, app platforms): the provider manages the platform; you manage application, identity, configuration and data.
- SaaS (email, CRM): the provider manages almost everything; you still manage users, access and data governance.
Common Mistakes
- Assuming the provider backs up and protects your data by default
- Leaving storage buckets or databases open to the internet
- Using over-privileged roles and long-lived access keys
- Not enabling audit logging, so incidents cannot be investigated
- Forgetting that identity is the new perimeter and not enabling multi-factor authentication
A Practical Checklist
- Know, for each service you use, what the provider documents as your responsibility
- Use least-privilege IAM and rotate or remove keys
- Encrypt data and manage keys deliberately
- Turn on logging and alerts across all accounts
- Review configuration regularly with posture-management tools
Our Cloud Security course covers this in its first module and then goes deep on securing platforms, applications and data on AWS, Azure and Google Cloud.
