VMware VSHIELD APP 1.0 - API Manuale Utente Scaricare il pdf (Pagina 4)

Page | 4

Manager assists in installing the “vShield Guest Driver” and VMware Tools includes the “vShield

Endpoint Driver” on each VM.

One of the jobs of the third-party Security Console is to aid in the deployment of its Security Virtual

Applianc) to each ESX host. The guest operating systems such as virtual desktops can contain

optionally a “Bitdefender Silent Agent” that provides the user with an interface to check their

protection status. There’s been a little of change in terminology in the recent release with this “silent

agent” now merely being referred to as a “client” or “BDTools”.

vShield and its version numbers is how customers referrence the product. Between VMware and its

partners a separate name is used called “EPSEC” API. vShield 1.0 used EPSEC 1.0 and vShield 5.0

uses EPSEC 2.0. This can be somewhat confusing if the partner your working with refers to the EPSEC

version numbering scheme. It’s perhaps best to stick with the vShield numbering, and just confirm

that the version of vShield you intend to use is compatiable with your version of the vSphere platform

you are using.

Below is a more vendor neutral diagram of the EPSEC 2.0 implementation

from VMware:

From the guest operating system perspective an endpoint driver is

installed into the virtual desktop, which communicates to an “ESX module”

on the ESX host called the the “Mux” (Multiplexer). The ESX host moves

information from the VMCI layer into the TCP stack, and communicates

via an internal vSwitch into the Security Virtual Appliance (SVA). This

means that communication is descrete and secure and neither the SVA or

the VM needs to exposed to the internet for virus definition downloads,

scans or remediation.

1 2 3 4 5 6 7 8 9 ... 34 35

Nessun commento

VMware VSHIELD APP 1.0 - API Manuale Utente Pagina 4