Support→Support for Business Products→Kaspersky Security for Virtualization 4.0 Agentless→Installation and Removal

Kaspersky Security for Virtualization 4.0 Agentless

How to install Kaspersky Security for Virtualization 4.0 Agentless on NSX

2018 Oct 18 ID: 13172

To install Kaspersky Security for Virtualization 4.0 Agentless on NSX, follow the nine consecutive steps described below.

Configuration is performed via VMware vSphere Web Client:

In the browser, open: https://<vCenter IP address>.
Follow the link Log in to vSphere Web Client.
Enter the user name and the password for connection to the VMware vCenter and click Login.

Before beginning installation, make sure that you have set the following parameters for each hypervisor in Agent VM Settings: network, storage for service virtual machines and SVM. For more information about setting parameters in Agent VM Settings, see the VMWare product documentation.

1. Prepare VMware ESXi hypervisors for Network Attack Blocker deployment.

2. Deploy Guest Introspection

To run Kaspersky Security in the infrastructure managed by VMware vCenter and VMware NSX Manager, deploy the Guest Introspection service on each cluster of VMware hypervisors where your SVMs with the File Anti-Virus component will be located. Thus, Guest Introspection service virtual machines must be deployed on each hypervisor in a cluster.

To deploy Guest Introspection:

Select Networking & Security.
Select Installation and click the Service Deployments tab.
Click the plus icon to launch the wizard. The window Deploy Network & Security Services appears.
At the first step of the wizard, select the Guest Introspection service in the table and click Next.

ksv4nola_13172_03

Select one or several VMware clusters on which you would like to install Kaspersky Security and then click Next.

ksv4nola_13172_04

At the next step, you can change the default settings and select the storage for the service virtual machines of Guest Introspection, which will be installed on the selected VMware clusters.

Select the network to be used by the Guest Introspection service virtual machines and the storage for deploying these VMs.
If you want to configure the parameters of assigning IP addresses for service virtual machines, click the Change link in the IP assignment section. The Select IP Assignment mode window opens.
Select Use IP Pool and click the plus icon. The Add Static IP Pool window opens.
Configure the pool of static addresses and click OK. The new pool appears in the list of pools.
Click the pool you have added and click OK. The name of the selected pool will appear in the Deploy Network & Security Services window. Click Next.

Make sure all parameters are correct and click Finish.

ksv4nola_13172_10

The wizard window closes. The current status of Guest Introspection service deployment process is shown in the Installation Status section of the VMware vSphere Web Client console.

ksv4nola_13172_11

Wait until Guest Introspection is deployed.

ksv4nola_13172_12

In the VMware vSphere Web Client console, select Hosts and Clusters and make sure Guest Introspection service virtual machines have been deployed successfully on each hypervisor in the cluster.

ksv4nola_13172_13

3. Read the license information for NSX for vSphere

4. View the list of registered services

5. Configure NSX security groups

Add all SVMs you want to protect with Kaspersky Security to the NSX Security Group. First, create the NSX Security Group and configure the rules for adding VMs to the group.

The following options of adding SVMs to the NSX Security Group are available:

Adding SVMs to the NSX Security Group dynamically.
The group includes all SVMs that meet the criteria which are running at the moment of NSX Security Group creation. Other SVMs that meet the criteria will be added to the group at their next startup. В
Adding specified VMware management objects to the NSX Security Group.
You can select the objects to be added to the group, e.g. the Datacenter object, the VMware cluster, a resource pool, оr specific VMs. By default, all child objects of the specified VMware management object are added to the group, including the VMs which are switched off at the moment. You can also specify theVMware management objects, which should not be added to the NSX Security Group.

You can combine these options when configuring the rules of adding SVMs to the NSX Security Group. For example, you can select adding the VMs to the group according to specified parameters dynamically and also specify the VMware management objects to be excluded from the group.
To configure a NSX security group:

Select Networking & Security.
Click Service Composer and select the Security Groups tab.
Click the Add icon. The wizard will be launched.

ksv4nola_13172_18

Enter the name for the new NSX Security Group, e.g. “Kaspersky Security Group” or “Protected by Kaspersky”.
Click Next.

ksv4nola_13172_19

If you want to set up adding VMs to the group dynamically, proceed to the Define dynamic membership step of the wizard.
1. Click the plus icon and then click Add in the Membership criteria 1 entry form.
2. Adjust the criteria for adding the VMs to the group. For example, to add all VMs which meet the Kaspersky Security hardware requirements, use the parameter Computer OS Name – Contains – Windows.

ksv4nola_13172_20

If you want to specify the VMware management objects to be added to the NSX Security Group, proceed to the Select objects to include step.
Select the object type in the Object Type field and move all VMware management objects you need to the Selected Objects list.

ksv4nola_13172_21

If you want to specify the VMware management objects to be excluded from the NSX Security Group, proceed to the Select objects to exclude step.
Select the object type in the Object Type field and move all VMware management objects you want to exclude to the Selected Objects list.

ksv4nola_13172_22

To check the specified parameters, proceed to the Ready to complete step.
Click Finish.

ksv4nola_13172_23

The wizard will close. On the Security Groups tab, you ca view the number of VMs which will be added to the group in the Virtual Machines section.

ksv4nola_13172_24

You can view the list of VMs added to the group. To do it, click the number in the Virtual Machines section.

ksv4nola_13172_25

If you selected adding the VMs to the group dynamically, the machines which are not running at the moment are not shown in the group. They will be added to the group the next time they are launched.

In the VMware vSphere Web Client console, select Hosts and Clusters and make sure the VMs you want to protect are in the group. For each virtual machine which meets the requirements of the group, in the Security Group Membership section of the Summary tab, the name of the NSX Security Group is specified.

ksv4nola_13172_26

6. Configure NSX security policies

To protect the VMs in the NSX Security Group, configure the NSX Security Policy and apply it to the NSX Security Group.

To configure the NSX Security Policy and apply it to the NSX Security Group:

Select Networking & Security.
Click Service Composer and select the Security Policies tab.
Click the policy creation icon. The policy creation wizard will open.
Enter the policy name and click Next.

ksv4nola_13172_27

If you want to use File Anti-Virus, at the next step of the wizard click the plus icon. The Add Guest Introspection Service window opens.
Type the name into the Name field and in the Service Name drop-down list select the Kaspersky File Antimalware Protection service. Click OK.

ksv4nola_13172_28

The wizard window shows the information about the Kaspersky File Antimalware Protection service. In the Action section, the action set for the service can be viewed.

ksv4nola_13172_29

If you want to use Network Attack Blocker, proceed to the Network Introspection Services tab.
If you want to check the outbound traffic of VMs:
1. Click the plus icon. The Add Network Introspection Service window opens.
2. Type the name into the Name field and in the Service Name drop-down list select the Kaspersky Network Protection service.
3. Enter the value for the Source field. Click the corresponding Change link located on the right. Select Policy's Security Groups and click OK.
4. Enter the value for the Destination field. Click the corresponding Change link located on the right. Select Any and click OK.
5. Click in the Add Network Introspection Service window.
If you want to check the inbound traffic of VMs:
1. Open the Add Network Introspection Service by clicking the plus icon.
2. Type the name into the Name field and in the Service Name drop-down list select the Kaspersky Network Protection service.
3. Enter the value for the Source field. Click the corresponding Change link located on the right. Select Any and click OK.
4. Enter the value for the Destination field. In the Add Network Introspection Service window, click the Change link located on the right from the Destination field. Select Policy's Security Groups and click OK.
5. Click in the Add Network Introspection Service window.

the wizard window shows the information about the Kaspersky Network Protection service. In the Action section, you can view the action set for the sevice. In the Source and Destination sections, the values set for outbound and inbound traffic scan are available.

ksv4nola_13172_35

Exit the wizard.
On the Security Policies tab, select the policy you have created and open the expandable list of Actions. Select Apply Policy. The window of applying the NSX Security Policy to the NSX Security Group opens.

ksv4nola_13172_36

Select the NSX Security Group with the SVMs and click OK.
The window closes. On the Security Policies tab, the Successful status will appear for the created policy in the Sync Status section.

ksv4nola_13172_37

The NSX Security Policy is now applied to the NSX Security Group.

7. Register the services on NSX

Publishing the installer to the web server

Installers of Kaspersky Security for Virtualization 4.0 Agentless must be available to the NSX Manager through HTTP(s). You can use the built-in web server of Kaspersky Security Center:

On a computer with Kaspersky Security Center installed, open the path C:\Program Files (x86)\Kaspersky Lab\Kaspersky Security Center\Share and create the folder named public.
Copy the installation files of Kaspersky Security for Virtualization 4.0 Agentless to this folder.

ksv4nola_13172_38

Installing Kaspersky Security Center components

Kaspersky Security Center components include the administration plug-in and the Integration Server required for interaction with vCenter and NSX. To install the components:

Run the file SecurityCenterComponents_x.x.x.x_setup.exe.
Select the language and click Next.
Read the License Agreement carefully and accept it if you agree to all its terms. Click Next.
View the Intergration Server parameters. Check if port 7271 is open. Click Next.
Click Finish.

Register the services of Kaspersky Security for Virtualization 4.0 Agentless

Open Kaspersky Security Center.
Click Next in the configuration wizard.
Click Finish when the update task is created.
Click Start the Integration Server Management Console in the main window.
Click Consider certificate to be trusted.
In the Virtual infrastructure protection, click Add.
Specify the connection settings to vCenter Server.
Click Certificate verification.
Click Consider as trusted.
In the Manage protection section, select Register Kaspersky Security services.
Specify the connection settings to NSX Manager.
Click Consider as trusted.
Go to http://x.x.x.x:8060/public/ksv, where “x.x.x.x” stands for the address of the computer with Kaspersky Security Center installed.
Copy the link to the OVF file.
Paste the link into the field and verify it.
Click Next.
In the next view, leave the settings as they are and click Next.
At the next step, you can configure tthe connection settings of the SVM to Kaspersky Security Center, NSX Manager to the Integration Server, and the SVM to the Integration Server.
Click Next.
Create a new password for klconfig and root. Click Next.
Check the settings and click Next.
When the process is completed, click Next and close the Integration Server management console.

Checking the services of Kaspersky Security for Virtualization 4.0 Agentless

Open the main menu and select Networking & Security.

ksv4nola_13172_54

Go to Service Definitions.
Make sure the Kaspersky Security for Virtualization service is registered on NSX Manager.

ksv4nola_13172_55

Go to the Service Managers tab.
Select Kaspersky Service Manager and the edit icon.

ksv4nola_13172_56

Pay attention to the Base API URL field. The field contains the Integration Server address, which is required for correct work of Kaspersky Security for Virtualization 4.0 Agentless.

ksv4nola_13172_57

Click Cancel.

8. Deploy the SVM with the File Anti-Virus component

The SVM with the File Anti-Virus component is deployed on VMware ESXi hypervisors when you deploy the Kaspersky File Antimalware Protection service on the VMware clusters. Deployment is performed via VMware vSphere Web Client:

To deploy the SVM with the File Anti-Virus component:

Select Networking & Security.
Select Installation and click the Service Deployments tab.
Click the plus icon to launch the wizard. The window Deploy Network & Security Services appears. The list shows the Kaspersky File Antimalware Protection service.
At the first step of the wizard, select the Kaspersky File Antimalware Protection service in the table and click Next.

ksv4nola_13172_58

Select one or several VMware clusters to which File Anti-Virus will be installed, and click Next.

ksv4nola_13172_59

At the next step of the wizard, you can change the default network parameters, select the storage for SVMs to be deployed on the hypervisors in the selected cluster.

ksv4nola_13172_60

Select the network to be used by SVMs and the storage for deploying the SVM with the File Anti-Virus component.
If you want to change the parameters of assigning IP addresses for SVMs, click the Change link in the IP assignment section. The Select IP Assignment mode window opens.
Select Use IP Pool and click the plus icon.

The Add Static IP Pool window opens.
Configure the pool of static addresses in the Add Static IP Pool window and click ОK.

The new pool appears in the list of pools.
Click the pool you have added and click OK. The name of the selected pool will appear in the Deploy Network & Security Services window.
Click Next.

Make sure all parameters are correct and click Finish.

ksv4nola_13172_65

The wizard window closes. The current status of Kaspersky File Antimalware Protection service deployment process is shown in the Installation Status section of the VMware vSphere Web Client console.

ksv4nola_13172_66

Wait until Kaspersky File Antimalware Protection is successfully deployed.

ksv4nola_13172_67

In the VMware vSphere Web Client console, select Hosts and Clusters and make sure SVMs have been deployed successfully on each hypervisor in the cluster.

ksv4nola_13172_68

9. Deploy an SVM with the Network Attack Blocker component

The SVMs with the Network Attack Blocker component are deployed on VMware ESXi hypervisors through deployment of the Kaspersky Network Protection service on VMware clusters. Deployment is performed via VMware vSphere Web Client:

Deploy an SVM with the Network Attack Blocker component:

Select Networking & Security.
Select Installation and click the Service Deployments tab.
Click the plus icon to launch the wizard. The window Deploy Network & Security Services appears. The list shows the Kaspersky Network Protection service.
At the first step of the wizard, select the Kaspersky Network Protection service in the table and click Next.

ksv4nola_13172_69

Select one or several VMware clusters on which you would like to install Kaspersky Network Protection and then click Next.

ksv4nola_13172_70

At the next step of the wizard, you can change the default network parameters, select the storage for SVMs to be deployed on the hypervisors in the selected cluster.

ksv4nola_13172_71

Select the network to be used by SVMs and the storage for deploying the SVM with the Network Attack Blocker component.
If you want to change the parameters of assigning IP addresses for SVMs, click the Change link in the IP assignment section. The Select IP Assignment mode window opens.
Select Use IP Pool and click the plus icon. The Add Static IP Pool window opens.
Configure the pool of static addresses in the Add Static IP Pool window and click OK.

The new pool appears in the list of pools.
Click the pool you have added and click OK. The name of the selected pool will appear in the Deploy Network & Security Services window.
Click Next.

Make sure all parameters are set correctly and click Finish.

ksv4nola_13172_76

The wizard window closes. The current status of Kaspersky Network Protection service deployment process is shown in the Installation Status section of the VMware vSphere Web Client console.

ksv4nola_13172_77

Wait until Kaspersky Network Protection is successfully deployed.

ksv4nola_13172_78

In the VMware vSphere Web Client console, select Hosts and Clusters and make sure SVMs have been deployed successfully on each hypervisor in the cluster.

ksv4nola_13172_79

Was this information helpful?

Yes No

Back to "Installation and Removal"

Kaspersky Security for Virtualization 4.0 Agentless

Hardware requirements for version 4.1.0.47 (SP1)

Software requirements for version 4.1.0.47 (SP1)

For Kaspersky Security to operate in a corporate LAN, one of the following versions of Kaspersky Security Center must be installed:

Kaspersky Security Center 10 Service Pack 2 Maintenance Release 1
Kaspersky Security Center 10 Service Pack 2

The full functionality of Kaspersky Security for Virtualization 4.0 Agentless is available only when using Kaspersky Security Center 10 Service Pack 2 Maintenance Release 1.

The following Kaspersky Security Center components must be installed in order to run the program:

Administration Server
Administration Console
Administration Agent This component is included in the Kaspersky Security SVM images.

For more detailed information about installing Kaspersky Security Center, see the Kaspersky Security Center documentation.

The operating system on the computer on which Kaspersky Security Center is installed must meet the requirements of the Integration Server component.

Software requirements of the Integration Server component

The computer must have one of the following operating systems to support installation and operation of the Integration Server component:

Windows Server 2016 (64-bit).
Windows Server 2012 R2 Datacenter / Standard (64-bit)
Windows Server 2012 R2 Essentials (64-bit)
Windows Server 2012 Datacenter / Standard (64-bit)
Windows Server 2012 Essentials (64-bit)
Windows Server 2008 R2 Datacenter / Enterprise / Standard Service Pack 1 (64-bit)
Windows Server 2008 Datacenter / Enterprise / Standard Service Pack 2 (32- or 64-bit)

Microsoft .NET Framework 4.6 is required for the installation of the Integration Server, Integration Server Management Console, and Kaspersky Security administration plug-in. This platform must be installed before installation of the Integration Server, Integration Server Management Console, and Kaspersky Security administration plug-in. You can download the Microsoft .Net Framework from the Microsoft website (https://www.microsoft.com/net/download/framework).

Software requirements of the File Anti-Virus component in a virtual infrastructure managed by a VMware vCenter server and VMware NSX Manager version 6.4.0

If you are using VMware NSX for vSphere version 6.4.0, the virtual infrastructure must meet the following software requirements in order for the File Anti-Virus component to function properly:

VMware ESXi 6.5a hypervisor or VMware ESXi 6.0 hypervisor Update 3
One of the following versions of VMware Tools:
- 10.0.12 (build 4448496) if Windows XP or Windows Server 2003 is installed on the virtual machine.
- 10.1.0 (build 4449150) or 10.1.5 (build 5055683) if a different supported Windows operating system is installed on the virtual machine.

When you install the VMware Tools suite, the VMware Devices Drivers / VMCI Driver / NSX File Introspection Driver component must be installed. When you install the VMware Tools suite with default settings, the VMware Devices Drivers / VMCI Driver / NSX File Introspection Driver component will not be installed.

For information about updating VMware Tools, see the VMware product documentation.

VMware vCenter Server 6.5a or VMware vCenter Server 6.0 Update 3
VMware NSX for vSphere 6.4.0
For the protection of virtual machines running a Linux operating system: VMware Linux Thin Agent driver (vmware-nsx-gi-file-1.0.0.4888131)

For more detailed information about installing the VMware Linux Thin Agent driver, see the VMware NSX for vSphere 6.3 documentation.

In a virtual infrastructure managed by a VMware vCenter server and VMware NSX Manager version 6.4.0, the File Anti-Virus component protects virtual machines that have the following guest operating systems installed:

Desktop operating systems:
- Windows 10 (32 / 64-bit)
- Windows 8.1 (32 / 64-bit)
- Windows 8 (32 / 64-bit)
- Windows 7 Service Pack 1 (32 / 64-bit)
Server operating systems:
- Windows Server 2016 (only with NSX 6.3.3 - 6.3.5 and VMware tools 10.1.10 and later).
- Windows Server 2012 R2 without ReFS (Resilient File System) support (64-bit)
- Windows Server 2012 without ReFS (Resilient File System) support (64-bit)
- Windows Server 2008 R2 Service Pack 1 (64-bit)
- Windows Server 2003 R2 Service Pack 2 (32 / 64-bit)
Linux server operating systems:
- Ubuntu Server 14.04 LTS (64-bit)
- Red Hat Enterprise Linux Server 7 (64-bit)
- SUSE Linux Enterpise Server 12 (64-bit)

On protected virtual machines running Linux operating systems, one of the following file systems must be used:

Local file systems: ext2, ext3, ext4, xfs, btrfs, vfat, iso9660
Network file systems: nfs, nfs4, cifs

Software requirements of the File Anti-Virus component in a virtual infrastructure managed by a VMware vCenter server and VMware NSX Manager version 6.3.1 - 6.3.5

If you are using VMware NSX for vSphere version 6.3.1 - 6.3.5, the virtual infrastructure must meet the following software requirements in order for the File Anti-Virus component to function properly:

VMware ESXi 6.5a Hypervisor, VMware ESXi 6.0 Hypervisor Update 3 or VMware ESXi 5.5 Hypervisor Update 3b.
One of the following versions of VMware Tools:
- 10.0.12 (build 4448496) if Windows XP or Windows Server 2003 is installed on the virtual machine.
- 10.1.0 (build 4449150) or 10.1.5 (build 5055683) if a different supported Windows operating system is installed on the virtual machine.

For information about updating VMware Tools, see the VMware product documentation.

VMware vCenter Server 6.5a, VMware vCenter Server 6.0 Update 3, VMware vCenter Server 5.5 Update 3b, VMware vCenter Server 5.5 Update 3e
VMware NSX for vSphere 6.3.1 - 6.3.5
For the protection of virtual machines running a Linux operating system: VMware Linux Thin Agent driver (vmware-nsx-gi-file-1.0.0.4888131)

For more detailed information about installing the VMware Linux Thin Agent driver, see the VMware NSX for vSphere 6.3 documentation.

In a virtual infrastructure managed by a VMware vCenter server and VMware NSX Manager version 6.3.1 - 6.3.5, the File Anti-Virus component protects virtual machines that have the following guest operating systems installed:

Desktop operating systems:
- Windows 10 (32 / 64-bit)
- Windows 8.1 (32 / 64-bit)
- Windows 8 (32 / 64-bit)
- Windows 7 Service Pack 1 (32 / 64-bit)
Server operating systems:
- Windows Server 2016 (only with NSX 6.3.3 - 6.3.5 and VMware tools 10.1.10 and later).
- Windows Server 2012 R2 without ReFS (Resilient File System) support (64-bit)
- Windows Server 2012 without ReFS (Resilient File System) support (64-bit)
- Windows Server 2008 R2 Service Pack 1 (64-bit)
- Windows Server 2003 R2 Service Pack 2 (32 / 64-bit)
Linux server operating systems:
- Ubuntu Server 14.04 LTS (64-bit)
- Red Hat Enterprise Linux Server 7 (64-bit)
- SUSE Linux Enterpise Server 12 (64-bit)

On protected virtual machines running Linux operating systems, one of the following file systems must be used:

Local file systems: ext2, ext3, ext4, xfs, btrfs, vfat, iso9660
Network file systems: nfs, nfs4, cifs

Software requirements of the File Anti-Virus component in a virtual infrastructure managed by a VMware vCenter server and VMware NSX Manager version 6.2.6

If you are using VMware NSX for vSphere version 6.2.6, the virtual infrastructure must meet the following software requirements in order for the File Anti-Virus component to function properly:

VMware ESXi 6.0 hypervisor Update 3 or VMware ESXi 5.5 hypervisor Update 3b.
One of the following versions of VMware Tools:
- 10.0.12 (build 4448496) if Windows XP or Windows Server 2003 is installed on the virtual machine.
- 10.1.0 (build 4449150) or 10.1.5 (build 5055683) if a different supported Windows operating system is installed on the virtual machine.

For information about updating VMware Tools, see the VMware product documentation.

VMware vCenter Server 6.0 Update 3 or VMware vCenter Server 5.5 Update 3e
VMware NSX for vSphere 6.2.6

In a virtual infrastructure managed by a VMware vCenter server and VMware NSX Manager version 6.2.6, the File Anti-Virus component protects virtual machines that have the following guest operating systems:

Desktop operating systems:
- Windows 10 (32 / 64-bit)
- Windows 8.1 (32 / 64-bit)
- Windows 8 (32 / 64-bit)
- Windows 7 Service Pack 1 (32 / 64-bit)
Server operating systems:
- Windows Server 2012 R2 without ReFS (Resilient File System) support (64-bit)
- Windows Server 2012 without ReFS (Resilient File System) support (64-bit)
- Windows Server 2008 R2 Service Pack 1 (64-bit)
- Windows Server 2003 R2 Service Pack 2 (32 / 64-bit)

Software requirements for the File Anti-Virus component in a virtual infrastructure managed by a VMware vCenter server and VMware vShield Manager

Technical support for customers using an infrastructure managed by a VMware vCenter server and VMware vShield Manager is only provided as part of the Kaspersky Premium Support plan (Kaspersky Maintenance Service Agreement, Enterprise / Business / Plus). Technical support for customers using an infrastructure managed by a VMware vCenter server and VMware NSX Manager is included in the standard support service.

For the File Anti-Virus component to function properly, a virtual infrastructure managed by a VMware vCenter server and VMware vShield Manager must meet the following software requirements:

VMware ESXi 6.0 hypervisor Update 2 or VMware ESXi 5.5 hypervisor Update 3b.
One of the following versions of VMware Tools:
- 10.0.12 (build 4448496) if Windows XP or Windows Server 2003 is installed on the virtual machine.
- 10.1.0 (build 4449150) or 10.1.5 (build 5055683) if a different supported Windows operating system is installed on the virtual machine.

For information about updating VMware Tools, see the VMware product documentation.

VMware vCenter Server 6.0 Update 2 or VMware vCenter Server 5.5 Update 3e
VMware vShield Endpoint from the VMware vCloud Networking and Security 5.5.4.3 suite.
VMware vShield Manager from the VMware vCloud Networking and Security 5.5.4.3 suite.

In a virtual infrastructure managed by a VMware vCenter server and VMware vShield Manager, the File Anti-Virus component protects virtual machines that have the following guest operating systems:

Desktop operating systems:
- Windows 10 (32 / 64-bit)
- Windows 8.1 (32 / 64-bit)
- Windows 8 (32 / 64-bit)
- Windows 7 (32 / 64-bit)
- Windows XP SP3 or later (32-bit)
Server operating systems:
- Windows Server 2016 (only with NSX 6.3.3 - 6.3.5 and VMware tools 10.1.10 and later)
- Windows Server 2012 R2 without ReFS (Resilient File System) support (64-bit)
- Windows Server 2012 without ReFS (Resilient File System) support (64-bit)
- Windows Server 2008 R2 Service Pack 1 (64-bit)
- Windows Server 2003 R2 Service Pack 2 (32 / 64-bit)

Software requirements of the Network Threat Detection component

For the Network Threat Detection component to work properly, the VMware virtual infrastructure must meet the following software requirements:

Option 1:
- VMware ESXi 6.5a Hypervisor, VMware ESXi 6.0 Hypervisor Update 3 or VMware ESXi 5.5 Hypervisor Update 3b
- VMware vCenter Server 6.5a, VMware vCenter Server 6.0 Update 3 or VMware vCenter Server 5.5 Update 3e
- VMware NSX for vSphere 6.3.1 - 6.4.0

The guest operating system system requirements of the protected virtual machine are identical to the guest operating system requirements imposed by File Anti-Virus in a virtual infrastructure managed by a VMware vCenter server and VMware NSX Manager version 6.3.1 - 6.3.5.

Option 2:
- VMware ESXi 6.0 hypervisor Update 3 or VMware ESXi 5.5 hypervisor Update 3b
- VMware vCenter Server 6.0 Update 3 or VMware vCenter Server 5.5 Update 3e
- VMware NSX for vSphere 6.2.6

A current license for NSX for vSphere Advanced or NSX for vSphere Enterprise is required in order for the Network Threat Detection component to work.

The Network Threat Detection component protects virtual machines that use the E1000 or VMXNET3 network adapter.

Hardware requirements for version 4.0.0.84

Software requirements for version 4.0.0.84

For Kaspersky Security to operate in a corporate LAN, one of the following versions of Kaspersky Security Center must be installed:

Kaspersky Security Center 10 Service Pack 2
Kaspersky Security Center 10 Service Pack 2 Maintenance Release 1

The full functionality of Kaspersky Security for Virtualization 4.0 Agentless is available only when using Kaspersky Security Center 10 Service Pack 2 Maintenance Release 1.

The operating system on the computer on which Kaspersky Security Center is installed must meet the requirements of the Integration Server component.

Software requirements of the Integration Server component

The computer must have one of the following operating systems to support installation and operation of the Integration Server component:

Windows Server 2016 Datacenter / Standard (in full installation or Server Core mode) (64-bit)
Windows Server 2012 R2 Datacenter / Standard (in full installation or Server Core mode) (64-bit)
Windows Server 2012 R2 Essentials (in full installation mode) (64-bit)
Windows Server 2012 Datacenter / Standard (in full installation or Server Core mode) (64-bit)
Windows Server 2012 Essentials (in full installation mode) (64-bit)
Windows Server 2008 R2 Datacenter / Enterprise / Standard Service Pack 1 (in full installation mode) (64-bit)
Windows Server 2008 Datacenter / Enterprise / Standard Service Pack 2 (in full installation mode) (32 / 64-bit)

Software requirements of the File Anti-Virus component in a virtual infrastructure managed by a VMware vCenter server and VMware NSX Manager

For the File Anti-Virus component to work properly, the VMware virtual infrastructure must meet the following software requirements:

VMware ESXi 6.0 hypervisor Update 2 or VMware ESXi 5.5 hypervisor Update 3b.
One of the following versions of VMware Tools:
10.0.12 (build 4448496) if Windows XP or Windows Server 2003 is installed on the virtual machine.
10.1.0 (build 4449150) if a different supported operating system is installed on the virtual machine.

For information about updating VMware Tools, see the VMware product documentation.

VMware vCenter Server 6.0 Update 2 or VMware vCenter Server 5.5 Update 3e
VMware NSX for vSphere 6.2.4.

In a virtual infrastructure managed by a VMware vCenter server and VMware NSX Manager, the File Anti-Virus component protects virtual machines that have the following guest operating systems:

Desktop operating systems:
- Windows 10 (32 / 64-bit)
- Windows 8.1 (32 / 64-bit)
- Windows 8 (32 / 64-bit)
- Windows 7 Service Pack 1 (32 / 64-bit)
Server operating systems:
- Windows Server 2012 R2 without ReFS (Resilient File System) support (64-bit)
- Windows Server 2012 without ReFS (Resilient File System) support (64-bit)
- Windows Server 2008 R2 Service Pack 1 (64-bit)
- Windows Server 2003 R2 Service Pack 2 (32 / 64-bit)

Software requirements for the File Anti-Virus component in a virtual infrastructure managed by a VMware vCenter server and VMware vShield Manager

For the File Anti-Virus component to function properly, a virtual infrastructure managed by a VMware vCenter server and VMware vShield Manager must meet the following software requirements:

VMware ESXi 6.0 hypervisor Update 2 or VMware ESXi 5.5 hypervisor Update 3b.
One of the following versions of VMware Tools:
10.0.12 (build 4448496) if Windows XP or Windows Server 2003 is installed on the virtual machine.
10.1.0 (build 4449150) if a different supported operating system is installed on the virtual machine.

When you install the VMware Tools suite, the VMware Devices Drivers / VMCI Driver / vShield Drivers component must be installed. When you install the VMware Tools suite with default settings, the VMware Devices Drivers / VMCI Driver / vShield Drivers component will not be installed.

For information about updating VMware Tools, see the VMware product documentation.

VMware vCenter Server 6.0 Update 2 or VMware vCenter Server 5.5 Update 3e
VMware vShield Endpoint from the VMware vCloud Networking and Security 5.5.4.3 suite.
VMware vShield Manager from the VMware vCloud Networking and Security 5.5.4.3 suite.

In a virtual infrastructure managed by a VMware vCenter server and VMware vShield Manager, the File Anti-Virus component protects virtual machines that have the following guest operating systems:

Desktop operating systems:
- Windows 10 (32 / 64-bit)
- Windows 8.1 (32 / 64-bit)
- Windows 8 (32 / 64-bit)
- Windows 7 (32 / 64-bit)
- Windows XP SP3 or later (32-bit)
Server operating systems:
- Windows Server 2012 R2 without ReFS (Resilient File System) support (64-bit)
- Windows Server 2012 without ReFS (Resilient File System) support (64-bit)
- Windows Server 2008 R2 (64-bit)
- Windows Server 2003 R2 (32- or 64-bit)

Software requirements of the Network Threat Detection component

For the Network Threat Detection component to work properly, the VMware virtual infrastructure must meet the following software requirements:

VMware ESXi 6.0 hypervisor Update 2 or VMware ESXi 5.5 hypervisor Update 3b.
VMware vCenter Server 6.0 Update 2 or VMware vCenter Server 5.5 Update 3e.
VMware NSX for vSphere 6.2.4.

A current license for NSX for vSphere Advanced or NSX for vSphere Enterprise is required in order for the Network Threat Detection component to work.

The requirements of the Network Threat Detection component for the guest operating system of the protected virtual machine are identical to the guest operating system requirements imposed by File Anti-Virus in a virtual infrastructure managed by a VMware vCenter server and VMware NSX Manager.

The Network Threat Detection component protects virtual machines that use the E1000 or VMXNET3 network adapter.

Database Update	Yes
Support	Yes
Error fix	No

Kaspersky Security for Virtualization 4.0 Agentless

How to install Kaspersky Security for Virtualization 4.0 Agentless on NSX

1. Prepare VMware ESXi hypervisors for Network Attack Blocker deployment.

2. Deploy Guest Introspection

3. Read the license information for NSX for vSphere

4. View the list of registered services

5. Configure NSX security groups

6. Configure NSX security policies

7. Register the services on NSX

Publishing the installer to the web server

Installing Kaspersky Security Center components

Register the services of Kaspersky Security for Virtualization 4.0 Agentless

Checking the services of Kaspersky Security for Virtualization 4.0 Agentless

8. Deploy the SVM with the File Anti-Virus component

9. Deploy an SVM with the Network Attack Blocker component

Kaspersky Security for Virtualization 4.0 Agentless

Status: Limited Support

Database Update

Support

Error fix

Documentation

License agreement

Download

Additional Downloads

Download version 4.0.0.84 with vShield support

Kaspersky Security for Virtualization 4.0 Agentless

Hardware requirements for version 4.1.0.47 (SP1)

Software requirements for version 4.1.0.47 (SP1)

Software requirements of the Integration Server component

Software requirements of the File Anti-Virus component in a virtual infrastructure managed by a VMware vCenter server and VMware NSX Manager version 6.4.0

Software requirements of the File Anti-Virus component in a virtual infrastructure managed by a VMware vCenter server and VMware NSX Manager version 6.3.1 - 6.3.5

Software requirements of the File Anti-Virus component in a virtual infrastructure managed by a VMware vCenter server and VMware NSX Manager version 6.2.6

Software requirements for the File Anti-Virus component in a virtual infrastructure managed by a VMware vCenter server and VMware vShield Manager

Software requirements of the Network Threat Detection component

Hardware requirements for version 4.0.0.84

Software requirements for version 4.0.0.84

Software requirements of the Integration Server component

Software requirements of the File Anti-Virus component in a virtual infrastructure managed by a VMware vCenter server and VMware NSX Manager

Software requirements for the File Anti-Virus component in a virtual infrastructure managed by a VMware vCenter server and VMware vShield Manager

Software requirements of the Network Threat Detection component

Have you found what you were looking for?

Thank you!

How can we improve this article?

Thank you for your feedback!