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

Shared Responsibility in IaaS

Understanding responsibility boundaries in Infrastructure-as-a-Service: provider manages physical to hypervisor, customer manages OS upward.

Shared Responsibility in IaaS

You'll learn: Where the provider's security duties end and yours begin when using Infrastructure-as-a-Service.

The IaaS Division Line

In Infrastructure-as-a-Service (IaaS), think of the cloud provider as owning and securing the building while you own and secure everything inside your apartment. The provider manages security up to the hypervisor layer—the physical data center, servers, network infrastructure, storage hardware, and the virtualization platform itself. You manage security from the operating system upward—the guest OS, applications, data, configurations, access controls, and everything running on your virtual machines.

What This Means in Practice

The provider ensures:

  • Physical security of data centers
  • Hardware reliability and patching
  • Network infrastructure security
  • Hypervisor security and isolation between tenants
  • Storage infrastructure protection

You are responsible for:

  • Operating system patching and hardening
  • Application security and updates
  • Data encryption (at rest and in transit)
  • Identity and access management for your resources
  • Firewall rules and network segmentation
  • Security monitoring and logging within your instances
  • Backup and disaster recovery of your data

Why the Boundary Matters

If a vulnerability exists in your Linux kernel or Windows Server OS, that's your responsibility to patch—even though the VM runs on the provider's infrastructure. Conversely, if a hypervisor vulnerability allows VM escape, that's the provider's responsibility to remediate. Understanding this line prevents dangerous security gaps where each party assumes the other is handling critical controls.

Key Takeaway: In IaaS, the provider secures the foundation (physical through hypervisor), but you own the security of everything from the guest OS up—treating your cloud VMs like servers you must fully manage and protect.