How is hardware isolated between tenants?
In Oracle Cloud Infrastructure (OCI), hardware isolation is treated as a fundamental design requirement rather than an afterthought. Oracle’s "Generation 2" cloud was architected specifically to prevent the "noisy neighbor" effect and eliminate the security risks common in traditional cloud environments.
Here is the technical breakdown of how OCI achieves true hardware isolation:
This is OCI’s most significant architectural differentiator. In traditional clouds, the "cloud control plane" (the code that manages the network and storage) runs within the server's hypervisor. If a tenant "escapes" their VM, they could theoretically access the hypervisor and the data of other tenants on that same box.
How OCI does it: Oracle moved the network and storage virtualization to a custom-designed SmartNIC (or Cloud Control Computer) that sits outside the physical server.
The Result: The server’s main CPU and memory have zero knowledge of the cloud’s management layer. This physical separation ensures that even if a tenant compromises their own OS or hypervisor, they are physically blocked from reaching the network control plane or other tenants.
To ensure a "pristine" environment for every new rental, OCI uses a hardware-based Root of Trust.
The Process: Every time a server is decommissioned by one tenant and prepared for another, OCI uses dedicated hardware to wipe the firmware and reinstall it from a known-good, secure source.
The Result: This prevents "persistent" threats—such as rootkits or malicious firmware—from surviving between one tenant’s rental and the next. You are effectively getting a "factory reset" server every time you deploy.
For the highest level of security, OCI offers Bare Metal servers.
The Difference: Unlike a Virtual Machine, which shares a physical server with others, a Bare Metal instance gives you the entire physical server.
No Hypervisor: There is no Oracle-managed hypervisor between your OS and the hardware. You have 100% of the CPU, memory, and local storage to yourself.
The Result: This provides the absolute maximum hardware isolation possible in a cloud environment, meeting the strictest regulatory and compliance standards (like those for government or financial sectors).
Many cloud providers sell more CPU and memory than the physical hardware actually possesses, betting that not all tenants will use 100% at the same time. This leads to performance dips when a "neighbor" gets busy.
OCI’s Policy: Oracle does not oversubscribe core resources. If you rent an OCPU, you are allocated a dedicated physical CPU core (or dedicated hardware threads).
The Result: Your performance is deterministic. Because the hardware isn't "stretched" across multiple tenants, your workload runs with the same speed every time, regardless of what other customers are doing.
If you want the flexibility of Virtual Machines but the hardware isolation of Bare Metal, you can use Dedicated Virtual Machine Hosts.
How it works: You rent an entire physical host and then run your own VMs on it.
The Result: You are the only tenant on that physical hardware. This eliminates "side-channel" attacks (like Spectre or Meltdown) that rely on sharing the same physical CPU chip with a stranger.
| Feature | VM Instances | Dedicated VM Hosts | Bare Metal |
| Network Isolation | Off-Box (SmartNIC) | Off-Box (SmartNIC) | Off-Box (SmartNIC) |
| CPU/RAM Sharing | Shared Physical Host | Your VMs Only | Single Tenant Only |
| Hypervisor | Managed by Oracle | Managed by Oracle | None (Customer Choice) |
| Hardware Wipe | Standard | On Host Termination | Deep Firmware Wipe |