Cloud providers and their customers split the work of security, and the split changes with the service you use. This lesson explains what each side secures, how the line moves between EC2 and S3, and what always stays with you. It is for cloud, security and engineering teams.
- What it is
Security of the cloud, and in it
The provider secures the cloud itself: the hardware, software, networking and facilities that run its services. You secure what you put in it. AWS calls this security "of" the cloud versus security "in" the cloud. The wording is AWS's, and Microsoft documents the same idea for Azure.
Source: AWS Shared Responsibility Model
- How it works
The line moves by service
With EC2, which AWS classes as infrastructure as a service, you manage the guest operating system (including updates and security patches), your applications, and the configuration of the security group firewall. With abstracted services such as S3 and DynamoDB, AWS operates the infrastructure layer, the operating system and the platform, and you manage your data (including encryption options), classify your assets and use IAM tools to apply the right permissions. Managed services such as RDS sit in between, so check each service's own documentation.
Source: AWS Shared Responsibility Model
- Why it matters
Your data, your permissions
Microsoft's guidance says that for all cloud deployment types you own your data and identities, and its responsibility matrix lists configurations and settings as the customer's in every model. AWS says the same for S3: customers manage their data and apply permissions with IAM. So an open bucket or an over-broad role sits on the customer side of the line. That is our reading of those responsibilities, not a statistic about how common such mistakes are.
Source: Microsoft Learn, Shared responsibility in the cloud; AWS Shared Responsibility Model
The takeaway: the provider secures the cloud, and you secure what's in it. The split shifts with each service. And your data and permissions are always yours to protect.
More short lessonsADIR also offers a free external pen test for cloud teams: see the offer.
Transcript
Who secures your workload in the cloud, you or the provider? The answer is both, and the line between you moves. The shared responsibility model splits security in two. The provider secures the cloud itself: the hardware, software, networking and facilities. You secure what you put in it. AWS calls it security of the cloud, versus security in the cloud. Where the line sits depends on the service. With EC2, you manage the guest operating system, its patches, your applications and the security group firewall. With S3, AWS runs the infrastructure, operating system and platform, and you manage your data, encryption options and permissions. Some things never move. Microsoft's guidance says that for all cloud deployment types, you own your data and identities. So a bucket left open, or a role with permissions that are too broad, sits on your side of the line, whatever the service. So, the provider secures the cloud, and you secure what's in it. The split shifts with each service. And your data and permissions are always yours to protect.
Narrated with an AI voice.

