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.3.1
If you are using VMware NSX for vSphere version 6.3.1, 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.
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, VMware vCenter Server 6.0 Update 3 or VMware vCenter Server 5.5 Update 3e.
- VMware NSX for vSphere 6.3.1
- 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, the File Anti-Viruscomponent 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 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 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.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 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.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 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
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.
- 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
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.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.