After
installing Kaspersky Security for Virtualization 1.1, you should configure the secure virtual machine (SVM) settings in a policy.
You should install Kaspersky Security 1.1 for Virtualization
control plugin on the adminitrator's workstation to be able to control the application via a policy.
How to create a policy:
- Start the Administration console.
- Go to the Managed computers node and select the KSC cluster to create the policy for.
- Open the Computers tab in the right frame to view the list of SVMs in the cluster.
- Go to the Policies tab and click Create a policy to start the new policy wizard.
- Enter the new policy name and click Next.
- Select Kaspersky Security For Virtualization 1.1 and click Next.
- The next step allows configuring the root protection profile. Once the policy is created, the root protection certificate is assigned to all the virtual machines within KSC cluster.
- Enable the option Enable protection in the Root protection profile settings.
- Click Edit to modify the default antivirus protection settings.
- Configure the protection profile. Read more.
- Click Next in the Root protection profile settings.
- Indicate packed files scan settings.
- Packed files that may cause harm. When this option is enabled, the application scans archived objects and extractors within self-extracting archives.
- Multi-packed files. When this option is enabled, the application scans multi-packed objects (three times using the same or different archivers).
- Click Next.
- Select the policy mode:
- Active policy. The policy applies once created. Only one policy can be active for a particular administration group.
- Inactive policy. The policy is not applied once created.
- Click Finish to create the policy.
Once there is an active policy, Kaspersky Security Center 9.0 distributes it to secure virtual machines.
Applying the settings according to the root protection profile, Kaspersky Security for Virtualization 1.1 will start protecting the virtual machines on ESXi hypervisors within a KSC cluster.
All the previously created policies cease to function after reinstalling or changing the vCenter server. You should delete the existing policies and create new ones.
