Cloud Compliance Inheritance and Mapping
You'll learn how to distinguish between controls your cloud provider handles versus those you must implement, and how to map provider certifications to your compliance requirements.
The Shared Responsibility Model in Compliance
When you move to the cloud, compliance doesn't vanish—it splits. Your cloud provider (AWS, Azure, GCP) already implements hundreds of security controls to maintain their own certifications (SOC 2, ISO 27001, FedRAMP, PCI DSS). You inherit these controls for the infrastructure layer.
Think of it like renting an apartment: The landlord ensures the building has fire exits, sprinklers, and meets building codes (inherited controls). You're responsible for locking your door, not leaving the stove on, and securing your belongings (customer controls).
What You Inherit
Cloud providers manage and certify controls for:
- Physical security of data centers
- Network infrastructure hardening
- Hypervisor security and VM isolation
- Hardware disposal and destruction
- Environmental controls (power, cooling)
You can reference these in your compliance documentation without re-implementing them.
What You Must Map and Implement
You remain responsible for:
- Data encryption (at rest and in transit)
- Identity and access management (IAM roles, user permissions)
- Application-layer security controls
- Security configurations (storage bucket policies, security groups)
- Logging and monitoring setups
- Incident response procedures
Compliance Mapping Process
- Review provider attestation reports (SOC 2 Type II, ISO certifications)
- Map inherited controls to your required framework (HIPAA, PCI DSS, GDPR)
- Identify coverage gaps where you must implement additional controls
- Document your responsibility matrix for auditors
Key Takeaway: Cloud compliance is about understanding the division line—inherit what the provider certifies, then map and implement controls for everything above that infrastructure layer.