Lesson 03 β AWS Shared Responsibility Model
Learning Path
βοΈ Phase 2 β AWS Cloud Security
π Module 01 β AWS Security Foundations
π― Lesson Objective
Section titled βπ― Lesson ObjectiveβBy the end of this lesson, you will be able to:
- Explain the AWS Shared Responsibility Model.
- Differentiate between Security of the Cloud and Security in the Cloud.
- Identify customer and AWS responsibilities for different AWS services.
- Apply the Shared Responsibility Model to real enterprise scenarios.
- Avoid common cloud security misconceptions.
π Lesson Information
Estimated Time: 2 Hours
Difficulty: Beginner
Prerequisites: Lesson 01 & Lesson 02
Hands-on Lab: Yes
Assignment: Yes
πΌ Business Value
Section titled βπΌ Business ValueβOne of the biggest misconceptions in cloud computing is:
βSince everything is hosted on AWS, AWS secures everything.β
This is incorrect.
While AWS secures the underlying cloud infrastructure, customers remain responsible for securing their applications, data, identities, operating systems and configurations.
Understanding these responsibilities helps organisations:
- Reduce security risks
- Prevent data breaches
- Meet compliance requirements
- Build secure cloud architectures
- Clearly define operational responsibilities
π What is the AWS Shared Responsibility Model?
Section titled βπ What is the AWS Shared Responsibility Model?βThe Shared Responsibility Model defines the division of security responsibilities between AWS and its customers.
AWS manages the security of the cloud.
Customers manage security in the cloud.
Both parties work together to achieve a secure cloud environment.
βοΈ Shared Responsibility Model
Section titled ββοΈ Shared Responsibility Modelβ AWS Shared Responsibility Model
+-------------------------------+ | Customer Responsibility | |-------------------------------| | Data | | Identity & Access | | Applications | | Operating System | | Network Configuration | | Encryption | | Security Groups | | Monitoring | +-------------------------------+
Security IN the Cloudββββββββββββββββββββββββββββββββββββββββββββββββββββ
Security OF the Cloud
+-------------------------------+ | AWS Responsibility | |-------------------------------| | Physical Data Centres | | Hardware | | Storage Infrastructure | | Networking Infrastructure | | Hypervisor | | Global Infrastructure | +-------------------------------+π Security OF the Cloud
Section titled βπ Security OF the CloudβAWS is responsible for protecting the infrastructure that runs AWS services.
Examples include:
- Physical security
- Data centre operations
- HVAC systems
- Physical networking
- Fibre infrastructure
- Global backbone
- Servers
- Storage hardware
- Hypervisors
- Availability Zones
- Regions
Customers never manage these components.
π Security IN the Cloud
Section titled βπ Security IN the CloudβCustomers are responsible for securing everything they deploy within AWS.
Typical responsibilities include:
- IAM Users
- IAM Roles
- IAM Policies
- MFA
- Operating System patches
- Application security
- Data encryption
- Security Groups
- Network ACLs
- Secrets
- Logging
- Monitoring
- Backup configuration
π’ Enterprise Example
Section titled βπ’ Enterprise ExampleβCloudNova launches a new web application on Amazon EC2.
Question:
Who is responsible for securing each layer?
| Component | Responsibility |
|---|---|
| Physical Server | AWS |
| Data Centre | AWS |
| Hypervisor | AWS |
| EC2 Operating System | Customer |
| Installed Software | Customer |
| Application Code | Customer |
| Database Credentials | Customer |
| IAM Policies | Customer |
| Security Groups | Customer |
π Shared Responsibility by AWS Service
Section titled βπ Shared Responsibility by AWS ServiceβAmazon EC2
Section titled βAmazon EC2β| AWS | Customer |
|---|---|
| Physical Infrastructure | Guest Operating System |
| Hypervisor | Patching |
| Hardware | Firewall Rules |
| Availability | Applications |
| Networking Infrastructure | IAM |
| Power & Cooling | Encryption |
Amazon S3
Section titled βAmazon S3βAWS manages:
- Storage infrastructure
- Hardware
- Availability
Customer manages:
- Bucket Policies
- IAM
- Encryption
- Public Access
- Object Permissions
- Lifecycle Policies
Amazon RDS
Section titled βAmazon RDSβAWS manages:
- Database platform
- Hardware
- Operating system
- Database engine patching
Customer manages:
- Database users
- Passwords
- Security Groups
- Encryption
- Database configuration
- Backup strategy
AWS Lambda
Section titled βAWS LambdaβAWS manages:
- Runtime
- Infrastructure
- Scaling
- Availability
Customer manages:
- Function code
- IAM execution role
- Secrets
- Environment variables
- Logging
- Third-party libraries
Amazon EKS
Section titled βAmazon EKSβAWS manages:
- Control Plane
Customer manages:
- Worker Nodes
- Kubernetes configuration
- RBAC
- Pods
- Containers
- Secrets
- Network Policies
β Common Misconceptions
Section titled ββ Common MisconceptionsβAWS patches my EC2 operating system.
Section titled βAWS patches my EC2 operating system.ββ False
Customers are responsible for patching EC2 instances.
AWS secures my S3 bucket.
Section titled βAWS secures my S3 bucket.ββ False
AWS secures the storage platform.
Customers secure bucket access.
AWS creates IAM users.
Section titled βAWS creates IAM users.ββ False
Customers create and manage IAM identities.
AWS encrypts everything automatically.
Section titled βAWS encrypts everything automatically.ββ False
Customers choose encryption options and manage encryption keys where applicable.
π’ CloudNova Enterprise Scenario
Section titled βπ’ CloudNova Enterprise ScenarioβCloudNova recently migrated its HR application to AWS.
During a security review, the following issues were identified:
- EC2 instances have not been patched for six months.
- An S3 bucket is publicly accessible.
- IAM users do not have MFA enabled.
- Security Groups allow unrestricted SSH access.
- Database passwords are weak.
The CIO asks:
βAWS is a secure cloud provider. Why do we still have these issues?β
As the Cloud Security Engineer, explain which issues are AWSβs responsibility and which belong to CloudNova.
π§ͺ Enterprise Mission 01 β Review AWS Account Identity
Section titled βπ§ͺ Enterprise Mission 01 β Review AWS Account IdentityβObjective
Section titled βObjectiveβIdentify which AWS account you are currently working in.
Step 1 β Open PowerShell
Section titled βStep 1 β Open PowerShellβVerify the AWS CLI:
aws --versionStep 2 β Display Current Identity
Section titled βStep 2 β Display Current Identityβaws sts get-caller-identityExample output:
{ "UserId": "AIDAXXXXXXXXXXXXX", "Account": "123456789012", "Arn": "arn:aws:iam::123456789012:user/student"}Record:
- Account ID
- IAM User
- ARN
π§ͺ Enterprise Mission 02 β Review IAM Account Summary
Section titled βπ§ͺ Enterprise Mission 02 β Review IAM Account SummaryβRun:
aws iam get-account-summaryObserve:
- Number of Users
- Groups
- Roles
- MFA Devices
- Account Settings
Questions:
- How many IAM users exist?
- Is MFA configured?
- How many roles are available?
π§ͺ Enterprise Mission 03 β Inspect AWS Resources
Section titled βπ§ͺ Enterprise Mission 03 β Inspect AWS ResourcesβList S3 Buckets:
aws s3api list-bucketsList EC2 Instances:
aws ec2 describe-instancesList Lambda Functions:
aws lambda list-functionsList RDS Databases:
aws rds describe-db-instancesThink about:
Who is responsible for securing each resource?
π§ͺ Enterprise Mission 04 β Shared Responsibility Exercise
Section titled βπ§ͺ Enterprise Mission 04 β Shared Responsibility ExerciseβComplete the table.
| Task | AWS | Customer |
|---|---|---|
| Physical Security | β | |
| Patch EC2 Operating System | β | |
| Configure IAM | β | |
| Replace Failed Hardware | β | |
| Configure Security Groups | β | |
| Encrypt S3 Data | β | |
| Secure Hypervisor | β | |
| Create Backups | β | |
| Configure MFA | β | |
| Manage Application Code | β |
π§ͺ Enterprise Mission 05 β AWS Documentation Review
Section titled βπ§ͺ Enterprise Mission 05 β AWS Documentation ReviewβVisit:
https://aws.amazon.com/compliance/shared-responsibility-model/Read the AWS Shared Responsibility documentation.
Identify:
- Three AWS responsibilities.
- Three customer responsibilities.
- One example where responsibility changes depending on the AWS service.
π‘ Security Tip
Section titled βπ‘ Security TipβManaged services reduce operational effort but do not eliminate customer security responsibilities.
For example:
- AWS patches the underlying RDS operating system.
- You are still responsible for:
- Database users
- Passwords
- Encryption
- Security Groups
- Database backups
- Data classification
π Knowledge Check
Section titled βπ Knowledge Checkβ- What is the Shared Responsibility Model?
- What is Security of the Cloud?
- What is Security in the Cloud?
- Who patches EC2 operating systems?
- Who manages IAM users?
- Who secures AWS data centres?
- Who secures S3 bucket permissions?
- Who configures Security Groups?
- Does AWS manage your application code?
- Why is the Shared Responsibility Model important?
π Assignment
Section titled βπ AssignmentβPrepare a Shared Responsibility Assessment Report for CloudNova Technologies.
Include:
- Explanation of the Shared Responsibility Model.
- Security of the Cloud vs Security in the Cloud.
- Responsibilities for:
- EC2
- S3
- RDS
- Lambda
- EKS
- Common misconceptions.
- Recommendations for improving CloudNovaβs cloud security posture.
Length: 2β3 pages.
π‘ Key Takeaways
Section titled βπ‘ Key TakeawaysβAfter completing this lesson, you should understand:
- AWS and customers share responsibility for cloud security.
- AWS secures the infrastructure that runs cloud services.
- Customers secure everything they deploy and configure within AWS.
- The level of customer responsibility changes depending on the AWS service model.
- Understanding this model is essential for designing secure cloud environments and avoiding security gaps.
π Further Reading
Section titled βπ Further Readingβ- AWS Shared Responsibility Model Documentation
- AWS Well-Architected Framework β Security Pillar
- AWS Security Best Practices
- AWS IAM User Guide
- AWS Security Blog
π Next Lesson
Section titled βπ Next Lessonββ‘οΈ Lesson 04 β AWS Security Best Practices