Shared Responsibility Model
Learning Path
π Phase 1 β Overview
π― Lesson Objective
Section titled βπ― Lesson ObjectiveβBy the end of this lesson, you will be able to:
- Understand the AWS Shared Responsibility Model.
- Differentiate between AWS responsibilities and customer responsibilities.
- Explain how responsibilities change across different AWS service models.
- Identify common security misconceptions.
- Apply the Shared Responsibility Model to real-world enterprise scenarios.
π Lesson Information
Estimated Time: 90 Minutes
Difficulty: Beginner
Prerequisites: Cloud Security Fundamentals
Hands-on Lab: Yes
Assignment: Yes
πΌ Business Value
Section titled βπΌ Business ValueβOne of the most common causes of cloud security incidents is misunderstanding who is responsible for securing cloud resources.
Many organisations assume that because they use AWS, AWS secures everything.
This assumption is incorrect.
AWS secures the cloud infrastructure, while customers are responsible for securing their workloads, identities, applications, and data.
Understanding this shared responsibility is essential for designing secure cloud environments.
π What is the Shared Responsibility Model?
Section titled βπ What is the Shared Responsibility Model?βCloud security is a partnership between AWS and the customer.
AWS is responsible for the Security OF the Cloud.
Customers are responsible for Security IN the Cloud.
AWS Cloud
+--------------------------------------+| || Security OF the Cloud || || β Data Centres || β Physical Security || β Networking Hardware || β Hypervisor || β Global Infrastructure || |+--------------------------------------+
Customer
+--------------------------------------+| || Security IN the Cloud || || β IAM || β Applications || β Operating Systems || β Data || β Encryption || β Network Configuration || β Logging || |+--------------------------------------+π Security OF the Cloud
Section titled βπ Security OF the CloudβAWS manages the underlying infrastructure that supports cloud services.
AWS responsibilities include:
- Physical data centres
- Buildings
- Power supply
- Cooling systems
- Networking hardware
- Storage hardware
- Physical servers
- Hypervisors
- Global infrastructure
- Hardware maintenance
Customers never manage these components.
π¨βπ» Security IN the Cloud
Section titled βπ¨βπ» Security IN the CloudβCustomers are responsible for everything they deploy.
Examples include:
- IAM users
- Roles
- Policies
- Password policies
- Multi-Factor Authentication
- EC2 operating systems
- Installed software
- Security Groups
- Network ACLs
- Customer data
- Encryption keys
- Application code
- API security
- Logging configuration
- Backups
These responsibilities remain with the customer regardless of organisation size.
π Responsibilities Change by Service
Section titled βπ Responsibilities Change by ServiceβThe level of customer responsibility depends on the AWS service being used.
Amazon EC2 (Infrastructure as a Service)
Section titled βAmazon EC2 (Infrastructure as a Service)βAWS manages:
- Physical servers
- Networking
- Storage hardware
- Hypervisor
Customer manages:
- Operating System
- Firewall rules
- Security Groups
- Installed software
- Applications
- IAM
- Data
- Backups
- Monitoring
Amazon RDS (Managed Database)
Section titled βAmazon RDS (Managed Database)βAWS additionally manages:
- Database software
- Operating system patching
- Infrastructure maintenance
Customer still manages:
- Database users
- Database permissions
- Encryption
- Backups
- Network access
- Database configuration
Amazon S3
Section titled βAmazon S3βAWS manages:
- Storage infrastructure
- Hardware
- Availability
Customer manages:
- Bucket policies
- Public access settings
- Object permissions
- Encryption
- Versioning
- Lifecycle policies
AWS Lambda
Section titled βAWS LambdaβAWS manages:
- Infrastructure
- Runtime environment
- Scaling
- Operating system
Customer manages:
- Function code
- IAM roles
- Secrets
- Environment variables
- Logging
- Permissions
π Responsibility Comparison
Section titled βπ Responsibility Comparisonβ| Component | AWS | Customer |
|---|---|---|
| Physical Data Centre | β | β |
| Networking Hardware | β | β |
| Hypervisor | β | β |
| Operating System (EC2) | β | β |
| IAM Users | β | β |
| IAM Policies | β | β |
| Customer Data | β | β |
| Application Code | β | β |
| Security Groups | β | β |
| Encryption Keys | β | β |
| CloudTrail Configuration | β | β |
π¨ Common Misconceptions
Section titled βπ¨ Common Misconceptionsββ βAWS automatically secures my EC2 instance.β
Section titled ββ βAWS automatically secures my EC2 instance.ββReality:
AWS secures the infrastructure.
You secure the operating system, applications, users, and data.
β βAWS creates backups automatically.β
Section titled ββ βAWS creates backups automatically.ββReality:
Backup configuration is your responsibility unless you explicitly enable managed backup services.
β βAWS protects my IAM users.β
Section titled ββ βAWS protects my IAM users.ββReality:
You must:
- Enable MFA
- Rotate credentials
- Remove unused accounts
- Apply least privilege
β βMy S3 bucket canβt become public.β
Section titled ββ βMy S3 bucket canβt become public.ββReality:
Incorrect bucket policies or ACLs can expose sensitive information to the internet.
π’ Enterprise Scenario
Section titled βπ’ Enterprise ScenarioβCloudNova Technologies
Section titled βCloudNova TechnologiesβThe development team launches a customer application on Amazon EC2.
Six months later:
- Operating system updates have not been installed.
- Administrator passwords have never been rotated.
- Security Groups allow access from 0.0.0.0/0.
- CloudTrail has not been enabled.
- Customer files are stored unencrypted.
Management asks:
βWhy didnβt AWS prevent this?β
As the Cloud Security Engineer:
- Explain the Shared Responsibility Model.
- Identify which issues belong to AWS.
- Identify which issues belong to CloudNova Technologies.
- Recommend remediation actions.
π§ͺ Hands-on Exercise 1 β Explore AWS Documentation
Section titled βπ§ͺ Hands-on Exercise 1 β Explore AWS DocumentationβVisit:
https://aws.amazon.com/compliance/shared-responsibility-model/Read the AWS Shared Responsibility Model.
Create a table with:
| AWS Responsibility | Customer Responsibility |
|---|---|
| Physical Security | IAM |
| Hypervisor | Operating Systems |
| Networking Hardware | Applications |
| Data Centres | Customer Data |
π§ͺ Hands-on Exercise 2 β Secure an AWS Account
Section titled βπ§ͺ Hands-on Exercise 2 β Secure an AWS AccountβLog in to your AWS account.
Verify:
- MFA enabled
- Billing alerts configured
- Root account protected
- No unused access keys
- Contact information updated
Document your findings.
π§ͺ Hands-on Exercise 3 β Review IAM Responsibilities
Section titled βπ§ͺ Hands-on Exercise 3 β Review IAM ResponsibilitiesβOpen:
AWS Console β IAM
Review:
- Users
- Groups
- Roles
- Policies
Questions:
- Which IAM resources did AWS create?
- Which IAM resources did you create?
- Who is responsible for securing them?
π§ͺ Hands-on Exercise 4 β Analyse AWS Services
Section titled βπ§ͺ Hands-on Exercise 4 β Analyse AWS ServicesβComplete the following table.
| AWS Service | AWS Responsibility | Customer Responsibility |
|---|---|---|
| EC2 | Infrastructure | OS, Applications, IAM |
| RDS | Database Platform | Users, Data |
| S3 | Storage Platform | Bucket Policies |
| Lambda | Runtime | Code, IAM |
| DynamoDB | Infrastructure | Data, Access Policies |
Discuss how customer responsibility changes as services become more managed.
π§ͺ Hands-on Exercise 5 β Security Review
Section titled βπ§ͺ Hands-on Exercise 5 β Security ReviewβReview the following fictional environment.
- Public EC2 instance
- Public S3 bucket
- IAM AdministratorAccess assigned to every user
- No CloudTrail
- No encryption
- No backups
For each issue, identify:
- Is AWS responsible?
- Is the customer responsible?
- How would you remediate it?
π Knowledge Check
Section titled βπ Knowledge CheckβAnswer the following questions:
- What is the Shared Responsibility Model?
- What is the difference between Security OF the Cloud and Security IN the Cloud?
- Who manages the physical data centres?
- Who secures EC2 operating systems?
- Who configures IAM policies?
- Who secures customer data?
- How do responsibilities change when using managed services?
π Assignment
Section titled βπ AssignmentβPrepare a Shared Responsibility Assessment Report for CloudNova Technologies.
Include:
- Explanation of the Shared Responsibility Model.
- AWS responsibilities.
- Customer responsibilities.
- Responsibilities for EC2, S3, RDS, and Lambda.
- Five common misconceptions.
- Recommendations to improve security posture.
Length: 2β3 pages.
π‘ Key Takeaways
Section titled βπ‘ Key TakeawaysβAfter completing this lesson, you should understand:
- Cloud security is a shared responsibility.
- AWS secures the infrastructure.
- Customers secure identities, workloads, applications, and data.
- Customer responsibilities vary depending on the AWS service.
- Understanding ownership helps prevent security gaps and compliance failures.
π Further Reading
Section titled βπ Further Readingβ- AWS Shared Responsibility Model
- AWS Well-Architected Framework β Security Pillar
- AWS IAM Best Practices
- CIS AWS Foundations Benchmark
- AWS Security Best Practices
π Next Lesson
Section titled βπ Next Lessonββ‘οΈ CIA Triad