Hyper-V
Microsoft's hypervisor, built into Windows Server.
Where It Sits
The small stack marks its layer. Beside it, each related technology links to its own page.
- App
- Framework
- Web Server
- Runtime
- Containers
- OS
- HypervisorHyper-V
- Firmware
- Hardware
- Data
Hyper-VVirtualisation
See It in the StackAbout
Hyper-V is Microsoft's hypervisor, built into Windows Server. It splits one physical machine into many virtual machines, each running its own operating system. It is a rival to VMware ESXi.
How to Spot It
These are signs that a system runs Hyper-V, seen from outside without signing in, such as a response header, a cookie, a path or a default port. They help you find where it runs across your own estate. A version shown to the world also tells anyone scanning which flaws might apply, so it is worth hiding.
- MAC prefix
00:15:5D (Hyper-V virtual network adapter)
If It Has a Flaw
A flaw in the hypervisor can let code in one virtual machine reach the host or the other virtual machines, breaking the wall that keeps them apart.
A flaw exposes what runs on it.
- Containers
Docker
Kubernetes- Operating System
Windows Server
Linux
Rivals
Rivals do the same job on the same layer, so a system usually runs one of them in any one place. A flaw in a rival does not reach Hyper-V.
Stacks and Code
Its code arrives from the sources listed, and each source's page says how bad code could get in through it.
- Its Code Comes From
- Vendor Updates