Module 29: Compute and Virtualization Security

CCSP Domain 3 — Cloud Platform & Infrastructure Security Section A 6–8 min read

The CCSP exam tests whether you understand the isolation boundaries between VMs, containers, and serverless — and which attack surfaces each model introduces.

The Hypervisor as Trust Boundary

The hypervisor is the single most critical security component in cloud computing. It creates and enforces isolation between virtual machines running on shared physical hardware.

For the exam, remember two hypervisor types:

Type 1 (bare-metal) — runs directly on hardware. Used by all major CSPs. Examples: Xen, KVM, ESXi, Nitro
Type 2 (hosted) — runs on top of a host OS. Used for development, not production cloud

The exam cares about Type 1 because that is what protects multi-tenant cloud environments. A compromise of the hypervisor means a compromise of every VM on that host.

If an exam question asks about the SINGLE POINT OF FAILURE for tenant isolation in cloud, the answer is the hypervisor.

VM Escape: The Worst-Case Scenario

VM escape occurs when code running inside a guest VM breaks out of its isolation boundary and interacts with the hypervisor or other VMs on the same host.

Why the exam tests this:

It represents complete failure of the multi-tenancy isolation model
It is the CSP’s responsibility to prevent (hypervisor patching, hardware security)
Customers cannot directly mitigate this — they depend on provider controls

Exam thinking: If a scenario asks what a customer should do about VM escape risk, the answer is usually to verify the CSP’s security practices through audits, certifications, or contractual agreements — not to deploy a customer-side technical control.

VM Security Lifecycle

The exam tests whether you can manage VM security across the full lifecycle:

Image hardening — start from a minimal, patched base image
Golden images — pre-approved, security-configured templates
VM sprawl — uncontrolled proliferation of VMs that become unpatched and forgotten
Snapshot management — snapshots can contain sensitive data and must be encrypted and access-controlled
Decommissioning — ensure data is wiped (cryptographic erasure) when VMs are terminated

VM sprawl is a governance problem, not a technical one. The exam expects you to address it with inventory management and automated lifecycle policies, not more security tools.

Container Security: Shared Kernel Risk

Containers share the host operating system kernel. This fundamental architecture decision creates a different security profile than VMs:

Weaker isolation — a kernel exploit compromises all containers on the host
Faster startup — smaller attack surface per container, but shared underlying risk
Image supply chain — base images pulled from public registries may contain vulnerabilities or malware
Orchestration risks — misconfigured Kubernetes clusters are a leading cause of cloud breaches

Exam pattern: When comparing container vs. VM isolation, the exam wants you to articulate that VMs provide hardware-level isolation (hypervisor boundary) while containers provide process-level isolation (kernel boundary). VMs are stronger isolation; containers are more efficient.

Serverless Compute Security

Serverless functions (Lambda, Cloud Functions, Azure Functions) abstract away the entire infrastructure layer. The exam tests these unique security considerations:

The customer manages only the code and its configuration
The CSP manages the runtime, OS, and infrastructure
Functions are ephemeral — they spin up, execute, and terminate
Attack surface is narrower but includes function permissions, event triggers, and dependencies

Key risks for the exam:

Overly permissive IAM roles assigned to functions
Event injection — manipulating input events to trigger unintended behavior
Dependency vulnerabilities — third-party libraries bundled with the function
Cold start data exposure — residual data from a previous invocation in a reused execution environment

Confidential Computing and Hardware-Based Security

The exam may reference emerging hardware-based protections:

Trusted Execution Environments (TEEs) — hardware-isolated memory regions that protect data even from the hypervisor
Intel SGX, AMD SEV, ARM TrustZone — specific implementations
Confidential VMs — encrypt VM memory to protect against compromised hypervisors

This is the cloud industry’s answer to the “but what if the CSP is malicious?” question. Confidential computing protects data in use — the third pillar beyond encryption at rest and in transit.

If the exam asks how to protect data from a compromised or malicious cloud provider, think confidential computing — not traditional encryption, which still requires the provider to handle decryption keys at some point.

AI Workload Considerations

Modern compute environments increasingly include GPU-accelerated instances for AI/ML training and inference. The exam may test awareness that GPU memory is not automatically cleared between workloads, creating potential data leakage between tenants sharing GPU resources. Treat AI compute isolation with the same rigor as any other sensitive workload.