Creating a Light Agent for Windows policy

To create a Light Agent for Windows policy:

  1. Open Kaspersky Security Center Administration Console.
  2. In the Managed devices folder of the console tree, select the folder with the name of the administration group for whose protected virtual machines you want to create a policy.

    On the Devices tab of the folder with the name of the administration group, you can view a list of protected virtual machines that belong to this administration group.

  3. In the workspace, select the Policies tab.
  4. Start the New Policy Wizard in one of the following ways:
    • Click the Create a policy button.
    • Right-click to open the context menu in the list of policies and select Create / Policy.
  5. At the first step of the Wizard, select Kaspersky Security for Virtualization 5.0 Light Agent for Windows from the list.

    Go to the next step in the wizard.

  6. Enter a name for the new policy.
  7. If you want to migrate the settings from a Light Agent for Windows policy of a previous version of Kaspersky Security into the policy being created, select the Use settings from policy for previous application version check box.

    Go to the next step in the wizard.

  8. At the next step, you can import Light Agent for Windows settings previously saved on a protected virtual machine into the policy you are creating. Settings are imported using a configuration file in CFG format that you can create in the local interface of Light Agent.

    To import settings, click the Select button and, in the Please select a configuration file window that opens, select a file with the .cfg extension. The path to the configuration file is shown in the Configuration file field.

    You can use a configuration file only from the Kaspersky Security for Virtualization 5.0 Light Agent application version.

    You can edit these settings imported from the configuration file at subsequent steps of the Policy Wizard.

    Go to the next step in the wizard.

  9. Configure the virtual machine control settings. The Wizard window shows a list of control components.

    If you are using Kaspersky Security Center 10 Service Pack 2 Maintenance Release 1, by default the settings of control components cannot be configured in the New Policy Wizard. You need to first enable the display of control settings in the settings of the Kaspersky Security Center Administration Console interface.

    You can perform the following actions:

    • Enable or disable the control component by using the check box to the left of the component name in the list. By default, the Application Startup Control and Integrity Monitoring components are disabled.
    • Configure the settings of each control component. To do so, select the control component in the list and click the Edit button located above the list of control components. In the opened window, configure the settings of the selected component and click OK.
    • Block or allow editing of the settings of each control component through the local interface of Light Agent for Windows. By default, editing of all control settings through the local interface is blocked.

      If you want to allow editing of control component settings through the local interface, select this component in the list and click the Open button located above the list of components, or click the lock icon to the left of the component name.

      If the editing of component settings via the local interface is blocked, Kaspersky Security uses the policy-configured component operation settings on all protected virtual machines. If the editing of component settings via the local interface is allowed, Kaspersky Security uses local component settings instead of the policy-configured settings.

    Go to the next step in the wizard.

  10. Configure the virtual machine protection settings. The Wizard window shows a list of protection components.

    You can perform the following actions:

    • Enable or disable automatic startup of the application on a virtual machine and configure the general anti-virus protection settings. To do so, select General Protection settings in the list and click the Edit button located above the list of protection components. In the opened window, configure the settings and click OK.
    • Enable or disable the protection component by using the check box to the left of the component name in the list. All protection components are enabled by default.
    • Configure the settings of each protection component. To do so, select the protection component in the list and click the Edit button located above the list of protection components. In the opened window, configure the settings of the selected component and click OK.
    • Block or allow the editing of settings of each protection component via the local interface of Light Agent for Windows. By default, editing of all protection settings through the local interface is blocked.

      If you want to allow editing of protection component settings through the local interface, select this component in the list and click the Open button located above the list of components, or click the lock icon to the left of the component name.

      If the editing of component settings via the local interface is blocked, Kaspersky Security uses the policy-configured component operation settings on all protected virtual machines. If editing of component settings through the local interface is allowed, Kaspersky Security uses the local component settings instead of the settings configured in the policy.

    Go to the next step in the wizard.

  11. Configure SVM discovery settings for Light Agents:
    • If you want to use the Integration Server, check the address and port used for connecting SVMs to the Integration Server. The fields show the default port (7271) and the domain name of the computer on which the Kaspersky Security Center Administration Console is installed. You can change the port and specify the IP address in IPv4 format or the fully qualified domain name (FQDN) of the Integration Server.

      If the computer hosting the Kaspersky Security Center Administration Console does not belong to a domain or your account does not belong to the KLAdmins group or to the group of local administrators, when proceeding to the next step of the wizard specify the administrator password of the Integration Server (password of the admin account) in the opened window.

      The New Policy Wizard checks the SSL certificate received from the Integration Server. If the certificate contains an error or is not trusted, the Integration Server certificate verification window opens. You can click the button in the window to view the details of the received certificate. To continue connecting to the Integration Server, click the Ignore button. The received certificate will be installed as a trusted certificate on the computer where the Kaspersky Security Center Administration Console is installed.

    • If you want to use a list of SVM addresses, use the Add button to enter one or several addresses.

    Go to the next step in the wizard.

  12. If necessary, edit the scan exclusions and protection exclusions that were configured by default. The Exclusions list contains the names of applications or names of application vendors that you can include in the trusted zone or exclude from it. The listed applications are used for administration and anti-virus protection of computer networks. To configure exclusions, do one of the following:
    • Select the check box to the left of the name of the application or vendor if you want to include the vendor’s application or applications in the trusted zone.

      If the check box is selected, files, folders, and processes recommended for these applications are included in the trusted zone, and the executable files of these applications are automatically added to the list of trusted applications.

    • Clear the check box to the left of the name of the application or vendor if you want to exclude the vendor’s application or applications from the trusted zone.

    The Citrix EdgeSight, Citrix Profile Manager, Citrix Provisioning Services, Citrix XenApp, and Citrix XenDesktop check boxes are selected by default to improve performance of these applications. The full list of recommended exclusions can be viewed on the Citrix website.

    Go to the next step in the wizard.

  13. If required, configure the settings for interaction between the local interface of Light Agent and the user, and the settings of notifications about events occurring during Light Agent operation.

    To ensure that Kaspersky Security can operate on a virtual machine that uses Windows Terminal Services technology or on a virtual machine with a Microsoft Windows desktop operating system employing Citrix XenApp technology, you must clear the Start the local interface of the application check box.

    If you use Light Agent on temporary virtual machines, you are advised to clear the Start the local interface of the application check box to improve virtual infrastructure performance.

    Go to the next step in the wizard.

  14. If required, configure the settings for protecting access to Light Agent functions and settings. To do this, perform the following actions:
    1. Select the Enable password protection check box.
    2. Specify the name and password of the user account that is allowed to access application settings in the local interface of Light Agent.
    3. Click the Settings button and, in the opened window, select the Light Agent operations that will be protected with a password.

    Go to the next step in the wizard.

  15. Exit the Policy Wizard.

The created policy will be displayed in the list of policies of the administration group on the Policies tab and in the Policies folder of the console tree.

The policy will be applied to protected virtual machines after the Kaspersky Security Center Administration Server relays the information to Kaspersky Security. Kaspersky Security starts protecting virtual machines on the hypervisor according to the policy settings.

If Network Agent is not running on a protected virtual machine, the created policy is not applied on this protected virtual machine.

If you chose the Inactive policy option during the previous step of the New Policy Wizard, the created policy is not applied on the protected virtual machines.

Page top