Cloud Shared Responsibility Compliance Checklist for AWS, Azure, and Google Cloud
cloud complianceAWSMicrosoft AzureGoogle Cloudshared responsibilitySaaS security

Cloud Shared Responsibility Compliance Checklist for AWS, Azure, and Google Cloud

SSecuring.website Editorial Team
2026-11-20
7 min read

A practical AWS, Azure, and Google Cloud checklist for assigning shared security responsibilities and reviewing cloud compliance over time.

Public cloud providers secure the underlying infrastructure, but your organization still owns important decisions about identities, configurations, data, applications, and evidence. This cloud shared responsibility compliance checklist helps AWS, Microsoft Azure, and Google Cloud customers assign control ownership, monitor recurring tasks, and prepare for security reviews without assuming that a provider certification covers the entire workload.

Overview

The shared responsibility model is a control-ownership framework. The provider generally operates and protects the physical facilities, hardware, core networking, and foundational cloud services. The customer remains responsible for how those services are configured and used. The boundary changes according to the service type: a virtual machine leaves more operating-system and application work with the customer than a fully managed database or serverless platform.

Compliance is therefore not achieved by selecting AWS, Azure, or Google Cloud alone. A provider may offer relevant assurance reports, certifications, security features, and compliance documentation, but your organization must still configure the environment, restrict access, protect data, retain evidence, and operate appropriate processes.

Start by documenting each workload, its data, its regions, its cloud services, and its control owner. A simple responsibility register can include:

  • Workload and environment name, such as production, staging, or development.
  • Cloud provider, account or subscription, project, region, and service type.
  • Data classification, business purpose, retention period, and applicable contractual or regulatory requirements.
  • Control, owner, implementation status, evidence location, review frequency, and next review date.

Use the provider's current responsibility documentation and service-specific terms as a starting point. Do not rely on a generic diagram when a workload uses multiple managed services, third-party integrations, or customer-managed encryption keys.

What to track

Shared responsibility comparison

The following table is a practical starting point for comparing cloud security responsibilities. The exact boundary depends on the service, deployment model, contract, region, and configuration.

Control areaAWS, Azure, and Google Cloud generally provideCustomer must verify and operate
Physical infrastructureData-center facilities, physical hardware, and foundational infrastructure controls.That the selected services and regions meet business, contractual, and data protection requirements.
Identity and accessIdentity platforms, authentication features, roles, policies, and access-management tools.Least-privilege roles, administrator protection, joiner-mover-leaver processes, access reviews, and emergency access controls.
Network securityCloud networking primitives, firewalls, private connectivity options, and traffic-control features.Network segmentation, exposed ports, routing, ingress and egress rules, private access, and administrative pathways.
EncryptionEncryption capabilities and key-management services, subject to service support and configuration.Encryption settings, key ownership, rotation, access policies, secrets handling, and recovery procedures.
Logging and monitoringPlatform logs, audit events, monitoring services, and alerting features.Which events are enabled, where logs are stored, retention, time synchronization, alert triage, and tamper-resistant evidence.
Workloads and dataService availability and the operation of the selected managed platform.Applications, operating systems where applicable, dependencies, input validation, data classification, retention, and secure deletion.
Resilience and recoveryService-level infrastructure resilience and published availability features.Backups, recovery objectives, restore testing, regional design, application failover, and business continuity decisions.
Compliance evidenceProvider assurance materials and service documentation.Customer policies, configurations, risk decisions, tickets, approvals, tests, training, and operating records.

Identity and access management

Inventory every human and machine identity with access to the cloud environment. Confirm that administrative accounts use strong authentication, that privileged access is limited and reviewed, and that inactive credentials are removed or disabled. Separate production from non-production access where practical, and document break-glass accounts with ownership, storage, monitoring, and test procedures.

Review role assignments, service accounts, workload identities, API keys, federated access, and permissions inherited through groups. A permission that is technically available but never reviewed is still a compliance concern. Record the date, reviewer, scope, exceptions, and remediation decision for each access review.

Network configuration and exposed services

Maintain a current diagram of virtual networks, subnets, routing, gateways, load balancers, firewalls, and private endpoints. Check for unintended public exposure, unrestricted administrative ports, overly broad security rules, and direct access to databases or storage. Treat development environments as in scope when they contain production data, credentials, or personal information.

For websites and APIs, combine cloud controls with application controls. Review TLS settings, security headers, secrets, and deployment changes; the website security headers checklist provides a related review for CSP, HSTS, and Permissions Policy.

Encryption, secrets, and data protection

Map sensitive data from collection through processing, storage, backup, export, and deletion. Confirm encryption at rest and in transit where required, then identify who can use or administer the relevant keys. Track key rotation, disabled or expired keys, secret exposure, and the recovery plan for lost access.

Cloud encryption does not replace privacy compliance. Record the cloud service and region in your data inventory or records of processing activities, and align retention and deletion settings with your documented requirements. The ROPA data-mapping guide can help connect cloud workloads to privacy records.

Logging, vulnerability management, and backups

Define the events required to investigate access, configuration, data, and administrative changes. Verify that logs reach an appropriate central destination, have a documented retention period, and are protected from unauthorized alteration. Test alerts rather than merely enabling them.

Track operating-system patches, container images, dependencies, infrastructure-as-code changes, managed-service versions, and vulnerability exceptions. For backups, document scope, frequency, encryption, retention, isolation, recovery objectives, and restore-test results. A backup that has never been restored should be treated as an unverified control.

Managed services, supplier evidence, and workload ownership

For every managed service, identify what remains yours: schemas, data permissions, network settings, authentication, application logic, retention, and monitoring. Review the provider's current service documentation and assurance reports during procurement and renewal. Keep the report, scope, period, complementary customer controls, and review notes with your vendor evidence.

Cloud providers are suppliers, but they may also sit inside a wider chain of processors and subcontractors. Update your vendor risk assessment, data processing agreement review, and transfer or residency analysis when services, regions, or processing purposes change. See the vendor risk assessment checklist and DPA checklist for related documentation.

Cadence and checkpoints

A recurring review is more reliable than a one-time cloud audit. Adapt the cadence to workload sensitivity, change volume, and contractual expectations.

Monthly checks

  • Review privileged access, new identities, failed authentication alerts, exposed resources, and high-risk configuration findings.
  • Check logging health, backup failures, unpatched assets, expiring certificates, secrets, and unresolved exceptions.
  • Compare cloud inventory with the approved asset register and investigate unknown accounts, projects, subscriptions, or regions.

Quarterly checks

  • Reperform access reviews and validate the removal of unnecessary permissions.
  • Test a representative backup restore and document recovery time, data integrity, and lessons learned.
  • Review network exposure, encryption and key access, incident contacts, supplier changes, and data-residency assumptions.
  • Sample evidence for SOC 2 readiness, an ISO 27001 program, customer questionnaires, or another applicable framework.

For a broader operational review, use a repeatable website security and compliance audit checklist. Keep each result linked to a ticket or decision record so an assessor can see not only the current state but also how issues were handled.

How to interpret changes

Not every cloud change creates the same compliance impact. Classify changes before deciding whether to update controls, evidence, contracts, or risk assessments.

  • Service change: A move from virtual machines to a managed database or serverless service may shift operating-system duties to the provider while increasing your responsibility for service configuration, identity, data, and application behavior.
  • Architecture change: A new region, account, subscription, project, network path, or disaster-recovery design can change residency, access, logging, and recovery assumptions.
  • Data change: New personal, confidential, or regulated data may require updated classification, retention, privacy records, contracts, and deletion workflows.
  • Ownership change: A new team, supplier, or deployment pipeline can leave controls without a clear owner. Reassign responsibilities and retain approval evidence.
  • Assurance change: A changed provider report scope or service eligibility may require a fresh gap review. Provider assurance is useful evidence, but it does not prove your configuration is compliant.

Prioritize changes that increase privilege, public exposure, data sensitivity, dependency concentration, or recovery difficulty. For material issues, document the risk, compensating controls, accountable owner, target date, and acceptance authority. Link cloud findings to your incident process when there is suspected unauthorized access or data exposure; the incident response plan template covers roles, escalation, and after-action review.

When to revisit

Review this checklist at least monthly for operational signals and quarterly for a structured control review. Revisit it immediately when deploying a new workload, adding a managed service, changing cloud regions, modifying identity architecture, onboarding a material supplier, processing a new category of data, or preparing for an assurance assessment.

Before each review, export or capture the current inventory, identity assignments, network exposure, logging status, backup results, vulnerability findings, key and secret status, provider evidence, and open exceptions. Assign each item a status such as implemented, partially implemented, not applicable, or needs remediation. Avoid marking a control complete when its operation or evidence is missing.

End every review with three actions: assign owners for gaps, set realistic due dates, and schedule the next checkpoint. When provider documentation or console workflows change, update your internal responsibility register and screenshots or procedures rather than copying an old provider diagram. A current, service-specific record is the most practical way to demonstrate cloud security responsibilities to your team, customers, and reviewers.

Related Topics

#cloud compliance#AWS#Microsoft Azure#Google Cloud#shared responsibility#SaaS security
S

Securing.website Editorial Team

Cybersecurity and Privacy Compliance Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.