Learn the concept.
Cloud security is shared work. The provider secures parts of the platform, while the customer remains responsible for important decisions about workloads, identities, configurations, and data.
Start with the service
Responsibilities vary between infrastructure, managed platforms, and software services.
Make ownership explicit
For each task, identify who implements the control and who verifies it.
Do not outsource assumptions
A provider’s security capabilities do not automatically make every customer configuration safe.
Field example01 / A
Put it in context
For an AWS virtual machine, the provider operates the underlying infrastructure. The customer typically manages the guest operating system, its updates, and application configuration. A managed service shifts some of those tasks, but not all customer duties.
Divide the work explicitly
Example: an ordinary customer-managed AWS EC2 virtual machine.
| Security task | Owner here | Example scope |
|---|---|---|
| Physical data center | Provider | Physical facilities and underlying infrastructure |
| Guest operating system | Customer | Configure and patch the guest OS |
| Application and data | Customer | Application configuration and data handling |
| Workload permissions | Customer | Choose who can do what |
Read the visualWho patches the guest OS in this example?
The customer. Check the responsibilities for the exact service instead of generalizing this table to all cloud products.
Make a decision.
Use what you just learned. A correct answer lets you save this lesson to your progress.
Take this with you.
Ask which party owns each specific control for the service you are actually using.
Next lesson: Small permissions, smaller blast radius