Compliance Inheritance Model
What you'll learn: How to determine which compliance controls your cloud provider handles versus what remains your responsibility under the shared responsibility model.
The Core Idea
The Compliance Inheritance Model describes how certain compliance controls are automatically inherited from your cloud provider, while others remain squarely on your shoulders. Think of it like renting an apartment in a building that's already up to fire code—you inherit the building's sprinkler system compliance, but you're still responsible for not blocking the fire exits in your unit.
When a cloud provider achieves certifications like SOC 2, ISO 27001, PCI DSS, HIPAA, or GDPR compliance, they're asserting control over the physical and environmental security of their infrastructure. You inherit these baseline controls without implementing them yourself.
What You Inherit vs. What You Own
Inherited from Provider:
- Physical data center security (locks, guards, cameras)
- Environmental controls (HVAC, power redundancy)
- Network infrastructure security
- Hypervisor and hardware maintenance
- Disposal of physical storage media
Your Responsibility:
- Data classification and encryption
- Access control policies (IAM, RBAC)
- Application-level security
- Backup and disaster recovery configurations
- Logging and monitoring setups
- Network security groups and firewall rules
The line shifts depending on service model: with IaaS you own more; with SaaS you own less. For example, with AWS KMS you inherit the HSM security controls, but you must configure key policies correctly to meet your audit requirements.
Key Takeaway: Compliance inheritance means your cloud provider's certifications cover infrastructure controls, but you must still implement and demonstrate application-layer, data, and access controls to meet your organization's compliance obligations—the provider's certificate alone doesn't make your workload compliant.