

# The shared responsibility model for security
<a name="sec-shared-responsibility"></a>

 Security and compliance is a shared responsibility between AWS and the customer. This shared model can help relieve the customer's operational burden as AWS operates, manages, and controls the components from the host operating system and virtualization layer down to the physical security of the facilities in which the service operates. Depending on the AWS service, the customer assumes responsibility for specific components and AWS assumes responsibility for others - specific examples will be covered by this guidance. Customers should carefully consider the services they choose as their responsibilities vary depending on the services used, the integration of those services into their IT environment, and applicable laws and regulations. The nature of this shared responsibility also provides the flexibility and customer control that permits the deployment. As shown in the following chart, this differentiation of responsibility is commonly referred to as Security "of" the Cloud versus Security "in" the Cloud. 

 **Security "of" the Cloud** – AWS is responsible for protecting the infrastructure that runs all of the services offered in the AWS Cloud. This infrastructure is composed of the hardware, software, networking, and facilities that run AWS Cloud services. 

 **Security "in" the Cloud** – Customer responsibility will be determined by the AWS Cloud services that a customer selects. This determines the amount of configuration work the customer must perform as part of their security responsibilities. For example, a service such as Amazon Elastic Compute Cloud (Amazon EC2) is categorized as Infrastructure as a Service (IaaS) and, as such, requires the customer to perform all of the necessary security configuration and management tasks. There are three categories of AWS services: infrastructure, platform, and abstracted. Customers that deploy an Amazon EC2 instance are responsible for management of the guest operating system (including updates and security patches), any application software or utilities installed by the customer on the instances, and the configuration of the AWS-provided firewall (called an EC2 security group) on each instance. For platform services, such as Amazon RDS, AWS is responsible for managing the infrastructure layer, the operating system, and the engine, while customers are responsible for configuring components of the database engine, the databases themselves, and the data. For abstracted services, such as Amazon S3 and Amazon DynamoDB, AWS operates the infrastructure layer, the operating system, and platforms, and customers access the endpoints to store and retrieve data. Customers are responsible for managing their data (including encryption options), classifying their assets, and using IAM tools to apply the appropriate permissions. The level of responsibility a customer accepts will depend on the services used. 

![AWS Shared Responsibility Model for security. The customer is responsible for security in the cloud: customer data; platform, applications, and identity and access management; operating system, network, and firewall configuration; and client-side and server-side data encryption and network traffic protection. AWS is responsible for security of the cloud: the software layer (compute, storage, database, networking) and the hardware and AWS global infrastructure of Regions, Availability Zones, and edge locations.](https://docs.aws.amazon.com/wellarchitected/latest/framework/images/aws-shared-responsibility.png)


 This shared responsibility model also extends to IT controls. Just as the responsibility to operate the IT environment is shared between AWS and its customers, so is the management, operation, and verification of IT controls shared. AWS can help relieve customer burden of operating controls by managing those controls associated with the physical infrastructure deployed in the AWS environment that may previously have been managed by the customer. As every customer is deployed differently in AWS, customers can take advantage of shifting management of certain IT controls to AWS, which results in a (new) distributed control environment. Customers can then use the AWS control and compliance documentation available through [AWS Artifact](https://aws.amazon.com/artifact/) to help perform control evaluation and verification procedures as required. The following are examples of controls that are managed by AWS, AWS customers, or both. 

 **Inherited controls** – Controls that a customer fully inherits from AWS. 
+  Physical and environmental controls 

 **Shared controls** – Controls that apply to both the infrastructure layer and customer layers, but in separate contexts or perspectives. In a shared control, AWS provides the requirements for the infrastructure and the customer must provide their own control implementation within their use of AWS services. Examples include: 
+  Patch management – AWS is responsible for patching and fixing flaws within the infrastructure, but customers are responsible for patching their guest operating system and applications. 
  +  For AWS platform services (such as Amazon ElastiCache, Amazon RDS, and Amazon OpenSearch Service), patch management responsibility is shared as follows: 
    +  AWS responsibility: Identify vulnerabilities, develop and validate patches, release patches within the service's patching SLA, and notify customers of available updates through the service's documented notification mechanism. 
    +  Customer responsibility: Review available updates and facilitate patching by selecting maintenance windows, applying service updates, or scheduling required restarts within the timeframes communicated by AWS. 
  +  For AWS abstracted services (such as Amazon ElastiCache Serverless, Amazon DynamoDB, and Amazon S3), patch management responsibility is shared as follows: 
    +  AWS responsibility: Apply patches without requiring customer action. 
    +  Customer responsibility: Consult patching and maintenance documentation for each AWS managed service they use to understand specific notification mechanisms, maintenance window options, and update application processes available to them. 
+  Configuration management – AWS maintains the configuration of its infrastructure devices, but customers are responsible for performing configuration of their own guest operating systems, databases, and applications. 
+  Awareness and training – AWS trains AWS employees, but customers must train their own employees. 

 **Customer specific** – Controls that are solely the responsibility of the customer based on the application they are deploying within AWS services. Examples include: 
+  Service and Communications Protection or Zone Security, which might require a customer to route or zone data within specific security environments. 
+  Implementation of compliance requirements that are on the customer-side of the shared responsibility model, for example: PCI-DSS requirements mandate network segmentation. Customers must implement network segmentation to meet this PCI-DSS requirement pursuant to the compliance framework. 