Explained: AWS Shared Responsibility Model

Introduction to AWS:

AWS is the leading cloud platform worldwide, providing over 200 fully featured services from data centers across the globe. It's trusted by millions of customers, from startups to large enterprises and government agencies, to reduce costs, increase agility, and accelerate innovation.
AWS was the first developer of cloud-based services and boasts an extensive range of offerings and a vast customer base.

Every year we hear about companies getting hit by cloud breaches, such as scams, big payouts and unsuspected victims. But what many of these story misses is the most crucial point i.e. its actually the customers, and not the cloud providers, who's are responsible for those breaches, this happens because customers often lack control to protect their data. Unfortunately, this trend is expected to continue. According to Gartner, until 2025, 99 percent of cloud security failures will likely be the customer's fault.

To reduce such risks of cloud breaches and data leaks, it’s imperative that organizations must understand their role in ensuring cloud security. So, Cloud security follows a shared responsibility model, which outlines the division of security responsibilities between the cloud service provider (CSP) and the cloud customer.

What you need to know about AWS Shared Responsibility Model?

The AWS Shared Responsibility Model (SRM) outlines which security controls are the responsibility of AWS, and which are of the Customers.

According to the model, AWS ensures the security OF its Global Cloud Infrastructure, including physical facilities, network, and hardware.

On the other hand, customers are accountable for securing their data IN the cloud by implementing network controls, configuring applications, managing identities and access, and other measures.

Responsibility of AWS:

AWS assumes certain responsibilities for ensuring the security and compliance of the underlying infrastructure and services provided.

AWS takes on the responsibility of securing and upkeeping the software that drives its services. This includes tasks such as patching, updating, and ensuring the availability and integrity of the software stack.

Compute -

AWS manages the foundational compute infrastructure, which includes physical servers, hypervisors, and virtualization layers. Additionally, AWS ensures the availability and optimal performance of compute resources.

Storage -

AWS is responsible for securing physical storage devices, storage area networks (SANs), and object storage services. Additionally, AWS ensures the durability and availability of data.

Database -

AWS is responsible for managing database, database servers, database engines, database storage as well as the data durability and availability.

Networking -

Responsibilities for AWS include physical network components, routing, and traffic isolation which all protect against unauthorized access or interception of network traffic.

AWS Global Infrastructure -

AWS takes on the responsibility of managing the data centers, servers, networking equipment, and storage devices that constitute its global infrastructure, ensuring availability, security, and reliability for customers.

Regarding Regions, AWS is accountable for overseeing the physical infrastructure across its global regions, which encompass various data center locations worldwide.

For Availability Zones (AZs), AWS guarantees the availability and reliability of these isolated data centers within its regions, which are designed to offer fault tolerance.

In terms of Edge Locations, AWS is tasked with managing and upkeeping its global network of edge locations. These distributed points of presence (PoPs) are utilized for content caching and acceleration, aligning with the shared responsibility model.

Responsibility of Customers:

Customers utilizing AWS services are accountable for securing their data, applications, and user access within the AWS environment. This encompasses the following responsibilities:

IAM and Access Management -

Customers are tasked with overseeing access to AWS resources through IAM (Identity and Access Management). This involves creating IAM users, groups, and roles, and assigning suitable permissions to regulate access to AWS services.

Operating System and Application -

Customers are responsible for ensuring the security of the operating systems and applications deployed on their EC2 instances and other compute services. This involves implementing timely security patches and updates to safeguard against known vulnerabilities.

Data Protection and Encryption -

Customers bear the responsibility of selecting suitable encryption methods to safeguard their sensitive data both at rest and in transit. While AWS offers encryption options, customers must determine the appropriate level of protection according to the sensitivity of their data.

Security at the Application Level -

Customers are accountable for ensuring the security of their applications, encompassing authentication, authorization, and encryption at the application level.

Data Backup and Recovery Measures -

Customers are tasked with implementing robust data backup and recovery solutions to guarantee the resilience and availability of their data, safeguarding against potential loss or downtime.

Challenges Associated with the AWS Shared Responsibility Model:

Migrating to the cloud within the AWS shared responsibility model can present challenges for customers. Misunderstandings about AWS providing complete security coverage, difficulty in grasping and meeting responsibilities, improper configuration, mismanagement of access controls, and non-compliance with regulations are frequent stumbling blocks. To overcome these hurdles, thorough planning, a clear understanding of responsibilities, proactive security measures, and staying abreast of regulatory and compliance obligations are vital. These steps are crucial for achieving a secure and compliant transition to the cloud with AWS.

Conclusion:

In summary, comprehending the AWS shared responsibility model is essential for organizations utilizing AWS services. This model distinctly outlines the security obligations of both AWS and its customers, enabling businesses to establish strong security protocols for safeguarding their data and applications. Prioritizing IAM best practices and enforcing data encryption are critical measures in creating a secure cloud environment. By adhering to these practices, businesses can confidently embrace AWS, ensuring the confidentiality and integrity of their resources while mitigating potential security risks.

Endcard:

Thank you for joining me on this insightful blog on the Shared Responsibility Model. If you found this blog helpful and informative, don't forget to give it a like!

Stay updated with my latest posts and never miss out on exciting content! Click that follow button to join and stay tuned!

Follow me on LinkedIn ->

Nandita Kumari