liveBook · Manning

Multitenancy

As explained in Fundamentals of Cybersecurity

Multi-tenancy is an architecture in which multiple tenants share infrastructure or a service while maintaining logical separation of their data and access.

Multitenancy means multiple customers, or tenants, share infrastructure. In a public cloud, the same physical server may run workloads for several customers at once. Sharing resources makes separation between tenants an important security consideration. section 13.6.1 section 13.4.2

Virtualization helps make this sharing possible. Virtual machines (VMs) provide stronger isolation because each has its own operating system. Containers share a host operating system, making them lighter and faster to start but less isolated. VMs may therefore be a better fit when tenants need strict separation, including for regulatory compliance. section 13.4.2

 
Virtual Machines (VMs)
Containers
Virtualization
Full (Hypervisor emulates entire hardware stack)
Lightweight (Container engine shares the host OS)
Isolation
Strong (each VM instance has its own OS)
Moderate (each container is a runtime environment on the same shared OS)
Startup Time
Slow (minutes)
Fast (seconds)
Performance
~15% loss
<2% loss
Density
10–100 instances per host
100–1000 instance per host
Security Risks
Compromise of OS is typically contained to that VM
Shared OS increases potential blast radius on OS security attacks
Ideal Use Case
Running multiple fully independent OS environments
Rapid deployment of microservices and applications
Virtualization
Full (Hypervisor emulates entire hardware stack)
Lightweight (Container engine shares the host OS)
Isolation
Strong (each VM instance has its own OS)
Moderate (each container is a runtime environment on the same shared OS)

Compare the VM and container rows for isolation, security risks, startup time, and resource density; stronger separation comes with a resource trade-off. section 13.4.2

Shared infrastructure does not make every security task the provider’s job. The cloud service model determines which layers the provider manages and which remain the customer’s responsibility. When assessing a shared cloud service, consider both tenant isolation and that division of responsibilities. section 13.5 section 13.6.1

How Fundamentals of Cybersecurity covers it

How deep it goes
Defines shared-resource tenancy and compares VM and container isolation, without detailing tenant-separation mechanisms.
Examples
Uses a physical server hosting several customers’ workloads and a VM-versus-container comparison to illustrate the trade-off.
What it assumes
Introduces the public-cloud sharing model directly and explains isolation through a VM–container comparison.
What you can do after
Evaluate/understand it by distinguishing shared infrastructure from tenant isolation and checking provider–customer responsibilities.
How it connects
Connects multitenancy to public cloud, virtualization, virtual machines, containers, and regulatory compliance.

Also explained in

Compare how 5 books explain multitenancy →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Fundamentals of Cybersecurity. The section links point to the parts of the book it draws on.