How to Test Cloud Trust Boundaries and Tenant Isolation

Summary
The article outlines a cloud pentesting approach that assesses trust boundaries across External, Overlay, and Underlay layers, focusing on whether a tenant can affect other tenants or provider systems and how to verify impact safely.
Key points
- The proposed model divides cloud infrastructure into External, Overlay, and Underlay layers, with trust boundaries between zones of differing privilege and responsibility.
- A cloud pentest should assess whether access from one tenant can affect other tenants’ data, provider IAM accounts, internal resources, or infrastructure—not merely whether code execution is possible.
- The article describes four stages for validating a boundary violation: network visibility, successful authentication, confirmed permissions, and a controlled action beyond the boundary.
- Cloud services with similar customer-facing features may use different internal architectures, so testers should reconstruct the environment from evidence such as processes, routes, certificates, and service configuration.
- Examples including ChaosDB and Azurescape illustrate how runtime escapes and service-account access can lead to cross-tenant impact.
- Testing should use authorized scope, synthetic data, and minimal reversible actions; provider-overlay and infrastructure testing requires provider authorization.
Article Details
- Topic
- Cloud penetration-testing methodology for assessing trust boundaries and tenant isolation across external, provider overlay, and infrastructure layers.
CVE
CVE-2026-19478GitLab · GitLabThe pentester interacts with the managed service interface and finds a vulnerability in it (for example, CVE-2026-19478 in the case of the GitLab web interface) or in add-on modules deployed by the cloud provider.CVE-2026-43284Linux · Linux; Red Hat · NVIDIA for RHEL 10; +28 moreNext, the attacker finds ways to escape the container (using CVE-2026-43284) into the runtime: the container runtime, hypervisor, or host agent.
Vendors
Products
Azure Cosmos DBSimilar logic was demonstrated in the public ChaosDB case: the Jupyter Notebook feature in Azure Cosmos DB created a risk of access to other tenants’ keys.KubernetesTenant plane is the set of IT services and data that a tenant manages directly: virtual machines, Kubernetes clusters, databases, object storage, and managed applications.OpenStackA provider can use OpenStack, Kubernetes, its own control plane, or a combination of them.
