Skip to content

Shared Responsibility Model

Learning Path

πŸ“˜ Phase 1 – Overview


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


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.


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 |
| |
+--------------------------------------+

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.


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.


The level of customer responsibility depends on the AWS service being used.


AWS manages:

  • Physical servers
  • Networking
  • Storage hardware
  • Hypervisor

Customer manages:

  • Operating System
  • Firewall rules
  • Security Groups
  • Installed software
  • Applications
  • IAM
  • Data
  • Backups
  • Monitoring

AWS additionally manages:

  • Database software
  • Operating system patching
  • Infrastructure maintenance

Customer still manages:

  • Database users
  • Database permissions
  • Encryption
  • Backups
  • Network access
  • Database configuration

AWS manages:

  • Storage infrastructure
  • Hardware
  • Availability

Customer manages:

  • Bucket policies
  • Public access settings
  • Object permissions
  • Encryption
  • Versioning
  • Lifecycle policies

AWS manages:

  • Infrastructure
  • Runtime environment
  • Scaling
  • Operating system

Customer manages:

  • Function code
  • IAM roles
  • Secrets
  • Environment variables
  • Logging
  • Permissions

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 ❌ βœ…

❌ β€œ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.


Reality:

Backup configuration is your responsibility unless you explicitly enable managed backup services.


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.


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:

  1. Explain the Shared Responsibility Model.
  2. Identify which issues belong to AWS.
  3. Identify which issues belong to CloudNova Technologies.
  4. 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.


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?

Answer the following questions:

  1. What is the Shared Responsibility Model?
  2. What is the difference between Security OF the Cloud and Security IN the Cloud?
  3. Who manages the physical data centres?
  4. Who secures EC2 operating systems?
  5. Who configures IAM policies?
  6. Who secures customer data?
  7. How do responsibilities change when using managed services?

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.


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.

  • AWS Shared Responsibility Model
  • AWS Well-Architected Framework – Security Pillar
  • AWS IAM Best Practices
  • CIS AWS Foundations Benchmark
  • AWS Security Best Practices

➑️ CIA Triad