Blue Lane VirtualShield



VirtualShield Deployment

 



VirtualShield requires VMware ESX Server 3 and deploys directly in the hypervisor. The simplest deployment scenario utilizes one virtual switch (vSwitch0) for the VirtualShield Manager and another virtual switch (vSwitch1) for VirtualShield and the servers that it protects.

In this example deployment scenario, vSwitch0 and vSwitch1 each have a physical NIC and thus dedicated traffic flows. A third virtual switch (vSwitch2) is placed behind the VirtualShield and connected to all the virtual servers. This configuration ensures that traffic passes through the VirtualShield to the protected virtual servers, so that VirtualShield can inspect all the traffic and correct problems that could exploit unpatched vulnerabilities.

Please note that the Blue Lane VirtualShield Manager runs inside the same hypervisor of the VirtualShield in this example. This is not required. In fact, a single VirtualShield Manager may run on a completely different hypervisor and control any number of VirtualShields running on other hypervisors.


Production-Ready Security for VMware Infrastructure 3




Download the Datasheet