Course contentsShow
← Security
Lesson 1691 of 3,05234. Cloud Security - Shared ResponsibilityFree lesson

Compliance Responsibility Mapping

Learning how regulatory compliance requirements map to shared responsibilities and understanding inheritance versus customer controls.

Compliance Responsibility Mapping

What you'll learn: How to map regulatory compliance requirements to the shared responsibility model and distinguish between controls you inherit versus those you must implement yourself.

When working in the cloud, compliance doesn't disappear—it gets divided. Compliance responsibility mapping is the process of determining which party (cloud provider or customer) is responsible for implementing and maintaining each control required by regulations like HIPAA, PCI-DSS, SOC 2, or GDPR.

Understanding Inherited vs. Customer Controls

Think of compliance like maintaining a rented apartment building. The landlord handles structural safety (fire suppression, building codes), but you're responsible for locking your door and not storing hazardous materials inside.

Inherited controls are those the cloud provider implements and maintains. For example:

  • Physical security of data centers (cameras, guards, biometrics)
  • Infrastructure patching and hardening
  • Network perimeter defenses
  • Environmental controls (fire suppression, cooling)

These typically satisfy compliance requirements "out of the box" because the provider's certifications cover them.

Customer controls remain your responsibility:

  • Data encryption (at rest and in transit)
  • Identity and access management policies
  • Application-level security
  • Data classification and handling
  • Audit logging configuration
  • Backup and disaster recovery procedures

The Mapping Process

Review your compliance framework and create a responsibility matrix. For each control requirement:

  1. Identify if it's inherited (provider handles it)
  2. Determine if it's shared (both parties contribute)
  3. Mark purely customer-owned controls

For instance, PCI-DSS requires encrypted storage. In IaaS, you must enable and manage encryption. In SaaS, it may be inherited if the provider encrypts all data by default.

Key Takeaway: Compliance responsibility mapping prevents dangerous gaps by clearly defining who implements each regulatory control—failing to understand this division leaves you accountable for controls you assumed were inherited.