- Blog Categories
- Project Management
- Agile Management
- IT Service Management
- Cloud Computing
- Business Management
- BI And Visualisation
- Quality Management
- Cyber Security
- DevOps
- Most Popular Blogs
- PMP Exam Schedule for 2026: Check PMP Exam Date
- Top 60+ PMP Exam Questions and Answers for 2026
- PMP Cheat Sheet and PMP Formulas To Use in 2026
- What is PMP Process? A Complete List of 49 Processes of PMP
- Top 15+ Project Management Case Studies with Examples 2026
- Top Picks by Authors
- Top 170 Project Management Research Topics
- What is Effective Communication: Definition
- How to Create a Project Plan in Excel in 2026?
- PMP Certification Exam Eligibility in 2026 [A Complete Checklist]
- PMP Certification Fees - All Aspects of PMP Certification Fee
- Most Popular Blogs
- CSM vs PSM: Which Certification to Choose in 2026?
- How Much Does Scrum Master Certification Cost in 2026?
- CSPO vs PSPO Certification: What to Choose in 2026?
- 8 Best Scrum Master Certifications to Pursue in 2026
- Safe Agilist Exam: A Complete Study Guide 2026
- Top Picks by Authors
- SAFe vs Agile: Difference Between Scaled Agile and Agile
- Top 21 Scrum Best Practices for Efficient Agile Workflow
- 30 User Story Examples and Templates to Use in 2026
- State of Agile: Things You Need to Know
- Top 24 Career Benefits of a Certifed Scrum Master
- Most Popular Blogs
- ITIL Certification Cost in 2026 [Exam Fee & Other Expenses]
- Top 17 Required Skills for System Administrator in 2026
- How Effective Is Itil Certification for a Job Switch?
- IT Service Management (ITSM) Role and Responsibilities
- Top 25 Service Based Companies in India in 2026
- Top Picks by Authors
- What is Escalation Matrix & How Does It Work? [Types, Process]
- ITIL Service Operation: Phases, Functions, Best Practices
- 10 Best Facility Management Software in 2026
- What is Service Request Management in ITIL? Example, Steps, Tips
- An Introduction To ITIL® Exam
- Most Popular Blogs
- A Complete AWS Cheat Sheet: Important Topics Covered
- Top AWS Solution Architect Projects in 2026
- 15 Best Azure Certifications 2026: Which one to Choose?
- Top 22 Cloud Computing Project Ideas in 2026 [Source Code]
- How to Become an Azure Data Engineer? 2026 Roadmap
- Top Picks by Authors
- Top 40 IoT Project Ideas and Topics in 2026 [Source Code]
- The Future of AWS: Top Trends & Predictions in 2026
- AWS Solutions Architect vs AWS Developer [Key Differences]
- Top 20 Azure Data Engineering Projects in 2026 [Source Code]
- 25 Best Cloud Computing Tools in 2026
- Most Popular Blogs
- Company Analysis Report: Examples, Templates, Components
- 400 Trending Business Management Research Topics
- Business Analysis Body of Knowledge (BABOK): Guide
- ECBA Certification: Is it Worth it?
- Top Picks by Authors
- Top 20 Business Analytics Project in 2026 [With Source Code]
- ECBA Certification Cost Across Countries
- Top 9 Free Business Requirements Document (BRD) Templates
- Business Analyst Job Description in 2026 [Key Responsibility]
- Business Analysis Framework: Elements, Process, Techniques
- Most Popular Blogs
- Best Career options after BA [2026]
- Top Career Options after BCom to Know in 2026
- Top 10 Power Bi Books of 2026 [Beginners to Experienced]
- Power BI Skills in Demand: How to Stand Out in the Job Market
- Top 15 Power BI Project Ideas
- Top Picks by Authors
- 10 Limitations of Power BI: You Must Know in 2026
- Top 45 Career Options After BBA in 2026 [With Salary]
- Top Power BI Dashboard Templates of 2026
- What is Power BI Used For - Practical Applications Of Power BI
- SSRS Vs Power BI - What are the Key Differences?
- Most Popular Blogs
- Data Collection Plan For Six Sigma: How to Create One?
- Quality Engineer Resume for 2026 [Examples + Tips]
- 20 Best Quality Management Certifications That Pay Well in 2026
- Six Sigma in Operations Management [A Brief Introduction]
- Top Picks by Authors
- Six Sigma Green Belt vs PMP: What's the Difference
- Quality Management: Definition, Importance, Components
- Adding Green Belt Certifications to Your Resume
- Six Sigma Green Belt in Healthcare: Concepts, Benefits and Examples
- Most Popular Blogs
- Latest CISSP Exam Dumps of 2026 [Free CISSP Dumps]
- CISSP vs Security+ Certifications: Which is Best in 2026?
- Best CISSP Study Guides for 2026 + CISSP Study Plan
- How to Become an Ethical Hacker in 2026?
- Top Picks by Authors
- CISSP vs Master's Degree: Which One to Choose in 2026?
- CISSP Endorsement Process: Requirements & Example
- OSCP vs CISSP | Top Cybersecurity Certifications
- How to Pass the CISSP Exam on Your 1st Attempt in 2026?
- Most Popular Blogs
- Top 7 Kubernetes Certifications in 2026
- Kubernetes Pods: Types, Examples, Best Practices
- DevOps Methodologies: Practices & Principles
- Docker Image Commands
- Top Picks by Authors
- Best DevOps Certifications in 2026
- 20 Best Automation Tools for DevOps
- Top 20 DevOps Projects of 2026
- OS for Docker: Features, Factors and Tips
- More
- Agile & PMP Practice Tests
- Agile Testing
- Agile Scrum Practice Exam
- CAPM Practice Test
- PRINCE2 Foundation Exam
- PMP Practice Exam
- Cloud Related Practice Test
- Azure Infrastructure Solutions
- AWS Solutions Architect
- IT Related Pratice Test
- ITIL Practice Test
- Devops Practice Test
- TOGAF® Practice Test
- Other Practice Test
- Oracle Primavera P6 V8
- MS Project Practice Test
- Project Management & Agile
- Project Management Interview Questions
- Release Train Engineer Interview Questions
- Agile Coach Interview Questions
- Scrum Interview Questions
- IT Project Manager Interview Questions
- Cloud & Data
- Azure Databricks Interview Questions
- AWS architect Interview Questions
- Cloud Computing Interview Questions
- AWS Interview Questions
- Kubernetes Interview Questions
- Web Development
- CSS3 Free Course with Certificates
- Basics of Spring Core and MVC
- Javascript Free Course with Certificate
- React Free Course with Certificate
- Node JS Free Certification Course
- Data Science
- Python Machine Learning Course
- Python for Data Science Free Course
- NLP Free Course with Certificate
- Data Analysis Using SQL
Shared Responsibility Model in Cloud Computing: AWS, Azure & GCP
Updated on Jul 10, 2026 | 0.6k+ views
Share:
Table of Contents
View all
- What Is the Shared Responsibility Model in Cloud Computing
- How the Shared Responsibility Model Changes Across Cloud Services
- Microsoft Azure Shared Responsibility
- AWS Shared Responsibility Model Explained
- How GCP Approaches the Shared Responsibility Model
- AWS vs Azure vs GCP Shared Responsibility Model
- What Are the Most Common Shared Responsibility Model Mistakes?
- How Businesses Can Strengthen Their Shared Responsibility Model Strategy
- Conclusion
The Shared Responsibility Model explains that cloud security is a joint responsibility between the Cloud Service Provider (CSP) and the customer.
The CSP is responsible for securing cloud infrastructure, including physical data centers, hardware, and core cloud services. The customer is responsible for protecting the data, applications, and configurations running inside that infrastructure.
Whether an organization uses AWS, Azure, or GCP, the responsibility for data ownership, user accounts, and access management always remains with the customer.
Understanding this model helps businesses manage cloud security properly and avoid common security gaps.
Cloud professionals can enhance their understanding of AWS security and architecture through the upGrad KnowledgeHut AWS Solutions Architect Certification Training, which covers key concepts required for building secure cloud solutions.
Master the Right Skills & Boost Your Career
Avail your free 1:1 mentorship session
What Is the Shared Responsibility Model in Cloud Computing
The Shared Responsibility Model in cloud computing is a security and compliance framework that divides accountability between the cloud provider and the customer.
The provider is responsible for the security of the cloud, meaning physical data centers, host infrastructure, networking hardware, and virtualization layers.
The customer is responsible for security in the cloud, meaning data classification, identity and access management, operating system patching (where applicable), and application-level configurations.
This division is not optional or negotiable. It is built into the architecture of every major cloud platform and forms the legal and technical baseline for compliance frameworks such as ISO 27001, SOC 2, HIPAA, and GDPR.
How the Shared Responsibility Model Changes Across Cloud Services
The shared responsibility model changes depending on the type of cloud service being used.
The level of management and security responsibility depends on whether an organization uses Infrastructure as a Service (IaaS), Platform as a Service (PaaS), or Software as a Service (SaaS).
Infrastructure as a Service (IaaS)
Examples:
- Amazon EC2
- Azure Virtual Machines
- Google Compute Engine
In IaaS, cloud providers are responsible for securing the physical infrastructure, including servers, storage, and networking. Organizations are responsible for managing:
- Operating systems
- Security patches
- Applications
- Firewalls
- User access
- Data security
IaaS provides the highest level of flexibility, but it also requires organizations to handle more security and management tasks.
Platform as a Service (PaaS)
Examples:
- Azure App Service
- AWS Elastic Beanstalk
- Google App Engine
In PaaS environments, cloud providers manage the infrastructure, operating system, and runtime environment. This reduces the amount of technical management required from organizations.
Organizations remain responsible for:
- Application code
- Data protection
- Identity management
- Access controls
PaaS allows development teams to focus more on creating applications instead of managing servers and infrastructure.
Software as a Service (SaaS)
Examples:
- Microsoft 365
- Salesforce
- Google Workspace
In SaaS, cloud providers handle most infrastructure and application maintenance tasks, including updates, availability, and system management.
Organizations are still responsible for:
- User accounts
- Password policies
- Data governance
- Permission management
- Regulatory compliance
A common misunderstanding is that SaaS removes all security responsibilities. However, organizations still need to manage access, protect data, and follow security and compliance requirements.
Microsoft Azure Shared Responsibility
The Azure framework follows the same concept, dividing tasks across the Microsoft cloud ecosystem.
Microsoft Is Responsible For:
- Physical buildings and data centers
- Host computer operating systems
- Core network infrastructure
- Hypervisor security (the software that splits physical servers into virtual ones)
- General data center operations
Customers Are Responsible For:
- Microsoft Entra ID permissions (formerly known as Azure Active Directory)
- Software and workload setups
- Data security and encryption
- User device protection (endpoints)
- Application code
- General identity management
Example:
For Azure Virtual Machines, customers must install security patches, manage antivirus software, configure firewall rules (Network Security Groups), and control administrator access.
For fully managed services such as Azure SQL Database, Microsoft handles the underlying infrastructure, operating systems, and database platform maintenance.
Customers remain responsible for managing data access, permissions, encryption settings, and compliance requirements.
Popular Azure Security Tools:
Microsoft Defender for Cloud: Continuously monitors security posture, identifies vulnerabilities, and protects cloud workloads across Azure environments.
Microsoft Sentinel: A cloud-native security information and event management (SIEM) platform that helps organizations detect, investigate, and respond to cyber threats.
Azure Key Vault: Securely stores secrets, certificates, encryption keys, passwords, and API credentials while reducing the risk of unauthorized access.
Azure Policy: Enables organizations to enforce security standards, governance controls, and compliance requirements across Azure resources.
Microsoft Entra ID: Manages user identities, authentication, and access controls through capabilities such as Single Sign-On (SSO), Multi-Factor Authentication (MFA), and Role-Based Access Control (RBAC).
Build advanced Azure architecture skills with the upGrad KnowledgeHut Azure Solutions Architect Certification Training and learn how to create secure and enterprise-ready cloud solutions.
AWS Shared Responsibility Model Explained
The AWS Shared Responsibility Model divides security tasks into two separate categories to ensure nothing is missed.
Security of the Cloud (AWS Responsibility)
AWS takes care of the physical and foundational parts of the system. This includes:
- Physical data centers and buildings
- Computer hardware and servers
- Global network infrastructure
- Regions and availability zones
- Core cloud systems that run managed services
Security in the Cloud (Customer Responsibility)
The organization using AWS is responsible for protecting whatever it puts inside the cloud. This includes:
- User accounts, passwords, and permissions (IAM)
- Operating systems on virtual servers (like EC2 instances)
- Application security and code
- Data encryption both at rest and during transfer
- Firewall rules and network security groups
- Backup and recovery plans
Example:
If a company accidentally sets a cloud storage folder (an S3 bucket) to "public" and confidential files are leaked, AWS is not responsible for the data breach. The customer controls all access settings and data visibility.
Key AWS Security Tools
Companies often strengthen their cloud safety using built-in tools like:
- AWS Identity and Access Management (IAM): Controls who can log in and what they can access.
- AWS Security Hub: Checks security settings across the entire cloud account in one place.
- AWS GuardDuty: Watches for strange or dangerous activity automatically.
- AWS Shield: Protects websites from massive cyberattacks that try to crash them.
- AWS Key Management Service (KMS): Creates and controls the keys used to lock and encrypt data.
Understanding this shared model helps businesses avoid simple setup mistakes, which cause most cloud security incidents.
How GCP Approaches the Shared Responsibility Model
Google Cloud Platform (GCP) follows the shared responsibility model with a strong focus on security built into its cloud services.
Google manages the security of cloud infrastructure, while organizations are responsible for protecting their data, applications, and access controls.
Google Cloud Responsibilities
Google is responsible for securing:
- Physical data centers
- Global networking infrastructure
- Hardware systems
- Core cloud services
- Virtualization technology
Google manages the security and reliability of the underlying cloud platform to provide a secure environment for businesses.
Customer Responsibilities
Organizations are responsible for managing:
- User access and permissions
- Data classification
- Application security
- Encryption settings
- Workload protection
- Compliance requirements
Although GCP managed services reduce the need for manual infrastructure management, organizations still remain responsible for controlling data access and maintaining proper security practices.
Popular GCP Security Tools
Many businesses use GCP security tools to improve protection and monitoring, including:
- Google Cloud IAM
- Security Command Center
- Cloud Armor
- Cloud Key Management Service
- Chronicle Security Operations
Even with highly managed cloud services, organizations must continue to manage user identities, permissions, and sensitive data to maintain a secure cloud environment.
AWS vs Azure vs GCP Shared Responsibility Model
Although terminology differs slightly, the overall concept remains consistent.
Responsibility |
AWS |
Azure |
GCP |
| Physical security | Provider | Provider | Provider |
| Networking | Provider | Provider | Provider |
| Hypervisor | Provider | Provider | Provider |
| IAM configuration | Customer | Customer | Customer |
| Data encryption | Customer | Customer | Customer |
| Application security | Customer | Customer | Customer |
| Compliance configuration | Customer | Customer | Customer |
| Backup strategy | Customer | Customer | Customer |
Regardless of platform, customers always own the security of their applications and data.
Building secure cloud environments requires knowledge of cloud architecture and best practices. The upGrad KnowledgeHut Cloud Computing Courses help professionals develop essential skills for designing and managing cloud solutions.
What Are the Most Common Shared Responsibility Model Mistakes?
Here are the most common mistakes organizations make.
1. Thinking the Cloud Provider Handles All Security
One of the biggest mistakes is believing that AWS, Azure, or GCP takes care of everything related to security.
In reality, cloud providers protect the infrastructure, but customers must secure:
- Data
- User accounts
- Access permissions
- Applications
- Cloud configurations
When businesses overlook these responsibilities, they increase the risk of security breaches and compliance issues.
2. Leaving Storage Open to the Public
Incorrectly configured storage services are a common cause of cloud data leaks.
Examples include:
- Public AWS S3 buckets
- Open Azure Blob Storage containers
- Misconfigured Google Cloud Storage buckets
A small mistake in permissions can expose sensitive business or customer data to anyone online.
3. Poor Identity and Access Management (IAM)
Many organizations give users more access than they actually need.
Common mistakes include:
- Too many admin privileges
- Shared user accounts
- Weak passwords
- Not enabling Multi-Factor Authentication (MFA)
- Keeping unused accounts active
Following the principle of least privilege helps reduce security risks.
4. Not Updating Software and Operating Systems
In cloud virtual machine environments, customers are responsible for keeping systems updated.
Failing to update:
- Operating systems
- Web servers
- Databases
- Applications
can leave known security vulnerabilities open to attackers.
5. Not Using Data Encryption
Cloud providers offer strong encryption tools, but customers usually need to enable and manage them.
Common issues include:
- Unencrypted databases
- Poor key management
- Unprotected backups
Encrypting data both at rest and in transit adds an important layer of protection.
6. Not Monitoring Cloud Resources
Many businesses set up cloud services but do not monitor them regularly.
Without proper monitoring, organizations can miss:
- Suspicious login attempts
- Unauthorized access
- Configuration changes
- Malware activity
Cloud security requires continuous monitoring, not a one-time setup.
7. Assuming Compliance Is Automatic
Just because a cloud provider meets standards like GDPR, HIPAA, or PCI DSS does not mean your organization is automatically compliant.
Customers are still responsible for:
- Managing access controls
- Protecting sensitive data
- Following regulatory requirements
- Maintaining audit records
Ignoring these responsibilities can lead to failed audits and fines.
8. Not Having Backup and Recovery Plans
Some businesses assume the cloud provider automatically backs up everything.
However, customers are often responsible for:
- Creating backup policies
- Setting retention periods
- Testing recovery procedures
- Building disaster recovery plans
Without proper backups, recovering from data loss can be difficult and costly.
9. Ignoring Employee Security Training
People are often the weakest link in security.
Without training, employees may:
- Share passwords
- Fall for phishing emails
- Misconfigure cloud resources
- Give unnecessary access to users
Regular security awareness training helps prevent these mistakes.
10. Not Reviewing Configurations Regularly
Cloud environments change quickly as new users, applications, and services are added.
If configurations are not reviewed regularly, businesses may end up with:
- Excessive permissions
- Outdated security rules
- Unused accounts
- Publicly exposed resources
Regular security reviews help identify problems before they become serious threats.
How Businesses Can Strengthen Their Shared Responsibility Model Strategy
Understanding responsibilities is only the first step. Organizations also need proper governance and security controls in place to act on that understanding.
1. Establish Strong Identity Management
Identity is often the weakest link in cloud security, so it deserves the most attention. Strong identity management includes:
- Multifactor authentication (MFA)
- Role based access control (RBAC)
- Least privilege access principles
2. Continuously Monitor Configurations
Misconfigurations remain one of the leading causes of cloud security incidents, and most of them go unnoticed until something breaks. Regular monitoring should cover:
- Storage permissions
- Network settings
- Security groups
- Public exposure risks
3. Encrypt Sensitive Data
Data should stay protected no matter where it sits or where it travels:
- At rest
- In transit
Encryption alone is not enough. It works best when paired with proper key management practices.
4. Conduct Routine Security Assessments
Security is not a one time setup; it needs regular checkups. Routine audits help catch:
- Compliance gaps
- Human errors
- Security vulnerabilities
- Excessive permissions
5. Implement Cloud Security Automation
Manual security checks cannot keep pace with how fast cloud environments change. Automation allows faster detection and quicker remediation of risks across AWS, Azure, and GCP environments, closing the gap between when a risk appears and when someone actually notices it.
Conclusion
The Shared Responsibility Model is the foundation of cloud security, where both the Cloud Service Provider (CSP) and the customer play important roles. Cloud providers secure the underlying infrastructure, while organizations are responsible for protecting their data, applications, identities, and configurations.
Whether using AWS, Azure, or GCP, understanding these responsibilities helps prevent security gaps and compliance issues. By implementing strong access controls, regular monitoring, encryption, and security best practices, businesses can create a safer and more reliable cloud environment.
Contact our upGrad KnowledgeHut experts and get personalized guidance on choosing the right course, career path, and certification for your goals.
Frequently Asked Questions (FAQs)
What happens if a customer ignores their responsibilities in the cloud?
Failing to secure your part of the cloud environment can lead to data breaches, unauthorized access, compliance violations, and financial losses. Even if the cloud provider's infrastructure is fully secure, customer-side misconfigurations can expose sensitive information. Regular security reviews help reduce these risks.
Why is Identity and Access Management (IAM) so important in cloud security?
IAM controls who can access cloud resources and what actions they are allowed to perform. Poorly managed permissions are one of the most common causes of cloud security incidents. Applying the principle of least privilege and regularly reviewing access rights helps keep your environment secure.
Are cloud providers responsible for customer data security?
No. Under the Shared Responsibility Model, cloud providers secure the infrastructure that runs cloud services, including physical data centers, networking, and hardware. Customers are responsible for protecting their own data by implementing encryption, managing user access, configuring security settings, and maintaining backups. Regardless of whether you use AWS, Azure, or GCP, ownership and security of customer data always remain your responsibility.
Who manages encryption in cloud environments?
Encryption is a shared responsibility. Cloud providers offer built-in encryption services and key management tools, but customers are typically responsible for enabling encryption, choosing appropriate encryption methods, managing encryption keys when using customer-managed keys, and ensuring sensitive data is protected both at rest and in transit. Proper encryption is essential for maintaining data security and regulatory compliance.
Is cloud compliance the responsibility of the cloud provider?
Cloud compliance is shared between the provider and the customer. Cloud providers maintain compliance for the underlying infrastructure and often hold certifications such as ISO 27001, SOC 2, or PCI DSS. However, customers must configure their cloud resources securely, manage access controls, protect sensitive data, and ensure their applications comply with industry-specific regulations. Using a compliant cloud platform alone does not guarantee organizational compliance.
How does responsibility change between IaaS, PaaS, and SaaS?
Customer responsibility decreases as cloud services become more managed. In Infrastructure as a Service (IaaS), customers manage operating systems, applications, and data while the provider manages the infrastructure. In Platform as a Service (PaaS), the provider also manages the operating system and runtime, leaving customers responsible for applications and data. With Software as a Service (SaaS), the provider manages nearly the entire technology stack, while customers primarily manage user accounts, access permissions, and data governance.
How does the Shared Responsibility Model support disaster recovery?
While cloud providers ensure the availability of their infrastructure, customers are responsible for creating backup strategies and disaster recovery plans for their applications and data. Regular testing of backups ensures business continuity in case of accidental deletion, cyberattacks, or system failures.
Which cloud teams should understand the Shared Responsibility Model?
This model is not just for security professionals. Cloud architects, developers, DevOps engineers, system administrators, IT managers, and compliance teams all share responsibility for maintaining a secure cloud environment. A common understanding across teams reduces security gaps and improves collaboration.
Does the Shared Responsibility Model help reduce cyberattack risks?
Yes, but only when both the cloud provider and the customer fulfill their responsibilities. Providers secure the cloud infrastructure, while customers must secure their workloads, user accounts, and data. Following the model correctly reduces the chances of misconfiguration, unauthorized access, and data breaches.
Why is continuous monitoring important in the Shared Responsibility Model?
Cloud environments are dynamic, with resources constantly being created, updated, or removed. Continuous monitoring helps organizations detect unusual activity, identify configuration changes, and respond to threats before they cause significant damage. It also supports ongoing compliance and security audits.
1668 articles published
KnowledgeHut is an outcome-focused global ed-tech company. We help organizations and professionals unlock excellence through skills development. We offer training solutions under the people and proces...
Get Free Consultation
By submitting, I accept the T&C and
Privacy Policy
