How to protect VDIs when using VMware Horizon View and GravityZone SVE

Bitdefender GravityZone provides full visibility into organizations' overall security posture, global security threats, and control over its security services that protect virtual or physical desktops, servers and mobile devices. All Bitdefender's Enterprise Security solutions are managed within the GravityZone through a single console, Control Center, that provides control, reporting, and alerting services for various roles within the organization

This article explains how to protect the Virtual Desktop infrastructure (VDI) in a VMware environment with the use of VMware Horizon View and GravityZone Security for Virtualized Environments.

Overview

VMware Horizon View delivers desktop services from your datacenter to enable end-user freedom and IT management and control.
Desktop and application virtualization offers IT a more streamlined, secure way to manage users and provide agile, on-demand desktop services.

Bitdefender GravityZone Security for Virtualized Environments (SVE), is an all-encompassing security solution for virtualized datacenters, protecting virtualized servers and desktops on Windows, Linux, and Solaris systems.
GravityZone SVE offers protection through Security Server and Bitdefender Tools. Security Server is a dedicated virtual machine that de-duplicates and centralizes most of the antimalware functionality of antimalware clients, acting as a scan server. Bitdefender Tools is the component to be installed on the virtual machines you want to protect.

Prerequisites

The prerequisites for GravityZone SVE are:

  • ESXi host;
  • vCenter Server;
  • Control Center with GravityZone SVE service;
  • Security Server (VMware version) deployed on at least on ESXi Host;
  • Bitdefender Tools installed on golden image.

How to protect the VDIs

You can use SVE in VMware environment also when vShield Endpoint is not installed. In non-vShield VMware environment, you must install Bitdefender Tools on every virtual machine.
Bitdefender Tools offloads anti-malware processing to the Security Server via TCP/IP. Network load will be at a minimum level due to the Bitdefender Tools local cache and the centralized cache on the Security Server. Bitdefender Tools employs a local cache that is prepopulated based on its environment variables; this way it is able to offload the scanning of only what is required while excluding objects that are safe.

Note: Using GravityZone SVE in a non-vShield VMware environment, there is no need to deploy a Security Server on each ESXi Hosts.

To protect the VDIs, follow the next steps:

  1. Integrate Control Center with vCenter:
    1. Open GravityZone Control Center
    2. Go to the Configuration page
    3. Select the Virtualization Tab
    4. Click the add Add button at the right side of the table and choose vCenter Server from the menu.

    vCenter integration

  2. Install Security Server on ESXi hosts.
    1. Go to the Network page and select Virtual Machines service.
    2. Select the host(s) on which you deploy the Security Server.
    3. Right-click to access the contextual menu and select the Tasks > Install Security Server option. The Security Server Installation window appears.

      Install Security Server

    4. In the General tab, select one of the following options:
      • Use common settings for all Security Servers. Using this option while deploying multiple Security Server instances requires the target hosts to share the same storage and have identical hardware specs. In addition, all security servers will be part of the same management network segment and they will be automatically configured by DHCP.

        Note: If DHCP is used, make sure all IPs assigned to Security Servers are reserved.

      • Configure each Security Sever differently. This option allows you to have different values for each setting of the Security Servers.
    5. Click Next to configure the Security Server instance(s):
      • Name – The name of the Security Server which will appear in VMware Inventory.
      • Deploy Container – the vCenter server parent container for the new Security Server.
      • Provisioning – the VMDK provisioning type.
      • Consolidation – the hardware resources assignation. If Custom level is selected, the administrator can specify the amount of CPU and Memory.
      • Set Administrative Password – at the time of the deployment the administrator can change the Security Server root password. If this option is not selected, the root account will have the default password and the only way this can be changed later is by accessing the VM's console.
      • Timezone – the time zone setting. Clock is automatically synchronized by the ntpd service.
      • Network Settings – the VMs management network settings.

      Security Server Installation window

    6. After all the configurations are done, if you have different settings for your Security Servers, click Next to proceed with the next instance, otherwise click Save. The deployment task starts.
      Note: You can view the deployment task progress in the Network > Tasks page. Check the task status, by clicking the link in the Status column. After the deployment task reaches the status In progress 100%, the new Security Server is powered on and boot process starts. Allow up to 3 minutes for the boot operation to complete. The deployment task will display the Finished status after the management agent on the Security Server synchronizes with GravityZone for the first time, announcing the administrator the new Security Server is operational.

    Security Server in Network inventory

  3. Create a virtual machine (with Windows 7 for example) with all the programs needed by users.
  4. Deploy Bitdefender Tools on this new virtual machine:
    1. Select the VM on which you deploy Bitdefender Tools.
    2. Right-click to access the contextual menu and select the Tasks > Install client option. The Bitdefender Tools Installation window appears.

      Install Bitdefender Tools

    3. Under Security Server Assignation, select the Security Server that will manage the virtual machine from the Security Server list, then click the add Add button at the right side of the table.
    4. Click Next.
    5. Under the Credentials Manager section, specify the administrative credentials required for remote authentication on the virtual machine.
  5. Configure the VMware Horizon View: connect to VMware Horizon View Administrator and create the pools for the VDIs.

    VMware Horizon View Administrator login

  6. Once VMware Horizon View is configured and a user is trying to connect from a VMware View Client to a VDI, new Virtual Desktops are created.

    VMware View Client login

  7. All the VDIs from VMware Horizon View will be protected.

    The VDIs in Network inventory

    Bitdefender Tools window

    To be sure that the VDIs are protected, you can do the following checks:
    • Try an EICAR test. Copy the 68 bytes string, in a .txt file and save it. If the VDI is protected, when you will reopen the .txt file, it will be empty. Also, the reports and charts from Control Center Dashboard and Reports page, the charts will show malware presence on the VDI.
    • On the Security Server you can check if your VDI is connected to it. The connection should be established on port 7081.
      netstat | grep ESTABLISHED
      tcp6 0 0 gz2svamp.tstlabs:7081 vdi-01.tstlabs.bi:65299 ESTABLISHED
      tcp6 0 0 gz2svamp.tstlabs:7081 vdi-02.tstlabs.bi:64235 ESTABLISHED

Rate this article:

Submit