Kaspersky Security Center Cloud Console

Contents

[Topic 5022]

Kaspersky Security Center Cloud Console Help

What's new

Find out what's new in the latest application release.

Configuring network protection

Manage the security of an organization by configuring Kaspersky application policies and tasks in accordance with the organization's requirements.

Hardware and software requirements

Check which operating systems and application versions are supported.

The updating icon in the form of 2 arrows: green abd black.

Kaspersky applications: regular updating databases and software modules

Maintain the reliability of the protection system.

Значок лицензирования.

Licensing of Kaspersky Security Center Cloud Console

Learn details about Kaspersky Security Center Cloud Console working in trial mode and in the commercial mode.

The bell alarm icon.

Monitoring and reporting

View your infrastructure, protection statuses of networked devices, and statistics to manage the current protection state of your organization. You can also use reports.

Initial configuration

Start working with your workspace, configure Kaspersky Security Center Cloud Console according to your needs.

Vulnerability and patch management

Find and fix vulnerabilities in third-party software.

Migration to Kaspersky Security Center Cloud Console

Migrate your existing administration groups and related objects from Kaspersky Security Center on-premises to Kaspersky Security Center Cloud Console.

Exporting events to SIEM systems

Configure exporting events to SIEM systems using the Syslog protocol.

Discovering networked devices

Discover the existing and new devices on your organization's network.

Working in a cloud environment

Protect virtual machines in cloud environments: Amazon Web Services, Microsoft Azure, Google Cloud Platform.

Adjustment of distribution points and/or connection gateways

Configure distribution points.

Quick Start Guide for Managed Service Providers (MSPs)

Learn how to work with Kaspersky Security Center Cloud Console, if you are an administrator of MSP.

Kaspersky applications: centralized deployment

Deploy Kaspersky applications.

 

 

Page top

[Topic 200431]

What's new

Update April, 2025

This update of Kaspersky Security Center Cloud Console includes the following improvements:

  • Kaspersky Security Center Cloud Console now supports the following Kaspersky applications:
    • Kaspersky Embedded Systems Security 3.4 for Linux
    • Kaspersky Endpoint Security 12.2 for Linux
    • Kaspersky Endpoint Security 12.8 for Windows
  • Upload and run an application (or script) for diagnostics on a managed device. You can now upload either the folder or archive containing the executable file, or the executable file itself. After the application is successfully executed, you can download the execution results.
  • Information about the users currently logged in to the managed device is now displayed in the General Sessions section of the device properties window.
  • New language support: Kaspersky Security Center Cloud Console infrastructure is available in the Chinese Simplified language.
  • User experience improvements:

Update February, 2025

This update of Kaspersky Security Center Cloud Console improves performance when opening and navigating the Web Console.

Update October, 2024

This update of Kaspersky Security Center Cloud Console includes the following improvements:

  • We have improved the integration with Microsoft Entra ID. Now, when a user signs out of the Microsoft Entra ID account that was used for authentication in Kaspersky Security Center Cloud Console, the session also ends for Kaspersky Security Center Cloud Console and the user is automatically signed out of the console.
  • You can now view and download policy revisions. Kaspersky Security Center Cloud Console allows you to view a report in the HTML format or save the revision to a JSON file.
  • Kaspersky Security Center Cloud Console now displays the latest task status known to the Administration Server.
  • The Report on network attacks now includes the MAC address and port of the attacking machine.
  • You can now close the right panel by clicking any place outside the panel. If you make any changes to the panel and then try to close it by clicking outside the panel, a confirmation window appears.
  • The table header now stays pinned at the top when you scroll the table.

Update September, 2024

This update of Kaspersky Security Center Cloud Console includes the following improvements:

  • Kaspersky Endpoint Agent 4.0 is supported.
  • A number of old browser versions are no longer supported (Chrome earlier than version 128, Edge earlier than version 128, Firefox ESR earlier than version 115, Safari earlier than version 17.6).

Update April, 2024

This update of Kaspersky Security Center Cloud Console includes the following new features and improvements:

  • A new Cloud Discovery feature. This feature allows you to monitor the use of cloud services on managed devices running Windows and to block access to cloud services that you consider unwanted. Cloud Discovery tracks user attempts to gain access to these services through both browsers and desktop applications.
  • Integration with Microsoft Entra ID to allow the users in your organization to sign in to Kaspersky Security Center Cloud Console with their Microsoft Entra ID account credentials. Note, this feature is not available in the Russian Federation.
  • You can now create connection profiles for connecting Network Agent to Administration Server. The connection profiles allow out-of-office users of laptops to change the method of connecting to an Administration Server or to switch between Administration Servers, depending on the current location of the device on the enterprise network.
  • You can now open the list of your workspaces right from the main menu of the application.
  • Two new localization languages were added—Traditional Chinese and Simplified Chinese.
  • The default event storage setting in the task settings was changed from Save all events to Save only task execution results. This option reduces space consumption in the workspace database. The change affects only tasks created for Kaspersky Security Center. This setting remains without modification in the tasks for Kaspersky security applications.
  • Kaspersky Security Center Cloud Console now additionally notifies you about the planned deletion of your workspace, 7 and 30 days after the last license key is deleted from the workspace or expires. This will give you more time to purchase another license and add its license key to the workspace.
  • Kaspersky Business Hub and Kaspersky Security Center Cloud Console infrastructure now support the Kaspersky Next licenses. The application logo is changed automatically in accordance with the license that you use.
  • Kaspersky Security Center Cloud Console now supports the following Kaspersky applications:
    • Kaspersky Endpoint Security for Windows version 12.4
    • Kaspersky Endpoint Security 12.0 for Mac Patch A
  • When you migrate from one Kaspersky security application to another and the current application is password-protected, you can specify the uninstallation password right in the remote installation task properties.
  • You can now customize the main menu of the application by pinning or unpinning your favorite menu sections. The pinned sections are added to the Pinned area for quick access.
  • Optimized application interface and user experience when you select the On completing another task option while scheduling a task.
  • The report on hardware now can include information about macOS devices.
  • You can now select one or more client devices in the list of devices, and then launch a previously created task for them.

Update February, 2024

This update of Kaspersky Security Center Cloud Console includes the following new features and improvements:

Update January, 2024

Kaspersky Security Center Cloud Console now supports Kaspersky Endpoint Security 12.4 for Windows.

Update December, 2023

This update of Kaspersky Security Center Cloud Console includes the following new features and improvements:

  • You can now check the connection to a SIEM system.
  • Kaspersky Security Center Cloud Console now supports polling of a Microsoft Active Directory domain controller and a Samba domain controller through a Linux-based distribution point.
  • Remote diagnostics of Linux-based managed devices.
  • Kaspersky Security Center Cloud Console now supports the following Kaspersky applications:
    • Kaspersky Endpoint Security for Windows version 12.3 Patch A
    • Kaspersky Endpoint Security 12.0 for Linux
    • Kaspersky Endpoint Security 12.0 for Mac
    • Kaspersky Endpoint Agent 3.16
    • Kaspersky Embedded Systems Security 3.3 for Windows
  • Two interface sections were hidden from the main menu as out of the scope of application functionality:
    • Encryption events (OperationsData encryption and protectionEncryption events)
    • IP ranges (Discovery & deploymentDiscoveryIP ranges)
  • We have updated the text of the Data Processing Agreement for Kaspersky Security Center Cloud Console.
  • A number of old browser versions are no longer supported (Firefox ESR earlier than version 102).

Update September, 2023

This update of Kaspersky Security Center Cloud Console includes the following new features and improvements:

Update June, 2023

This update of Kaspersky Security Center Cloud Console includes the following new features and improvements:

  • A new Hardening Guide was released. We highly recommend that you carefully read the guide and follow the security recommendations for configuring Kaspersky Security Center Cloud Console and your network infrastructure.
  • Kaspersky Security Center Cloud Console now supports Kaspersky Endpoint Security 11.3 for Mac.
  • Kaspersky Security Center Cloud Console now supports Kaspersky Endpoint Security 11.4 for Linux.
  • You can use Kaspersky Security Center Cloud Console to export event selections to a file, and then import the event selections to Kaspersky Security Center Windows or Kaspersky Security Center Linux.
  • You can now use a distribution point as a push server for the devices managed by Network Agent. This feature allows you to make sure that continuous connectivity between a managed device and the Administration Server is established.
  • Reorganization of the section with settings to integrate Kaspersky Security Center Cloud Console with other Kaspersky applications.
  • Reorganization of the user interface of the Remote diagnostics section.
  • You can now save information about all devices included in a device selection to a CSV file at once.
  • A number of improvements in the user interface and usability, including the ability to select all items in a table.

Update March, 2023

This update of Kaspersky Security Center Cloud Console includes the following new features and improvements:

  • Kaspersky Security Center Cloud Console now supports clusters and server arrays as managed devices. If a Kaspersky application is installed on a cluster node, Network Agent sends this information to Administration Server. In Web Console, clusters and server arrays are listed separately from other managed devices. You manage each cluster or server array as an individual, inseparable object.
  • Kaspersky Security Center Cloud Console now supports Kaspersky Endpoint Security 12.0 for Windows.
  • The maximum number of entries that a report can include was increased up to 2500 for a report in Web Console and up to 10,000 for a report that you export to a file.
  • You can now choose whether or not you want to include the managed devices with the OK status in the Protection status report.
  • You can now activate Kaspersky Security Center Cloud Console by using one of the following licenses or add the license keys of the listed licenses to an existing workspace:
    • Kaspersky Symphony Security
    • Kaspersky Symphony EDR
    • Kaspersky Symphony MDR
    • Kaspersky Symphony XDR
  • A special edition of Network Agent for Windows XP was released.
  • The updated Network Agent for Linux supports the KSN Proxy service. Along with Windows-based distribution points, you can now use Linux-based distribution points to forward Kaspersky Security Network (KSN) requests from the managed devices. This feature allows you to redistribute and optimize traffic on the network.
  • The updated Network Agent for Linux supports the Applications registry feature. Network Agent can compile a list of applications installed on a Linux-based managed device, and then transmit this list to Administration Server.
  • You can use Kaspersky Security Center Cloud Console to export policies and tasks to a file, and then import the policies and tasks to Kaspersky Security Center Windows or Kaspersky Security Center Linux.

Update November, 2022

This update of Kaspersky Security Center Cloud Console includes the following new features and improvements:

  • Kaspersky Security Center Cloud Console now supports Kaspersky Endpoint Security 11.3 for Linux.
  • Kaspersky Security Center Cloud Console now supports Kaspersky Managed Detection and Response 2.1.18.
  • Kaspersky Security Center Cloud Console now supports updated versions of Kaspersky Endpoint Security for Mac 11.2 and 11.2.1, to support macOS 13.
  • Videos in the Introduction & tutorials section have been updated.

Update October, 2022

This update of Kaspersky Security Center Cloud Console includes the following new features and improvements:

  • We have updated the text of the Data Processing Agreement for Kaspersky Security Center Cloud Console.
  • Kaspersky Security Center Cloud Console infrastructure now notifies you about a workspace that has no active license key and that may be deleted if you do not add a new license key.
  • Kaspersky Security Center Cloud Console now supports Kaspersky Endpoint Security 11.11.0 for Windows.
  • Kaspersky Security Center Cloud Console now supports Kaspersky Endpoint Detection and Response Optimum 2.3.
  • Kaspersky Embedded Systems Security 3.2 for Windows is supported.

Update September, 2022

This update of Kaspersky Security Center Cloud Console includes the following new features and improvements:

  • You can now assign dedicated administrators for virtual Administration Servers. You create a user account for an administrator, and then grant the administrator the access rights to a virtual Administration Server. The assigned administrator has access only to the selected virtual Administration Server and cannot connect to the primary Administration Server or other secondary Administration Servers, physical or virtual.
  • Optimized user experience when you delete a license key for Kaspersky Security Center Cloud Console. The new mechanism prevents you from deleting your last active license key by accident.
  • You can now use Linux-based distribution points to download anti-virus databases for Kaspersky security applications through the Download updates to the repositories of distribution points task.
  • Network Agent is now available in Japanese localization.
  • In the Kaspersky Security Center Cloud Console interface, the all uppercase style of the section names has been changed to sentence-style capitalization.

Update August, 2022

New language support: Kaspersky Security Center Cloud Console is fully available in the Japanese language.

Update July, 2022

This update of Kaspersky Security Center Cloud Console includes the following new features and improvements:

  • New versions of supported Kaspersky applications:
    • Kaspersky Endpoint Agent 3.13
    • Kaspersky Endpoint Security 11.2.1 for Mac
    • Kaspersky Security for iOS 1.0.0
    • Kaspersky Endpoint Security 11.10.0 for Windows
  • We have updated the text of the Agreement and Data Processing Agreement for Kaspersky Security Center Cloud Console.
  • New language support: Kaspersky Security Center Cloud Console infrastructure is now available in Japanese. The support of the Japanese language inside Kaspersky Security Center Cloud Console workspaces is coming soon.

Update April, 2022

This update of Kaspersky Security Center Cloud Console includes the following new features and improvements:

  • Kaspersky Security Center Cloud Console now supports Kaspersky Endpoint Security 11.9.0 for Windows.
  • Kaspersky Security Center Cloud Console now supports the Japanese localization of Kaspersky Embedded Systems Security.

Update March 09, 2022

This update of Kaspersky Security Center Cloud Console includes the following new features and improvements:

Update February 11, 2022

This update of Kaspersky Security Center Cloud Console includes the following new features and improvements:

  • Licenses for Kaspersky Embedded Systems Security for Windows are now supported.
  • Kaspersky Endpoint Security 11.8.0 for Windows is supported.
  • You can install Kaspersky Endpoint Security 11.8.0 for Windows using a distribution package in Japanese.
  • Kaspersky Endpoint Agent 3.12 is supported.

Update December 10, 2021

This update of Kaspersky Security Center Cloud Console includes the following new features and improvements:

Update October 18, 2021

This update of Kaspersky Security Center Cloud Console includes the following new features and improvements:

  • Kaspersky Security Center Cloud Console now supports Kaspersky Endpoint Detection and Response Optimum 2.0.
  • You can now manage mobile devices running Android by using Kaspersky Security Center Cloud Console.
  • Kaspersky Marketplace is available as a new menu section: you can now search for a Kaspersky application by using Kaspersky Security Center Cloud Console.
  • A new menu section, Kaspersky announcements, is available. Kaspersky announcements keep you informed by providing information related to the Kaspersky applications installed on the managed devices. Kaspersky Security Center Cloud Console periodically updates the information in the section.
  • You can now manage secondary Administration Servers running under Linux operating systems via Kaspersky Security Center Cloud Console.

Update September 07, 2021

This update of Kaspersky Security Center Cloud Console includes the following new features and improvements:

  • You can now use Active Directory Federation Services (ADFS) to log in to Kaspersky Security Center Cloud Console by using your Active Directory account, without creating a new user account.
  • Kaspersky Security Center Cloud Console now works with the following cloud environments: Amazon Web Services, Microsoft Azure, and Google Cloud. To protect virtual machines (or instances) in a cloud environment, you need one of the Kaspersky Hybrid Cloud Security licenses. The Cloud Environment Configuration Wizard is available.
  • The maximum number of devices per one workspace is now 25,000.
  • Integration with SIEM systems now is available in Kaspersky Security Center Cloud Console. You can export events to SIEM systems by using the Syslog protocol.
  • You can now create virtual Administration Servers. Each virtual Administration Server can have its own structure of administration groups, policies, tasks, reports, and events. You can use virtual Administration Servers for the management of client organizations with complicated workflows within your workspace. However, you cannot migrate virtual Administration Servers from Kaspersky Security Center running on-premises to Kaspersky Security Center Cloud Console.
  • You can now adjust the width of columns in tables, and sort and search for data.
  • We have improved the stability and availability of Kaspersky Business Hub and Kaspersky Security Center Cloud Console.

Update October 27, 2020

This update of Kaspersky Security Center Cloud Console includes the following new features and improvements:

  • Kaspersky Security Center Cloud Console now supports Kaspersky Endpoint Security 11.6.0 for Windows, Kaspersky Endpoint Security 11.1 for Mac Patch A, and Kaspersky Endpoint Agent 3.10 (as part of Kaspersky Endpoint Detection and Response Optimum).
  • You can now use the following licenses:
    • Kaspersky Endpoint Detection and Response Optimum
    • Kaspersky Endpoint Security for Business Advanced
    • Kaspersky Total Security for Business
  • The following features are implemented:
  • The navigation menu is now vertical, which resembles the Microsoft Management Console-based interface of Kaspersky Security Center.
  • Technical training videos are now available; they will help you to learn how the application works.

Update June 30, 2020

This update of Kaspersky Security Center Cloud Console includes the following new features and improvements:

  • Kaspersky Security Center Cloud Console now supports Kaspersky Security 11 for Windows Server (starting from September, 2020).
  • Kaspersky Security Center Cloud Console now supports Kaspersky Endpoint Agent 3.9 and Kaspersky Endpoint Security 11.4.0 for Windows.
  • The Quick Start Wizard has been improved: some steps have been removed, the sequence of steps has been slightly changed, and some texts have been edited for usability.
  • Kaspersky Security Center Cloud Console is now available in the Italian language.
  • You can now revoke the End User License Agreement (EULA) for any managed Kaspersky application via the interface of Kaspersky Security Center Cloud Console. You must uninstall the selected application before revoking its EULA.
  • You can now delete workspaces. If you mark a workspace for deletion, it is by default deleted automatically in seven days. However, you can force the deletion of the workspace, so that it is deleted immediately.
  • Two-step verification for signing in to the console is implemented.
Page top

[Topic 166361]

Kaspersky Security Center Cloud Console

The section contains information about the purpose of Kaspersky Security Center Cloud Console and its main features and components.

Kaspersky Security Center Cloud Console is an application hosted and maintained by Kaspersky. You do not have to install Kaspersky Security Center Cloud Console on your computer or server. Kaspersky Security Center Cloud Console enables the administrator to install Kaspersky security applications on devices on a corporate network, remotely run scan and update tasks, and manage the security policies of managed applications. The administrator can use a detailed dashboard that provides a snapshot of corporate device statuses, detailed reports, and granular settings in protection policies.

In this section

About Kaspersky Security Center Cloud Console

Hardware and software requirements for Kaspersky Security Center Cloud Console

Compatible Kaspersky applications and solutions

Localization of Kaspersky Security Center Cloud Console

Comparison of Kaspersky Security Center and Kaspersky Security Center Cloud Console

Page top

[Topic 195506]

About Kaspersky Security Center Cloud Console

Kaspersky Security Center Cloud Console is an application aimed at corporate network administrators and employees responsible for protection of devices in a wide range of organizations.

Kaspersky Security Center Cloud Console enables you to do the following:

  • Install Kaspersky applications on devices on your network and manage the installed applications.
  • Create a hierarchy of administration groups to manage a selection of client devices as a whole.
  • Create virtual Administration Servers and arrange them in a hierarchy.
  • Protect your network devices, including workstations and servers:
    • Manage an antimalware protection system built on Kaspersky applications.
    • Use the detection and response (EDR and MDR) capabilities (a license for Kaspersky Endpoint Detection and Response and/or for Kaspersky Managed Detection and Response is required), including:
      • Analyzing and investigating incidents
      • Incident visualization through creating a threat development chain graph
      • Accepting or rejecting responses manually or setting up the auto-accept of all responses
  • Use Kaspersky Security Center Cloud Console as a multi-tenant application.
  • Remotely manage Kaspersky applications installed on client devices.
  • Perform centralized deployment of license keys for Kaspersky applications to client devices.
  • Create and manage security policies for devices on your network.
  • Create and manage user accounts.
  • Create and manage user roles (RBAC).
  • Create and manage tasks for applications installed on your network devices.
  • View reports on the security system status for every client organization individually.

You manage Kaspersky Security Center Cloud Console by using a cloud-based Administration Console that ensures interaction between your device and Administration Server over a browser. Administration Server is an application designed for managing Kaspersky applications installed on your network devices. When you connect to Kaspersky Security Center Cloud Console by using your browser, the browser establishes a connection with Kaspersky Security Center Cloud Console Server.

The Administration Server and connected database management system (DBMS) are deployed in a cloud environment and provided to you as a service. Maintenance of both Administration Server and the DBMS is provided as part of the service. All software components of Kaspersky Security Center Cloud Console are kept up-to-date. The Administration Server and created objects (such as policies and tasks) are backed up regularly to keep them safe.

Kaspersky Security Center Cloud Console is a multi-language application. You can change the interface language at any time, without reopening the application.

Updates functionality (including providing anti-virus signature updates and codebase updates), as well as KSN functionality may not be available in the software in the U.S.

See also:

Initial configuration of Kaspersky Security Center Cloud Console

Ports used by Kaspersky Security Center Cloud Console

How local application settings relate to policies

Page top

[Topic 166364]

Hardware and software requirements for Kaspersky Security Center Cloud Console

Administration Console

For a client, the use of Kaspersky Security Center Cloud Console requires only a browser.

You can only use a single browser window or tab to work with Kaspersky Security Center Cloud Console.

The minimum screen resolution is 1366x768 pixels.

The hardware and software requirements for the device are identical to the requirements of the browser that is used with Kaspersky Security Center Cloud Console.

Browser:

  • Google Chrome 133.0.6943.53 or later
  • Microsoft Edge 134.0.3124.66 or later
  • Safari 17.6 on macOS
  • "Yandex" Browser 25.2.3.809 or later
  • Mozilla Firefox Extended Support Release 128.8.0 or later

Network Agent

Minimum hardware requirements:

  • CPU with operating frequency of 1 GHz or higher. For a 64-bit OS, the minimum CPU frequency is 1.4 GHz.
  • RAM: 512 MB.
  • Available disk space: 1 GB.

Minimum hardware requirements for Vulnerability and patch management:

  • CPU with operating frequency of 1.4 GHz or higher. A 64-bit OS is required.
  • RAM: 8 GB.
  • Available disk space: 1 GB.

    Operating systems supported by Network Agent

Operating systems. Microsoft Windows workstations

Microsoft Windows Embedded POSReady 2009 with latest Service Pack 32-bit

Microsoft Windows Embedded 7 Standard with Service Pack 1 32-bit/64-bit

Microsoft Windows Embedded 8.1 Industry Pro 32-bit/64-bit

Microsoft Windows 10 Enterprise 2015 LTSB 32-bit/64-bit

Microsoft Windows 10 Enterprise 2016 LTSB 32-bit/64-bit

Microsoft Windows 10 IoT Enterprise 2015 LTSB 32-bit/64-bit

Microsoft Windows 10 IoT Enterprise 2016 LTSB 32-bit/64-bit

Microsoft Windows 10 Enterprise 2019 LTSC 32-bit/64-bit

Microsoft Windows 10 IoT Enterprise version 1703, 1709, 1803, 1809 32-bit/64-bit

Microsoft Windows 10 20H2, 21H2 IoT Enterprise 32-bit/64-bit

Microsoft Windows 10 IoT Enterprise 32-bit/64-bit

Microsoft Windows 10 IoT Enterprise version 1909 32-bit/64-bit

Microsoft Windows 10 IoT Enterprise LTSC 2021 32-bit/64-bit

Microsoft Windows 10 IoT Enterprise version 1607 32-bit/64-bit

Microsoft Windows 10 TH1 (July 2015) Home/Pro/Pro for Workstations/Enterprise/Education 32-bit/64-bit

Microsoft Windows 10 TH2 (November 2015) Home/Pro/Pro for Workstations/Enterprise/Education 32-bit/64-bit

Microsoft Windows 10 RS1 (August 2016) Home/Pro/Pro for Workstations/Enterprise/Education 32-bit/64-bit

Microsoft Windows 10 RS2 (April 2017) Home/Pro/Pro for Workstations/Enterprise/Education 32-bit/64-bit

Microsoft Windows 10 RS3 (Fall Creators Update, v1709) Home/Pro/Pro for Workstations/Enterprise/Education 32-bit/64-bit

Microsoft Windows 10 RS4 (April 2018 Update, 17134) Home/Pro/Pro for Workstations/Enterprise/Education 32-bit/64-bit

Microsoft Windows 10 RS5 (October 2018) Home/Pro/Pro for Workstations/Enterprise/Education 32-bit/64-bit

Microsoft Windows 10 RS6 (May 2019) Home/Pro/Pro for Workstations/Enterprise/Education 32-bit/64-bit

Microsoft Windows 10 19H1, 19H2 Home/Pro/Pro for Workstations/Enterprise/Education 32-bit/64-bit

Microsoft Windows 10 20H1 (May 2020 Update) Home/Pro/Pro for Workstations/Enterprise/Education 32-bit/64-bit

Microsoft Windows 10 20H2 (October 2020 Update) Home/Pro/Pro for Workstations/Enterprise/Education 32-bit/64-bit

Microsoft Windows 10 21H1 (May 2021 Update) Home/Pro/Pro for Workstations/Enterprise/Education 32-bit/64-bit

Microsoft Windows 10 21H2 (October 2021 Update) Home/Pro/Pro for Workstations/Enterprise/Education 32-bit/64-bit

Microsoft Windows 10 22H2 (October 2023 Update) Home/Pro/Pro for Workstations/Enterprise/Education 32-bit/64-bit

Microsoft Windows 11 Home/Pro/Pro for Workstations/Enterprise/Education 64-bit

Microsoft Windows 11 22H2 Home/Pro/Pro for Workstations/Enterprise/Education 64-bit

Microsoft Windows 11 23H2 Home/Pro/Pro for Workstations/Enterprise/Education 64-bit

Microsoft Windows 11 24H2 Home/Pro/Pro for Workstations/Enterprise/Education 64-bit

Microsoft Windows 8.1 Pro/Enterprise 32-bit/64-bit

Microsoft Windows 8 Pro/Enterprise 32-bit/64-bit

Microsoft Windows 7 Professional/Enterprise/Ultimate/Home Basic/Premium with Service Pack 1 and later 32-bit/64-bit

Microsoft Windows XP Professional with Service Pack 3 and later 32-bit (supported by Network Agent version 14.0.0.20023)

Microsoft Windows XP Professional for Embedded Systems with Service Pack 3 32-bit (supported by Network Agent version 14.0.0.20023)

Operating systems. Microsoft Windows servers

Microsoft Windows MultiPoint Server 2011 Standard/Premium 64-bit

Microsoft Windows Server 2008 Standard/Enterprise/Datacenter/Foundation with Service Pack 2 32-bit/64-bit

Microsoft Windows Server 2008 R2 Standard/Datacenter/Enterprise/Foundation with Service Pack 1 and later 64-bit

Microsoft Windows Server 2012 Server Core/Datacenter/Essentials/Foundation/Standard 64-bit

Microsoft Windows Server 2012 R2 Server Core/Datacenter/Essentials/Foundation/Standard 64-bit

Microsoft Windows Server 2016 Server Core/Datacenter/Essentials/Standard (Installation Option) (LTSB) 64-bit

Microsoft Windows Server 2019 Standard/Datacenter/Core 64-bit

Microsoft Windows Server 2019 RS5 Essentials/Standard 64-bit

Microsoft Windows Server 2022 Standard/Datacenter/Core 64-bit

Microsoft Windows Server 2022 21H2 Standard/Datacenter 64-bit

Microsoft Windows Server 2025 Standard/Datacenter/Core 64-bit

Microsoft Windows Small Business Server 2011 Standard/Essentials/Premium Add-on 64-bit

Operating systems. Linux

Debian GNU/Linux 12 (Bookworm) 32-bit/64-bit

Debian GNU/Linux 11.x (Bullseye) 32-bit/64-bit

Ubuntu Server 16.04 LTS (Xenial Xerus) 32-bit/64-bit

Ubuntu Server 24.04 LTS 64-bit

Ubuntu Server 22.04 LTS 64-bit

Ubuntu Server 20.04 LTS (Focal Fossa) 64-bit

CentOS 7.x 64-bit

CentOS Stream 8 64-bit

CentOS Stream 9 64-bit

Red Hat Enterprise Linux Server 9.x 64-bit

Red Hat Enterprise Linux Server 8.x 64-bit

Red Hat Enterprise Linux Server 7.x 64-bit

openSUSE Leap 15 64-bit

SUSE Linux Enterprise Server 15 (all Service Packs) 64-bit

SUSE Linux Enterprise Server 12 (all Service Packs) 64-bit

Oracle Linux 7 64-bit

Oracle Linux 8 64-bit

Oracle Linux 9 64-bit

Linux Mint 20.x 64-bit

Linux Mint 21.x 64-bit

Linux Mint 22.x 64-bit

Alma Linux 8.x 64-bit

Alma Linux 9.x 64-bit

Rocky Linux 8.x 64-bit

Rocky Linux 9.x 64-bit

Amazon Linux 2 64-bit

Kylin 10 64-bit

Operating systems. macOS

macOS Monterey (12.x)

macOS Ventura (13.x)

macOS Sonoma (14.x)

macOS Sequoia (15.x)

For Network Agent, the Apple Silicon (M1) architecture is also supported, as well as Intel.

The following virtualization platforms are supported:

  • VMware vSphere 6.7
  • VMware vSphere 7.0
  • Citrix XenServer 7.1 LTSR
  • Citrix XenServer 8.x
  • Parallels Desktop 18
  • Oracle VM VirtualBox 7.x
  • Microsoft Hyper-V Server 2019 64-bit
  • Microsoft Hyper-V Server 2022 64-bit
  • Kernel-based Virtual Machine (all Linux operating systems supported by Network Agent)

In Microsoft Windows XP, Network Agent might not perform some operations correctly.

See also:

Requirements for a distribution point

Compatible Kaspersky applications and solutions

Page top

[Topic 172903]

Compatible Kaspersky applications and solutions

Licenses for different products grant different sets of Kaspersky applications and solutions.

You can deploy and manage the following Kaspersky applications and solutions via Kaspersky Security Center Cloud Console:

  • Kaspersky Security for Windows Server 11.0.1
  • Kaspersky Endpoint Security 12.8 for Windows (only Lite encryption (AES56) is supported)
  • Kaspersky Endpoint Security 12.2 for Linux
  • Kaspersky Endpoint Security 12.1 for Mac
  • Kaspersky Embedded Systems Security 3.4 for Windows
  • Kaspersky Embedded Systems Security 3.4 for Linux
  • Kaspersky Endpoint Agent 4.0
  • Kaspersky Endpoint Security for Android
  • Kaspersky Security for iOS

You can integrate the following solutions to view and process security incidents:

  • Kaspersky Managed Detection and Response
  • Kaspersky Endpoint Detection and Response Optimum
  • Kaspersky Endpoint Detection and Response Expert

If you install a new application version on a managed device, but use an outdated policy for the new application version rather than update the policy, the application still provides data to Kaspersky Security Center Cloud Console, but Kaspersky Security Center Cloud Console cannot process this data as described in the Processed data of managed applications section of the documentation. For Kaspersky Security Center Cloud Console to process this data, you must create a new policy for the new version of the application.

See also:

Scenario: Migration without a hierarchy of Administration Servers

Page top

[Topic 197020]

Localization of Kaspersky Security Center Cloud Console

The interface and documentation of Kaspersky Security Center Cloud Console are available in the following languages:

  • English
  • French
  • German
  • Italian
  • Japanese
  • Portuguese (Brazil)
  • Russian
  • Simplified Chinese
  • Spanish
  • Spanish (LATAM)
  • Traditional Chinese
Page top

[Topic 187522]

Comparison of Kaspersky Security Center and Kaspersky Security Center Cloud Console

You can use Kaspersky Security Center in the following ways:

  • As a cloud solution

    Kaspersky Security Center is installed for you in cloud environment and Kaspersky gives you access to the Administration Server as a service. You manage the network security system through the cloud-based Administration Console named Kaspersky Security Center Cloud Console. This console has an interface similar to the interface of Kaspersky Security Center Web Console.

  • As an on-premises solution (Windows-based or Linux-based)

    You install Kaspersky Security Center on a local device and manage the network security system through the Microsoft Management Console-based Administration Console or Kaspersky Security Center Web Console.

    In addition to the Windows-based application, Kaspersky Security Center Linux is also available. Kaspersky Security Center Linux is designed to deploy and manage protection of Linux devices by using Linux-based Administration Server to meet the requirements of pure Linux environments. The Windows-based Kaspersky Security Center and Kaspersky Security Center Linux have different sets of features.

The table below lets you compare the main features of Kaspersky Security Center and Kaspersky Security Center Cloud Console.

Feature comparison of Kaspersky Security Center running on-premises and as a cloud solution

 

Feature or property

Kaspersky Security Center running on-premises

Kaspersky Security Center Cloud Console

Administration Server location

On-premises

Cloud

Database management system (DBMS) location

On-premises

Cloud

Web-based administration console

Yes.

Yes.

Maintenance of Administration Server and DBMS

Managed by customer

Managed by Kaspersky

Hierarchy of Administration Servers

Yes.

Yes.

(Administration Server of Kaspersky Security Center Cloud Console can only act as a primary Administration Server in the hierarchy and can only be used for policies and tasks monitoring)

Administration group hierarchy

Yes.

Yes.

Migration of the managed devices and related objects from Kaspersky Security Center on-premises to Kaspersky Security Center Cloud Console

Yes.

Yes.

Network polling

Yes.

Yes.

(by distribution points only)

Maximum number of managed devices

100,000

25,000

Protection of Windows, Linux, and macOS managed devices

Yes.

Yes.

Protection of mobile devices

Yes.

Yes.

(only Kaspersky Endpoint Security for Android and Kaspersky Security for iOS are supported)

Protection of public cloud infrastructure

Yes.

Yes.

Device-centric security management

Yes.

Yes.

Application policies

Yes.

Yes.

Tasks for Kaspersky applications

Yes.

Yes.

Kaspersky Security Network

Yes.

Yes.

KSN proxy server

Yes.

Yes.

(on distribution points only)

Kaspersky Private Security Network

Yes.

No.

Centralized deployment of license keys for Kaspersky applications

Yes.

Yes.

Switching managed devices to another Administration Server

Yes.

No.

(you must reinstall Network Agents on managed devices to switch them to another Administration Server)

Support for virtual Administration Servers

Yes.

Yes.

Installing third-party software updates and fixing third-party software vulnerabilities

Yes.

Yes.

(to fix third-party software vulnerabilities, only recommended fixes can be installed)

Notifications about events occurred on managed devices

Yes.

Yes.

Creating and managing user accounts

Yes.

Yes.

Maximum number of events in the database

400,000

(can be increased up to 45,000,000)

400,000

(depends on the number of managed devices)

Integration with SIEM systems

Yes.

Yes.

(by using the Syslog format and TLS over TCP protocol only)

Using Administration Server as a WSUS server

Yes.

No.

Monitoring the statuses of policies and tasks

Yes.

Yes.

Support of clusters and server arrays in administration groups

Yes.

Yes.

Remote installation of operating systems

Yes.

No.

SNMP support

Yes.

No.

Maximum number of virtual Servers

500

200

Cloning the hard drive of a device

Yes.

No.

See also:

Licenses and the minimum number of devices for each license

Page top

[Topic 291461]

Architecture and basic concepts

This section explains the application architecture and basic concepts related to Kaspersky Security Center Cloud Console.

In this section

Architecture

Ports used by Kaspersky Security Center Cloud Console

Basic concepts

Page top

[Topic 4531]

Architecture

This section provides a description of the components of Kaspersky Security Center Cloud Console and their interaction.

On the scheme, customer's infrastructure elements connect with Kaspersky Security Center Cloud Console infrastructure through various TCP ports.

Kaspersky Security Center Cloud Console architecture

Kaspersky Security Center Cloud Console managed via the cloud-based console includes two main components: Kaspersky Security Center Cloud Console infrastructure and customer's infrastructure.

Kaspersky Security Center Cloud Console infrastructure consists of the following:

  • Cloud-based Administration Console. Provides a web interface for creating and maintaining the protection system of a client organization's network that is managed by Kaspersky Security Center Cloud Console.
  • Cloud services. Includes update servers and activation servers.
  • Kaspersky Security Network (KSN). Servers that contain a Kaspersky database with continuously updated information about the reputation of files, web resources, and software. Kaspersky Security Network ensures faster responses by Kaspersky applications to threats, improves the performance of some protection components, and reduces the likelihood of false positives.

Customer's infrastructure may consist of the following:

  • Distribution point. Computer that has Network Agent installed and is used for update distribution, network polling, remote installation of applications, getting information about computers in an administration group, and / or broadcasting domain. The administrator selects the appropriate devices and assigns them distribution points manually.
  • Managed devices. Computers of customer's network protected through Kaspersky Security Center Cloud Console. Network Agent and a Kaspersky security application must be installed on each managed device.
  • Secondary Administration Server running on-premises (optional). You can use an on-premises Administration Server to create a hierarchy of Administration Servers.

Page top

[Topic 158830]

Ports used by Kaspersky Security Center Cloud Console

To use Kaspersky Security Center Cloud Console, which is part of the Kaspersky infrastructure, you must open the following ports on the client devices to allow the internet connection (see table below):

Ports that must be open on client devices to allow the internet connection

Port (or port range)

Protocol

Purpose of the port (or port range)

23100-23199

TCP/TLS

Receiving connections from Network Agents and secondary Administration Servers on Kaspersky Security Center Cloud Console Administration Server at *.ksc.kaspersky.com.

The Kaspersky infrastructure can use any port within this range and any web address within this mask. The port and the web address can change from time to time.

23700-23799

(only if you manage mobile devices)

TCP/TLS

Receiving connections from mobile devices.

Connection to the Kaspersky Security Center Cloud Console Administration Server at *.ksc.kaspersky.com.

The Kaspersky infrastructure can use any port within this range and any web address within this mask. The port and the web address can change from time to time.

27200-27299

TCP/TLS

Receiving connections for application activation from managed devices (except for mobile devices).

Connection to the Kaspersky Security Center Cloud Console Administration Server at *.ksc.kaspersky.com.

The Kaspersky infrastructure can use any port within this range and any web address within this mask. The port and the web address can change from time to time.

29200-29299

TCP/TLS

Tunneling connections to managed devices by using the klsctunnel utility through Kaspersky Security Center Cloud Console Administration Server at *.ksc.kaspersky.com.

The Kaspersky infrastructure can use any port within this range and any web address within this mask. The port and the web address can change from time to time.

443

HTTPS

Connection to Kaspersky Security Center Cloud Console discovery service at *.ksc.kaspersky.com.

The Kaspersky infrastructure can use any web address within this mask.

1443

TCP

Connection to Kaspersky Security Network

80

TCP

Connection is used to check validity of the Kaspersky Security Center certificates at *.digicert.com.

The Kaspersky infrastructure can use any web address within this mask.

The table below lists the ports that must be open on client devices where Network Agent is installed.

Ports that must be open on client devices

Port number

Protocol

Port purpose

Scope

15000

 

UDP

Receiving data from connection gateways (if in use)

Managing client devices

15000

UDP broadcast

Getting data about other Network Agents within the same broadcasting domain

Delivering updates and installation packages

15001

UDP

Receiving multicast requests from a distribution point (if in use)

Receiving updates and installation packages from a distribution point

Please note that the klnagent process can also request free ports from the dynamic port range of an endpoint operating system. These ports are allocated to the klnagent process automatically by the operating system, so klnagent process can use some ports that are used by another software. If the klnagent process affects that software operations, change the port settings in this software, or change the default dynamic port range in your operating system to exclude the port used by the software affected.

Also take into account that recommendations on the compatibility of Kaspersky Security Center Cloud Console with third-party software are described for reference only and may not be applicable to new versions of third-party software. The described recommendations for configuring ports are based on the experiences of Technical Support and our best practices.

The table below lists the additional ports that must be open on client devices where Network Agent is installed as a distribution point.

Ports used by Network Agent functioning as distribution point

Port number

Protocol

Port purpose

Scope

13000

TCP/TLS

Receiving connections from Network Agents

Managing client devices and delivering updates and installation packages

13111
(only if KSN proxy service is run on the device)

TCP

Receiving requests from managed devices to KSN proxy server

KSN proxy server

13295
(only if you use the distribution point as a push server)

TCP/TLS

Sending push notifications to managed devices

Distribution point used as a push server

15111
(only if KSN proxy service is run on the device)

UDP

Receiving requests from managed devices to KSN proxy server

KSN proxy server

17111
(only if KSN proxy service is run on the device)

HTTPS

Receiving requests from managed devices to KSN proxy server

KSN proxy server

If you have one or more Administration Servers on your network and use them as secondary Administration Servers when the primary Administration Server is located in the Kaspersky infrastructure, please refer to the list of ports that are used by Kaspersky Security Center running on-premises. Use those ports for interaction between your secondary Administration Server (or secondary Administration Servers) and client devices.

See also:

Initial configuration of Kaspersky Security Center Cloud Console

Scenario: Migration without a hierarchy of Administration Servers

Page top

[Topic 3305]

Network Agent

Interaction between the Administration Server and devices is performed by the Network Agent component of Kaspersky Security Center Cloud Console. Network Agent must be installed on all devices on which Kaspersky Security Center Cloud Console is used to manage Kaspersky applications.

Network Agent is installed on a device as a service with the following set of attributes:

  • With the name "Kaspersky Security Center Network Agent"
  • Set to automatically start when the operating system starts
  • Using the LocalSystem account

A device that has Network Agent installed is called a managed device or device. You can install Network Agent on a Windows, Linux, or Mac device.

The name of the process that Network Agent starts is klnagent.exe.

Network Agent synchronizes the managed device with the Administration Server. Kaspersky Security Center Cloud Console automatically synchronizes the Administration Server with the managed devices several times per hour. The Administration Server sets the synchronization interval (also referred to as the heartbeat) depending on the number of managed devices.

See also:

Network Agent installation package settings

Usage of Network Agent for Windows, Linux, and macOS: Comparison

Network Agent policy settings

Page top

[Topic 165736]

Administration groups

An administration group (hereinafter also referred to as group) is a logical set of managed devices combined on the basis of a specific trait for the purpose of managing the grouped devices as a single unit within Kaspersky Security Center Cloud Console.

All managed devices within an administration group are configured to do the following:

  • Use the same application settings (which you can specify in group policies).
  • Use a common operating mode for all applications through the creation of group tasks with specified settings. Examples of group tasks include creating and installing a common installation package, updating the application databases and modules, scanning the device on demand, and enabling real-time protection.

A managed device can belong to only one administration group.

You can create hierarchies that have any degree of nesting for Administration Servers and groups. A single hierarchy level can include secondary and virtual Administration Servers, groups, and managed devices. You can move devices from one group to another without physically moving them. For example, if a worker's position in the enterprise changes from that of accountant to developer, you can move this worker's computer from the Accountants administration group to the Developers administration group. Thereafter, the computer will automatically receive the application settings required for developers.

See also:

Creating administration groups

Adjustment of distribution points and connection gateways

Page top

[Topic 3304]

Hierarchy of Administration Servers

Administration Servers can be arranged in a "primary/secondary" hierarchy. Each Administration Server can have several secondary Administration Servers on different nesting levels of the hierarchy. The nesting level for secondary Administration Servers is unrestricted. The administration groups of the primary Administration Server will then include the client devices of all secondary Administration Servers.

Kaspersky Security Center Cloud Console Administration Server can only act as a primary Administration Server and can have as secondary servers only Administration Servers running on-premises.

When migrating from the Administration Server that runs on-premises to the Kaspersky Security Center Cloud Console Administration Server, you can arrange the Administration Servers in a hierarchy. Then, to mitigate the migration, you can shift only part of your managed devices to the management of the Kaspersky Security Center Cloud Console Administration Server. The rest of the managed devices remain under the management of the on-premises Administration Server. This enables you to test management features of Kaspersky Security Center Cloud Console on a limited number of managed devices. At the same time, you can configure policies, tasks, reports and other objects to test management and monitoring of your entire network. This lets you switch back to the objects configured on the on-premises Administration Server if necessary.

Each device included in the hierarchy of administration groups can be connected to one Administration Server only. You must independently monitor the connection of devices to Administration Servers. Use the feature for device search in administration groups of different Administration Servers based on network attributes.

See also:

Creating a hierarchy of Administration Servers: adding a secondary Administration Server

Page top

[Topic 30636]

Virtual Administration Server

Virtual Administration Server (also referred to as virtual Server) is a component of Kaspersky Security Center Cloud Console intended for managing anti-virus protection of the network of a client organization. Each virtual Administration Server can have its own structure of administration groups and its own means of management and monitoring, such as policies, tasks, reports, and events. The functional scope of virtual Administration Servers can be used by organizations with complicated workflows.

Virtual Administration Server has the following restrictions:

  • Virtual Administration Servers are supported only in the commercial mode of Kaspersky Security Center Cloud Console.
  • Virtual Administration Server does not support creation of secondary Administration Servers (including virtual Servers).
  • You cannot migrate virtual Administration Servers from Kaspersky Security Center to Kaspersky Security Center Cloud Console.
  • Virtual Administration Servers cannot be managed by dedicated administrators. By default, the administrator that manages the primary Administration Server also manages all of the virtual Administration Servers.
  • Users created on a virtual Server cannot be assigned a role on the Administration Server.
  • In the virtual Administration Server properties window, the number of sections is limited.

See also:

Hierarchy of Administration Servers

Enabling and disabling a virtual Administration Server

Deleting a virtual Administration Server

Page top

[Topic 98876]

Distribution point

A distribution point is a device with Network Agent installed that is used for update distribution, remote installation of applications, and retrieval of information about networked devices.

The features and use cases of Network Agent installed on a device used as a distribution point vary depending on the operating system.

A distribution point can perform the following functions:

  • Distribute updates and installation packages to client devices within the group (including distribution through multicasting using UDP). Updates can be received from Kaspersky update servers through an update task created for the distribution point.

    Distribution point devices running macOS cannot download updates from Kaspersky update servers.

    If one or more devices running macOS are within the scope of the Download updates to the repositories of distribution points task, the task completes with the Failed status, even if it has successfully completed on all Windows devices.

  • Distribute policies and group tasks through multicasting using UDP.
  • Act as a gateway for connection to the Administration Server for managed devices since a direct connection cannot be established in the cloud infrastructure.
  • Poll the network to detect new devices and update information about existing ones.
  • Perform remote installation of third-party software and Kaspersky applications through Microsoft Windows tools, including installation on client devices without Network Agent.

    This feature enables you to remotely transfer Network Agent installation packages to client devices located on networks to which the Administration Server has no direct access.

  • Act as a proxy server participating in the Kaspersky Security Network.

    This feature is not supported by distribution point devices running Linux or macOS.

    You can enable KSN proxy server on the distribution point side to make the device act as a KSN proxy server. In this case, the KSN proxy service (ksnproxy) is run on the device.

Files are transmitted from the Administration Server to a distribution point over HTTP or, if SSL connection is enabled, over HTTPS. Using HTTP or HTTPS results in a higher level of performance, compared to SOAP, through reducing traffic.

Devices with Network Agent installed must be assigned distribution points manually according to administration groups. The full list of distribution points for specified administration groups is displayed in the report about the list of distribution points.

The scope of a distribution point is the administration group to which it has been assigned by the administrator, as well as its subgroups of all levels of embedding. However, the device acting as the distribution point may not be included in the administration group to which it has been assigned. If multiple distribution points have been assigned in the hierarchy of administration groups, Network Agent on the managed device connects to the nearest distribution point in the hierarchy.

A network location can also be the scope of distribution points. The network location is used for manual creation of a set of devices to which the distribution point will distribute updates. Network location can be determined only for devices running a Windows operating system.

Kaspersky Security Center Cloud Console assigns each Network Agent a unique IP multicast address that differs from every other address. This enables you to avoid network overload that might occur due to IP overlaps.

If two or more distribution points are assigned to a single network area or to a single administration group, one of them becomes the active distribution point, and the rest become standby distribution points. The active distribution point downloads updates and installation packages directly from the Administration Server, while standby distribution points receive updates from the active distribution point only. In this case, files are downloaded once from the Administration Server and then are distributed among distribution points. If the active distribution point becomes unavailable for any reason, one of the standby distribution points becomes active. The Administration Server automatically assigns a distribution point to act as standby.

The distribution point status (Active/Standby) is displayed with a check box in the klnagchk report.

A distribution point requires at least 4 GB of free disk space. If the free disk space of the distribution point is less than 2 GB, Kaspersky Security Center Cloud Console creates a security issue with the Warning importance level. The security issue will be published in the device properties, in the Security issues section.

Running remote installation tasks on a device assigned as distribution point requires additional free disk space. The volume of free disk space must exceed the total size of all installation packages to be installed.

Running any updating (patching) tasks and vulnerability fix tasks on a device assigned as distribution point requires additional free disk space. The volume of free disk space must be at least twice the total size of all patches to be installed.

Devices functioning as distribution points must be protected, including physical protection, against any unauthorized access.

See also:

Adjustment of distribution points and connection gateways

Scenario: Kaspersky applications initial deployment

Page top

[Topic 165761]

Management web plug-in

A special component—the management web plug-in—is used for remote administration of Kaspersky software by means of Kaspersky Security Center Cloud Console. Hereinafter, a management web plug-in is also referred to as a management plug-in. A management plug-in is an interface between Kaspersky Security Center Cloud Console and a specific Kaspersky application. With a management plug-in, you can configure tasks and policies for the application.

The management plug-in provides the following:

  • Interface for creating and editing application tasks and settings
  • Interface for creating and editing policies and policy profiles for remote and centralized configuration of Kaspersky applications and devices
  • Transmission of events generated by the application
  • Kaspersky Security Center Cloud Console functions for displaying operational data and events of the application, and statistics relayed from client devices

See also:

Kaspersky Security Center Cloud Console

Kaspersky applications initial deployment

Page top

[Topic 3313]

Policies

A policy is a set of Kaspersky application settings that are applied to an administration group and its subgroups. You can install several Kaspersky applications on the devices of an administration group. Kaspersky Security Center Cloud Console provides a single policy for each Kaspersky application in an administration group. A policy has one of the following statuses (see the table below):

The status of the policy

Status

Description

Active

The current policy that is applied to the device. Only one policy may be active for a Kaspersky application in each administration group. Devices apply the settings values of an active policy for a Kaspersky application.

Inactive

A policy that is not currently applied to a device.

Out-of-office

If this option is selected, the policy becomes active when the device leaves the corporate network.

Policies function according to the following rules:

  • Multiple policies with different values can be configured for a single application.
  • Only one policy can be active for the current application.
  • You can activate an inactive policy when a specific event occurs. For example, you can enforce stricter anti-virus protection settings during virus outbreaks.
  • A policy can have child policies.

Generally, you can use policies as preparations for emergency situations, such as a virus attack. For example, if there is an attack via flash drives, you can activate a policy that blocks access to flash drives. In this case, the current active policy automatically becomes inactive.

In order to prevent maintaining multiple policies, for example, when different occasions assume changing of several settings only, you may use policy profiles.

A policy profile is a named subset of policy settings values that replaces the settings values of a policy. A policy profile affects the effective settings formation on a managed device. Effective settings are a set of policy settings, policy profile settings, and local application settings that are currently applied for the device.

Policy profiles function according to the following rules:

  • A policy profile takes an effect when a specific activation condition occurs.
  • Policy profiles contain values of settings that differ from the policy settings.
  • Activation of a policy profile changes the effective settings of the managed device.
  • A policy can include a maximum of 100 policy profiles.

See also:

Initial configuration of Kaspersky Security Center Cloud Console

Policies and policy profiles

Creating a policy

Page top

[Topic 165778]

Policy profiles

Sometimes it may be necessary to create several instances of a single policy for different administration groups; you might also want to modify the settings of those policies centrally. These instances might differ by only one or two settings. For example, all the accountants in an enterprise work under the same policy—but senior accountants are allowed to use flash drives, while junior accountants are not. In this case, applying policies to devices only through the hierarchy of administration groups can be inconvenient.

To help you avoid creating several instances of a single policy, Kaspersky Security Center Cloud Console enables you to create policy profiles. Policy profiles are necessary if you want devices within a single administration group to run under different policy settings.

A policy profile is a named subset of policy settings. This subset is distributed on target devices together with the policy, supplementing it under a specific condition called the profile activation condition. Profiles only contain settings that differ from the "basic" policy, which is active on the managed device. Activation of a profile modifies the settings of the "basic" policy that were initially active on the device. The modified settings take values that have been specified in the profile.

See also:

Policies and policy profiles

Creating a policy profile

Page top

[Topic 3316]

How local application settings relate to policies

You can use policies to set identical values of the application settings for all devices in a group.

The values of the settings that a policy specifies can be redefined for individual devices in a group by using local application settings. You can set only the values of settings that the policy allows to be modified, that is, the unlocked settings.

The value of a setting that the application uses on a client device is defined by the lock position (The lock icon.) for that setting in the policy:

  • If a setting modification is locked, the same value (defined in the policy) is used on all client devices.
  • If a setting modification is unlocked, the application uses a local setting value on each client device instead of the value specified in the policy. The setting can then be changed in the local application settings.

This means that, when a task is run on a client device, the application applies settings that have been defined in two different ways:

  • By task settings and local application settings, if the setting is not locked against changes in the policy.
  • By the group policy, if the setting is locked against changes.

Local application settings are changed after the policy is first applied in accordance with the policy settings.

See also:

About policies

Policies and policy profiles

Page top

[Topic 180068]

Licensing of Kaspersky Security Center Cloud Console

Following this scenario, you can start using Kaspersky Security Center Cloud Console and managed security applications under a license.

Kaspersky Security Center Cloud Console enables you to perform centralized distribution of license keys for Kaspersky applications on client devices, monitor their use, and renew licenses.

If you are already using Kaspersky Security Center Cloud Console, you can visit Kaspersky Marketplace to view the entire range of Kaspersky business solutions, select the ones you need, and proceed to the purchase at the Kaspersky website.

Checking out the features of Kaspersky Security Center Cloud Console in the trial mode before purchasing a license

You can first to try Kaspersky Security Center Cloud Console for free. To do this, create a trial workspace which will terminate in 30 days. If you want a commercial workspace that you can use as long as you want, you will have to purchase a license.

Trial mode does not allow you to subsequently switch to commercial mode. Any trial workspace will be automatically deleted with all its contents when the 30-day period expires.

Stages

The scenario proceeds in stages:

  1. Getting an activation code for licensing Kaspersky Security Center Cloud Console in the commercial mode. Purchasing a license (or licenses)

    Different licenses grant the usage of different Kaspersky applications and services, so you might want to purchase more than one license.

    Find out what licenses that you can purchase and the minimum number of devices for each license.

    Kaspersky Security Center Cloud Console comes as part of several Kaspersky solutions. Choose what solution you want to use and purchase a license for it. You will need to contact Kaspersky or one of Kaspersky partners with a special request if you want to purchase a license that covers 10,000 or more devices.

    Use the table to check which Vulnerability and patch management features are available under which license.

    If you want to use Kaspersky Security Center Cloud Console in a cloud environment such as Microsoft Azure, read about the licensing options for cloud environments.

    If you are a Manage Service Provider (MSP), read about licensing of Kaspersky Security Center Cloud Console for MSPs.

  2. Activation of Kaspersky Security Center Cloud Console when creating the workspace

    You specify your license key to activate Kaspersky Security Center Cloud Console when creating a workspace.

    If you have more than one license key, specify any of them, and later you must add other license keys in Kaspersky Security Center Cloud Console to activate managed Kaspersky applications.

  3. Adding license keys for managed applications to the Administration Server repository

    Before deployment of the license keys, you must add these license keys to the Administration Server repository.

    The license key that you specified when creating the workspace is automatically added to the Administration Server repository.

    If you have more than one license keys, add your license keys one by one to the Kaspersky Security Center Cloud Console Administration Server repository.

  4. Deploying license keys for managed applications

    Choose a method of deployment of the license key (or license keys) to all the devices you want to protect:

    • Automatic deployment

      If you use different managed applications and you have to deploy a specific activation code for applications, choose another way of deploying that activation code.

      Kaspersky Security Center enables you to automatically deploy available license keys for managed applications. For example, three license keys are stored in the Administration Server repository. You have enabled the Automatically distribute license key to managed devices option for all three license keys. A Kaspersky security application—for example, Kaspersky Endpoint Security for Windows—is installed on the organization's devices. A new managed application on a device is discovered for which a license key must be deployed. For instance, two of the license keys from the repository can be deployed for the managed application on the device: license key named Key_1 and license key named Key_2. One of these license keys is deployed for the managed application. In this case, it cannot be predicted which of the two license keys will be deployed because automatic deployment of license keys does not provide for any administrator activity.

      When a license key is deployed, the number of installations is recounted for that license key. You must make sure that the number of applications for which the license key was deployed does not exceed the license limit. If the number of installations exceeds the license limit, all devices that were not covered by the license will be assigned Critical status.

      How-to instructions:

    • Deployment through the Add license key task for a managed application

      If you opt to use the Add license key task for a managed application, you can select the license key that must be deployed to devices, and then select the devices in any convenient way—for example, by selecting an administration group or a device selection.

      How-to instructions:

    • Adding an activation code or a key file manually to the devices

      You can activate the installed Kaspersky application locally, by using the tools provided in the application interface. Please refer to the documentation of the installed application.

  5. Checking on which devices the managed Kaspersky applications are activated

    To make sure that the license keys are deployed correctly, view the list of the license keys that are used for an application.

  6. Configuring events related to the license expiration

    Configure events so that you will be notified when your license keys are used up or about to expire:

See also

About the trial mode of Kaspersky Security Center Cloud Console

Using Kaspersky Marketplace to choose Kaspersky business solutions

Licenses and the minimum number of devices for each license

Events of the licensing limit exceeded

Methods of distribution of the activation codes to the managed devices

Adding a license key to the Administration Server repository

Deploying a license key to client devices

Automatic distribution of a license key

Viewing information about license keys in use in the Administration Server repository

Viewing information about the license keys used for a specific Kaspersky application

Deleting a license key from the repository

Viewing the list of devices where a Kaspersky application is not activated

Revoking consent with an End User License Agreement

Renewing licenses for Kaspersky applications

Use of Kaspersky Security Center Cloud Console after the license expiration

Licensing definitions

Licenses and the minimum number of devices for each license

Deleting a license key from the repository

Viewing the list of devices where a Kaspersky application is not activated

Renewing licenses for Kaspersky applications

Initial configuration of Kaspersky Security Center Cloud Console

Page top

[Topic 186413]

About the trial mode of Kaspersky Security Center Cloud Console

The trial mode is a special mode of Kaspersky Security Center Cloud Console intended to acquaint the user with the features of Kaspersky Security Center Cloud Console. In this mode, you can perform activities within a workspace whose validity period is limited to 30 days. The trial mode is activated automatically as soon as you create a trial workspace. The set of features available in trial mode is identical to the scope under the standard Kaspersky Endpoint Security for Business Advanced license.

In Kaspersky Security Center Cloud Console, you do not have to license the Administration Server, because the features that require a special license are not supported. If you want to use Kaspersky Security Center Cloud Console in trial mode, you automatically get a trial license when you create your first workspace.

Trial mode does not allow you to subsequently switch to commercial mode. Any trial workspace will be automatically deleted with all its contents when the 30-day period expires.

The following restrictions are imposed on the use of the Kaspersky Security Center Cloud Console features in trial mode:

  • You cannot create a hierarchy of Administration Servers. No virtual Administration Servers can be created.
  • The Licensing section is available as read-only. All operations are prohibited in this section, including the addition and removal of license keys.
  • You cannot create custom installation packages.
  • You cannot create custom roles for users.
  • The Virus outbreak feature is not available. Virus outbreak events are not stored, and no notifications are sent.
  • The Deleted objects repository is not available.
  • You cannot enable the addition of batched events (those published in large quantities) to the database.
  • Migration of Administration Servers from on-premises mode to Cloud Console mode is not supported.
  • KSN statistical information from the Administration Server components, such as Administration Server or Network Agent, is not sent to Kaspersky.

Some limits are also imposed on creation of some objects of the application (see the table below). If any of these limits are exceeded when an attempt is made to create such an object, the object creation will be blocked, and an error message about the limit will be displayed.

Limitations on creation of Kaspersky Security Center Cloud Console objects in trial mode

Type of limitation

Value

Policies

8

Tasks

17

License keys

1

Installation packages

5

Device selections (preset instances not included)

5

Event selections (preset instances not included)

5

Device moving rules

3

Report templates of the same type

10

Internal security groups

20

Managed devices

20

See also:

About KSN

Licensing of Kaspersky Security Center Cloud Console

Page top

[Topic 221110]

Using Kaspersky Marketplace to choose Kaspersky business solutions

Marketplace is a section in the main menu that enables you to view the entire range of Kaspersky business solutions, select the ones you need, and proceed to the purchase at the Kaspersky website. You can use filters to view only those solutions that fit your organization and the requirements for your information security system. When you select a solution, Kaspersky Security Center Cloud Console redirects you to the related webpage at the Kaspersky website to learn more about that solution. Each webpage enables you to proceed to the purchase or contains instructions on the purchase process.

In the Marketplace section, you can filter Kaspersky solutions by using the following criteria:

  • Number of devices (endpoints, servers, and other types of assets) that you want to protect:
    • 50–250
    • 250–1000
    • More than 1000
  • Maturity level of your organization's information security team:
    • Foundations

      This level is typical for enterprises that only have an IT team. The maximum possible number of threats is blocked automatically.

    • Optimum

      This level is typical for enterprises that have a specific IT security function within the IT team. At this level, companies require solutions that enable them to counter commodity threats and threats that circumvent existing preventive mechanisms.

    • Expert

      This level is typical for enterprises with complex and distributed IT environments. The IT security team is mature or the company has an SOC (Security Operations Center) team. The required solutions enable the companies to counter complex threats and targeted attacks.

  • Types of assets that you want to protect:
    • Endpoints: workstations of employees, physical and virtual machines, embedded systems
    • Servers: physical and virtual servers
    • Cloud: public, private, or hybrid cloud environments; cloud services
    • Network: local area network, IT infrastructure
    • Service: security-related services provided by Kaspersky

To find and purchase a Kaspersky business solution:

  1. In the main menu, go to Marketplace.

    By default, the section displays all available Kaspersky business solutions.

  2. To view only those solutions that suit your organization, select the required values in the filters.
  3. Click the solution that you want to purchase or you want to learn more about.

You will be redirected to the solution webpage. You can follow the on-screen instructions to proceed to the purchase.

See also:

Licensing of Kaspersky Security Center Cloud Console

About the trial mode of Kaspersky Security Center Cloud Console

Licenses and the minimum number of devices for each license

Events of the licensing limit exceeded

Methods of distribution of the activation codes to the managed devices

Adding a license key to the Administration Server repository

Deploying a license key to client devices

Automatic distribution of a license key

Viewing information about license keys in use in the Administration Server repository

Viewing information about the license keys used for a specific Kaspersky application

Deleting a license key from the repository

Viewing the list of devices where a Kaspersky application is not activated

Revoking consent with an End User License Agreement

Renewing licenses for Kaspersky applications

Use of Kaspersky Security Center Cloud Console after the license expiration

Licensing definitions

Licensing of Kaspersky Security Center Cloud Console

Page top

[Topic 195507]

Licenses and the minimum number of devices for each license

If you want to use Kaspersky Security Center Cloud Console in commercial mode, you must purchase a license before creating your first workspace. The table below shows the licenses that you can purchase and the minimum number of devices for each license (even if you want to protect fewer devices):

Licenses that grant the usage of Kaspersky Security Center Cloud Console

License

Minimum number of devices (even if you want to protect a fewer number)

Kaspersky Endpoint Security for Business Select

For commercial licenses: 300

For commercial (subscription) licenses: 100

Kaspersky Endpoint Security for Business Advanced

For commercial licenses: 300

For commercial (subscription) licenses: 100

Kaspersky Total Security for Business

300

Kaspersky Endpoint Detection and Response Optimum

For commercial licenses: 300

For commercial (subscription) licenses: 100

Kaspersky Endpoint Detection and Response Expert

50

Kaspersky Hybrid Cloud Security, Desktop

For commercial licenses: 300

For commercial (subscription) licenses: 100

Kaspersky Hybrid Cloud Security, Server

50

Kaspersky Hybrid Cloud Security, Core

20

Kaspersky Hybrid Cloud Security, CPU

20

Kaspersky Hybrid Cloud Security Enterprise, Desktop

For commercial licenses: 300

For commercial (subscription) licenses: 100

Kaspersky Hybrid Cloud Security Enterprise, Server

50

Kaspersky Hybrid Cloud Security Enterprise, CPU

20

Kaspersky Embedded Systems Security

300

Kaspersky Embedded Systems Security Compliance Edition

300

Kaspersky Symphony (currently only available in Russia)

300

Kaspersky Next EDR Foundations

300 users (each user license can apply to 1 PC/Mac device and 2 mobile devices)

Kaspersky Next EDR Optimum

300 users (each user license can apply to 1 PC/Mac device and 2 mobile devices)

Kaspersky Next XDR Expert

250 users (each user license can apply to 1 PC/Mac device and 2 mobile devices)

The maximum devices per one workspace is 25,000. If you want to protect more than 10,000 devices, you need to create a separate workspace. To do this, send a request to Kaspersky Technical Support. This request must contain the following information:

  • User Email—The email address of the user registered on Kaspersky Security Center Cloud Console. This user is granted administrator rights on the created workspace.

    After you create an account on Kaspersky Security Center Cloud Console, you do not have to register a company and create a workspace for it. Specify information about the company and the workspace in the request.

  • Company Name—The name of the company in which you want to use Kaspersky Security Center Cloud Console.
  • Company Country—The country in which the company is located.
  • Workspace Name—The name of the workspace to be created for the company.
  • Estimated Endpoints Count—The total number of client devices (including mobile devices) that you want to protect in the new workspace.
  • Workspace Country—The country in which you want to locate your new workspace. This parameter affects the selection of the data center to store the workspace.

    The Company Country and Workspace Country parameters may be the same.

  • Activation Code—The activation code that you receive after you have purchased Kaspersky Security Center Cloud Console. Make sure that the license you want to buy covers all client devices that must be protected.

After you send the request, Kaspersky specialists register the specified company and create a workspace for it. When the workspace creation is completed, you will receive an email notification. You can log in to your account on Kaspersky Security Center Cloud Console to view the result.

See also:

Licensing of Kaspersky Security Center Cloud Console

Using Kaspersky Marketplace to choose Kaspersky business solutions

About the trial mode of Kaspersky Security Center Cloud Console

Page top

[Topic 138255]

Events of the licensing limit exceeded

Kaspersky Security Center Cloud Console allows you to get information about events when some licensing limits are exceeded by Kaspersky applications installed on client devices.

The importance level of such events when a licensing limit is exceeded is defined according to the following rules:

  • If the currently used units covered by a single license constitute 90% to 100% of the total number of units covered by the license, the event is published with the Info importance level.
  • If the currently used units covered by a single license constitute 100% to 110% of the total number of units covered by the license, the event is published with the Warning importance level.
  • If the number of currently used units covered by a single license exceeds 110% of the total number of units covered by the license, the event is published with the Critical event importance level.
Page top

[Topic 223114]

Methods of distribution of the activation codes to the managed devices

The Kaspersky applications installed on managed devices must be licensed by applying an activation code to each of the applications. You cannot use key files for licensing of managed applications; only activation codes are accepted. An activation code can be deployed in the following ways:

  • Automatic deployment
  • The Add license key task for a managed application
  • Manual activation of a managed application

Kaspersky applications can use more than one license key at the same time. For example, Kaspersky Endpoint Security for Windows can use two license keys—one for Kaspersky Endpoint Security for Windows and one for activation of the Endpoint Detection and Response functions.

In addition, Kaspersky applications can have not only an active license key, but also a reserve license key. A Kaspersky application uses an active key at the current moment and stores a reserve key to apply after the active key expires. You can add a new active or reserve license key by any of the methods listed above. The application for which you add a license key defines whether the key is active or reserve. The key definition does not depend on the method that you use to add a new license key.

See also:

Licensing of Kaspersky Security Center Cloud Console

Page top

[Topic 179952]

Adding a license key to the Administration Server repository

When adding a license key using Kaspersky Security Center Cloud Console, the settings of the license key are saved on the Administration Server. Based on this information, the application generates a license key usage report and notifies the administrator of license expirations and violation of license restrictions that are set in the properties of license keys. You can configure notifications of the use of license keys within the Administration Server settings.

To add a license key to the Administration Server repository:

  1. In the main menu, go to OperationsLicensingKaspersky licenses.
  2. Click the Add button.
  3. Specify the activation code in the text field and click the Send button.
  4. Click the Close button.

The license key or several license keys are added to the Administration Server repository.

See also:

Licensing of Kaspersky Security Center Cloud Console

About the trial mode of Kaspersky Security Center Cloud Console

Using Kaspersky Marketplace to choose Kaspersky business solutions

Licenses and the minimum number of devices for each license

Events of the licensing limit exceeded

Methods of distribution of the activation codes to the managed devices

Deploying a license key to client devices

Automatic distribution of a license key

Viewing information about license keys in use in the Administration Server repository

Viewing information about the license keys used for a specific Kaspersky application

Deleting a license key from the repository

Viewing the list of devices where a Kaspersky application is not activated

Revoking consent with an End User License Agreement

Renewing licenses for Kaspersky applications

Use of Kaspersky Security Center Cloud Console after the license expiration

Licensing definitions

Deleting a license key from the repository

Viewing information about the license keys used for a specific Kaspersky application

Licenses and the minimum number of devices for each license

Licensing of Kaspersky Security Center Cloud Console

Page top

[Topic 179954]

Deploying a license key to client devices

Kaspersky Security Center Cloud Console allows you to distribute a license key to client devices automatically or through the Application activation task. You can use the task to distribute keys to a specific device group. During distribution of a license key via the task, the licensing limit on the number of devices is not taken into account. Use the automatic key distribution to cease distribution of a license key automatically when the licensing limit is reached.

If you enable automatic distribution of a license key, do not create an Application activation task to distribute that key to client devices. Otherwise, the load on the Administration Server will increase due to frequent synchronization.

Before deployment, add the license key to the Administration Server repository.

To distribute a license key to client devices through the Application activation task:

  1. In the main menu, go to Assets (Devices) → Tasks.
  2. Click Add.

    The New task wizard starts. Proceed through the wizard by using the Next button.

  3. In the Application drop-down list, select the application for which you want to add a license key.
  4. In the Task type list, select the Application activation task.
  5. In the Task name field, specify the name of the new task.
  6. Select the devices to which the task will be assigned.
  7. At the Selecting a license key step of the wizard, click the Add key link to add the license key.
  8. On the key adding pane, add the license key by using one of the following options:

    You need to add the license key only if you did not add it to the Administration Server repository prior to creating the Application activation task.

    • Select the Enter activation code option to enter an activation code, and then do the following:
      1. Specify the activation code, and then click the Send button.

        Information about the license key appears in the key adding pane.

      2. Click the Save button.

        If you want to distribute the license key to managed devices automatically, enable the Automatically distribute license key to managed devices option.

        The key adding pane closes.

    • Select the Add key file option to add a key file, and then do the following:
      1. Click the Select key file button.
      2. In the window that opens, select a key file, and then click the Open button.

        Information about the license key appears in the license key adding pane.

      3. Click the Save button.

        If you want to distribute the license key to managed devices automatically, enable the Automatically distribute license key to managed devices option.

        The key adding pane closes.

  9. Select the license key in the table of keys.
  10. At the License information step of the wizard, clear the default Use as a reserve key check box if you want to replace the active license key.

    For example, this is needed when the organization changes, and another organization's key is required on the device; or if the key was reissued, and a new license expires earlier than the current license. To avoid errors, you have to clear the Use as a reserve key check box.

    If you want to find out more information about the issues that may occur when adding a license key to Kaspersky Security Center and the ways to resolve them, refer to the Kaspersky Security Center Knowledge Base.

  11. At the Finish task creation step of the wizard, enable the Open task details when creation is complete option to modify the default task settings.

    If you do not enable this option, the task will be created with the default settings. You can modify the default settings later.

  12. Click the Finish button.

    The wizard creates the task. If you enabled the Open task details when creation is complete option, the task properties window automatically opens. In this window, you can specify the general task settings and, if required, change the settings specified during task creation.

    You can also open the task properties window by clicking the name of the created task in the list of tasks.

    The task is created, configured, and displayed in the list of tasks.

  13. To run the task, select it in the task list, and then click the Start button.

    You can also set a task start schedule on the Schedule tab of the task properties window.

    For a detailed description of scheduled start settings, refer to the general task settings.

After the task is completed, the license key is deployed to the selected devices.

See also:

Licensing of Kaspersky Security Center Cloud Console

About the trial mode of Kaspersky Security Center Cloud Console

Using Kaspersky Marketplace to choose Kaspersky business solutions

Licenses and the minimum number of devices for each license

Events of the licensing limit exceeded

Methods of distribution of the activation codes to the managed devices

Adding a license key to the Administration Server repository

Automatic distribution of a license key

Viewing information about license keys in use in the Administration Server repository

Viewing information about the license keys used for a specific Kaspersky application

Deleting a license key from the repository

Viewing the list of devices where a Kaspersky application is not activated

Revoking consent with an End User License Agreement

Renewing licenses for Kaspersky applications

Use of Kaspersky Security Center Cloud Console after the license expiration

Licensing definitions

Initial configuration of Kaspersky Security Center Cloud Console

Licenses and the minimum number of devices for each license

Licensing of Kaspersky Security Center Cloud Console

Page top

[Topic 180049]

Automatic distribution of a license key

Kaspersky Security Center Cloud Console allows automatic distribution of license keys to managed devices if they are located in the license keys repository on the Administration Server.

To distribute a license key to managed devices automatically:

  1. In the main menu, go to OperationsLicensingKaspersky licenses.
  2. Click the name of the license key that you want to distribute to devices automatically.
  3. In the license key properties window that opens, switch the toggle button to Automatically distribute license key to managed devices.
  4. Click the Save button.

The license key will be automatically distributed to all compatible devices.

License key distribution is performed by means of Network Agent. No license key distribution tasks are created for the application.

During automatic distribution of a license key, the licensing limit on the number of devices is taken into account. The licensing limit is set in the properties of the license key. If the licensing limit is reached, distribution of this license key on devices ceases automatically.

Note that an automatically distributed license key may not be displayed in the virtual Administration Server repository in the following cases:

  • The license key is not valid for the application.
  • The virtual Administration Server does not have managed devices.
  • The license key has already been used for devices managed by another virtual Administration Server and the limit on the number of devices has been reached.

If you specify the Automatically distribute license key to managed devices option for a subscription license key for activating any application on a managed device, and at the same time you have an active trial license key, then your trial license key will be automatically replaced by the subscription license key eight days before the expiration date.

See also:

Licensing of Kaspersky Security Center Cloud Console

About the trial mode of Kaspersky Security Center Cloud Console

Using Kaspersky Marketplace to choose Kaspersky business solutions

Licenses and the minimum number of devices for each license

Events of the licensing limit exceeded

Methods of distribution of the activation codes to the managed devices

Adding a license key to the Administration Server repository

Deploying a license key to client devices

Viewing information about license keys in use in the Administration Server repository

Viewing information about the license keys used for a specific Kaspersky application

Deleting a license key from the repository

Viewing the list of devices where a Kaspersky application is not activated

Revoking consent with an End User License Agreement

Renewing licenses for Kaspersky applications

Use of Kaspersky Security Center Cloud Console after the license expiration

Licensing definitions

Initial configuration of Kaspersky Security Center Cloud Console

Licenses and the minimum number of devices for each license

Licensing of Kaspersky Security Center Cloud Console

Page top

[Topic 180055]

Viewing information about license keys in use in the Administration Server repository

To view the list of the license keys added to the Administration Server repository,

In the main menu, go to OperationsLicensingKaspersky licenses.

The displayed list contains the activation codes added to the Administration Server repository.

To view detailed information about a license key:

  1. In the main menu, go to OperationsLicensingKaspersky licenses.
  2. Click the name of the required license key.

In the license key properties window that opens, you can view:

  • On the General tab—The main information about the license key
  • On the Devices tab—The list of client devices where the license key was used for activation of the installed Kaspersky application

See also:

Licensing of Kaspersky Security Center Cloud Console

About the trial mode of Kaspersky Security Center Cloud Console

Using Kaspersky Marketplace to choose Kaspersky business solutions

Licenses and the minimum number of devices for each license

Events of the licensing limit exceeded

Methods of distribution of the activation codes to the managed devices

Adding a license key to the Administration Server repository

Deploying a license key to client devices

Automatic distribution of a license key

Viewing information about the license keys used for a specific Kaspersky application

Deleting a license key from the repository

Viewing the list of devices where a Kaspersky application is not activated

Revoking consent with an End User License Agreement

Renewing licenses for Kaspersky applications

Use of Kaspersky Security Center Cloud Console after the license expiration

Licensing definitions

Licenses and the minimum number of devices for each license

Licensing of Kaspersky Security Center Cloud Console

Page top

[Topic 222233]

Viewing information about the license keys used for a specific Kaspersky application

To learn what license keys are in use for a Kaspersky application:

  1. In the main menu, go to Assets (Devices) → Managed devices.

    If the device belongs to the Unassigned devices group, go to Discovery & deploymentUnassigned devices instead.

  2. Click the name of the required device.
  3. In the device properties window that opens, select the Applications section.
  4. In the list of applications that opens, select the application whose license keys you want to view.
  5. In the application properties window that opens, on the General tab, select the License keys section.

    The information is displayed in the workspace of this section.

See also:

Licensing of Kaspersky Security Center Cloud Console

Page top

[Topic 180115]

Deleting a license key from the repository

You can delete a license key from the Administration Server repository. Note that Kaspersky Security Center Cloud Console automatically deletes your workspace after 90 days in the following cases:

If your workspace is deleted, you cannot manage the protection of your network by means of Kaspersky Security Center Cloud Console. You also permanently lose your data from Kaspersky Security Center Cloud Console. If necessary, you can delete your workspace manually. Otherwise, we recommend that you keep at least one license key in the Administration Server repository.

If you delete a license key and you added a reserve license key earlier, the reserve license key automatically becomes the active license key after the former active key is deleted or expired.

When you delete the active license key that is deployed to a managed device, the application will continue working on the managed device.

To delete a license key from the Administration Server repository:

  1. Check that Administration Server does not use a license key that you want to delete. If the Administration Server does, you cannot delete the key. To perform the check:
    1. In the main menu, click the settings icon () next to the Administration Server.

      The Administration Server properties window opens.

    2. On the General tab, select the License keys section.
    3. If the required license key is displayed in the section that opens, click the Remove active license key button, and then confirm the operation. After that, the Administration Server does not use the deleted license key, but the key remains in the Administration Server repository. If the required license key is not displayed, the Administration Server does not use it.
  2. In the main menu, go to OperationsLicensingKaspersky licenses.
  3. Select the required license key, and then click the Delete button.
  4. In the window that appears, select the I understand the risk and want to remove the license key check box. This means that if you delete the last license key, you are aware of the subsequent deletion of the workspace and loss of control over the managed devices. Next, click the Remove button.

As a result, the selected license key is deleted from the repository.

You can add a deleted license key again or add a new one. If you deleted the last license key, you can also add a license key as long as your workspace is not deleted. Kaspersky Security Center Cloud Console notifies administrators of the workspace 30 days, 7 days, and 1 day prior to deletion.

See also:

Licensing of Kaspersky Security Center Cloud Console

About the trial mode of Kaspersky Security Center Cloud Console

Using Kaspersky Marketplace to choose Kaspersky business solutions

Licenses and the minimum number of devices for each license

Events of the licensing limit exceeded

Methods of distribution of the activation codes to the managed devices

Adding a license key to the Administration Server repository

Deploying a license key to client devices

Automatic distribution of a license key

Viewing information about license keys in use in the Administration Server repository

Viewing information about the license keys used for a specific Kaspersky application

Viewing the list of devices where a Kaspersky application is not activated

Revoking consent with an End User License Agreement

Renewing licenses for Kaspersky applications

Use of Kaspersky Security Center Cloud Console after the license expiration

Licensing definitions

Adding a license key to the Administration Server repository

Licenses and the minimum number of devices for each license

Licensing of Kaspersky Security Center Cloud Console

Page top

[Topic 195469]

Viewing the list of devices where a Kaspersky application is not activated

You can view the list of all the devices on which a Kaspersky application is installed but not activated (for example, a license is missing or has expired).

To view the devices where a Kaspersky application is not activated:

  1. In the main menu, go to Assets (Devices) → Tasks.

    The list of tasks is displayed.

  2. Click the name of the Update task related to the Kaspersky application in question.

    The task properties window is displayed with several named tabs.

  3. In the task properties window, select the Results section.

    In the Device or secondary Server column are displayed the devices on which the task was successful.

  4. Sort the Device or secondary Server column.

    In the Device or secondary Server column are displayed the devices on which the task was successful. The devices where the task failed because of a missing license are devices where the application is not activated.

See also:

Licensing of Kaspersky Security Center Cloud Console

About the trial mode of Kaspersky Security Center Cloud Console

Using Kaspersky Marketplace to choose Kaspersky business solutions

Licenses and the minimum number of devices for each license

Events of the licensing limit exceeded

Methods of distribution of the activation codes to the managed devices

Adding a license key to the Administration Server repository

Deploying a license key to client devices

Automatic distribution of a license key

Viewing information about license keys in use in the Administration Server repository

Viewing information about the license keys used for a specific Kaspersky application

Deleting a license key from the repository

Revoking consent with an End User License Agreement

Renewing licenses for Kaspersky applications

Use of Kaspersky Security Center Cloud Console after the license expiration

Licensing definitions

Licenses and the minimum number of devices for each license

Licensing of Kaspersky Security Center Cloud Console

Page top

[Topic 199089]

Revoking consent with an End User License Agreement

If you decide to stop protecting some of your client devices, you can revoke the End User License Agreement (EULA) for any managed Kaspersky application. You must uninstall the selected application and its installation packages before revoking its EULA. The installation packages must be deleted from the Administration Server and its virtual Administration Servers.

The EULAs that were accepted on a virtual Administration Server can be revoked on the virtual Administration Server or on the primary Administration Server. The EULAs that were accepted on a primary Administration Server can be revoked only on the primary Administration Server.

To revoke a EULA for managed Kaspersky applications:

  1. In the main menu, click the settings icon () next to the name of the required Administration Server.

    The Administration Server properties window opens.

  2. On the General tab of the Administration Server properties window, select the End User License Agreements section.

    A list of EULAs—accepted upon creation of installation packages or at the seamless installation of updates—is displayed.

  3. In the list, select the EULA that you want to revoke.

    You can view the following properties of the EULA:

    • Date when the EULA was accepted
    • Name of the user who accepted the EULA
    • Whether or not the EULA can be revoked
  4. Click the acceptance date of any EULA to open its properties window that displays the following data:
    • Name of the user who accepted the EULA
    • Date when the EULA was accepted
    • Unique identifier (UID) of the EULA
    • Full text of the EULA
    • List of objects (installation packages, seamless updates) linked to the EULA, and their respective names and types
  5. In the lower part of the EULA properties window, click the Revoke License Agreement button.

    If the selected EULA can be revoked only by uninstalling the application or if this EULA can be revoked only on the primary Administration Server, a notification about this restriction is displayed instead of the Revoke License Agreement button.

    If there exist any objects (installation packages and their respective tasks) that prevent the EULA from being revoked, the notification about it is displayed. You cannot proceed with revocation until you delete these objects.

    In the window that opens, you are informed that you must first uninstall the Kaspersky application corresponding to the EULA.

  6. Click the button to confirm revocation.

The EULA is revoked. It is no longer displayed in the list of License Agreements in the End User License Agreements section. The EULA properties window closes; the application is no longer installed.

See also:

Licensing of Kaspersky Security Center Cloud Console

About the trial mode of Kaspersky Security Center Cloud Console

Using Kaspersky Marketplace to choose Kaspersky business solutions

Licenses and the minimum number of devices for each license

Events of the licensing limit exceeded

Methods of distribution of the activation codes to the managed devices

Adding a license key to the Administration Server repository

Deploying a license key to client devices

Automatic distribution of a license key

Viewing information about license keys in use in the Administration Server repository

Viewing information about the license keys used for a specific Kaspersky application

Deleting a license key from the repository

Viewing the list of devices where a Kaspersky application is not activated

Renewing licenses for Kaspersky applications

Use of Kaspersky Security Center Cloud Console after the license expiration

Licensing definitions

Licenses and the minimum number of devices for each license

Licensing of Kaspersky Security Center Cloud Console

Page top

[Topic 214791]

Renewing licenses for Kaspersky applications

You can renew a Kaspersky application license that has expired or is about to expire (in less than 30 days).

If the last license key is expired, Kaspersky Security Center Cloud Console automatically deletes your workspace after 90 days. As a result, you cannot manage the protection of your network by means of Kaspersky Security Center Cloud Console. You also permanently lose your data from Kaspersky Security Center Cloud Console. We recommend that you renew outdated license keys or add new ones to the Administration Server repository to keep your workspace.

To view a notification about an expired license or a license that is about to expire:

  1. Do either of the following:
    • In the main menu, go to OperationsLicensingKaspersky licenses.
    • In the main menu, go to Monitoring & reporting → Dashboard, and then click the View expiring licenses link next to a notification.

    The Kaspersky licenses window opens, where you can view and renew the expiring and expired licenses.

  2. If you want to renew a license, click the Renew license link next to the required license.

    By clicking a license renewal link, you agree to transfer the following data to Kaspersky: software ID, software version, software localization, license ID, and an attribute that shows if the license was provided by a partner company. The data is required to determine the renewal terms of your license.

  3. In the window of the license renewal service that opens follow the instructions to renew a license.

    The expiring license is renewed.

In Kaspersky Security Center Cloud Console, the notifications are displayed when a license is about to expire, according to the following schedule:

  • 30 days before the expiration
  • 7 days before the expiration
  • 3 days before the expiration
  • 24 hours before the expiration
  • When a license has expired

See also:

Licensing of Kaspersky Security Center Cloud Console

About the trial mode of Kaspersky Security Center Cloud Console

Using Kaspersky Marketplace to choose Kaspersky business solutions

Licenses and the minimum number of devices for each license

Events of the licensing limit exceeded

Methods of distribution of the activation codes to the managed devices

Adding a license key to the Administration Server repository

Deploying a license key to client devices

Automatic distribution of a license key

Viewing information about license keys in use in the Administration Server repository

Viewing information about the license keys used for a specific Kaspersky application

Deleting a license key from the repository

Viewing the list of devices where a Kaspersky application is not activated

Revoking consent with an End User License Agreement

Use of Kaspersky Security Center Cloud Console after the license expiration

Licensing definitions

Licenses and the minimum number of devices for each license

Page top

[Topic 195207]

Use of Kaspersky Security Center Cloud Console after the license expiration

After the license expiration, Kaspersky might grant you the use of Kaspersky Security Center Cloud Console for up to 90 days without limitations. During this period, the Administration Server, Network Agent, and Kaspersky Security Center Cloud Console web interface work without limitations. Kaspersky Security Center Cloud Console also sends KSN statistics to Kaspersky in accordance with the current KSN access settings. The managed applications work with only limited functionality (for details, refer to the documentation for these applications).

When the license has been expired for 90 days, Kaspersky Security Center Cloud Console automatically deletes your workspace. If you want to keep the workspace, renew at least one expired license key or add a new one to the repository.

Page top

[Topic 200780]

Licensing definitions

This section contains definitions for concepts related to licensing of Kaspersky applications managed via Kaspersky Security Center Cloud Console.

In this section

About the license

About the license certificate

About the license key

About the activation code

About the subscription

Page top

[Topic 69240]

About the license

A license is a time-limited right to use Kaspersky Security Center Cloud Console, granted under the terms of the signed License Contract (End User License Agreement).

The scope of services and validity period depend on the license under which the application is used.

The following license types are provided:

  • Trial

    A free license intended for trying out the application. A trial license usually has a short term.

    When a trial license expires, all Kaspersky Security Center Cloud Console features become disabled. To continue using the application, you need to purchase a commercial license.

    You can use the application under a trial license for only one trial period.

  • Commercial

    A paid license.

    When a commercial license expires, key features of the application become disabled. To continue using Kaspersky Security Center Cloud Console, you must renew your commercial license. After a commercial license expires, you cannot continue using the application and must remove it from your device.

    We recommend renewing your license before it expires, to ensure uninterrupted protection against all security threats.

Page top

[Topic 73976]

About the license certificate

A license certificate is a document that you receive along with a key file or an activation code.

A license certificate contains the following information about the license provided:

  • License key or order number
  • Information about the user who has been granted the license
  • Information about the application that can be activated under the license provided
  • Limit of the number of licensing units (e.g., devices on which the application can be used under the license provided)
  • License validity start date
  • License expiration date or license term
  • License type
Page top

[Topic 69295]

About the license key

A license key is a sequence of bits that you can apply to activate and then use the application in accordance with the terms of the End User License Agreement. License keys are generated by Kaspersky specialists.

You can add a license key to the application by entering an activation code. The license key is displayed in the application interface as a unique alphanumeric sequence after you add it to the application.

The license key may be blocked by Kaspersky in case the terms of the License Agreement have been violated. If the license key has been blocked, you need to add another one if you want to use the application.

A license key may be active or additional (or reserve).

An active license key is a license key that is currently used by the application. An active license key can be added for a trial or commercial license. The application cannot have more than one active license key.

An additional (or reserve) license key is a license key that entitles the user to use the application, but is not currently in use. The additional license key automatically becomes active when the license associated with the current active license key expires. An additional license key can be added only if an active license key has already been added.

A license key for a trial license can be added as an active license key. A license key for a trial license cannot be added as an additional license key.

Page top

[Topic 111091]

About the activation code

Activation code is a unique sequence of 20 alphanumeric characters. You enter an activation code to add a license key that activates Kaspersky Security Center Cloud Console. You receive the activation code through the email address that you specified after purchasing Kaspersky Security Center Cloud Console or after ordering the trial version of Kaspersky Security Center Cloud Console.

To activate the application by using the activation code, you need internet access to establish connection with Kaspersky activation servers. If access to the servers using system DNS is not possible, the application uses public DNS servers.

If the application was activated with an activation code, the application in some cases sends regular requests to Kaspersky activation servers in order to check the current status of the license key. You must provide the application internet access to make it possible to send requests.

If you have lost your activation code after installing the application, contact the Kaspersky partner from whom you purchased the license.

You cannot use key files for activating managed applications; only activation codes are accepted.

See also:

Initial configuration of Kaspersky Security Center Cloud Console

Page top

[Topic 91039]

About the subscription

Subscription to Kaspersky Security Center Cloud Console is an order for use of the application under the selected settings (subscription expiration date, number of protected devices). You can register your subscription to Kaspersky Security Center Cloud Console with your service provider (for example, your internet provider). A subscription can be renewed manually or in automatic mode; also, you can cancel it.

A subscription can be limited (for example, one-year) or unlimited (with no expiration date). To continue using Kaspersky Security Center Cloud Console after a limited subscription expires, you must renew it. An unlimited subscription is renewed automatically if it has been prepaid to the service provider in due dates.

When a limited subscription expires, you may be provided a grace period for renewal during which the application continues to function. The availability and duration of the grace period is defined by the service provider.

To use Kaspersky Security Center Cloud Console under subscription, you must apply the activation code received from the service provider.

You can apply a different activation code for Kaspersky Security Center Cloud Console only after your subscription expires or when you cancel it.

Depending on the service provider, the set of possible actions for subscription management may vary. The service provider might not provide a grace period for subscription renewal and so the application loses its functionality.

Activation codes purchased under subscription cannot be used for activating earlier versions of Kaspersky Security Center Cloud Console.

When the application is used under subscription, Kaspersky Security Center Cloud Console automatically attempts to access the activation server at specified time intervals until the subscription expires. If access to the server using system DNS is not possible, the application uses public DNS servers. You can renew your subscription on the service provider's website.

Page top

[Topic 175956]

Data provision

Kaspersky Security Center Cloud Console enables the user to identify and control devices (and the device owners) connected to Kaspersky Security Center Cloud Console, by means of the features of managed applications.

Data provision methods:

  1. The User enters data in the Kaspersky Security Center Cloud Console interface.
  2. Network Agent receives data from the device and transfers it to Administration Server.
  3. Network Agent receives data retrieved by the Kaspersky managed application and transfers it to Administration Server. The list of data processed by Kaspersky managed applications is provided in the Help of the corresponding applications.
  4. Data is transferred from secondary Administration Servers running on-premises.

Kaspersky Security Center Cloud Console automatically deletes workspaces 30 days after the trial license term expires, 90 days after the commercial license term expires.

After the license term expires, Kaspersky saves User's data related to alerts and incidents in the User's workspaces for 30 days.

Under the current license, the storage term for alerts and for incidents is 360 days. After this period, the older alerts and the older incidents are automatically deleted.

The final deletion of the data listed in this section may take up to 24 hours.

In this section

Data sent to Kaspersky servers

Data necessary for the functioning of the workspace

Data necessary for the functioning of managed applications

User data processed locally

About legal documents of Kaspersky Security Center Cloud Console

Page top

[Topic 195122]

Data sent to Kaspersky servers

Data sent during activation

When using the Activation Code to activate Software, in order to verify the legitimacy of using the software, the User agrees to periodically provide Kaspersky with the following information:

  • Activation code
  • Unique activation identifier for the current license

Kaspersky can also use this information to generate statistical information about the distribution and use of Kaspersky software.

Data sent during updating

Upon receipt of Updates from the Rightholder's update servers, in order to improve the quality of the update mechanism, the User agrees to periodically provide the following information to Kaspersky:

  • Software ID received from the license
  • Full version of the software
  • Software license ID
  • Software installation ID (PCID)
  • ID of the software update startup

Kaspersky can also use this information to generate statistical information about the distribution and use of Kaspersky software.

Data for ensuring uninterrupted operation, efficient work, and verifying the legitimate use of Kaspersky Security Center Cloud Console

The following information can be used for the specified purpose:

  • Names and versions of Kaspersky security applications connected to the workspace, as well as number of devices on which these security applications are installed.
  • Number of devices with Kaspersky security applications installed that have been connected to all workspaces and distribution of these connected devices by type.
  • Workspace identifier, company identifier, workspace country and region, and workspace creation date.
  • Number of users in the workspace, date of the last authentication in the workspace.
  • Details of the currently used license (license type, license limit on the number of devices, number of connected devices, and expiration date of the previously used license).

Data transferred when following the links in the interface of Kaspersky Security Center Cloud Console

Following the links in the Administration Console or Kaspersky Security Center Cloud Console, the User agrees to the automatic transfer of the following data:

  • Kaspersky Security Center Cloud Console localization
  • License ID
  • Whether the license was purchased through a partner

The list of data provided via each link depends on the purpose and location of the link.

Page top

[Topic 195127]

Data necessary for the functioning of the workspace

Kaspersky Security Center Cloud Console processes the following data:

  1. Details of devices detected on the organization's network

    Network Agent receives the data listed below from the networked devices and transfers it to Administration Server:

    1. Technical specifications of the detected device and its components required for device identification that have been received by means of network polling:
      • Active Directory polling:

        Active Directory devices: distinguished name of the device; Windows domain name received from the domain controller; device name in the Windows environment; NetBIOS domain name; DNS domain and DNS name of the device; Security Account Manager (SAM) account (name for logging in to the system used for support of clients and servers running earlier operating system versions, such as Windows NT 4.0, Windows 95, Windows 98, and LAN Manager); distinguished name of the domain; distinguished names of the groups to which the device belongs; distinguished name of the user managing the device; and globally unique identifier (GUID) and parent GUID of the device.

        When the Active Directory network is polled, the following types of data are also processed for the purpose of displaying information about the managed infrastructure and use of this information by the user, for example, during protection deployment:

      • Active Directory organizational units: distinguished name of the organizational unit; distinguished name of the domain; GUID and parent GUID of the organizational unit.
      • Active Directory domains: Windows domain name received from the domain controller; DNS domain; GUID of the domain.
      • Active Directory users: display name of the user; distinguished name of the user; distinguished name of the domain; name of the user's organization; name of the department where the user works; distinguished name of another user acting as the user's manager; full name of the user; SAM account; Email address; alternate email address; main phone number; alternate phone number; mobile phone number; user's position name; distinguished names of the groups to which the user belongs; user globally unique identifier (GUID); user security identifier (SID) (unique binary value used to identify the user as a security principal); and user principal name (UPN)—internet-style login name for a user based on the Internet standard RFC 822. The UPN is shorter than the distinguished name and easier to remember. By convention, the UPN maps to the user email name.
      • Active Directory groups: distinguished name of the group; email address; distinguished name of the domain; SAM account; distinguished names of other groups to which the group belongs; SID group; group GUID.
    2. Samba domain polling:

      Samba devices: distinguished name of the device; domain name received from the domain controller; NetBIOS device name; NetBIOS domain name; DNS domain and DNS name of the device; Security Account Manager (SAM) account; distinguished name of the domain; distinguished names of the groups to which the device belongs; distinguished name of the user managing the device; globally unique identifier (GUID) and parent GUID of the device.

      • Samba organization units: distinguished name of the organizational unit; distinguished name of the domain; GUID and parent GUID of the organizational unit.
      • Samba domain: domain name received from the domain controller; DNS domain; GUID of the domain.
      • Samba users: display name of the user; distinguished name of the user; name of the user's organization; name of the department where the user works; distinguished name of another user acting as the user's manager; full name of the user; SAM account; Email address; alternate email address; main phone number; alternate phone number; mobile phone number; user's position name; distinguished names of the groups to which the user belongs; user globally unique identifier (GUID); user security identifier (SID) (unique binary value used to identify the user as a security principal); user principal name (UPN)—internet-style login name for a user based on the Internet standard RFC 822. The UPN is shorter than the distinguished name and easier to remember. By convention, the UPN maps to the user email name.
      • Samba groups: distinguished name of the group; email address; distinguished name of the domain; SAM account; distinguished names of other groups to which the group belongs; SID group; group GUID.
    3. Windows domain polling:
      • Name of the Windows domain or workgroup
      • Device NetBIOS name
      • DNS domain and DNS name of the device
      • Device name and description
      • Device visibility on the network
      • Device IP address
      • Device type (workstation, server, SQL Server, domain controller, etc.)
      • Type of operating system on the device
      • Version of the device operating system
      • Time the information about the device was last updated
      • Time the device was last visible on the network
    4. IP range polling:
      • Device IP address
      • Device DNS name or NetBIOS name
      • Device name and description
      • Device MAC address
      • Time the device was last visible on the network
  2. Details of managed devices.

    Network Agent transfers the data listed below from the device to Administration Server. The user enters the display name and description of the device in the Kaspersky Security Center Cloud Console interface:

    1. Technical specifications of the managed device and its components required for device identification:
      • Display name (generated on the basis of the NetBIOS name, can be modified manually) and description of the device (entered manually)
      • Windows domain name and type (Windows NT domain / Windows workgroup)
      • Device name in the Windows environment
      • DNS domain and DNS name of the device
      • Device IP address
      • Device subnet mask
      • Device network location
      • Device MAC address
      • Device serial number (if available)
      • Type of operating system on the device
      • Whether the device is a virtual machine together with hypervisor type
      • Whether the device is a dynamic virtual machine as part of Virtual Desktop Infrastructure (VDI)
      • Device GUID
      • Network Agent instance ID
      • Network Agent installation ID
      • Network Agent permanent ID
    2. Other specifications of managed devices and their components required for audit of managed devices and for making decisions about whether specific patches and updates are applicable:
      • Windows Update Agent (WUA) status
      • Operating system architecture
      • Operating system vendor
      • Operating system build number
      • Operating system release ID
      • Operating system location folder
      • If the device is a virtual machine—the virtual machine type
      • Device response waiting time
      • Whether Network Agent is running in stand-alone mode
    3. Detailed information about activity on managed devices:
      • Date and time of the last update
      • Date and time the device was last visible on the network
      • Restart waiting status ("Restart is required.")
      • Time the device was turned on
    4. Details of device user accounts and their work sessions
    5. Distribution point operation statistics if the device is a distribution point:
      • Date and time the distribution point was created
      • Work folder name
      • Work folder size
      • Number of synchronizations with the Administration Server
      • Date and time the device last synchronized with the Administration Server
      • Number and total size of transferred files
      • Number and total size of files downloaded by clients
      • Volume of data downloaded by clients using Transmission Control Protocol (TCP)
      • Volume of data sent to clients using multicasting
      • Volume of data downloaded by clients using multicasting
      • Number of multicast distributions
      • Total volume of multicast distribution
      • Number of synchronizations with clients after the last synchronization with the Administration Server
    6. Name of the virtual Administration Server which manages the device
    7. Details of cloud devices:
      • Cloud Region
      • Virtual Private Cloud (VPC)
      • Cloud availability zone
      • Cloud subnet
      • Cloud placement group
    8. Details of mobile devices. The managed application transfers this data from the mobile device to Administration Server. The full list of data is available in the documentation of the managed application.
  3. Details of Kaspersky applications installed on the device.

    The managed application transfers data from the device to Administration Server through Network Agent:

    1. Kaspersky managed applications and Kaspersky Security Center Cloud Console components installed on the device
    2. Settings of Kaspersky applications installed on the managed device:
      • Kaspersky application name and version
      • Status
      • Real-time protection status
      • Last device scan date and time
      • Number of threats detected
      • Number of objects that failed to be disinfected
      • Tasks for Kaspersky security application
      • Availability and status of the application components
      • Time of last update and version of anti-virus databases
      • Details of Kaspersky application settings
      • Information about the active license keys
      • Information about the reserve license keys
      • Application installation date
      • Application installation ID
    3. Application operation statistics: events related to changes in the status of Kaspersky application components on the managed device and to performance of tasks initiated by the application components
    4. Device status defined by the Kaspersky application
    5. Tags assigned by the Kaspersky application
    6. Set of installed and applicable updates for the Kaspersky application:
      • Display name, version, and language of the application
      • Internal name of the application
      • Application name and version from the registry key
      • Application installation folder
      • Patch version
      • List of installed application autopatches
      • Whether the application is supported by Kaspersky Security Center Cloud Console
      • Whether the application is installed on a cluster
    7. Details of data encryption errors on devices: error ID, time of occurrence, operation type (encryption/decryption), error description, file path, description of encryption rule, device ID, and user name
  4. Events of Kaspersky Security Center Cloud Console components and Kaspersky managed applications.

    Network Agent transfers data from the device to Administration Server.

    The description of an event can contain the following data:

    1. Device name
    2. Device user name
    3. Name of the administrator who connected to the device remotely
    4. Name, version, and vendor of the application installed on the device
    5. Path to the application installation folder on the device
    6. Path to the file on the device and file name
    7. Application name and command-line parameters under which the application was run
    8. Patch name, patch file name, patch ID, level of the vulnerability fixed by the patch, description of the patch installation error
    9. Device IP address
    10. Device MAC address
    11. Device restart status
    12. Name of the task that published the event
    13. Whether the device switched to stand-alone mode and reason for switching
    14. Information about the security issue on the device: security issue type, security issue name, severity level, security issue description, security issue details transmitted by the Kaspersky application
    15. Size of free disk space on the device
    16. Whether the Kaspersky application is running in limited functionality mode, IDs of functional scopes
    17. Old and new value of the Kaspersky application setting
    18. Description of the error that occurred when the Kaspersky application or any of its components performed the operation
  5. Settings of Kaspersky Security Center Cloud Console components and Kaspersky managed applications presented in policies and policy profiles.

    The user enters data in the Kaspersky Security Center Cloud Console interface.

  6. Task settings of Kaspersky Security Center Cloud Console components and Kaspersky managed applications

    The user enters data in the Kaspersky Security Center Cloud Console interface.

  7. Data processed by the Vulnerability and patch management feature.

    Network Agent transfers the data listed below from the device to Administration Server:

    1. Details of applications and patches installed on managed devices (Applications registry). Applications can be identified on the basis of information about executable files detected on managed devices by the Application Control feature:
      • Application/patch ID
      • Parent application ID (for a patch)
      • Application/patch name and version
      • Whether the application/patch is an .msi file of Windows Installer
      • Application/patch vendor
      • Localization language ID
      • Application/patch installation date
      • Application installation path
      • Technical Support website of application/patch vendor
      • Technical Support phone number
      • ID of the installed application instance
      • Comment
      • Uninstallation key
      • Key for installation in silent mode
      • Patch classification
      • Web address for additional information about the patch
      • Registry key of the application
      • Application build number
      • User SID
      • Operating system type (Windows, Unix)
    2. Information about the hardware detected on managed devices (Hardware registry):
      • Device ID
      • Device type (motherboard, CPU, RAM, mass storage device, video adapter, sound card, network interface controller, monitor, optical disc device)
      • Device name
      • Description
      • Vendor
      • Serial number
      • Revision
      • Information about the driver: developer, version, description, and release date
      • Information about BIOS: developer, version, serial number, and release date
      • Chipset
      • Clock rate
      • Number of CPU cores
      • Number of CPU threads
      • CPU platform
      • Storage device rotation speed
      • RAM: type, part number
      • Video memory
      • Sound card codec
    3. Details of vulnerabilities in third-party software detected on managed devices:
      • Vulnerability identifier
      • Vulnerability severity level (Warning, High, Critical)
      • Vulnerability type (Microsoft, third-party)
      • Web address of the page on which the vulnerability is described
      • Time the vulnerability entry was created
      • Vendor name
      • Localized vendor name
      • Vendor ID
      • Application name
      • Localized name of the application
      • Application installation code
      • Application version
      • Application localization language
      • List of CVE identifiers from the vulnerability description
      • Kaspersky protection technologies blocking the vulnerability (File Threat Protection, Behavior Detection, Web Threat Protection, Mail Threat Protection, Host Intrusion Prevention, ZETA Shield)
      • Path to the object file in which the vulnerability was detected
      • Vulnerability detection time
      • IDs of the Knowledge Base articles from the vulnerability description
      • IDs of the security bulletins from the vulnerability description
      • List of updates for the vulnerability
      • Whether an exploit exists for the vulnerability
      • Whether malware exists for the vulnerability
    4. Details of updates available for third-party applications installed on managed devices:
      • Application name and version
      • Vendor
      • Application localization language
      • Operating system
      • List of patches according to installation sequence
      • Original version of the application to which the patch is applied
      • Application version after patch installation
      • Patch ID
      • Build number
      • Installation flags
      • License Agreements for the patch
      • Whether the patch is a prerequisite for installation of other patches
      • List of required installed applications and their updates
      • Sources of information about the patch
      • Additional information about the patch (addresses of web pages)
      • Web address for patch download, file name, version, revision, and SHA256
    5. Details of Microsoft updates found by the WSUS feature:
      • Update revision number
      • Microsoft update type (Driver, Software, Category, Detectoid)
      • Update importance level according to the Microsoft Security Response Center (MSRC) bulletin (Low, Medium, High, Critical)
      • IDs of the MSRC bulletins related to the update
      • IDs of articles in the MSRC Knowledge Base
      • Update name (header)
      • Update description
      • Whether the update installer is interactive
      • Installation flags
      • Update classification (Critical Updates, Definition Updates, Drivers, Feature Packs, Security Updates, Service Packs, Tools, Update Rollups, Updates, Upgrade)
      • Information about the application to which the update is applied
      • End User License Agreement (EULA) ID
      • EULA text
      • Whether the EULA must be accepted for update installation
      • Information about the associated updates (ID and revision number)
      • Update ID (Global Microsoft Windows update identity)
      • IDs of the superseded updates
      • Whether the update is hidden
      • Whether the update is mandatory
      • Update installation status (Not applicable, Not assigned for installation, Assigned, Installing, Installed, Failed, Restart is required, Not assigned for installation (new version))
      • CVE IDs for the update
      • Company that released the update, or the "Company missing" value
    6. List of Microsoft updates found by the WSUS feature that must be installed on the device.
  8. Information about executable files detected on managed devices by the Application Control feature (may be associated with information from the Applications registry). A full list of data is given in the section that describes data for devices managed through the corresponding application.

    The managed application transfers data from the device to Administration Server through Network Agent.

  9. Information about files placed in Backup. A full list of data is given in the section that describes data for devices managed through the corresponding application.

    The managed application transfers data from the device to Administration Server through Network Agent.

  10. Information about files requested by Kaspersky specialists for detailed analysis. A full list of data is given in the section that describes data for devices managed through the corresponding application.

    The managed application transfers data from the device to Administration Server through Network Agent.

  11. Information about the status and triggering of Adaptive Anomaly Control rules. A full list of data is given in the section that describes data for devices managed through the corresponding application.

    The managed application transfers data from the device to Administration Server through Network Agent.

  12. Information about devices (memory units, information transfer tools, information hardcopy tools, and connection buses) installed or connected to the managed device and detected by the Device Control feature. A full list of data is given in the section that describes data for devices managed through the corresponding application.

    The managed application transfers data from the device to Administration Server through Network Agent.

  13. Data about alerts:
    • Date and time of the first telemetry event in the alert
    • Date and time of the last telemetry event in the alert
    • Name of the triggered rule (the User enters this in the Kaspersky Security Center Cloud Console interface)
    • Alert status
    • Resolution (False Positive, True Positive, Low Priority)
    • ID and name of the user who is assigned for the alert
    • Unique ID in the Kaspersky Security Center Cloud Console database and the name of the device related to the events that are alert sources
    • SID and name of the user of the device related to the events that are alert sources
    • Observables, that is, observable data related to the events that are alert sources:
      • IP address
      • MD5 hash sum of the file and file path
      • Web address
      • Domain
    • Additional details of the object related to the alert (received from the application)
    • Comments to the alert:
      • Date and time when the comment was added
      • User who added the comment
      • Text of the comment
    • Alert changelog:
      • Date and time of the change
      • User who performed the change
      • Change description
  14. Data about security issues:
    • Date and time of the first event in the security issue
    • Date and time of the last event in the security issue
    • Security issue name (the user enters this in the Kaspersky Security Center Cloud Console interface)
    • Brief description of the security issue
    • Security issue priority
    • Security issue status
    • ID and name of the user assigned for the security issue
    • Resolution (False Positive, True Positive, Low Priority, Merged)
    • Comment to the security issue:
      • Date and time when the comment was added
      • User who added the comment
      • Text of the comment
    • Security issue changelog:
      • Date and time of the change
      • User who performed the change
      • Change description
  15. Data processed by the data encryption feature of Kaspersky applications.

    The managed application transfers the data listed below from the device to Administration Server through Network Agent. The user enters the description of the drive in the Kaspersky Security Center Cloud Console interface:

    1. List of drives on the devices:
      • Drive name
      • Encryption status
      • Drive type (boot drive, disk drive)
      • Drive serial number
      • Description
    2. Details of data encryption errors on the devices:
      • Date and time when the error occurred
      • Operation type (encryption, decryption)
      • Error description
      • File path
      • Rule description
      • Device ID
      • User name
      • Error ID
    3. Data encryption settings of the Kaspersky application.

      A full list of data is given in the section that describes data for devices managed through the corresponding application.

  16. Details of the entered activation codes.

    The User enters data in the Kaspersky Security Center Cloud Console interface.

  17. User accounts.

    The User enters the data listed below in the Kaspersky Security Center Cloud Console interface:

    1. Name
    2. Description
    3. Full name
    4. Email address
    5. Main phone number
    6. Password
    7. One-time security code for two-step verification
  18. Data required for user authentication using Active Directory:
    1. Active Directory Federation Services (ADFS) settings:
      • Main URL of the authentication provider
      • Trusted root certificates for ADFS
      • Client ID generated in ADFS
      • Secret key for protection of access to ADFS
      • Scope of the tokens
      • Active Directory domain with which the integration is performed
      • Name of the token field containing the user SID
      • Name of the token field containing the array of SIDs of the user's groups

      The User enters data in the Kaspersky Security Center Cloud Console interface.

  19. Data required to authenticate users by using Microsoft Entra ID.
    1. Microsoft Entra ID integration settings:
      • ID of the Microsoft Entra ID tenant
      • Client ID generated in the Microsoft Entra ID tenant
      • Client secret created in the Microsoft Entra ID tenant

    The user enters data in the Kaspersky Security Center Cloud Console interface.

    1. Data about users and groups in the Microsoft Entra ID tenant, which Kaspersky Security Center Cloud Console receives as a result of the Microsoft Entra ID polling:
      • Data about users in the Microsoft Entra ID tenant: user object identifier; user security identifier; user display name; name of the user's organization; name of the department in which the user works; user position; email address; primary phone number; mobile phone number; user login; names of groups to which the user belongs.
      • Data about users created in Microsoft Entra ID as a result of synchronization with on-premises Active Directory: user security identifier in on-premises Active Directory; domain name in on-premises Active Directory; user login in on-premises Active Directory; SAM account of the user in on-premises Active Directory; distinguished user name in on-premises Active Directory.
      • Data about groups in the Microsoft Entra ID tenant: group object identifier; group security identifier; group display name; email address; names of other groups to which the group belongs.
      • Data about groups created in Microsoft Entra ID as a result of synchronization with on-premises Active Directory: the security identifier of the group in on-premises Active Directory; SAM account of the group in on-premises Active Directory.
  20. Revision history of management objects: Administration Server, Administration group, Policy, Task, User / security group, Installation package.
    1. The User enters the data listed below in the Kaspersky Security Center Cloud Console interface:
      • Administration Server
      • Administration group
      • Policy
      • Task
      • User / Security group
      • Installation package
    2. IP address of the device on which the User created a revision. Administration Server detects the IP address automatically.
  21. Registry of deleted management objects.

    The User enters data in the Kaspersky Security Center Cloud Console interface.

  22. Installation packages created from the file, as well as installation settings.

    The User enters data in the Kaspersky Security Center Cloud Console interface.

  23. Data required for the display of Kaspersky announcements in Kaspersky Security Center Cloud Console:
    1. Information about managed Kaspersky applications used by the User: application ID, full version number.
    2. The User's localization of the Kaspersky Security Center Cloud Console interface.
    3. Information about the activation of the Software on the Device: Software license ID; Software license term; Software license expiration date and time; type of Software license used; Software subscription type; Software subscription expiration date and time; current status of the Software subscription; reason of current/changing status of Software subscription; ID of the price list item through which the Software license was purchased.
    4. Information about the legal agreement accepted by the User while using the Software: type of the legal agreement; version of the legal agreement; flag indicating whether the user has accepted the terms of the legal agreement.
    5. Information about the announcements received from the Rightholder: announcement ID; time of receipt of the announcement; status of receiving the announcement.

    The User enters data in the Kaspersky Security Center Cloud Console interface.

  24. Kaspersky Security Center Cloud Console user settings.

    The User enters the data listed below in the Kaspersky Security Center Cloud Console interface:

    1. User interface localization language
    2. User interface theme
    3. Display settings of the monitoring panel
    4. Information about the status of notifications: Already read / Not yet read
    5. Status of columns in spreadsheets: Show/Hide
    6. Tutorial progress
  25. Data received when using the Remote diagnostics feature on a managed device: trace files, system information, details of Kaspersky applications installed on the device, dump files, log files, results of running diagnostic scripts received from Technical Support.
  26. Data that the User enters in the Kaspersky Security Center Cloud Console interface:
    1. Administration group name when creating a hierarchy of administration groups
    2. Email address when configuring email notifications
    3. Tags for devices and tagging rules
    4. Tags for applications
    5. User categories of applications
    6. Role name when assigning a role to a user
    7. Information about subnets: subnet name, description, address, and mask
    8. Settings of reports and selections
    9. Any other data entered by the User
  27. Data received from a secondary Administration Server deployed on-premises.

    The data processed by the Kaspersky Security Center Administration Server is described in Kaspersky Security Center Online Help.

    When connecting a Kaspersky Security Center Administration Server deployed on-premises as a secondary in relation to Kaspersky Security Center Cloud Console, Kaspersky Security Center Cloud Console processes the following types of data from the secondary Administration Server:

    1. Information about the devices on the organization's network received as a result of device discovery in the Active Directory network or Windows network, or through scanning of IP intervals
    2. Information about the Active Directory organizational units, domains, users, and groups received as a result of Active Directory network polling
    3. Information about managed devices, their technical specifications, including those required for device identification, accounts of device users and their working sessions
    4. Information about mobile devices transferred by using the Exchange ActiveSync protocol
    5. Information about mobile devices transferred by using the iOS MDM protocol
    6. Details of Kaspersky applications installed on the device: settings, operation statistics, device status defined by the application, installed and applicable updates, tags
    7. Information transferred with event settings from Kaspersky Security Center components and Kaspersky managed applications
    8. Settings of Kaspersky Security Center components and Kaspersky managed applications presented in policies and policy profiles
    9. Task settings of Kaspersky Security Center components and Kaspersky managed applications
    10. Data processed by the Vulnerability and patch management feature: details of applications and patches; information about the hardware; details of vulnerabilities in third-party software detected on managed devices; details of updates available for third-party applications; details of Microsoft updates found by the WSUS feature
    11. User categories of applications
    12. Details of executable files detected on managed devices by the Application Control feature
    13. Details of files placed in Backup
    14. Details of files placed in Quarantine
    15. Details of files requested by Kaspersky specialists for detailed analysis
    16. Information about the status and triggering of Adaptive Anomaly Control rules
    17. Details of devices (memory units, information transfer tools, information hardcopy tools, and connection buses) installed or connected to the managed device and detected by the Application Control feature
    18. Encryption settings of the Kaspersky application: repository of encryption keys, device encryption status
    19. Information about the errors of data encryption performed on devices using the Data encryption feature of Kaspersky applications
    20. List of managed programmable logic controllers (PLCs)
    21. Details of the entered activation codes
    22. User accounts
    23. Revision history of management objects
    24. Registry of deleted management objects
    25. Installation packages created from the file, as well as installation settings
    26. Kaspersky Security Center Web Console user settings
    27. Any data that the user enters in the Administration Console or Kaspersky Security Center Cloud Console interface
    28. Certificate for secure connection of managed devices to the Kaspersky Security Center components
  28. Information uploaded from the managed device when using the Remote Diagnostics feature: diagnostic files (dump files, log files, trace files, etc.) and data contained in those files.
  29. Data required for Kaspersky Security Center Cloud Console integration with an SIEM system for event export:
    • Data required for connection and authentication:
      • SIEM system connection address and port
      • SIEM server authentication certificate
      • Trusted certificate and private key for client authentication of Kaspersky Security Center Cloud Console in the SIEM system

      The User enters data in the Kaspersky Security Center Cloud Console interface.

    • Data that Kaspersky Security Center Cloud Console receives from the SIEM system: public key of the SIEM server certificate for the SIEM server authentication.
  30. Data required for Kaspersky Security Center Cloud Console interaction with cloud environment:
    1. Amazon Web Services (AWS):
      • Access key ID of the IAM user account
      • Secret key of the IAM user account
    2. Microsoft Azure:
      • Azure Application ID
      • Azure subscription ID
      • Azure Application password
      • Account name for Azure repository
      • Account access key for Azure repository
    3. Google Cloud:
      • Google client email
      • Project ID
      • Private key

      The User enters data in the Kaspersky Security Center Cloud Console interface.

  31. Data transferred by an unsupported Kaspersky application

    When you install Network Agent on a device that has a Kaspersky application installed but not supported by Kaspersky Security Center Cloud Console, this Kaspersky application will still transfer data to Kaspersky Security Center Cloud Console. (The list of data is provided in the "About data provision" section of the Help system of the application.) However, Kaspersky Security Center Cloud Console will not be able to process the data transferred by the unsupported application in the way that the process is described for the main functionality of Kaspersky Security Center Cloud Console.

    The list of supported Kaspersky applications is presented in Kaspersky Security Center Cloud Console Online Help.

  32. Statistical information about user attempts to gain access to cloud services.

    A managed application transfers data from the device to Administration Server through Network Agent. For the full list of transferred data, refer to Help of the managed application.

  33. Data for creating a threat development chain.

    A managed application transfers data from the device to Administration Server through Network Agent. For the full list of transferred data, refer to Help of the managed application.

  34. Data required for integration of Kaspersky Security Center with the Kaspersky Managed Detection and Response service.

    Token for the integration initiation, integration token, and user session token. The User enters the token to initiate the integration in the Kaspersky Security Center Cloud Console interface. The Kaspersky Managed Detection and Response service transfers both the integration token and user session token through the MDR plug-in.

Page top

[Topic 195128]

Data necessary for the functioning of managed applications

The following managed applications transfer data from the device to Administration Server through Network Agent:

  • Kaspersky Endpoint Security for Windows
  • Kaspersky Endpoint Security for Linux
  • Kaspersky Endpoint Security for Mac
  • Kaspersky Endpoint Agent
  • Kaspersky Security for Windows Server
  • Kaspersky Security for Mobile
  • Kaspersky Embedded Systems Security for Windows
  • Kaspersky Embedded Systems Security for Linux

The list of processed data is published at https://ksc.kaspersky.com/Home/LegalDocuments, in the Kaspersky Security Center Cloud Console Data Processing Agreement. On the legal documents webpage, find the text block named Kaspersky Security Center Cloud Console Agreement, and then scroll down the text block to the Data for devices managed through the relevant managed application. You can also use your browser's standard Find function with the same purpose.

See also:

Compatible Kaspersky applications and solutions

Page top

[Topic 195132]

User data processed locally

The only Kaspersky Security Center component that can be deployed locally in a Kaspersky Security Center Cloud Console is Network Agent.

User data list processed locally:

  • All data listed in the User Data section processed within the framework and infrastructure of Kaspersky, except for data that the administrator enters through the Kaspersky Security Center Cloud Console interface
  • Kaspersky Event Log of Network Agent
  • Traces of Network Agent
  • Logs, including logs created by the Network Agent installer, Kaspersky Security Center utilities

The dump, log, and trace files of Network Agent contain random data and may contain personal data. Files are stored unencrypted on the device on which Network Agent is installed. Files are not transferred to Kaspersky automatically. The user can transfer this data to Kaspersky manually at the request of the Technical Support to solve problems in the operation of Kaspersky Security Center.

Page top

[Topic 179583]

About legal documents of Kaspersky Security Center Cloud Console

To use Kaspersky Security Center Cloud Console, you must read and express your agreement with the terms and conditions of the legal documents specified on the Kaspersky Security Center Cloud Console website. You can view the terms and conditions of AO Kaspersky Lab Privacy Policy for websites when you sign in to Kaspersky Security Center Cloud Console to manage a workspace. You can read Kaspersky Security Center Cloud Console Agreement and Kaspersky Security Center Cloud Console Data Processing Agreement when you create a company workspace.

Please carefully read the texts of all the legal documents before you start using Kaspersky Security Center Cloud Console.

End User License Agreement for Kaspersky applications

The End User License Agreement (hereinafter also referred to as License Agreement or EULA) is a binding agreement between you and AO Kaspersky Lab stipulating the terms under which you may use the Kaspersky applications.

You can view the terms of the End User License Agreement by using the following methods:

  • In the window which is displayed during Kaspersky application installation package creation.
  • In the license.txt file, in the Kaspersky application installation folder, on the managed device.

You can revoke your acceptance of the End User License Agreement at any time.

If you do not accept the terms of the License Agreement for a Kaspersky application, you cannot use this application.

Page top

[Topic 245736]

Hardening Guide

Kaspersky Security Center Cloud Console is an application hosted and maintained by Kaspersky. You do not have to install Kaspersky Security Center Cloud Console on your computer or server. Kaspersky Security Center Cloud Console enables the administrator to install Kaspersky security applications on devices on a corporate network, remotely run scan and update tasks, and manage the security policies of managed applications.

Kaspersky Security Center Cloud Console is designed for centralized execution of basic administration and maintenance tasks on an organization's network. The application provides the administrator access to detailed information about the organization's network security level. Kaspersky Security Center Cloud Console allows you to configure all components of protection built by using Kaspersky applications.

Kaspersky Security Center Cloud Console has full access to protection management of client devices and is the most important component of the organization's security system. Therefore, increased protection methods are required for Kaspersky Security Center Cloud Console.

The Hardening Guide describes recommendations and features of configuring Kaspersky Security Center Cloud Console and its components, aimed to reduce the risks of its compromise.

The Hardening Guide contains the following information:

  • Configuring accounts to access Kaspersky Security Center Cloud Console
  • Managing protection of client devices
  • Configuring protection for managed applications
  • Transferring information to third-party applications

Before you start to work with Kaspersky Security Center Cloud Console, you will be prompted to read the brief version of the Hardening Guide.

Note that you cannot use Kaspersky Security Center Cloud Console until you confirm that you have read the Hardening Guide.

To read the Hardening Guide:

  1. Open Kaspersky Security Center Cloud Console and log in to it. Kaspersky Security Center Cloud Console checks whether you have confirmed reading the current version of the Hardening Guide.

    If you have not yet read the Hardening Guide, a window opens and displays a brief version of it.

  2. Do one of the following:
    • If you want to view the brief version of the Hardening Guide as a text document, click the Open in new window link.
    • If you want to view the full version of the Hardening Guide, click the Open the Hardening guide in Online Help link.
  3. After you read the Hardening Guide, select the I confirm that I have fully read and understand the Hardening guide check box, and then click the Accept button.

Now, you can work with Kaspersky Security Center Cloud Console.

When a new version of the Hardening Guide appears, Kaspersky Security Center Cloud Console will prompt you to read it.

In this section

Planning Kaspersky Security Center Cloud Console architecture

Accounts and authentication

Managing protection of client devices

Configuring protection for managed applications

Event transfer to third-party systems

Page top

[Topic 245772]

Planning Kaspersky Security Center Cloud Console architecture

In general, the choice of a centralized management architecture depends on the location of protected devices, access from adjacent networks, delivery schemes of database updates, and so on.

At the initial stage of architecture development, we recommend getting acquainted with the Kaspersky Security Center Cloud Console components and their interaction with each other, as well as with schemas for data traffic and port usage.

Based on this information, you can form an architecture that specifies:

Page top

[Topic 245774]

Accounts and authentication

Using two-step verification with Kaspersky Security Center Cloud Console

Kaspersky Security Center Cloud Console provides two-step verification for users.

Two-step verification can help you increase the security of your account in Kaspersky Security Center Cloud Console. When this feature is enabled, every time you sign in to Kaspersky Security Center Cloud Console with your email address and password, you enter an additional one-time security code. You can receive a one-time security code by SMS or by generating this code in your authenticator app (depending on the two-step verification method that you set up).

We strongly do not recommend installing the authenticator app on the same device from which the connection to Kaspersky Security Center Cloud Console is established. You can install an authenticator app on your mobile device.

Prohibition on saving the administrator password

If you use Kaspersky Security Center Cloud Console, we strongly do not recommend saving the administrator password in the browser installed on the user device.

If the browser is compromised, an intruder can gain access to the saved passwords. Also, if a user device with saved passwords is stolen or lost, an intruder can gain access to protected data.

Restricting the Main Administrator role membership

We recommend restricting the Main Administrator role membership.

By default, after a user creates a workspace, the Main Administrator role is assigned to this user. It is useful for management, but it is critical from a security point of view, because the Main Administrator role has an extensive range of privileges. The assignment of this role to users should be strictly regulated.

You can use the predefined user roles with a preconfigured set of rights to administer Kaspersky Security Center Cloud Console.

Configuring access rights to application features

We recommend using flexible configuration of access rights to the features of Kaspersky Security Center Cloud Console for each user or group of users.

Role-based access control allows the creation of standard user roles with a predefined set of rights and the assignment of those roles to users depending on their scope of duties.

The main advantages of the role-based access control model:

  • Ease of administration
  • Role hierarchy
  • Least privilege approach
  • Segregation of duties

You can assign built-in roles to certain employees based on their positions, or create completely new roles.

While configuring roles, pay attention to the privileges associated with changing the protection state of the Administration Server device and remote installation of third-party software:

  • Managing administration groups.
  • Operations with Administration Server.
  • Remote installation.
  • Changing the parameters for storing events and sending notifications.

    This privilege allows you to set notifications that run a script or an executable module on the Administration Server device when an event occurs.

Separate account for remote installation of applications

In addition to the basic differentiation of access rights, we recommend restricting the remote installation of applications for all accounts (except for the Main Administrator or another specialized account).

We recommend using a separate account for remote installation of applications. You can assign a role or permissions to the separate account.

Page top

[Topic 245787]

Managing protection of client devices

Automatic rules for moving devices between administration groups

We recommend restricting the use of automatic rules for moving devices between administration groups.

If you use automatic rules for moving devices, this may lead to propagation of policies that provide more privileges to the moved device than the device had before relocation.

Also, moving a client device to another administration group may lead to propagation of policy settings. These policy settings may be undesirable for distribution to guest and untrusted devices.

This recommendation does not apply for one-time initial allocation of devices to administration groups.

Security requirements for distribution points and connection gateways

Devices with Network Agent installed can act as a distribution point and perform the following functions:

  • Distribute updates and installation packages received from Administration Server to client devices within the group.
  • Perform remote installation of third-party software and Kaspersky applications on client devices.
  • Poll the network to detect new devices and update information about existing ones.
  • Act as a KSN proxy server for client devices.

Taking into account the available capabilities, we recommend protecting devices that act as distribution points from any type of unauthorized access (including physical).

Page top

[Topic 246284]

Configuring protection for managed applications

Configuring network protection

Ensure that you have completed the Kaspersky Security Center Cloud Console initial configuration scenario. This scenario also includes performing the steps of the quick start wizard.

When the quick start wizard is running, policies and tasks with default parameters are created. These parameters may not be optimal or may even be prohibited in your organization. Therefore, we recommend configuring the created policies and tasks, and create additional policies and tasks if necessary for your organization network.

Specifying the password for disabling protection and uninstalling the application

To prevent intruders from disabling Kaspersky security applications, we strongly recommend enabling password protection for disabling protection and deinstallation of Kaspersky security applications. You can set the password, for example, for Kaspersky Endpoint Security for Windows, Kaspersky Security for Windows Servers, Network Agent, and other Kaspersky applications. After you enable password protection, we recommend locking these settings by closing the "lock."

Specifying the password for manual connection of a client device to the Administration Server (klmover utility)

The klmover utility allows you to manually connect a client device to the Administration Server. When Network Agent is installed on a client device, the utility is automatically copied to the Network Agent installation folder.

To prevent intruders from moving devices out of your Administration Server's control, we strongly recommend enabling password protection for running the klmover utility. To enable password protection, select the Use uninstallation password option in the Network Agent policy settings.

Enabling the Use uninstallation password option also enables password protection for the Cleaner tool (cleaner.exe).

The klmover utility is used only for moving managed devices under management of a virtual Administration Server.

Using Kaspersky Security Network

In all policies of managed applications and in the properties of Kaspersky Security Center Cloud Console, we recommend enabling the use of Kaspersky Security Network (KSN) and accepting the KSN Statement. When you update or upgrade Kaspersky Security Center Cloud Console, you can accept the updated KSN Statement.

Discovering new devices

We recommend properly configuring device discovery settings: set up integration with Active Directory and specify IP address ranges for discovering new devices.

For security purposes, you can use the default administration group that includes all new devices and the default policies affecting this group.

Page top

[Topic 245779]

Event transfer to third-party systems

Monitoring and reporting

For timely response to security issues, we recommend configuring the monitoring and reporting features.

Export of events to SIEM systems

For fast detection of security issues before significant damage occurs, we recommend using event export in a SIEM system.

Email notifications of audit events

For timely response to emergencies, we recommend configuring Kaspersky Security Center Cloud Console to send notifications about the audit events, critical events, failure events, and warnings that it publishes.

Since these events are intra-system events, a small number of them can be expected, which is quite applicable for mailing.

Page top

[Topic 249191]

Interface of Kaspersky Security Center Cloud Console

Kaspersky Security Center Cloud Console is managed through the web interface.

The application window contains the following items:

  • Main menu in the left part of the window
  • Work area in the right part of the window

Main menu

The main menu contains the following sections:

Work area

The work area displays the information you choose to view in the sections of the application web interface window. It also contains control elements that you can use to configure how the information is displayed.

Page top

[Topic 256056]

Changing the language of the Kaspersky Security Center Cloud Console interface

You can select the language of the Kaspersky Security Center Cloud Console interface.

To change the interface language:

  1. In the main menu, go to SettingsLanguage.
  2. Select one of the supported localization languages.
Page top

[Topic 296464]

Changing the Kaspersky Security Center Cloud Console home page

The home page is displayed after you sign in to Kaspersky Security Center Cloud Console.

By default, the Home page settings tab of the Quick links section is set as the home page. If necessary, you can change the home page.

To change the home page:

  1. In the Quick links section, hover the mouse cursor over the item that you want to set as the home page.
  2. After the home () icon is displayed, click the icon.

The home page is changed, an appropriate message is displayed on the screen, and the item selected as a home page is marked with the home () icon.

The Marketplace and Settings sections cannot be set as a home page.

Page top

[Topic 272710]

Adding and removing bookmarks

You can add frequently used sections of Kaspersky Security Center Cloud Console to bookmarks to access them quickly from the Bookmarks section in the main menu.

If you did not add any section to bookmarks, the Bookmarks section is not displayed in the main menu.

You can add to bookmarks only the sections that display pages. For example, if you go to Assets (Devices)Managed devices, a page with the table of devices opens, which means you can add the Managed devices section to bookmarks. If a window or no element is displayed after you select the section in the main menu, then you cannot add such a section to bookmarks.

To add a section to bookmarks:

  1. In the main menu, hover the mouse cursor over the section you want to add to bookmarks.
  2. After the bookmark () icon is displayed, click the icon.

The section is displayed in the Bookmarks section.

The maximum number of sections that you can add to bookmarks is five.

To remove a section from bookmarks:

  1. In the main menu, go to the Bookmarks section.
  2. Hover the mouse cursor over the section you want to remove, and then click the bookmark () icon.

The section is removed from bookmarks.

You can also add and remove elements from bookmarks in the Quick links section by hovering the mouse cursor over them and clicking the bookmark () icon. The selected item will be marked with the bookmark () icon and displayed in the Bookmarks section in the main menu. If you want to remove the item from the bookmarks, click the bookmark () icon.

The Bookmarks section is displayed only in the main menu. It is never displayed on the Quick links page.

Page top

[Topic 153504]

Initial configuration of Kaspersky Security Center Cloud Console

This section outlines the main scenario for Kaspersky Security Center Cloud Console deployment starting with a workspace creation and finishing with the monitoring of the network protection status.

For information about deployment of Kaspersky Security Center running on-premises, refer to Kaspersky Security Center Online Help.

We recommend that you assign a minimum of one working day for completion of this scenario.

The scenario guides you through the following:

  • Starting work with a of your company as an administrator
  • Discovering devices on your network (if necessary, you will assign distribution points and manually install distribution packages on them)
  • Deploying managed Kaspersky applications on the client devices; configuring tools for network protection, monitoring, and regular updates of Kaspersky databases, software modules, and applications

When you complete this scenario, the network protection based on Kaspersky applications will be configured. You will be able to proceed to monitoring of the network protection status.

Prerequisites

Before you start:

Stages

Kaspersky Security Center Cloud Console configuration proceeds in stages:

  1. Configuring ports

    Make sure that all necessary ports are open for interaction between your network and the Kaspersky infrastructure. Also, if you plan to use the hierarchy of Administration Servers, make sure that all necessary ports are open for interaction involving the secondary Administration Server (or secondary Administration Servers) and client devices.

  2. Creating the workspace for your company

    Create an account, and then create a workspace for your company.

  3. Running quick start wizard

    Open and sign in to Kaspersky Security Center Cloud Console. When you sign in for the first time, you are automatically prompted to run the quick start wizard. You can also start the quick start wizard manually at any time.

    When the quick start wizard is complete, you will have installation packages of Network Agent and security applications. These installation packages are required for further deployment of Kaspersky Security Center Cloud Console.

  4. Deployment of Kaspersky applications

    Perform the scenario of initial deployment of Kaspersky applications. One of the scenario steps refers to the network polling operation. This operation is required to discover client devices of your network. Network polling and its settings are described in the scenario of discovering networked devices.

    If you are deploying Kaspersky Security for Windows Server, make sure that the databases for this application are up to date.

  5. Licensing Kaspersky security applications

    When Kaspersky security applications are deployed to the managed devices, the applications must be licensed by applying an activation code to each of the applications. Deploy your activation codes to the Kaspersky applications installed on the managed devices. You have several options to license Kaspersky security applications.

  6. Configuring network protection

    Perform the network protection configuration to fine-tune the policies and tasks created through the quick start wizard.

  7. Regular updating of Kaspersky databases, software modules, and applications

    To keep your network protected against viruses and other threats, you have to configure regular updates of Kaspersky databases, software modules, and applications.

  8. Updating third-party software and fixing third-party software vulnerabilities (optional)

    Kaspersky Security Center Cloud Console enables you to manage updates of Microsoft applications installed on client devices. You can also fix vulnerabilities in Microsoft applications through installation of required updates.

  9. Configuring tools for monitoring the network protection status

    Select and configure widgets, reports and other tools that allow you to monitor the network protection status.

When Kaspersky Security Center Cloud Console is deployed and configured, you can proceed to monitoring the network protection status.

See also:

Ports used by Kaspersky Security Center Cloud Console

Basic concepts

Architecture

Page top

[Topic 143156]

About workspace management in Kaspersky Security Center Cloud Console

Using Kaspersky Security Center Cloud Console, you can do the following:

  • Create an account.
  • Edit an account.
  • Register a company and create a workspace.
  • Edit information about the company and workspaces.
  • Delete a workspace and a company.
  • Delete an account.
Page top

[Topic 143188]

Getting started with Kaspersky Security Center Cloud Console

This section describes how to sign up for and start using Kaspersky Security Center Cloud Console.

Signing up for Kaspersky Security Center Cloud Console consists of the following steps:

  1. Creating and confirming an account.
  2. Registering a company and creating a workspace.

Page top

[Topic 239398]

Creating an account

This article describes how to create an

.

As an alternative, you can create an account on My Kaspersky, and then use it to sign in to Kaspersky Security Center Cloud Console and create your workspace.

Your My Kaspersky account must be created directly on the website and not by using an external authentication provider (like Google). Otherwise, you will not be able to use Kaspersky Security Center Cloud Console.

To create an account in Kaspersky Security Center Cloud Console:

  1. In your browser, go to Kaspersky Security Center Cloud Console.
  2. Click the Create an account button on the start page of Kaspersky Security Center Cloud Console.

    The Kaspersky Account portal opens.

  3. On the Sign up to enter Kaspersky Security Center Cloud Console page, enter the email address and password for your account (see the figure below).

    Sign up to enter Kaspersky Security Center Cloud Console window.

    Creating an account in Kaspersky Security Center Cloud Console

  4. Click the Privacy Policy link and carefully read the Privacy Policy text.
  5. If you are aware and agree that your data will be handled and transmitted (including to third countries) as described in the Privacy Policy and you confirm that you have fully read and understand the Privacy Policy, select the check box next to the text of consent to data processing in accordance with the Privacy Policy, and then click the Create button.

    If you do not accept the Privacy Policy, do not use Kaspersky Security Center Cloud Console.

  6. A message from Kaspersky is sent to the email address that you specified. The message contains a one-time security code.

    Open the email message, and then copy the one-time security code that it contains.

  7. Return to Kaspersky Account, and then paste the code to the entry field.

Creation of the account in Kaspersky Security Center Cloud Console is complete.

See also:

Granting access to your company and its workspaces

Page top

[Topic 143266]

Registering a company and creating a workspace

Immediately after the account is created, you can register a company and create a workspace for it.

If you want to protect more than 10,000 devices, you do not have to register a company and create a workspace on Kaspersky Security Center Cloud Console as described below. Instead, send a request to Kaspersky Technical Support. In the request, specify information about your company and the workspace that you want to create.

Before you start, make sure that you know the following:

  • The name of the company in which you intend to use the software solution.
  • The country in which the company is located. If the company is located in Canada, you must also know the province.
  • The total number of company computers and mobile devices that you want to protect.

To register a company and create a workspace in Kaspersky Security Center Cloud Console:

  1. In your browser, go to Kaspersky Security Center Cloud Console.
  2. Click the Sign in button on the start page of Kaspersky Security Center Cloud Console.
  3. Enter the email address and password that you specified when you created the account, and then click the Sign in button.

    The Create a workspace wizard starts. Proceed through the wizard by using the Next button.

  4. On the Step 01: Terms of Use of Kaspersky Security Center Cloud Console page of the wizard, do the following:
    1. Carefully read the Agreement, the Privacy Policy, and the Data Processing Agreement for the software solution.
    2. If you agree to the terms and conditions of the Agreement and the Data Processing Agreement and if you are aware and agree that your data will be handled and transmitted (including to third countries) as described in the Privacy Policy, and you confirm that you have fully read and understand the Privacy Policy, select the check boxes next to the three listed documents and click the Accept button.

      If you do not agree to the terms and conditions, do not use Kaspersky Security Center Cloud Console.

      If you click the Decline button, the workspace creation process will be terminated.

  5. On the Step 02: Company information page of the wizard, specify the main details of your company.

    Fill in the following fields:

    • Name of your company (required)

      Specify the name of the company in which you intend to use the software solution. You can enter a string up to 255 characters long. The string can contain upper- and lowercase characters, numerals, whitespaces, dots, commas, minuses, dashes, and underscores. The specified company name will be displayed in Kaspersky Security Center Cloud Console.

    • Additional company description field (optional)

      You may specify additional information about the company that you register. You can enter a string up to 255 characters long. The string can contain upper- and lowercase characters, numerals, whitespaces, dots, commas, minuses, dashes, and underscores.

  6. On the Step 03: Workspace information page of the wizard, specify the information about the workspace that you want to create for your company.

    Fill in the following required fields:

    • Workspace name. Specify the name of the workspace in which you intend to use the software solution. You can enter a string up to 255 characters long. The string can contain upper- and lowercase characters, numerals, whitespaces, dots, commas, minuses, dashes, and underscores. The specified workspace name will be displayed in Kaspersky Security Center Cloud Console.
    • Country. In the drop-down list, select the country in which your workspace is located. If you select Canada, also specify the province in the State drop-down list that appears below this field.
    • Number of devices. Enter the total number of computers and mobile devices that you want to protect in this workspace.

      In the entry field, you can enter a number from 300 to 10,000.

  7. On the Step 04: License for new workspace page of the wizard, do either of the following:
    • If you want to try Kaspersky Security Center Cloud Console, click the I want to request a trial workspace link.

      We recommend that you connect your own devices to your trial workspace and test any modifications to the settings, noting the results.

      You will not be able to switch a trial workspace to commercial mode by entering an activation code. To switch to commercial mode, you must delete the workspace and create it again.

    • If you want to use Kaspersky Security Center Cloud Console in the commercial mode, enter the activation code and click the Verify button.

Registration of a company and creation of a workspace in Kaspersky Security Center Cloud Console is complete.

After the workspace is prepared, you receive an email message with the link to access the workspace.

Page top

[Topic 134563]

Opening your Kaspersky Security Center Cloud Console workspace

Right after you create a workspace for Kaspersky Security Center Cloud Console, the workspace opens automatically. Later, you can open your workspace, as described in this section.

If you are an administrator of a virtual Administration Server, you have access only to the virtual Administration Server. After you sign in and open the workspace, Kaspersky Security Center Cloud Console provides you the interface of the virtual Administration Server. You cannot switch to the primary Administration Server or other secondary Administration Servers.

An administrator of a virtual Administration Server must have access to a single virtual Administration Server. If you do not have access rights on the primary Server and have access rights on multiple virtual Servers, you cannot sign in to Kaspersky Security Center Cloud Console.

To open your Kaspersky Security Center Cloud Console workspace:

  1. In your browser, go to Kaspersky Security Center Cloud Console.
  2. Sign in to your account on Kaspersky Security Center Cloud Console by specifying the user name and the password.
  3. If you set up two-step verification, enter the one-time security code that is either sent to you by SMS or generated in your authenticator app (depending on the two-step verification method that you set up).

    The portal page displays the company for which you are an administrator and the list of its workspaces.

  4. Click the name of the required workspace or the Go to workspace link to proceed to the workspace.

    Occasionally, a workspace may be unavailable due to maintenance. If this is the case, you will not be able to proceed to your Kaspersky Security Center Cloud Console workspace.

    You cannot open a workspace that is marked for deletion.

  5. If any of the Kaspersky Security Center Cloud Console legal documents have been changed since you accepted their terms and conditions, the portal page displays the changed documents.

    Do the following:

    1. Carefully read the displayed documents.
    2. If you agree to the terms and conditions of the displayed documents, select the check boxes next to the listed documents, and then click the I accept the terms button.

      If you do not agree to the terms and conditions, stop using the selected Kaspersky software solution.

      If you click the I decline button, the operation will be terminated.

Your Kaspersky Security Center Cloud Console workspace opens.

Page top

[Topic 271824]

Returning to the list of workspaces

After you open your workspace, you can go back to the portal page that has the list of workspaces registered under your account in Kaspersky Security Center Cloud Console.

To return to the list of workspaces,

In the main menu, go to your account settings, and then select Manage workspaces.

The portal page displays the company for which you are an administrator and the list of its workspaces. If you have Kaspersky Security Center Cloud Console open on several tabs, you are signed out on all tabs.

Page top

[Topic 177033]

Signing out of Kaspersky Security Center Cloud Console

When you have finished your work, you should securely close your current session by signing out of Kaspersky Security Center Cloud Console.

To sign out of Kaspersky Security Center Cloud Console,

In the main menu, go to your account settings, and then select Sign out.

Kaspersky Security Center Cloud Console is closed, and the account page is displayed. You can close this browser page, if necessary. All data from your workspace will be saved.

See also:

Opening your Kaspersky Security Center Cloud Console workspace

Page top

[Topic 143157]

Managing the company and the list of workspaces

This section describes how to view the company information and the list of workspaces registered under your account in Kaspersky Security Center Cloud Console, change information about the company and workspaces, and delete a workspace and a company.

At present, you can register only one company and create one workspace. In future releases of Kaspersky Security Center Cloud Console, you will be able to create additional workspaces for your company. This will help you map your company structure to workspaces, by creating a separate workspace for each company branch.

In this section

Editing information about a company and a workspace

Deleting a workspace and a company

Canceling deletion of a workspace

Page top

[Topic 150560]

Editing information about a company and a workspace

You can modify the information about a company and a workspace that you specified when you added the company to Kaspersky Security Center Cloud Console.

To modify information about a company and/or a workspace:

  1. In your browser, go to Kaspersky Security Center Cloud Console.
  2. Sign in to your account on Kaspersky Security Center Cloud Console by specifying the user name and the password.
  3. If you set up two-step verification, enter the one-time security code that is either sent to you by SMS or generated in your authenticator app (depending on the two-step verification method that you set up).

    The portal page displays the company for which you are an administrator and a list of its workspaces.

  4. If you want to edit the company name and description, do the following:
    1. Click the Edit (A pencil.) icon in the area with the company information.
    2. Modify the company name and/or description as you want.
    3. Click the Save button.

      To cancel the changes, click the Cancel button.

  5. If you want to edit the workspace name, do the following:
    1. Click the Edit (A pencil.) icon in the area with the workspace information.
    2. Modify the workspace name as you want.
    3. Click the Save button.

      To cancel the changes, click the Cancel button.

The modified information is displayed in Kaspersky Security Center Cloud Console.

Page top

[Topic 143435]

Deleting a workspace and a company

A workspace of a company can be deleted either manually or automatically. After the last workspace is deleted, the company information is also deleted automatically.

Manual deletion

You can delete a workspace of a company if that company has decided to stop using the workspace.

After the workspace is deleted, all security applications will remain on the managed devices. Therefore, we recommend that before deleting the workspace you either disable password protection of all security applications or uninstall security applications from the managed devices.

To delete a workspace and a company:

  1. In your browser, go to Kaspersky Security Center Cloud Console.
  2. Sign in to your account on Kaspersky Security Center Cloud Console by specifying the user name and the password.
  3. If you set up two-step verification, enter the one-time security code that is either sent to you by SMS or generated in your authenticator app (depending on the two-step verification method that you set up).

    The portal page displays the company for which you are an administrator and a list of its workspaces.

  4. Select the workspace that you want to delete.
  5. On the right, in the section containing the selected workspace, click the Delete (Trash can.) icon.

    The Delete workspace window opens.

  6. In the Delete workspace window, confirm that you want to delete the workspace.

The workspace is marked for deletion. The information block for the workspace is highlighted with a red border.

The information block for the workspace is duplicated at the bottom of the page, in the Marked for deletion section.

You cannot go to a workspace that is marked for deletion and manage it.

If you have not been able to mark a workspace for deletion, contact Kaspersky Technical Support. After a Technical Support engineer at Kaspersky receives your request, the workspace and the company will be deleted.

Workspaces that are marked for deletion may remain in that status for a period of seven days after being marked. After seven days, they are automatically deleted.

During that period, you can forcibly delete a workspace that is marked for deletion or cancel deletion of a workspace.

To forcibly delete a workspace:

  1. In your browser, go to Kaspersky Security Center Cloud Console.
  2. Sign in to your account on Kaspersky Security Center Cloud Console by specifying the user name and the password.
  3. If you set up two-step verification, enter the one-time security code that is either sent to you by SMS or generated in your authenticator app (depending on the two-step verification method that you set up).

    The portal page displays the company for which you are an administrator and a list of its workspaces.

  4. In the Marked for deletion section, in the information block for the workspace marked for deletion, click the Force deletion option.

    The Delete workspace window opens.

  5. In the Delete workspace window, enter the ID of the workspace that you want to delete.

    You are prompted to confirm the ID of the workspace to make sure that you are not mistakenly deleting the workspace. After a workspace is deleted, it cannot be restored.

    The workspace ID is displayed in the workspace information section under its name.

  6. In the Delete workspace window, click OK.

The workspace is deleted. All data about users,

, and their settings, is deleted.

Automatic deletion

Kaspersky Security Center Cloud Console automatically deletes a workspace:

  • 30 days after the trial license expires.
  • 90 days after all commercial or subscription licenses in the Administration Server repository expire.
  • 90 days after you delete the last license key (active, reserve, or not in use) added manually in the repository.

Kaspersky Security Center Cloud Console notifies administrators of the workspace 30 days, 7 days, and 1 day prior to deletion.

Page top

[Topic 150561]

Canceling deletion of a workspace

You can cancel the deletion of a workspace that has been marked for deletion.

You cannot cancel the deletion of a workspace that already has been deleted.

To cancel the deletion of a workspace:

  1. In your browser, go to Kaspersky Security Center Cloud Console.
  2. Sign in to your account on Kaspersky Security Center Cloud Console by specifying the user name and the password.
  3. If you set up two-step verification, enter the one-time security code that is either sent to you by SMS or generated in your authenticator app (depending on the two-step verification method that you set up).

    The portal page displays the company for which you are an administrator and a list of its workspaces.

  4. In the Marked for deletion section, in the information block for the workspace marked for deletion, click the Cancel deletion link.

Workspace deletion is canceled. You can now go to the workspace and continue working with it.

Page top

[Topic 224445]

Managing access to the company and its workspaces

This section contains information about granting and revoking access to your company and its workspaces.

Kaspersky Security Center Cloud Console provides you with two access levels:

  • Administrator

    A user with this access level can fully manage the company and its workspaces.

  • User

    A user with this access level can view the list of available workspaces and enter these workspaces.

In this section

Granting access to your company and its workspaces

Revoking access to your company and its workspaces

Page top

[Topic 224447]

Granting access to your company and its workspaces

You can grant access to your company and its workspaces if you want another user to be able to log in to your company and manage it according to the selected access level.

Before you can grant access to a user, the user must create an account in Kaspersky Security Center Cloud Console.

To grant access to your company and its workspaces:

  1. In your browser, go to Kaspersky Security Center Cloud Console.
  2. Sign in to your account on Kaspersky Security Center Cloud Console by specifying the user name and the password.
  3. If you set up two-step verification, enter the one-time security code that is either sent to you by SMS or generated in your authenticator app (depending on the two-step verification method that you set up).

    The portal page displays the company for which you are an administrator and a list of its workspaces.

  4. Click the Show access control link.

    The list of accounts with access to the company expands.

  5. Click the Grant access link.
  6. In the Email address field, specify the email address of the account to which you want to grant access.
  7. In the Access level list, select the access level that you want to assign to the entered account:
    • Administrator

      A user with this access level can fully manage the company and its workspaces.

    • User

      A user with this access level can view the list of available workspaces and enter these workspaces.

    You cannot grant several access levels to the same account within the same company.

  8. Click the Grant button.

The specified account is granted access to your company and its workspaces. The user can log in to the company and manage it according to the selected access level.

If you have granted the User access level to the account, you must assign a role to the added user. Otherwise, the user will not be able to enter the workspace.

Page top

[Topic 224448]

Revoking access to your company and its workspaces

You can revoke access to your company and its workspaces if you no longer want a user to be able to log in to your company and manage it (for example, after the user quits the company).

You cannot revoke your own access to the company.

To revoke access to your company and its workspaces:

  1. In your browser, go to Kaspersky Security Center Cloud Console.
  2. Sign in to your account on Kaspersky Security Center Cloud Console by specifying the user name and the password.
  3. If you set up two-step verification, enter the one-time security code that is either sent to you by SMS or generated in your authenticator app (depending on the two-step verification method that you set up).

    The portal page displays the company for which you are an administrator and a list of its workspaces.

  4. Click the Show access control link.

    The list of accounts with access to the company expands.

  5. Click the Revoke (Trash can.) icon next to the account whose access you want to revoke.
  6. In the Revoke access to company window that opens, click OK to confirm the operation.

The access of the selected account to your company and its workspaces is revoked. The user cannot log in to the company and manage it any more.

Page top

[Topic 135429]

Resetting your password

If you forget your password for your Kaspersky Security Center Cloud Console account, you can restore access to your account by resetting your password.

To reset the account password:

  1. In your browser, go to Kaspersky Security Center Cloud Console.
  2. Click the Sign in button.
  3. In the Sign in to Kaspersky Security Center Cloud Console window of the Kaspersky Account portal that appears, click the Forgot your password? link.
  4. Enter the email address that you specified when creating your account.
  5. Click Next.
  6. A message from Kaspersky is sent to the email address that you specified. The message contains a one-time security code.

    Open the email message, and then copy the one-time security code that it contains.

  7. Return to Kaspersky Account, and then paste the code to the entry field.
  8. If you configured a secret question, answer this question.

    If you set up two-step verification, enter the one-time security code that is either sent to you by SMS or generated in your authenticator app (depending on the two-step verification method that you set up).

  9. In the window that opens, type a new password.
  10. Click Save.

    The new password for signing in to Kaspersky Security Center Cloud Console is saved.

If you did not receive an email message, check the email address that you entered, your spam folder, and then try again. If you do not receive a message when you try again, the email address you specified is probably not registered on the website. Please contact Kaspersky Technical Support.

Page top

[Topic 123598]

Editing the settings of an account in Kaspersky Security Center Cloud Console

This section provides instructions on how to edit and delete an account in Kaspersky Security Center Cloud Console.

In this section

Changing an email address

Changing a password

Using two-step verification

Deleting an account in Kaspersky Security Center Cloud Console

Page top

[Topic 126916]

Changing an email address

To change your email address in the settings of your account in Kaspersky Security Center Cloud Console:

  1. In Kaspersky Security Center Cloud Console, click the link containing your account name, and then select Manage user account.

    The My Profile window of the Kaspersky Account portal opens.

  2. Click the Change your email address link (see the figure below).

    User account settings window. Email address tab.

    Changing the email address in the settings of an account in Kaspersky Security Center Cloud Console

  3. In the New email address entry field, enter your new email.

    Please enter the address carefully. If you enter an invalid address, you will not be able to proceed to your account and use Kaspersky Security Center Cloud Console.

  4. Click the Next button.
  5. In the Enter your current password window that opens, specify the password of your account in Kaspersky Security Center Cloud Console, and then click the Next button.
  6. A message from Kaspersky is sent to the email address that you specified. The message contains a one-time security code.

    Open the email message, and then copy the one-time security code that it contains.

  7. Return to Kaspersky Account, and then paste the code to the entry field.
  8. Go back to Kaspersky Security Center Cloud Console by clicking the Go back to Kaspersky Security Center Cloud Console link or exit the portal by clicking the AccountSign out link.

Your email address is now changed in the Kaspersky Security Center Cloud Console account settings and in the My Kaspersky account settings. A message is sent to your new email address to notify you that your email address for gaining access to the account has been changed. The next time you sign in to Kaspersky Security Center Cloud Console, you will have to specify your new email address.

Page top

[Topic 126917]

Changing a password

To change your password in the settings of your account in Kaspersky Security Center Cloud Console:

  1. In Kaspersky Security Center Cloud Console, click the link containing your account name, and then select Manage user account.

    The My Profile window of the Kaspersky Account portal opens.

  2. Click the Change password link (see the figure below).

    User account settings window. Password tab.

    Changing the account password in Kaspersky Security Center Cloud Console

  3. In the Password entry field, enter your new password.

    Under the entry field, the requirements for the password are shown. You cannot save the new password until you comply with the requirements.

  4. Click the Save button.
  5. In the Enter your current password window that opens, specify the password of your account in Kaspersky Security Center Cloud Console, and then click the Next button.
  6. Select or clear the Automatically request password change every 180 days check box.

    By default, this check box is selected.

  7. Go back to Kaspersky Security Center Cloud Console by clicking the Go back to Kaspersky Security Center Cloud Console link or exit the portal by clicking the AccountSign out link.

Your password is now changed. You will have to enter the new password when signing in to Kaspersky Security Center Cloud Console and when signing in to My Kaspersky.

Page top

[Topic 126918]

Using two-step verification

This section describes two-step verification, which can help you increase the security of your account in Kaspersky Security Center Cloud Console.

In this section

About two-step verification

Scenario: Setting up two-step verification

Setting up two-step verification by SMS

Setting up two-step verification by using an authenticator app

Changing your mobile phone number

Disabling two-step verification

Page top

[Topic 116212]

About two-step verification

Two-step verification can help you increase the security of your account in Kaspersky Security Center Cloud Console. When this feature is enabled, every time you sign in to Kaspersky Security Center Cloud Console with your email address and password, you enter an additional one-time security code. With two-step verification, criminals cannot sign in to your account if they steal or guess your password, they must have access to your mobile phone as well. Also, when two-step verification is enabled, you must enter an additional one-time security code if you forget your password.

After you set up two-step verification, you are responsible for keeping your mobile phone physically secure and for maintaining access to your phone number.

You can get a one-time security code in either of the following ways:

  • A security code is sent by SMS to your mobile phone number.

    In this case, if you lose access to your mobile phone, you are not able to sign in to your account in Kaspersky Security Center Cloud Console until you restore access to your phone number.

  • A security code is generated in an authenticator app that is installed on your mobile phone.

    We strongly recommend that you set up two-step verification by using an authenticator app. In this case, you can sign in to your account even if your mobile phone is not connected to the internet or a mobile network.

    We have tested only Google Authenticator and Microsoft Authenticator for compatibility with Kaspersky Security Center Cloud Console, and these applications were free to use at that time. The interfaces of these applications may be unavailable in your preferred language. Please also check the GDPR compliance and privacy policies of the applications before using them. Kaspersky is in no way sponsored, endorsed by, or otherwise affiliated with any of the owners of these applications.

    Microsoft Authenticator can be installed on mobile devices only.

    We also recommend that you install an authenticator app on a device other than your mobile phone. This will allow you to sign in to your account if your mobile phone is ever lost or stolen.

    In this case, if you lose access to your mobile phone and you do not have an authenticator app on another device, you are not able to sign in to your account in Kaspersky Security Center Cloud Console until you restore access to your phone number. After that, use the security code that is sent by SMS.

If you previously configured a secret question to restore your password if it is lost, the security question feature will be permanently disabled after you set up two-step verification.

Page top

[Topic 123558]

Scenario: Setting up two-step verification

Two-step verification can help you increase the security of your account in Kaspersky Security Center Cloud Console. After you complete the scenario in this section, two-step verification of your account will be set up.

The scenario proceeds in stages:

  1. Adding your phone number

    At this stage, you set up two-step verification by SMS.

  2. Installing and configuring an authenticator app

    Install and configure an authenticator app.

    We strongly recommend that you set up two-step verification by using an authenticator app. In this case, you can sign in to your account even if your mobile phone is not connected to the internet or a mobile network.

    We also recommend that you install an authenticator app on a device other than your mobile phone. This will allow you to sign in to your account if your mobile phone is ever lost or stolen.

  3. Changing your phone number

    If necessary, you can change the phone number that you use for two-step verification.

Page top

[Topic 99990]

Setting up two-step verification by SMS

To set up two-step verification by SMS:

  1. In Kaspersky Security Center Cloud Console, click the link containing your account name, and then select Manage user account.

    The My Profile window of the Kaspersky Account portal opens.

  2. If two-step verification is disabled, enable the Two-step verification is disabled toggle switch.
  3. In the No phone number provided window that appears, click the Confirm button.
  4. Under Enter your phone number, specify the mobile phone number that you want to use in two-step verification, and then click the Provide phone number button.

    You can use the same phone number for up to five accounts.

    A 6-digit security code is sent to the specified phone number.

  5. Under Enter the verification code that was sent to <phone number>, enter the received security code.
  6. In the Enter your current password window that opens, specify the password of your account in Kaspersky Security Center Cloud Console, and then click the Next button.

Two-step verification is set up. Now, every time you sign in with your email address and password, or if you forget your password, you will need to enter a one-time security code that you get by SMS to the specified phone number.

You can now install and configure an authenticator app, change your phone number, or disable two-step verification.

Page top

[Topic 134652]

Setting up two-step verification by using an authenticator app

Authenticator apps cannot be used in Kaspersky Security Center Cloud Console as a standalone verification method. You must first set up two-step verification by SMS. If you disable two-step verification via your mobile phone number, verification via an authenticator app is turned off automatically. After you have set up both verification via SMS and via an app, you will be able to select a verification method on the sign-in page or if you forget your password.

To set up two-step verification by an authenticator app:

  1. Set up two-step verification by SMS.
  2. Download, install, and run the authenticator app that you want to use.

    We have tested only Google Authenticator and Microsoft Authenticator for compatibility with Kaspersky Security Center Cloud Console, and these applications were free to use at that time. The interfaces of these applications may be unavailable in your preferred language. Please also check the GDPR compliance and privacy policies of the applications before using them. Kaspersky is in no way sponsored, endorsed by, or otherwise affiliated with any of the owners of these applications.

    Microsoft Authenticator can be installed on mobile devices only.

    If you want, you can use other apps at your own risk. The app that you use must support 6-digit security codes.

    We also recommend that you install an authenticator app on a device other than your mobile phone. This will allow you to sign in to your account if your mobile phone is ever lost or stolen.

  3. In Kaspersky Security Center Cloud Console, click the link containing your account name, and then select Manage user account.

    The My Profile window of the Kaspersky Account portal opens.

  4. If two-step verification is disabled, enable the Two-step verification is disabled toggle switch.
  5. Enable the Authenticator app is disabled toggle switch.

    The portal page displays a QR code.

    If you want to set up the authenticator app on a device that cannot scan QR codes, click the I can't scan it link. A 16-character secret key is displayed.

  6. In the authenticator app on each device, scan the QR code to create an account. Please refer to your app's documentation for more information.

    If you want to set up the authenticator app on a device that cannot scan QR codes, create an account in the authenticator app, and then enter the displayed secret key.

    A 6-digit security code is generated in your authenticator apps.

  7. Verify that the security codes generated in your apps are the same on each device.
  8. Return to the Kaspersky Account portal, and then click the Next button.
  9. Enter the generated security code.
  10. In the Enter your current password window that opens, specify the password of your account in Kaspersky Security Center Cloud Console, and then click the Next button.

Two-step verification by an authenticator app is set up. Now, every time you sign in with your email address and password, or if you forget your password, you will need to enter a one-time security code that is generated in your authenticator app.

You can now disable the use of an authenticator app or completely disable two-step verification.

Page top

[Topic 134658]

Changing your mobile phone number

To change the mobile phone number that is used in two-step verification by SMS:

  1. In Kaspersky Security Center Cloud Console, click the link containing your account name, and then select Manage user account.

    The My Profile window of the Kaspersky Account portal opens.

  2. If two-step verification is disabled, enable the Two-step verification is disabled toggle switch.
  3. Under Phone number, click the Change phone number link.
  4. Under Enter your phone number, specify the new mobile phone number that you want to use in two-step verification, and then click the Provide phone number button.

    A 6-digit security code is sent to the specified phone number.

  5. Under Enter the verification code that was sent to <phone number>, enter the received security code.

Your mobile phone number is changed. Now, one-time security codes will be sent to the new phone number.

Page top

[Topic 134659]

Disabling two-step verification

If you no longer want to use two-step verification, you can disable it, as described in this section.

Disabling two-step verification will decrease the security of your account. We strongly recommend that you continue using two-step verification.

If you set up two-step verification by SMS, you can disable two-step verification. If you set up two-step verification by an authenticator app, you can disable the use of the app or completely disable two-step verification.

To disable the use of an authenticator app:

  1. In Kaspersky Security Center Cloud Console, click the link containing your account name, and then select Manage user account.

    The My Profile window of the Kaspersky Account portal opens.

  2. Disable the Authenticator app is enabled toggle switch.
  3. In the confirmation window that opens, click the Confirm button.
  4. In the Enter your current password window that opens, specify the password of your account in Kaspersky Security Center Cloud Console, and then click the Next button.

The use of an authenticator app is disabled. The settings of two-step verification by an authenticator app are deleted. You can now delete accounts in your authenticator apps.

Later, you can set up two-step verification by an authenticator app again.

To completely disable two-step verification:

  1. In Kaspersky Security Center Cloud Console, click the link containing your account name, and then select Manage user account.

    The My Profile window of the Kaspersky Account portal opens.

  2. Disable the Two-step verification is enabled toggle switch.
  3. In the confirmation window that opens, click the Confirm button.
  4. In the Enter your current password window that opens, specify the password of your account in Kaspersky Security Center Cloud Console, and then click the Next button.

Two-step verification is disabled. If you used two-step verification by an authenticator app, the settings of two-step verification are deleted. You can now delete accounts in your authenticator apps.

Later, you can set up two-step verification again.

Page top

[Topic 101543]

Deleting an account in Kaspersky Security Center Cloud Console

If you want to stop using Kaspersky Security Center Cloud Console, you can delete your account.

When deleting an account, all data associated with that account is lost.

After you delete your account, you can no longer gain access to your workspaces in Kaspersky Endpoint Security Cloud, Kaspersky Security for Microsoft Office 365, and Kaspersky Security Center Cloud Console. If you were the only administrator in a workspace, the workspace will be duly deleted. Additionally, you lose access to your My Kaspersky account.

To delete an account in Kaspersky Security Center Cloud Console:

  1. In Kaspersky Security Center Cloud Console, click the link containing your account name, and then select Manage user account.

    The My Profile window of the Kaspersky Account portal opens.

  2. Click the AccountDelete link.
  3. In the Delete your account window that opens, read the information about the consequences of account deletion, and then click the Delete button to confirm the account deletion.
  4. In the Enter your current password window that opens, specify the password of your account in Kaspersky Security Center Cloud Console, and then click the Next button.

Your account is deleted.

Page top

[Topic 138096]

Selecting the data centers used to store Kaspersky Security Center Cloud Console information

A workspace for Kaspersky Security Center Cloud Console is created by using servers from a network of global data centers based on a cloud platform. The selection of data centers to host a workspace depends on the country that you specified when you registered the workspace in Kaspersky Security Center Cloud Console (see the table below). The distribution packages of security applications are hosted on the same servers as workspaces.

Matching the company location with a data center region

Country in which the company is located

Data center region

Argentina

Brazil

Bolivia

Brazil

Brazil

Brazil

Chile

Brazil

Colombia

Brazil

Ecuador

Brazil

Guyana

Brazil

Peru

Brazil

Paraguay

Brazil

Suriname

Brazil

Uruguay

Brazil

Venezuela

Brazil

Antigua and Barbuda

Mexico or Brazil

Anguilla

Mexico or Brazil

Aruba

Mexico or Brazil

Barbados

Mexico or Brazil

Saint Barthelemy

Mexico or Brazil

Bonaire, Sint Eustatius and Saba

Mexico or Brazil

Belize

Mexico or Brazil

Costa Rica

Mexico or Brazil

Cuba

Mexico or Brazil

Curacao

Mexico or Brazil

Dominica

Mexico or Brazil

Dominican Republic

Mexico or Brazil

Grenada

Mexico or Brazil

Guadeloupe

Mexico or Brazil

Guatemala

Mexico or Brazil

Honduras

Mexico or Brazil

Haiti

Mexico or Brazil

Jamaica

Mexico or Brazil

Saint Kitts and Nevis

Mexico or Brazil

Cayman Islands

Mexico or Brazil

Saint Lucia

Mexico or Brazil

Saint Martin

Mexico or Brazil

Martinique

Mexico or Brazil

Montserrat

Mexico or Brazil

Nicaragua

Mexico or Brazil

Panama

Mexico or Brazil

Sint Maarten

Mexico or Brazil

Trinidad and Tobago

Mexico or Brazil

Saint Vincent and the Grenadines

Mexico or Brazil

British Virgin Islands

Mexico or Brazil

Japan

Mexico or Ireland

Canada (New Brunswick)

Mexico or Brazil

Canada (Newfoundland and Labrador)

Mexico or Brazil

Canada (Nova Scotia)

Mexico or Brazil

Canada (Ontario)

Mexico or Brazil

Canada (Prince Edward Island)

Mexico or Brazil

Canada (Quebec)

Mexico or Brazil

Albania

Ireland

Bosnia and Herzegovina

Ireland

Bulgaria

Ireland

Belarus

Ireland

Czech Republic

Ireland

Denmark

Ireland

Estonia

Ireland

Finland

Ireland

United Kingdom

Ireland

Greenland

Ireland

Greece

Ireland

Croatia

Ireland

Hungary

Ireland

Ireland

Ireland

Iceland

Ireland

Kyrgyzstan

Ireland

Kazakhstan

Ireland

Lithuania

Ireland

Latvia

Ireland

Moldova

Ireland

Montenegro

Ireland

Macedonia

Ireland

Mongolia

Ireland

Norway

Ireland

Poland

Ireland

Romania

Ireland

Serbia

Ireland

Russian Federation

Ireland

Sweden

Ireland

Slovenia

Ireland

Slovakia

Ireland

Tajikistan

Ireland

Turkmenistan

Ireland

Uzbekistan

Ireland

Canada (Alberta)

Mexico or Brazil

Canada (British Columbia)

Mexico or Brazil

Canada (Manitoba)

Mexico or Brazil

Canada (Northwest Territories)

Mexico or Brazil

Canada (Nunavut)

Mexico or Brazil

Canada (Yukon)

Mexico or Brazil

Canada (Saskatchewan)

Mexico or Brazil

Mexico

Mexico or Brazil

Other countries

Ireland

Page top

[Topic 242745]

Access to public DNS servers

If access to Kaspersky servers by using the system DNS is not possible, Kaspersky Security Center Cloud Console can use the following public DNS servers, in the following order:

  1. Google Public DNS (8.8.8.8)
  2. Cloudflare DNS (1.1.1.1)
  3. Alibaba Cloud DNS (223.6.6.6)
  4. Quad9 DNS (9.9.9.9)
  5. CleanBrowsing (185.228.168.168)

Requests to these DNS servers may contain domain addresses and the public IP address of client devices, because Network Agent establishes a TCP/UDP connection to the DNS server. If Kaspersky Security Center Cloud Console is using a public DNS server, data processing is governed by the privacy policy of the relevant service.

Page top

[Topic 200848]

Scenario: Creating a hierarchy of Administration Servers managed through Kaspersky Security Center Cloud Console

Expand all | Collapse all

This scenario describes the actions that you must perform to create a hierarchy of Administration Servers managed through Kaspersky Security Center Cloud Console, which thus assumes the role of primary Administration Server. This hierarchy can be subsequently used for migration of managed devices and objects from Kaspersky Security Center to Kaspersky Security Center Cloud Console, as well as management of secondary Administration Servers and devices through Kaspersky Security Center Cloud Console.

Kaspersky Security Center Cloud Console can only act as primary Administration Server, while Administration Servers running on-premises can only act as secondary Administration Servers. Other hierarchical schemes are not available.

Prerequisites

Before you start, make sure that the following prerequisites are met:

  • Upgrading Administration Server running on-premises to version 12 or later.
  • Installing Kaspersky Security Center Web Console on the Administration Server running on-premises.
  • Installing the web plug-ins for the applications that you intend to manage through Kaspersky Security Center Cloud Console.
  • Upgrading the managed applications to versions supported by Kaspersky Security Center Cloud Console.
  • Making sure that the Download updates to the Administration Server repository task on the Administration Server running on-premises does not have the primary Administration Server assigned as the update source; modifying the task settings accordingly, if necessary.

After the hierarchy is created, the policies and tasks that are effective in Kaspersky Security Center Cloud Console are applied on the secondary Administration Server, thus superseding its existing policies and tasks. If you want to avoid this behavior, delete all policies and tasks of Kaspersky Security Center Cloud Console before the hierarchy creation. Alternatively, you can change the status of each Kaspersky Security Center Cloud Console policy to Inactive in its settings and disable the Distribute to secondary and virtual Administration Servers option in the settings of each Kaspersky Security Center Cloud Console task.

You can delete your hierarchy of Administration Servers at any time, if necessary.

Stages of hierarchy creation

The basic scenario provides for a secondary Administration Server that cannot be accessed over the internet. However, the set of actions within some of the steps described below may vary if the secondary Administration Server is accessible over the internet. Also, some of the steps must be skipped in this case.

Creation of a hierarchy of Administration Servers comprises the following stages:

  1. Retrieving the certificate of the secondary Administration Server

    If the secondary Administration Server is accessible over the internet, skip this step.

    In Kaspersky Security Center Web Console running on-premises, open the Administration Server properties and on the General tab, open the General section. Click the View Administration Server certificate link. The certificate file, in the CER format, is automatically saved in the folder specified in your browser settings.

  2. Retrieving the connection settings and certificates from Kaspersky Security Center Cloud Console

    If the secondary Administration Server is accessible over the internet, skip this step.

    In Kaspersky Security Center Cloud Console, open the Administration Server properties and on the General tab open the Hierarchy of Administration Servers section. The following connection settings are displayed:

    • HDS address

      Displays the web address used for connection to Hosted Discovery Service (HDS).

    • HDS port

      Displays the number of the port used for connection to HDS.

    The section also contains two links:

    • View Administration Server certificate

      Clicking this link starts the download of the public key of the Kaspersky Security Center Cloud Console instance certificate.

    • HDS Root CA certificate

      Clicking this link starts the download of the file in .pem format that contains a list of trusted root certificates issued by Certification Authorities (CA). This file is designed for use by the secondary Administration Server: it is required to verify the HDS certificate.

    Copy the connection settings manually—by using the clipboard or any other convenient way—and save them to a file of any convenient format. Click the View Administration Server certificate link and wait until the certificate file is downloaded. Click the HDS Root CA certificate link and wait until the file with the list of trusted root certificates issued by Certification Authorities is downloaded. Both files are saved to the folder specified in your browser settings.

  3. Selecting the secondary Administration Server for connection

    In the Administration Server properties, proceed to the Administration servers tab. In the hierarchy of administration groups, select the check box next to the administration group that you want to contain the secondary Administration Server with all its managed devices. Click the Connect secondary Administration Server button.

    On the page that opens, in the Secondary Administration Server display name field specify the name under which the secondary Administration Server must be displayed in the hierarchy. It is used for your convenience only and so it can differ from the actual secondary Administration Server name, if necessary. Click Next.

    If the secondary Administration Server is accessible over the internet, you must also specify the address of the secondary Administration Server in the Secondary Administration Server address (optional) field.

    On the next page, click the Browse button and specify the .pem file that you saved from the secondary Administration Server. Click Next.

  4. Enabling and configuring proxy server

    The actions described in this step are optional. Perform them only if your connection requires the use of proxy server.

    Click Next. On the Connection and authentication settings page, you can enable and configure the use of proxy server, if necessary. Select the Use proxy server check box and specify the following proxy settings:

  5. Specifying the authentication settings and adding the secondary Administration Server to the hierarchy

    Click Next. On the Secondary Administration Server credentials page, specify the following settings:

    • User name

      The user name under which you log in to the secondary Administration Server.

    • Password

      The password used to log in to the secondary Administration Server.

    Click Next and wait until the secondary Administration Server appears in the hierarchy.

    If the secondary Administration Server is accessible over the internet, it connects to the primary Administration Server.

    If the secondary Administration Server is accessible over the internet and the connection between the two Administration Servers is successfully established, skip all further steps.

    If the secondary Administration Server cannot be accessed over the internet, it becomes visible but you must perform additional actions on the secondary Administration Server to gain control of it.

  6. Configuring the connection in Kaspersky Security Center Web Console running on-premises

    In Kaspersky Security Center Web Console running on-premises, open the Administration Server properties and on the General tab, open the Hierarchy of Administration Servers section. Select the This Administration Server is secondary in the hierarchy check box. In the Type of primary Administration Server list, select the Kaspersky Security Center Cloud Console option.

    Kaspersky Security Center Web Console checks whether the primary Administration Server is specified as the update source in the Download updates to the Administration Server repository task. If the primary Administration Server is specified as the update source, you get the corresponding warning message and a link to the task settings. You can modify the settings and then go back to the hierarchy creation, or you can skip this action and proceed with the hierarchy creation.

    In the Settings to establish connection between secondary and primary Administration Servers group, specify the following settings:

    • HDS server address (from primary Administration Server on Cloud Console)

      Enter the address of the HDS server in Fully Qualified Domain Name (FQDN) format, which you have copied and saved from the Administration Server properties in Kaspersky Security Center Cloud Console.

    • HDS server ports

      Enter the number(s) of the HDS server port(s), which you have copied and saved from the Administration Server properties in Kaspersky Security Center Cloud Console.

  7. Adding the certificates to the secondary Administration Server

    Click the Specify primary Administration Server certificate button and specify the certificate file that you saved from the Administration Server properties in Kaspersky Security Center Cloud Console.

    Click the Specify Hosted Discovery Service certificates button and specify the .pem file that you saved from the Administration Server properties in Kaspersky Security Center Cloud Console.

    If you have enabled the use of proxy server when connecting the secondary Administration Server in Kaspersky Security Center Cloud Console, select the Use proxy server check box and specify the same proxy settings as in Kaspersky Security Center Cloud Console.

    You can also select the Connect primary Administration Server to secondary Administration Server in DMZ check box if the secondary Administration Server is in a

    .

    The secondary Administration Server connects to the primary Administration Server.

Results

Upon performing the above steps, you can make sure that the hierarchy is created successfully:

  • The active policies of the primary Administration Server become effective on the secondary Administration Server. The tasks of the primary Administration Server are distributed to the secondary Administration Server. If the Distribute to secondary and virtual Administration Servers option is enabled in the settings of a group task, every such task is also distributed to the secondary Administration Server.
  • Policy settings that are locked against changes on the primary Administration Server are displayed as locked against changes in all policies on the secondary Administration Server.
  • Policies applied by the primary Administration Server are displayed in the list of policies of the secondary Administration Server (Assets (Devices)Policies & profiles).
  • Group tasks distributed by the primary Administration Server are displayed in the list of tasks of the secondary Administration Server (Assets (Devices)Tasks).
  • Policies and tasks created on the primary Administration Server cannot be modified on the secondary Administration Server.
  • In Kaspersky Security Center Cloud Console, in the structure of administration groups the secondary Administration Server is displayed within the group that you selected when you added this Administration Server.
Page top

[Topic 186799]

Migration to Kaspersky Security Center Cloud Console

This section describes the process of migration to Kaspersky Security Center Cloud Console from:

In this section

About migration from Kaspersky Security Center Web Console

About migration from Kaspersky Endpoint Security Cloud

Page top

[Topic 195229]

Methods of migration to Kaspersky Security Center Cloud Console

By using the migration feature, you can transfer your networked devices from Kaspersky Security Center under management by Kaspersky Security Center Cloud Console. Your managed devices will be switched without losing the principal settings, such as membership in administration groups; as well as the essential objects, such as policies and tasks related to the managed applications.

You can choose either of the two available methods to migrate your Administration Servers to Kaspersky Security Center Cloud Console:

  • Migration without a hierarchy of Administration Servers:
    • Enables transfer of managed devices and related objects to Kaspersky Security Center Cloud Console, even if the Administration Server on-premises is not secondary in regard to Kaspersky Security Center Cloud Console.
    • May require transfer of files (on a removable drive, by email, through shared folders, or in any other convenient way) if Kaspersky Security Center Web Console and Kaspersky Security Center Cloud Console are opened on different physical devices.

    You can also perform migration with virtual Administration Servers if your network includes them.

  • Migration using a hierarchy of Administration Servers:
    • Enables transfer of managed devices and related objects to Kaspersky Security Center Cloud Console by using only the interface of Kaspersky Security Center Cloud Console, so no physical transfer of files is needed.
    • Requires that the Administration Server running on-premises act as secondary to Kaspersky Security Center Cloud Console. You can create such a hierarchy before starting migration.

For the full disk encryption, Kaspersky Security Center Cloud Console supports only BitLocker.

See also:

Scenario: Migration of devices running Linux or macOS operating systems

Page top

[Topic 186772]

Scenario: Migration without a hierarchy of Administration Servers

This section describes the migration of the managed devices and related objects (such as policies, tasks, reports) from Kaspersky Security Center Web Console running on-premises to Kaspersky Security Center Cloud Console. You can include a single administration group in the migration scope to restore the same administration group in Kaspersky Security Center Cloud Console.

This group must contain the managed devices of a single operating system. If your network includes the devices of different operating systems or Linux distributives, allocate them in different administration groups, and then migrate each group separately.

After you finish the migration, all Network Agents within the migration scope are upgraded and managed by Kaspersky Security Center Cloud Console.

The steps listed in this section cover the migration process performed when no hierarchy of Administration Servers exists, that is, no connection has been established between Kaspersky Security Center Cloud Console and Kaspersky Security Center Web Console running on-premises.

Prerequisites

Before you start, do the following:

  • Upgrade Administration Server running on-premises to version 14.2 or later.
  • Install Kaspersky Security Center Web Console version 12.1 or later.
  • Upgrade Network Agent on the managed devices to version 12 or later.
  • On Windows devices, use Network Agent without an uninstallation password.

    If the password has already been set, do one of the following in Kaspersky Security Center Web Console:

    • Disable the Use uninstallation password option in the Network Agent policy settings.
    • Uninstall Network Agent remotely by using the Uninstall application remotely task. In the Application to uninstall field of the task, select Kaspersky Security Center Network Agent. Do not forget to enter the uninstallation password.
  • Upgrade the managed applications to the versions supported by Kaspersky Security Center Cloud Console.
  • Make sure that you have policies for the latest versions of the managed applications. If you use outdated policies, create new ones for the application versions supported by Kaspersky Security Center Cloud Console.
  • To use actual policies, upgrade the web plug-ins for the applications that you intend to manage through Kaspersky Security Center Cloud Console.
  • Uninstall Kaspersky applications from managed devices if these applications are not supported by Kaspersky Security Center Cloud Console.
  • Decrypt all the data (disk-level or file-level) that was encrypted by Kaspersky Endpoint Security for Windows on managed devices running the Windows operating system, and disable the encryption feature on the managed devices through the application policy or locally. For more information, see Help for Kaspersky Endpoint Security for Windows.

    If the Windows device still stores any files or folders encrypted through Kaspersky Endpoint Security for Windows, the Network Agent upgrade will be canceled during the migration process. A notification will prompt you to decrypt all data on the device and disable the encryption feature.

Kaspersky Security Center Cloud Console allows for a maximum of 25,000 managed devices per one Administration Server.

Migration stages

Migration to Kaspersky Security Center Cloud Console comprises the following stages:

  1. Planning the migration scope and checking the prerequisites

    Estimate the scope of the migration process, that is, review the administration group to export and assess the number of managed devices in it. Also, make sure that all the activities listed as migration prerequisites have been completed successfully.

  2. Exporting managed devices, objects, and settings from Kaspersky Security Center Web Console

    Use the Migration wizard of Kaspersky Security Center Web Console running on-premises to export your managed devices together with their objects.

    The maximum export file size is 4 GB.

  3. Importing the export file to Kaspersky Security Center Cloud Console

    Transfer the information about your managed devices and objects to Kaspersky Security Center Cloud Console. For this purpose, use the Migration wizard of Kaspersky Security Center Cloud Console to import the export file and create a Network Agent stand-alone installation package.

  4. Re-installing Network Agent on managed devices

    Go back to the Migration wizard in Kaspersky Security Center Web Console running on-premises to create a remote installation task. You will be able to use this task (immediately or later) to re-install Network Agent on your managed devices and complete the migration process.

Results

Upon finishing with the migration, you can make sure that it was successful:

  • Network Agent is re-installed on all managed devices.
  • All devices are managed through Kaspersky Security Center Cloud Console.
  • All object settings that were effective before migration are preserved.

See also:

Methods of migration to Kaspersky Security Center Cloud Console

Migration wizard

Migration with a hierarchy of Administration Servers

Scenario: Migration of devices running Linux or macOS operating systems

Scenario: Reverse migration from Kaspersky Security Center Cloud Console to Kaspersky Security Center

Page top

[Topic 195012]

Step 1. Exporting managed devices, objects, and settings from Kaspersky Security Center Web Console

Expand all | Collapse all

Migration of managed devices from Kaspersky Security Center Web Console to Kaspersky Security Center Cloud Console requires that you first create an export file containing information about the hierarchy of administration groups that are on your current Administration Server running on-premises. The export file must also contain information about the objects and their settings. The export file will be used for subsequent import to Kaspersky Security Center Cloud Console.

The maximum export file size is 4 GB.

To export objects and their settings from Kaspersky Security Center Web Console:

  1. In the main menu of Kaspersky Security Center Web Console, go to OperationsMigration.
  2. On the welcome page of the Migration wizard, click Next. The Managed devices to export page opens, displaying the entire hierarchy of administration groups of the corresponding Administration Server.
  3. On the Managed devices to export page, click the chevron icon () next to the Managed devices group name to expand the hierarchy of administration groups. Select the administration group that you want to export.

    After migration from Kaspersky Security Center running on-premises to Kaspersky Security Center Cloud Console performed for two administration groups, the Remote installation tasks for these groups appear with the same name.

  4. Select the managed applications whose policies and tasks must be transferred to Kaspersky Security Center Cloud Console together with group objects. To select the managed applications whose objects are to be exported, select the check boxes next to their names in the list.

    Although Kaspersky Security Center Administration Server is present on the list, selecting the corresponding check box does not result in the export of its policies.

    To make sure that your managed applications are supported by Kaspersky Security Center Cloud Console, click the corresponding link. It will redirect you to the Online Help topic containing the list of applications managed by Kaspersky Security Center Cloud Console.

    If you select applications that are not supported by Kaspersky Security Center Cloud Console, the policies and tasks of these applications will be exported anyway and then imported, but you will not be able to manage them in Kaspersky Security Center Cloud Console due to unavailability of the dedicated plug-ins.

  5. View the list of group objects exported by default and specify non-group objects to be exported together with the selected administration group, if necessary. Configure the export scope by including or excluding various objects, such as global tasks, custom device selections, reports, custom roles, internal users and security groups, and custom application categories. This page includes the following sections:
    • Global tasks

      The list of global tasks of managed applications, as well as global tasks of Network Agent.

      If a global task that you selected applies to a specific object selection, this selection will also be exported.

      Although the global tasks of Administration Server are present on the list, you cannot export them; selecting those tasks does not affect the export scope. Remote installation tasks also remain outside the export scope, because their respective installation packages cannot be exported.

    • Device selections

      The list of custom device selections.

    • Reports

      The editable list of report instances to be exported.

      If a report that you selected applies to a specific object selection, this selection will also be exported.

      Kaspersky Security Center Cloud Console contains the same set of report templates as Kaspersky Security Center Web Console, so you can select for export only the reports that you created manually or reconfigured.

    • Group objects

      The list of group objects to be exported by default. The following objects related to the selected administration group will be exported in their entirety by default:

      • Administration group structure, that is, all subgroups of the selected administration group.
      • Devices that have been included in the administration groups to be exported.
      • Tags that have been assigned to the devices to be exported.

        If a tag was created in Kaspersky Security Center Web Console but never assigned to any device, it will not be exported. The auto-tagging rules will not be exported, either.

      • Group policies of the managed applications that have been selected.

        Administration Server policies and Network Agent policies are not exported.

      • Group tasks of the managed applications that have been selected and Network Agent group tasks.

        Administration Server tasks are not exported.

      You can also prevent certain types of non-group objects from being exported:

      • To cancel export for custom roles (that is, those created by the user only), select the Exclude custom roles from export check box.
      • To cancel export for internal users and security groups, select the Exclude internal users and security groups from export check box.
      • To cancel export for custom application categories with content added manually, select the Exclude custom application categories from export check box.

    If you transfer devices of various operating systems to Kaspersky Security Center Cloud Console, non-group objects only need to be migrated once.

    The Migration wizard checks the total number of managed devices included in the selected administration group. If this number exceeds 10,000, an error message appears. The Next button remains unavailable (dimmed) until the number of managed devices in the selected administration group falls within the limit.

  6. After you defined the migration scope, click Next to start the export process. The Creating the export file page opens, where you can view the export progress for each type of object that you included in the migration scope. Wait until the refresh icons () next to all items in the list of objects are replaced with green check marks (). The export process finishes and the export file is automatically downloaded to the default download location defined in your browser settings. The name of the export file appears in the lower part of the browser window.
  7. When the Export has completed successfully page is displayed, proceed to the next stage performed in Kaspersky Security Center Cloud Console.

    If you use Kaspersky Security Center Web Console and Kaspersky Security Center Cloud Console on different devices, you will have to copy the export file to a removable drive or choose other ways of transferring the file.

See also:

Scenario: Migration without a hierarchy of Administration Servers

Page top

[Topic 195040]

Step 2. Importing the export file to Kaspersky Security Center Cloud Console

To transfer information about managed devices, objects, and their settings that you exported from Kaspersky Security Center Web Console, you must import it to Kaspersky Security Center Cloud Console deployed in your workspace. This enables you to create a stand-alone installation package and use it for re-installation of Network Agent on your managed devices.

Before you start the Migration wizard in Kaspersky Security Center Cloud Console, make sure its current localization language is the same as the Kaspersky Security Center Web Console language during the export process. Switch the language, if necessary.

If you have previously completed the quick start wizard in your Kaspersky Security Center Cloud Console workspace, the Managed devices group includes policies and tasks created with the default settings. Delete these policies and tasks before importing the ones that you exported from Kaspersky Security Center Web Console.

To import the export file to Kaspersky Security Center Cloud Console:

  1. In the main menu of Kaspersky Security Center Cloud Console, go to OperationsMigration.
  2. On the welcome page of the Migration wizard, click Import. In the File Explorer window that opens, select the export file by browsing to the folder where it was saved, and click Open. Wait until the refresh icon () next to the file uploading status is replaced with the green check mark ().
  3. Click Next. The next page opens, displaying the entire hierarchy of administration groups of the Administration Server in Kaspersky Security Center Cloud Console.
  4. Select the check box next to the target administration group to which the group objects must be restored and click Next. The Migration wizard displays a list of Network Agent installation packages available in Kaspersky Security Center Cloud Console.
  5. Select the installation package containing the relevant version and localization of Network Agent and click Next.

    Select the Kaspersky Network Agent for Windows installation package only if you have previously completed the quick start wizard in your Kaspersky Security Center Cloud Console workspace and if you perform the migration of Windows devices.

    Wait until the Migration wizard creates a stand-alone installation package. The maximum file size of the stand-alone installation package for Network Agent is 200 MB.

    The file is unpacked and automatically downloaded to the default download location defined in your browser settings. The non-group objects and the group objects are restored to the target administration group.

    When the import completes, the exported structure of administration groups, including the details of devices, appears under the target administration group that you selected. If the name of the object that you restore is identical to the name of an existing object, the restored object has an incremental suffix added.

    If you have imported the entire Managed devices group, we recommend that you rename the newly imported subgroup to avoid confusion:

    1. Go to the Hierarchy of groups section.
    2. Click the name of the subgroup in the groups tree.
    3. In the properties window that opens, in the Name field enter a different name (for example, "Migrated devices").

    We recommend that you check whether the objects (policies, tasks, and managed devices) included in the export scope have been successfully imported to Kaspersky Security Center Cloud Console. To do this, go to the Assets (Devices) section and view whether the imported objects appear on the lists in the Policies & profiles, Tasks, and Managed devices subsections.

    You cannot minimize the Migration wizard and perform any concurrent operations during the import. Wait until the refresh icons () next to all items in the list of objects are replaced with green check marks () and the import finishes. After this, the devices start switching to Kaspersky Security Center Cloud Console.

  6. Click Finish to close the Migration wizard window.
  7. If you want to find and download the stand-alone installation package again, go to Discovery & deploymentDeployment & assignmentInstallation packages and click the View the list of stand-alone packages button. In the list that opens, select the stand-alone installation package that you have created and click the Download button.

    If you use Kaspersky Security Center Web Console and Kaspersky Security Center Cloud Console on different devices, you must copy the stand-alone installation package to a removable drive or choose other ways of transferring the file.

See also:

Scenario: Migration without a hierarchy of Administration Servers

Page top

[Topic 195045]

Step 3. Re-installing Network Agent on devices managed through Kaspersky Security Center Cloud Console

After you create the Network Agent stand-alone installation package, you can proceed to creation of a remote installation task. Performing this task enables you to re-install Network Agent on all managed devices so that these devices are switched under management through Kaspersky Security Center Cloud Console.

To reduce the risk of data loss, we recommend that you first perform the actions for a small administration group counting up to 20 managed devices located within the corporate network and including no physical servers. After finishing with these actions, check whether re-installation completed successfully and proceed to the full reinstallation scope.

To create a remote installation task and re-install Network Agent:

  1. Go back to the Migration wizard in Kaspersky Security Center Web Console running on-premises.

    We recommend using the Migration wizard to create a remote installation task to re-install Network Agent as described below. If it is necessary to use a custom remote installation task, you first need to manually create a custom installation package from the Network Agent stand-alone installation package. Please note that when creating a custom installation package, you must specify the "-s" key in the executable file command line. Otherwise, Network Agent reinstallation from this custom installation package completes with an error.

    Depending on the current state of the Migration wizard, you can do one of the following:

    • If you have not closed the Migration wizard after the export and your session has not expired, click the Go to Step 3 of the Migration wizard button. Select the Upload stand-alone installation package check box and click the Select stand-alone installation package button. In the browser window that opens, specify the Network Agent stand-alone installation package.
    • If you have to start the Migration wizard again for any reason, select the Upload stand-alone installation package check box and click the Select stand-alone installation package button. In the browser window that opens, specify the Network Agent stand-alone installation package. After that, the Migration wizard again displays the hierarchy of administration groups of this Administration Server. Select the same group for which you created the export file and click Next.

      The Migration wizard checks again the total number of managed devices included in the selected administration group. If this number exceeds 10,000, an error message appears. The Next button remains unavailable (dimmed) until the number of managed devices in the selected administration group falls within the limit.

  2. Wait until the stand-alone installation package is uploaded and click Next. The Migration wizard creates a custom installation package and a remote installation task for it. The task scope will include the administration group that you selected on the Managed devices to export page; the task startup schedule will be set to Manually by default. The Migration wizard displays the creation progress. Wait until the refresh icons () are replaced with the green check marks () and click Next.
  3. If necessary, select the Run newly created remote installation task check box (cleared by default) for the devices in the selected administration group of the Administration Server running on-premises and all of its subgroups. In this case, the devices will be switched under management of Kaspersky Security Center Cloud Console—but only after Network Agent installation completes. The full path will be displayed to the administration group in which the task will be run.

    The task must only be started after the import to Kaspersky Security Center Cloud Console finishes. Otherwise, the device names may be duplicated in the list.

  4. Click Finish to close the Migration wizard and start the remote installation task for the following purposes:
    • Upgrading the Network Agent instances
    • Switching the Network Agent instances under management through Kaspersky Security Center Cloud Console

    If you have left the Run newly created remote installation task check box cleared, you can start the task later manually, if necessary.

You can check that you can now manage the migrated Network Agent instances through Kaspersky Security Center Cloud Console. To do this, go to Assets (Devices)Managed devices. Make sure that migrated managed devices have the confirmation icon () in the Visible, Network Agent is installed, and Network Agent is running columns. Also, make sure that these devices do not have the Not connected for a long time status description.

See also:

Scenario: Migration without a hierarchy of Administration Servers

Page top

[Topic 195257]

Migration with a hierarchy of Administration Servers

Expand all | Collapse all

This section describes the migration of managed devices and related objects from Kaspersky Security Center Web Console running on-premises to Kaspersky Security Center Cloud Console. The process involves a hierarchy: Kaspersky Security Center Web Console running on-premises acts as the secondary Administration Server and Kaspersky Security Center Cloud Console acts as the primary Administration Server.

Every administration group that you transfer to Kaspersky Security Center Cloud Console must contain the managed devices of a single operating system. If your network includes the devices of different operating systems, allocate them in different administration groups, and then migrate each group separately.

After you finish the migration, all Network Agents in the group within the migration scope are upgraded and managed through Kaspersky Security Center Cloud Console.

Before you start, do the following:

  • Upgrade Administration Server running on-premises to version 14.2 or later.
  • Install Kaspersky Security Center Web Console version 12.1 or later.
  • Upgrade Network Agent on the managed devices to version 12 or later.
  • On Windows devices, use Network Agent without an uninstallation password.

    If the password has already been set, do one of the following in Kaspersky Security Center Web Console:

    • Disable the Use uninstallation password option in the Network Agent policy settings.
    • Uninstall Network Agent remotely by using the Uninstall application remotely task. In the Application to uninstall field of the task, select Kaspersky Security Center Network Agent. Do not forget to enter the uninstallation password.
  • Upgrade the managed applications to the versions supported by Kaspersky Security Center Cloud Console.
  • Make sure that you have policies for the latest versions of the managed applications. If you use outdated policies, create new ones for the application versions supported by Kaspersky Security Center Cloud Console.
  • To use actual policies, upgrade the web plug-ins for the applications that you intend to manage through Kaspersky Security Center Cloud Console.
  • Uninstall Kaspersky applications from managed devices if these applications are not supported by Kaspersky Security Center Cloud Console.
  • Decrypt all the data (disk-level or file-level) that was encrypted by Kaspersky Endpoint Security for Windows on managed devices running the Windows operating system, and disable the encryption feature on the managed devices through the application policy or locally. For more information, see Help for Kaspersky Endpoint Security for Windows.

    If the Windows device still stores any files or folders encrypted through Kaspersky Endpoint Security for Windows, the Network Agent upgrade will be canceled during the migration process. A notification will prompt you to decrypt all data on the device and disable the encryption feature.

Kaspersky Security Center Cloud Console allows for a maximum of 25,000 managed devices per one Administration Server.

To perform a migration to Kaspersky Security Center Cloud Console:

  1. Estimate the scope of the migration process, that is, review the administration group to export and assess the number of managed devices in it. Make sure that all the activities listed as migration prerequisites have been completed successfully.
  2. In Kaspersky Security Center Cloud Console, proceed to the secondary Administration Server for the managed devices that you want to migrate.
  3. In the main menu, go to OperationsMigration.

    The welcome page of the Migration wizard opens.

  4. On the welcome page, click Next.

    The Managed devices to export page opens, displaying the entire hierarchy of administration groups of the secondary Administration Server.

  5. On the Managed devices to export page, click the chevron icon () next to the Managed devices group name, and then expand the hierarchy of administration groups. Select the administration group that you want to export.

    The Migration wizard checks the total number of managed devices included in the selected administration group. If this number exceeds 10,000, an error message appears. The Next button remains unavailable (dimmed) until the number of managed devices in the selected administration group falls within the limit.

  6. Select the managed applications whose policies and tasks must be transferred to Kaspersky Security Center Cloud Console together with group objects. To select the managed applications whose objects are to be exported, select the check boxes next to their names in the list.

    Although Kaspersky Security Center Administration Server is present on the list, selecting the corresponding check box does not result in the export of its policies.

    To make sure that your managed applications are supported by Kaspersky Security Center Cloud Console, click the corresponding link. It will redirect you to the Online Help topic containing the list of applications managed by Kaspersky Security Center Cloud Console.

    If you select applications that are not supported by Kaspersky Security Center Cloud Console, the policies and tasks of these applications will be migrated anyway, but you will not be able to manage them in Kaspersky Security Center Cloud Console, due to the unavailability of the dedicated plug-ins.

  7. View the list of group objects exported by default. You can also specify non-group objects to be exported together with the selected administration group, if necessary, such as global tasks, custom device selections, reports, custom roles, internal users and security groups, and custom application categories with content added manually. This page includes the following sections:
    • Global tasks

      The list of global tasks of managed applications, as well as global tasks of Network Agent.

      If a global task that you selected applies to a specific object selection, this selection will also be exported.

      Although the global tasks of Administration Server are present on the list, you cannot export them; selecting those tasks does not affect the export scope. Remote installation tasks also remain outside the export scope, because their respective installation packages cannot be exported.

    • Device selections

      The list of custom device selections.

    • Reports

      The editable list of report instances to be exported.

      If a report that you selected applies to a specific object selection, this selection will also be exported.

      Kaspersky Security Center Cloud Console contains the same set of report templates as Kaspersky Security Center Web Console, so you can select for export only the reports that you created manually or reconfigured.

    • Group objects

      The list of group objects to be exported by default. The following objects related to the selected administration group will be exported in their entirety by default:

      • Administration group structure, that is, all subgroups of the selected administration group.
      • Devices that have been included in the administration groups to be exported.
      • Tags that have been assigned to the devices to be exported.

        If a tag was created in Kaspersky Security Center Web Console but never assigned to any device, it will not be exported. The auto-tagging rules will not be exported, either.

      • Group policies of the managed applications that have been selected.

        Administration Server policies and Network Agent policies are not exported.

      • Group tasks of the managed applications that have been selected and Network Agent group tasks.

        Administration Server tasks are not exported.

      You can also prevent certain types of non-group objects from being exported:

      • To cancel export for custom roles (that is, those created by the user only), select the Exclude custom roles from export check box.
      • To cancel export for internal users and security groups, select the Exclude internal users and security groups from export check box.
      • To cancel export for custom application categories with content added manually, select the Exclude custom application categories from export check box.

    If you transfer devices of various operating systems to Kaspersky Security Center Cloud Console, non-group objects only need to be migrated once.

  8. After you defined the migration scope, click Next to start the export process. The Creating the export file page opens, where you can view the export progress for each type of object that you included in the migration scope. Wait until each refresh icon (), located next to each item in the list of objects, is replaced with a green check mark (). The export finishes and the export file is automatically saved to a temporary folder. The next page opens, displaying the entire hierarchy of administration groups in Kaspersky Security Center Cloud Console, which acts as the primary Administration Server.
  9. Select the check box next to the administration group to which the group objects must be imported, and then click Next. The file is unpacked, and the non-group objects and the group objects are restored to the target administration group.

    If the name of the object that you restore is identical to the name of an existing object, the restored object has an incremental suffix added.

    When the import completes, the exported structure of administration groups, including the details of devices, appears under the target administration group that you selected. The non-group objects are also imported.

    You cannot minimize the Migration wizard and perform any concurrent operations during the import. Wait until each refresh icon (), located next to each item in the list of objects, is replaced with a green check mark () and the import finishes. After this, the devices start switching to Kaspersky Security Center Cloud Console.

  10. After the import completes, the Migration wizard displays a list of Network Agent installation packages available in Kaspersky Security Center Cloud Console for an appropriate operating system. Select the installation package containing the relevant version and localization of Network Agent.

    Select the Kaspersky Network Agent for Windows installation package only if you have previously completed the quick start wizard in your Kaspersky Security Center Cloud Console workspace and if you perform the migration of Windows devices.

  11. Click Next.

    The Migration wizard creates a new stand-alone installation package (or uses an existing one) and a custom installation package based on it, as well as the corresponding remote installation task. The task scope includes the administration group that you selected on the Managed devices to export page. The task startup schedule is set to Manually by default. The Migration wizard displays the creation progress.

  12. Wait until each refresh icon () is replaced with a green check mark (), and then click Next.
  13. If necessary, select the Run newly created remote installation task check box (cleared by default) for the devices in the selected administration group in Kaspersky Security Center Web Console running on-premises and all of its subgroups. After the Network Agent installation completes, you can manage the selected devices through Kaspersky Security Center Cloud Console. The full path is displayed to the administration group in which the task is to be run.

    The remote installation task must only be started after the import to Kaspersky Security Center Cloud Console finishes. Otherwise, the devices may be duplicated.

  14. Click Finish to close the Migration wizard and start the remote installation task for the following purposes:
    • Upgrading the Network Agent instances
    • Managing the Network Agent instances through Kaspersky Security Center Cloud Console

    If you have left the Run remote installation task check box cleared, you can start the task later manually, if necessary.

You can check that you can now manage the migrated Network Agent instances through Kaspersky Security Center Cloud Console. To do this, go to Assets (Devices)Managed devices. Make sure that migrated managed devices have the confirmation icon () in the Visible, Network Agent is installed, and Network Agent is running columns. Also, make sure that these devices do not have the Not connected for a long time status description.

See also:

Scenario: Migration without a hierarchy of Administration Servers

Page top

[Topic 200394]

Scenario: Migration of devices running Linux or macOS operating systems

This section describes how to migrate devices running Linux or macOS operating systems from Kaspersky Security Center Web Console running on-premises to Kaspersky Security Center Cloud Console. The basic scenarios of migration without a hierarchy of Administration Servers and migration with such a hierarchy allow transferring all devices and related objects to Kaspersky Security Center Cloud Console. However, if your network includes devices running not only Windows, but also Linux or macOS, you need to transfer the devices of each operating system type separately. As a result, you have to perform the migration several times.

Prerequisites

Before you start, do the following:

  • Upgrade Administration Server running on-premises to version 12 Patch A or later.
  • Install Kaspersky Security Center Web Console of version 12.1 or later.
  • Upgrade Network Agent on managed devices to version 12 or later.
  • Upgrade the managed applications to the versions supported by Kaspersky Security Center Cloud Console.
  • Make sure that you have policies for the latest versions of the managed applications. If you use outdated policies, create new ones for the application versions supported by Kaspersky Security Center Cloud Console.
  • To use actual policies, upgrade the web plug-ins for the applications that you intend to manage through Kaspersky Security Center Cloud Console.
  • Uninstall Kaspersky applications from managed devices if these applications are not supported by Kaspersky Security Center Cloud Console, and then replace the uninstalled applications with supported ones.

Kaspersky Security Center Cloud Console allows for a maximum of 25,000 managed devices per one Administration Server.

Migration stages

Migration to Kaspersky Security Center Cloud Console comprises the following stages:

  1. Grouping managed devices by their operating systems

    If your network includes devices running different operating systems (Windows, Linux, or macOS), place the devices of each operating system in separate administration groups in Kaspersky Security Center Web Console. Also, create an administration group for each Linux distribution. For example, if you have Debian and Red Hat Linux devices, allocate them in different administration groups. This will allow you to perform the migration successfully because different Network Agent installation packages are required for various operating systems.

  2. Perform separately the migration of every administration group and its application objects

    The managed devices of each operating system must migrate separately, to include their policies and tasks. For example, if you have Windows, macOS, Ubuntu, and CentOS devices, first, transfer the devices running the Windows operating system to Kaspersky Security Center Cloud Console, then macOS, then Ubuntu, and eventually, CentOS. You can transfer the managed devices in any order.

    To do this, perform the migration without the hierarchy of Administration Servers or migration with such a hierarchy, depending on whether your network includes secondary Administration Servers. During the migration, use the Network Agent installation package corresponding to the operating system of the transferred devices. For example, select the Kaspersky Security Center 13.2 Network Agent for Linux devices to perform the migration successfully.

    Note that non-group objects, such as global tasks, custom device selections, or reports, only need to be migrated once.

Results

Upon finishing with the migration, you can make sure that it was successful:

  • The proper version of Network Agent is re-installed on each managed device running the Linux or macOS operating system.
  • All Linux or macOS devices are managed through Kaspersky Security Center Cloud Console.
  • All object settings that were effective before migration are preserved.
Page top

[Topic 196539]

Scenario: Reverse migration from Kaspersky Security Center Cloud Console to Kaspersky Security Center

You may want to migrate the managed devices from Kaspersky Security Center Cloud Console to Kaspersky Security Center Administration Server. For example, this process can be used to roll back migration to Kaspersky Security Center Cloud Console.

Prerequisites

Before you start, make sure that the following prerequisites are met:

  • Kaspersky Security Center Cloud Console is available and has managed devices connected.
  • Kaspersky Security Center 14.2 (or later) Administration Server is available and has a Network Agent installation package of version 13 or later.

Reverse migration stages

Reverse migration comprises the following stages:

  1. Creating a Network Agent stand-alone installation package in Kaspersky Security Center Administration Server on-premises

    In Kaspersky Security Center Administration Server running on-premises, create a Network Agent stand-alone installation package.

    During the creation process, you can select the Move unassigned devices to this group option to specify an administration group to which you want to move Network Agents after installation. If you have specified the administration group, an automatic moving rule is created that will move to the target administration group all Network Agents installed with this stand-alone installation package.

    To ensure correct reverse migration, make sure that you select the Network Agent version that is equal to or later than the version used in Kaspersky Security Center Cloud Console.

  2. Creating a custom installation package in Kaspersky Security Center Cloud Console

    In Kaspersky Security Center Cloud Console, create a custom installation package based on the stand-alone installation package that you created and saved from Kaspersky Security Center Administration Server running on-premises.

    To enable package installation in silent mode, in the Executable file command line field, specify the -s key.

  3. Creating a remote installation task

    In Kaspersky Security Center Cloud Console, create a remote installation task using the custom installation package that you have created.

  4. Running the remote installation task

    Start the remote installation task that you created. The task initiates the re-installation of all Network Agents in the specified administration group; and it also switches the Network Agents under management of Kaspersky Security Center Administration Server running on-premises by changing the connection address and modifying other connection settings.

    If you did not specify any target administration group during creation of the stand-alone installation package, all devices are moved to the Unassigned devices group.

Results

Upon finishing with the migration, you can make sure that it was successful:

  • All devices within the scope of the remote installation task that were previously managed through Kaspersky Security Center Cloud Console are now managed by Kaspersky Security Center Administration Server running on-premises.
  • The devices are automatically moved to the administration group specified in the installation package settings.

The remote installation task in Kaspersky Security Center Cloud Console cannot be completed: it has no more target devices since all of them have modified connection settings. You have to stop the task manually after you make sure that the error icon (The red exclamation mark icon.) has appeared in the Visible column of the Managed Devices list for all devices from the migration scope.

Page top

[Topic 153952]

Migration with virtual Administration Servers

If you have virtual Administration Servers in your existing Kaspersky Security Center on-premises infrastructure, you cannot migrate from Kaspersky Security Center on-premises to Kaspersky Security Center Cloud Console by using the Migration wizard. Also, you will be able to migrate only your customers' devices. You will have to create policies, tasks, and reports manually.

You can perform one of the following migration scenarios:

In this section

Scenario: Migration with virtual Administration Servers by moving devices

Scenario: Manual migration with virtual Administration Servers

Scenario: Moving devices from administration groups under management of virtual Servers

Page top

[Topic 228022]

Scenario: Migration with virtual Administration Servers by moving devices

To perform the migration from Kaspersky Security Center Web Console running on-premises to Kaspersky Security Center Cloud Console, you can move your devices from virtual Administration Servers to a primary Administration Server.

Prerequisites

Before migration, you must perform a number of actions, including upgrading Administration Server running on-premises to version 12 or later and upgrading the managed applications to versions supported by Kaspersky Security Center Cloud Console.

Migration scenario

The scenario proceeds in stages:

  1. Creating an administration group for each of your virtual Administration Servers

    You create the group in your Kaspersky Security Center running on-premises.

  2. Moving your customers' devices

    In Kaspersky Security Center running on-premises, move your customers' devices from each virtual Administration Server to the respective administration group created at the previous stage.

  3. Migration

    Perform migration as described for the network without a hierarchy of Administration Servers.

  4. Moving devices under management of virtual Administration Servers (optional step)

    If you want to manage your customers through virtual Administration Servers, move the devices from the administration groups under management of virtual Administration Servers.

  5. Creating policies, tasks, and reports

    Create policies, tasks, and reports as required.

Results

Upon finishing with the migration, you can make sure that it was successful:

  • Network Agent is re-installed on all managed devices.
  • All devices are managed through Kaspersky Security Center Cloud Console.
  • All object settings that were effective before migration are preserved.

Page top

[Topic 228023]

Scenario: Manual migration with virtual Administration Servers

You can migrate from Kaspersky Security Center Web Console running on-premises to Kaspersky Security Center Cloud Console manually.

Prerequisites

Before migration, you must perform a number of actions, including upgrading Administration Server running on-premises to version 12 or later and upgrading the managed applications to versions supported by Kaspersky Security Center Cloud Console.

Migration scenario

The scenario proceeds in stages:

  1. Creating an administration group for each of your virtual Administration Servers

    In Kaspersky Security Center Cloud Console, create an administration group that corresponds to each of your virtual Administration Servers.

  2. Creating a stand-alone installation package for Network Agent

    Create a stand-alone installation package for Network Agent. During creation, specify the administration group that you created at the previous stage. This means that you must create an individual stand-alone installation package for each administration group.

    This stage occurs in your Kaspersky Security Center Cloud Console.

  3. Downloading the stand-alone installation packages

    Download the stand-alone installation packages that you created at the previous stage. This stage occurs in your Kaspersky Security Center Cloud Console.

  4. Creating an archive with each stand-alone installation package

    Available archive types are: ZIP, CAB, TAR, or TAR.GZ.

  5. Creating custom installation packages for Network Agent

    Create custom installation packages for Network Agent. During creation, use archives that you created at the previous stage.

    This stage occurs in your Kaspersky Security Center running on-premises.

  6. Creating remote installation tasks

    Create remote installation tasks to install Network Agent from the created custom installation packages.

    When creating a task, specify a corresponding administration group.

    This stage occurs in your Kaspersky Security Center running on-premises.

  7. Running the created remote installation tasks

    Network Agents are updated. The Kaspersky Security Center Cloud Console Administration Server takes over the management of them.

    All devices are migrated to Kaspersky Security Center Cloud Console and are placed in administration groups that were specified when you created stand-alone installation packages for Network Agent.

  8. Moving devices under management of virtual Administration Servers (optional step)

    If you want to manage your customers through virtual Administration Servers, move the devices from the administration groups under management of virtual Administration Servers.

  9. Creating policies, tasks, and reports

    Create policies, tasks, and reports as required.

Results

Upon finishing with the migration, you can make sure that it was successful:

  • Network Agent is re-installed on all managed devices.
  • All devices are managed through Kaspersky Security Center Cloud Console.

    All object settings that were effective before migration are preserved.

Page top

[Topic 223067]

Scenario: Moving devices from administration groups under management of virtual Servers

You may want to manage your customers through virtual Administration Servers. If you migrated devices and other items from Kaspersky Security Center on-premises to Kaspersky Security Center Cloud Console, the devices are located in administration groups. To manage the customers' devices through virtual Administration Servers, you must move the devices from the administration groups under the management of virtual Administration Servers.

Prerequisites

You have created a virtual Administration Server for each of your customers.

All devices of each customer are located in an individual administration group.

Stages

The scenario proceeds in stages:

  1. Creating a stand-alone installation package for Network Agent

    Switch to each of the created virtual Administration Server, then create a stand-alone installation package for Network Agent. You can switch Administration Servers in the main menu by clicking the chevron icon (The chevron icon.) to the right of the current Administration Server name, and then selecting the required Administration Server.

  2. Downloading the stand-alone installation packages

    Download the stand-alone installation packages that you created at the previous stage.

  3. Create an archive with each stand-alone installation package

    Available archive types are: ZIP, CAB, TAR, or TAR.GZ.

  4. Creating custom installation packages for Network Agent

    Create custom installation packages for Network Agent. During creation, use archives that you created at the previous stage.

    This stage occurs on the primary Administration Server.

  5. Creating remote installation tasks

    Create remote installation tasks to install Network Agent from the created custom installation packages.

    When creating a task, specify a corresponding administration group.

    This stage occurs on the primary Administration Server.

  6. Run the created remote installation tasks

    Network Agents are updated. The devices are moved under management of virtual Administration Servers.

  7. Creating policies, tasks, and reports

    Create policies, tasks, and reports as required.

Results

You can now manage the migrated customers' devices by using virtual Administration Servers.

Page top

[Topic 271993]

About migration from Kaspersky Endpoint Security Cloud

You can migrate your workspace from Kaspersky Endpoint Security Cloud to Kaspersky Security Center Cloud Console.

For a detailed description of the migration procedure, refer to the Kaspersky Endpoint Security Cloud Help.

After the migration is finished, a new workspace is created in Kaspersky Security Center Cloud Console, and you receive a corresponding email notification. The new workspace has the same name as the workspace in Kaspersky Endpoint Security Cloud.

Go to the new workspace and make sure that the objects are transferred:

  • Kaspersky Next license is displayed in the Licensing section and in the Administration Server properties window.
  • In the main menu, go to Assets (Devices)Managed devices.

    All the devices running Windows and macOS are displayed in the list of managed devices.

    The transferred devices are automatically connected to the workspace created in Kaspersky Security Center Cloud Console. This may take a while.

  • In the main menu, go to Assets (Devices)Policies & profiles.

    In the list of policies, the Network Agent policy is displayed with the password protection configured.

Page top

[Topic 191740]

About quick start wizard

The quick start wizard in Kaspersky Security Center Cloud Console enables you to create a minimum of necessary tasks and policies, adjust a minimum of settings, and start creating installation packages of Kaspersky applications. Using the wizard, you can make the following changes to Kaspersky Security Center Cloud Console:

  • Initiate downloading of installation packages for managed Kaspersky applications.
  • Create a Network Agent stand-alone installation package for devices running Windows, Linux, or macOS.
  • Create Kaspersky Security Center Network Agent policy.
  • Create the Download updates to the repositories of distribution points task.
  • Create policies and tasks for managed Kaspersky applications.
  • Configure interaction with .

After the quick start wizard has finished, installation packages for Network Agent and managed Kaspersky applications appear in the Discovery & deploymentDeployment & assignmentInstallation packages list.

The quick start wizard creates policies for managed applications, such as Kaspersky Endpoint Security for Windows, unless such policies are created for the Managed devices group. The quick start wizard creates tasks if tasks with the same names do not exist for the Managed devices group.

Kaspersky Security Center Cloud Console automatically prompts you to run the quick start wizard after you have created a company workspace and have started Kaspersky Security Center Cloud Console for the first time. You can also start the quick start wizard manually at any time.

Page top

[Topic 188031]

Starting quick start wizard

Kaspersky Security Center Cloud Console automatically prompts you to run the quick start wizard after you have created a company workspace and have started Kaspersky Security Center Cloud Console for the first time. You can also start the quick start wizard manually at any time.

If you start the quick start wizard again, tasks and policies created at the previous run of the wizard are not created again.

To start the quick start wizard manually:

  1. In the main menu, click the settings icon () next to the name of the Administration Server.

    The Administration Server properties window opens.

  2. On the General tab, select the General section.
  3. Click Start quick start wizard.

Alternatively, you can start the quick start wizard by selecting Discovery & deploymentDeployment & assignmentQuick start wizard.

The wizard prompts you to perform initial configuration of Kaspersky Security Center Cloud Console. Follow the instructions of the wizard. Proceed through the wizard by using the Next button. Use the Back button to return to the previous step of the wizard.

See also:

About quick start wizard

Step 1. Selecting installation packages to download

Step 2. Configuring a proxy server

Step 3. Configuring Kaspersky Security Network

Step 4. Configuring third-party update management

Step 5. Creating a basic network protection configuration

Step 6. Closing the quick start wizard

Page top

[Topic 180305]

Step 1. Selecting installation packages to download

In the list, select the Kaspersky applications to install on the client devices. Kaspersky Security Center Cloud Console will create installation packages for the selected applications. Afterwards, you will use the created installation packages to install the applications.

When selecting an installation package to download, pay attention to the language: installation packages are available in different languages.

Select the following applications:

  • Kaspersky Security Center Network Agent

    When selecting Network Agent installation packages, consider the following:

    • Network Agent must be installed on every client device. Therefore, select a Network Agent appropriate for each operating system running on the client devices.
    • Network Agent must be installed manually through a stand-alone installation package on a device that you select to act as a distribution point. Distribution points are required to perform network polling and remote installation of Kaspersky security applications on client devices. Therefore, you must select at least one installation package of Network Agent. While you proceed to the next steps of the wizard, Kaspersky Security Center Cloud Console creates the Network Agent stand-alone installation package.

      Compared to Windows-based distribution points, Linux-based and macOS-based distribution points have limited functionality. It is strongly recommended that you select Windows-based computers to act as distribution points.

      You can select Network Agents for Windows, Linux, and macOS. If you select Network Agent only for one operating system, for example, macOS, then a stand-alone installation package will be created for the selected operating system. If you select Network Agent for several operating systems, Kaspersky Security Center Cloud Console creates only one stand-alone installation package according to the following priorities: Windows is of the highest priority, then Linux, and then macOS. For example, if you select Network Agents for Linux and macOS, then Kaspersky Security Center Cloud Console creates a stand-alone installation package for Network Agent for Linux. You can create a Network Agent stand-alone installation package for any of these operating systems manually at any time.

  • Kaspersky security applications

    Select installation packages appropriate for the operating systems that are installed on client devices in your organization.

See also:

About quick start wizard

Starting quick start wizard

Page top

[Topic 175963]

Step 2. Configuring a proxy server

Expand all | Collapse all

If your organization uses a proxy server to connect to the internet, specify the proxy server settings at this step of the wizard. These settings are added to the Network Agent installation package. After installation, Network Agent automatically uses these settings on each client device.

Specify the following settings for proxy server connection:

  • Use proxy server
  • Address
  • Port number
  • Proxy server authentication

    If this option is enabled, in the entry fields you can specify the credentials for proxy server authentication.

    We recommend that you specify the credentials of an account that has minimum privileges required only for the proxy server authentication.

    By default, this option is disabled.

  • User name

    User name of the account under which connection to the proxy server is established.

    We recommend that you specify the credentials of an account that has minimum privileges required only for the proxy server authentication.

  • Password

    Password of the account under which connection to the proxy server is established.

    We recommend that you specify the credentials of an account that has minimum privileges required only for the proxy server authentication.

See also:

Ports used by Kaspersky Security Center Cloud Console

About quick start wizard

Starting quick start wizard

Page top

[Topic 175970]

Step 3. Configuring Kaspersky Security Network

Expand all | Collapse all

If at the first step of the wizard you downloaded the Kaspersky Endpoint Security for Windows installation package, the text of the KSN Statement for the following applications is displayed:

  • Kaspersky Endpoint Security for Windows
  • Kaspersky Security Center installed on local devices
  • Kaspersky Security Center Cloud Console installed in the cloud environment

If you did not download the Kaspersky Endpoint Security for Windows installation package, the KSN Statement for this application is not displayed.

In trial mode, only the KSN Statement for Kaspersky Endpoint Security for Windows is displayed.

Carefully read the Kaspersky Security Network Statement. Select one of the following options:

  • I agree to use Kaspersky Security Network

    Kaspersky Security Center Cloud Console and managed applications installed on client devices will automatically transfer their operation details to Kaspersky Security Network. Participation in Kaspersky Security Network ensures faster updates of databases containing information about viruses and other threats, which ensures a faster response to emergent security threats.

  • I do not agree to use Kaspersky Security Network

    Kaspersky Security Center Cloud Console and managed applications will provide no information to Kaspersky Security Network.

    If you select this option, the use of Kaspersky Security Network will be disabled.

By default, the use of KSN is disabled. Later, if you change your mind about using KSN, you can enable (or disable) the corresponding option in the Administration Server properties window, in the KSN Settings section.

See also:

About KSN

Page top

[Topic 203283]

Step 4. Configuring third-party update management

This step is not displayed if the Find vulnerabilities and required updates task already exists.

If you want to get a list of updates for the applications installed on the managed devices and a list of found vulnerabilities and recommended fixes for them, enable the Search for third-party software updates and vulnerability fixes option. If this option is enabled, Kaspersky Security Center Cloud Console creates the Find vulnerabilities and required updates task.

See also:

Scenario: Updating third-party software

Scenario: Finding and fixing software vulnerabilities

Creating the Find vulnerabilities and required updates task

Creating the Install required updates and fix vulnerabilities task

Page top

[Topic 176001]

Step 5. Creating a basic network protection configuration

At this step of the wizard, click the Create button to create objects required for initial protection of your client devices.

Kaspersky Security Center Cloud Console performs two operations:

  • Creating basic policies and tasks with default settings

    The following policies are created:

    • Kaspersky Security Center Network Agent policy
    • Policies for managed Kaspersky applications

    The following tasks are created:

    • The Download updates to the repositories of distribution points task
    • The Find vulnerabilities and required updates task

      This task is only created if you enabled the Search for third-party software updates and vulnerability fixes option on the previous step of the wizard.

    • Tasks for managed Kaspersky applications
  • Creating a stand-alone installation package for Network Agent

    You will use this package to install Network Agent on distribution points. Kaspersky Security Center Cloud Console creates the stand-alone installation package on the basis of the Network Agent installation package that you selected at the previous step of the wizard. During the package creation, you must read and accept the terms of EULA for Network Agent. When the stand-alone installation package is created, you will be prompted to download it to the device you are using at the moment.

    Network Agent stand-alone installation package creation can take some time. You can proceed to the next step of the wizard. The process will continue in background mode. If necessary, you can track the installation package download status in the Package status column (Discovery & deploymentDeployment & assignmentInstallation packages).

    For authentication reasons, each stand-alone installation package is signed by using a certificate. The certificate is reissued from time to time. After each procedure of certificate reissue, Kaspersky Security Center Cloud Console automatically updates the signatures of all created stand-alone installation packages. For downloaded stand-alone installation packages, an automatic signature update cannot be performed. Therefore, the certificate expires and a certificate error might occur while you install an application from a stand-alone installation package. In this case, download the stand-alone installation package again.

See also:

About quick start wizard

Starting quick start wizard

Step 1. Selecting installation packages to download

Creating a stand-alone installation packages for Network Agent

Page top

[Topic 176020]

Step 6. Closing the quick start wizard

On the quick start wizard completion page, read about the additional operations you must perform in order to deploy Kaspersky security applications on the client devices. Follow the stages provided in the scenario of Kaspersky applications initial deployment.

See also:

About quick start wizard

Starting quick start wizard

Step 1. Selecting installation packages to download

Step 2. Configuring a proxy server

Step 3. Configuring Kaspersky Security Network

Step 4. Configuring third-party update management

Step 5. Creating a basic network protection configuration

Scenario: Kaspersky applications initial deployment

Page top

[Topic 175982]

Scenario: Kaspersky applications initial deployment

This scenario describes how to install Kaspersky applications on client devices in Kaspersky Security Center Cloud Console. First, you must deploy distribution points on your network. Then, by means of the distribution points, you must perform network polling and discover networked devices on your network. After that, you can deploy Kaspersky applications on networked devices.

When the scenario is complete, the Kaspersky applications are deployed on the selected client devices in your organization's network. You can manage all the devices with Kaspersky applications installed.

Prerequisites

Before you start, make sure that the following prerequisites are met:

  • The quick start wizard has finished.
  • Network Agent and security applications installation packages are created.
  • The address https://aes.s.kaspersky-labs.com/endpoints/ is included in managed device firewall exceptions.
  • You have information about internet settings for client devices in your organization, information about the gateway, and proxy server settings.
  • Client devices in your organization are not encrypted.

Stages

The Kaspersky applications initial deployment proceeds in stages:

  1. Selecting a device to act as a distribution point

    In Kaspersky Security Center Cloud Console, a distribution point is intended for:

    • Network polling and device discovery
    • Remote installation of Network Agent on client devices
    • Connection of client devices to Administration Server (when a distribution point is acting as a connection gateway)

    Select a device on your organization's network to act as a distribution point for an

    . The selected device must meet the requirements for distribution point. Depending on the amount of client devices in your organization's network, select the correct number of devices to act as distribution points.

  2. Creating a stand-alone installation package for Network Agent

    Create a stand-alone installation package for Network Agent to install on the distribution point.

    If your client devices do not have direct internet access to connect to Administration Server, in the Network Agent installation package settings, configure the connection gateway and proxy server settings.

  3. Installing Network Agent on the selected device to act as a distribution point

    Deliver the stand-alone installation package for Network Agent to the selected device by any method. For example, you can copy the stand-alone installation package to a removable drive (such as a flash drive), or place it in a shared folder.

    In the Properties window of the stand-alone installation package file, verify that the stand-alone installation package for Network Agent is signed by Kaspersky.

    Run the installation of the stand-alone installation package for Network Agent on the selected device. Network Agent is now installed according to the settings of the Network Agent installation package and is connected to Administration Server. The device with Network Agent is placed in the administration group that was specified when the stand-alone installation package for Network Agent was created.

    If you install Network Agent by using a stand-alone installation package on a device running Microsoft Windows XP Professional for Embedded Systems 32-bit, the installation fails. To resolve this issue, preliminarily install the update KB2868626 for Windows XP from the Microsoft website: https://www.catalog.update.microsoft.com/Search.aspx?q=KB2868626.

  4. Assigning the device with Network Agent installed to act as a distribution point

    Assign the device with Network Agent installed to act as a distribution point.

  5. Configuring and performing network polling for the distribution point

    Configure network polling for the distribution point with the Network Agent installed. As an option, you can configure network polling in the Network Agent policy.

    After network polling according to schedule is complete, the client devices connected to your organization's network are discovered and placed in the Unassigned devices group.

  6. Creating installation packages for Network Agent and managed Kaspersky applications

    If you did not start the quick start wizard, or skipped the step of creating installation packages, create installation packages for Kaspersky applications. You must create installation packages both for Network Agent and for managed Kaspersky applications appropriate for the operating system installed on client devices on your organization's network.

  7. Removing third-party security applications

    If third-party security applications are installed on client devices on your organization's network, remove them before installing the Kaspersky application.

  8. Installing Kaspersky applications on client devices

    Create tasks to install Network Agent and managed Kaspersky applications on client devices on your organization's network. When creating the tasks, use the Install application remotely task type. For the task to install Network Agent, use the Using operating system resources through distribution points option. For the task to install managed Kaspersky applications, use the Using Network Agent option. After the tasks are created, you can configure their settings. Make sure that the schedule for each task meets your requirements. First, the task to install Network Agent must be run. Then, after Network Agent is installed on client devices, the task to install managed Kaspersky applications must be run.

    As an option, you can create one remote installation task to install Network Agent and managed Kaspersky applications on client devices on your organization's network. In this case, in the Installation packages block, use the Select installation package option and the Select Network Agent option; in the Force installation package download block, use the Using operating system resources through distribution points option.

    You also can create several remote installation tasks to install managed Kaspersky applications for different administration groups or different device selections.

    If you have client devices that are out of the network with distribution point, for example, laptops of remote users, you must create and deliver the Network Agent stand-alone installation package to those client devices by any method. Install Network Agent stand-alone installation package locally on those client devices. Then you can install managed Kaspersky applications on those remote users' devices following the same instructions as for other devices discovered by the distribution point.

    Run the remote installation tasks.

    As an option, to install Kaspersky applications, you can start the Protection deployment wizard.

  9. Installing Kaspersky Security for Mobile

    If you plan to manage corporate mobile devices, follow the instructions provided in the Kaspersky Security for Mobile Help for information about deployment of Kaspersky Endpoint Security for Android.

  10. Verifying initial deployment of Kaspersky applications

    Generate and view the Report on Kaspersky application versions. Make sure that the managed Kaspersky applications are installed on all client devices in your organization.

For the full disk encryption, Kaspersky Security Center Cloud Console supports only BitLocker.

See also:

Creating installation packages for Kaspersky applications

Distributing installation packages to secondary Administration Servers

Creating a stand-alone installation packages for Network Agent

Viewing the list of stand-alone installation packages

Creating custom installation packages

Requirements for a distribution point

Network Agent installation package settings

Virtual infrastructure

Usage of Network Agent for Windows, Linux, and macOS: Comparison

Specifying settings for remote installation on Unix devices

Replacing third-party security applications

Options for manual installation of applications

Forced deployment through the remote installation task of Kaspersky Security Center Cloud Console

Protection deployment wizard

Network settings for interaction with external services

Preparing a device running Astra Linux in the closed software environment mode for installation of Network Agent

Preparing a Linux device and installing Network Agent on a Linux device remotely

Installing applications by using a remote installation task

Starting and stopping Kaspersky applications

Page top

[Topic 181528]

Creating installation packages for Kaspersky applications

To deploy Kaspersky applications on networked devices in your organization, you must create installation packages of Kaspersky applications in Kaspersky Security Center Cloud Console.

To create a Kaspersky application installation package:

  1. Do one of the following:
    • In the main menu, go to Discovery & deployment → Deployment & assignmentInstallation packages.
    • In the main menu, go to Operations → RepositoriesInstallation packages.

    You can also view notifications about new packages in the list of onscreen notifications. If there are notifications about a new package, you can click the link next to the notification and proceed to the list of available installation packages.

    A list of installation packages available on the Administration Server is displayed.

  2. Click Add.

    The New package wizard starts. Proceed through the wizard by using the Next button.

  3. Select Create an installation package for a Kaspersky application.

    A list of distribution packages available on Kaspersky web servers appears.

  4. Click the name of a distribution package, for example, Kaspersky Endpoint Security for Windows (<version number>).

    A window opens with information about the distribution package.

  5. Read the information and click the Download and create installation package button.

    If a distribution package cannot be automatically converted to an installation package, the Download distribution package button is displayed instead of the Download and create installation package button. In this case, download the distribution package, and then use the downloaded file to create a custom installation package.

    The download of the installation package starts. You can close the wizard's window. In this case, the download process will continue in background mode. You can track the installation package download status as well as filter and sort the statuses in the Package status column.

    If the download process stops and the download status switches to Accept EULA, then click the installation package name, and then proceed to step 6 of the instruction. By default, the installation packages with In progress and Accept EULA statuses are placed in the beginning of the list.

    If you plan to perform migration from Kaspersky Security Center Web Console to Kaspersky Security Center Cloud Console and your organization's security regulations require the use of proxy when accessing the corporate network, this may affect the migration process. After you create a Network Agent installation package, you must specify the proxy settings to ensure connection between the Network Agent instances on managed devices and your Kaspersky Security Center Cloud Console workspace:

    1. Click the installation package name.
    2. In the installation package properties window that opens, go to the Settings tab.
    3. Open the Connection section.
    4. Select the Use proxy server option and fill in the Proxy server address and Proxy server port fields.
  6. For some Kaspersky applications, during the download process the Show EULA button is displayed. If it is displayed, do the following:
    1. Click the Show EULA button to read the End User License Agreement (EULA).
    2. Read the EULA, which is displayed on the screen, and click the Accept button.

      The download continues after you accept the EULA. If you click Decline, the download is stopped.

  7. When the download is complete, click the Close button (The Close button.) to close the window with information about the distribution package.

The installation package is created. The installation package appears in the list of installation packages.

You cannot add an installation package with the same localization language several times. For example, if you already added the Kaspersky Endpoint Security for Windows (English) installation package, you can add Kaspersky Endpoint Security for Windows installation packages localized in other languages, except English.

See also:

About legal documents of Kaspersky Security Center Cloud Console

Revoking consent with an End User License Agreement

Scenario: Migration without a hierarchy of Administration Servers

Scenario: Kaspersky applications initial deployment

Page top

[Topic 6383]

Distributing installation packages to secondary Administration Servers

To distribute installation packages to secondary Administration Servers:

  1. Establish a connection with the Administration Server that controls the relevant secondary Administration Servers.
  2. Create a task of installation package distribution to secondary Administration Servers in one of the following ways:
    • If you want to create a task for secondary Administration Servers in the selected administration group, launch the creation of a group task for this group.
    • If you want to create a task for specific secondary Administration Servers, launch the creation of a task for specific devices.

    The New task wizard starts. Follow the instructions of the wizard.

    In the New task window of the New task wizard, in the Task type field select Distribute installation package. You can also edit the default name of the task in the Task name field.

    At the next step, specify the secondary Administration Servers for the task scope and follow the instructions of the New task wizard. When you finish, the New task wizard will create the task of distributing the selected installation packages to specific secondary Administration Servers.

    When you create the Distribute installation package task for secondary Administration Servers running on-premises, the distribution scope—aside from custom installation packages—will only include the installation packages of Kaspersky applications that are supported by Kaspersky Security Center Web Console running on-premises, regardless of which distribution option has been selected (All installation packages or Selected installation packages).

  3. Run the task manually or wait for it to launch according to the schedule you specified in the task settings.

The selected installation packages will be copied to the specific secondary Administration Servers.

See also:

Scenario: Kaspersky applications initial deployment

Page top

[Topic 182663]

Creating a stand-alone installation packages for Network Agent

You and device users in your organization can use stand-alone installation packages to install Network Agent on devices locally. Stand-alone installation packages can be created for devices running Windows, Linux, or macOS.

In Kaspersky Security Center Cloud Console, you can create stand-alone installation packages only for Network Agent.

A stand-alone installation package is an executable file that can be sent by email, or transferred to a client device by another method. The received file can be run locally on the client device to install Network Agent without involving Kaspersky Security Center Cloud Console.

For Network Agent for Linux and Network Agent for macOS, the stand-alone installation package is a script file with the .sh extension. When you run this file, the script unpacks the attached archive, which contains the installation package and its settings, and then starts the installation.

If you install Network Agent by using a stand-alone installation package on a device running Microsoft Windows XP Professional for Embedded Systems 32-bit, the installation fails. To resolve this issue, preliminarily install the update KB2868626 for Windows XP from the Microsoft website: https://www.catalog.update.microsoft.com/Search.aspx?q=KB2868626.

For authentication reasons, each stand-alone installation package is signed by using a certificate. The certificate is reissued from time to time. After each procedure of certificate reissue, Kaspersky Security Center Cloud Console automatically updates the signatures of all created stand-alone installation packages. For downloaded stand-alone installation packages, an automatic signature update cannot be performed. Therefore, the certificate expires and a certificate error might occur while you install an application from a stand-alone installation package. In this case, download the stand-alone installation package again.

To create a stand-alone installation package:

  1. Do one of the following:
    • In the main menu, go to Discovery & deployment Deployment & assignmentInstallation packages.
    • In the main menu, go to Operations RepositoriesInstallation packages.

    A list of installation packages is displayed. If the Network Agent installation package is not in the list, create this installation package manually.

  2. In the list of installation packages, click the name of the Network Agent installation package.

    The properties window of the Network Agent installation package is displayed.

  3. Configure settings of the Network Agent installation package, if necessary, and close the properties window of the Network Agent installation package.
  4. In the list of installation packages, select an installation package and, above the list, click the Deploy button.
  5. Select the Using a stand-alone package option.

    The Stand-alone installation package creation wizard starts. Proceed through the wizard by using the Next button.

  6. Make sure that the Install Network Agent together with this application option is enabled, if you want to install Network Agent together with the selected application.

    By default, this option is enabled. It is recommended to enable this option if you are not sure whether Network Agent is installed on the device. If Network Agent is already installed on the device, after the stand-alone installation package with Network Agent is installed Network Agent will be updated to the newer version.

    If you disable this option, Network Agent will not be installed on the device and the device will be unmanaged.

    If a stand-alone installation package for the selected application already exists on Administration Server, the wizard informs you about this fact. In this case, you must select one of the following actions:

    • Create stand-alone installation package. Select this option, for example, if you want to create a stand-alone installation package for a new application version and also want to retain a stand-alone installation package that you created for a previous application version. The new stand-alone installation package is placed in another folder.
    • Use existing stand-alone installation package. Select this option if you want to use an existing stand-alone installation package. The process of package creation will not be started.
    • Rebuild existing stand-alone installation package. Select this option if you want to create a stand-alone installation package for the same application again. The stand-alone installation package is placed in the same folder.
  7. On the Move to list of managed devices step, the Do not move devices option is selected by default. If you do not want to move the client device to any administration group after Network Agent installation, do not change choice of option.

    If you want to move client device after Network Agent installation, select the Move unassigned devices to this group option and specify an administration group to which you want to move the client device. By default, the device is moved to the Managed devices group.

  8. Select the Open the list of stand-alone packages option if you want the list of stand-alone installation packages to be displayed after the wizard is finished.
  9. Click the Finish button.

    The Stand-alone installation package creation wizard closes.

The Network Agent stand-alone installation package is created. The created stand-alone installation package is displayed in the list of stand-alone installation packages, which you can view.

See also:

Scenario: Kaspersky applications initial deployment

Page top

[Topic 187184]

Viewing the list of stand-alone installation packages

You can view the list of stand-alone installation packages and properties of each stand-alone installation package.

To view the list of stand-alone installation packages for all installation packages:

  1. Do one of the following:
    • In the main menu, go to Discovery & deployment Deployment & assignmentInstallation packages.
    • In the main menu, go to Operations RepositoriesInstallation packages.

    A list of installation packages is displayed.

  2. Above the list, click the View the list of stand-alone packages button.

A list of stand-alone installation packages is displayed.

In the list of stand-alone installation packages, their properties are displayed as follows:

  • Package name. Stand-alone installation package name that is automatically formed as the application name included in the package and the application version.
  • Network Agent installation package name.
  • Network Agent version.
  • Size. File size in megabytes (MB).
  • Group. Name of the group to which the client device is moved after Network Agent installation.
  • Created. Date and time of the stand-alone installation package creation.
  • Modified. Date and time of the stand-alone installation package modification.
  • File hash. The property is used to certify that the stand-alone installation package was not changed by third-party persons and a user has the same file that you created and transferred to the user.

To view the list of stand-alone installation packages for specific installation package:

Select the installation package in the list and, above the list, click the View the list of stand-alone packages button.

In the list of stand-alone installation packages, you can do the following:

  • Download a stand-alone installation package to your device by clicking the Download button.

    For authentication reasons, each stand-alone installation package is signed by using a certificate. The certificate is reissued from time to time. After each procedure of certificate reissue, Kaspersky Security Center Cloud Console automatically updates the signatures of all created stand-alone installation packages. For downloaded stand-alone installation packages, an automatic signature update cannot be performed. Therefore, the certificate expires and a certificate error might occur while you install an application from a stand-alone installation package. In this case, download the stand-alone installation package again.

  • Remove a stand-alone installation package by clicking the Remove button.

See also:

Scenario: Kaspersky applications initial deployment

Page top

[Topic 182501]

Creating custom installation packages

You can use custom installation packages for the following:

A custom installation package is a folder with a set of files, including an executable file. A source to create a custom installation package is an archive file. The archive file contains file or files that have to be included in the custom installation package. Creating a custom installation package, you can specify command-line options, for example, to install the application in a silent mode.

You cannot create custom installation packages in the trial mode of Kaspersky Security Center Cloud Console.

To create a custom installation package:

  1. Do one of the following:
    • In the main menu, go to Discovery & deployment Deployment & assignmentInstallation packages.
    • In the main menu, go to Operations RepositoriesInstallation packages.

    A list of installation packages available on the Administration Server is displayed.

  2. Click Add.

    The New package wizard starts. Proceed through the wizard by using the Next button.

  3. Select Create an installation package from a file.
  4. Specify the installation package name and click the Browse button.

    A standard Open window lets you choose an archive file to create the installation package.

  5. Select an archive file located on the available disks.

    You can upload a ZIP, CAB, TAR, or TAR.GZ archive file. It is not possible to create an installation package from an SFX (self-extracting archive) file.

    Files are downloaded to the Kaspersky Security Center Cloud Console Administration Server.

    If Administration Server detects that the archive includes Kaspersky application, an error message is displayed. You can download installation packages for Kaspersky applications from Kaspersky Web Servers. This operation is available by selecting OperationsKaspersky applicationsCurrent application versions.

  6. If the selected archive file includes several executable files, select one executable file that has to be run to install the application using the created installation package.
  7. If you want, specify an executable file command-line parameters.

    You can specify command-line parameters to install the application from the installation package in silent mode. Refer to the application vendor's documentation for details of the command-line parameters.

    Creation of the installation package starts.

    The wizard informs you when the process is finished.

    If the installation package is not created, an error message is displayed.

    In Kaspersky Security Center Cloud Console, the total size of all installation packages on the Administration Server is limited to 500 MB. If in the process of creating an installation package the total size limit is exceeded, delete the installation packages created earlier. The size of an installation package is displayed in its properties.

  8. Click the Finish button to close the wizard.

The created custom installation package is downloaded to the Administration Server. After downloading, the installation package appears in the list of installation packages.

In the list of installation packages, you can view the following properties of a custom installation package:

  • Name. Custom installation package name.
  • Package status. Installation package download status.
  • Source. Application vendor name.
  • Application. Application name packed into the custom installation package.
  • Version. Application version.
  • Language. Language of the application packed into the custom installation package.
  • Size (MB). Size of the custom installation package.
  • Operating system. Operating system for which the custom installation package is created.
  • Created. Installation package creation date.
  • Modified. Installation package modification date.
  • Type. Kaspersky application or third-party application.

In the list of installation packages, by clicking the link with the name of a custom installation package, you can change command-line parameters and the custom installation package name.

See also:

Scenario: Kaspersky applications initial deployment

Page top

[Topic 92569]

Requirements for a distribution point

To handle up to 10,000 client devices, a distribution point must meet, at a minimum, the following requirements (a configuration for a test stand is provided):

  • CPU:  Intel Core i7-7700 CPU, 3.60 GHz 4 cores.
  • RAM: 8 GB.
  • Free storage space: 120 GB.

In addition, a distribution point must have internet access and must always be connected.

If any remote installation tasks are pending on the Administration Server, the device with the distribution point will also require an amount of free disk space that is equal to the total size of the installation packages to be installed.

If one or multiple instances of the task for update (patch) installation and vulnerability fix are pending on the Administration Server, the device with the distribution point will also require additional free disk space, equal to twice the total size of all patches to be installed.

See also:

Scenario: Kaspersky applications initial deployment

Page top

[Topic 154925]

Network Agent installation package settings

Expand all | Collapse all

To configure a Network Agent installation package:

  1. Do one of the following:
    • In the main menu, go to Discovery & deployment Deployment & assignmentInstallation packages.
    • In the main menu, go to Operations RepositoriesInstallation packages.

    A list of installation packages available on the Administration Server is displayed.

  2. Click the link with the name of the Network Agent installation package.

The properties window of the Network Agent installation package opens. The information in the window is grouped on tabs and in sections.

General

The General section displays general information about the installation package:

  • Installation package name
  • Name and version of the application for which the installation package has been created
  • Installation package size
  • Installation package creation date
  • Path to the installation package folder

Settings

This section presents the settings required to ensure proper functioning of Network Agent immediately after it is installed. The settings in this section are available only on devices running Windows.

In the Destination folder group of settings, you can select the client device folder in which Network Agent will be installed.

  • Install in default folder

    If this option is selected, Network Agent will be installed in the <Drive>:\Program Files\Kaspersky Lab\NetworkAgent folder. If this folder does not exist, it will be created automatically.

    By default, this option is selected.

  • Install in specified folder

    If this option is selected, Network Agent will be installed in the folder specified in the entry field.

In the following group of settings, you can set a password for the Network Agent remote uninstallation task:

  • Use uninstallation password

    If this option is enabled, by clicking the Modify button you can enter the uninstall password (only available for Network Agent on devices running Windows operating systems).

    By default, this option is disabled.

  • Status
  • Protect Network Agent service against unauthorized removal or termination, and prevent changes to the settings

    When this option is enabled, after Network Agent is installed on a managed device, the component cannot be removed or reconfigured without required privileges. The Network Agent service cannot be stopped. This option has no effect on domain controllers.

    Enable this option to protect Network Agent on workstations operated with local administrator rights.

    By default, this option is disabled.

  • Automatically install applicable updates and patches for components that have the Undefined status

    If this check box is selected, all downloaded updates and patches for Network Agent will be installed automatically.

    If this check box is cleared, all downloaded updates and patches will only be installed after you change their status to Approved. Updates and patches with Undefined status will not be installed.

    By default, this check box is selected.

Connection

In this section, you can configure connection of Network Agent to the Administration Server:

  • Use UDP port

    UDP port number

    In this field you can specify the port to connect Administration Server to Network Agent using UDP protocol.

    The default UDP port is 15000.

  • Open Network Agent ports in Microsoft Windows Firewall

    If this option is enabled, the ports used by Network Agent are added to the Microsoft Windows Firewall exclusion list.

    By default, this option is enabled.

  • Do not use proxy server
  • Use proxy server

    Proxy server address

    Proxy server port

  • Proxy server authentication

    If this option is enabled, in the entry fields you can specify the credentials for proxy server authentication.

    We recommend that you specify the credentials of an account that has minimum privileges required only for the proxy server authentication.

    By default, this option is disabled.

    User name

    User name of the account under which connection to the proxy server is established.

    We recommend that you specify the credentials of an account that has minimum privileges required only for the proxy server authentication.

    Password

    Password of the account under which connection to the proxy server is established.

    We recommend that you specify the credentials of an account that has minimum privileges required only for the proxy server authentication.

For compatibility purposes, it is not recommended to specify proxy connection settings in the Network Agent installation package settings.

Advanced

In this section, you can configure how the connection gateway and virtual machine are used, as well as whether to register a user as a device owner:

  • Connect to Administration Server by using a connection gateway
  • Connection gateway address
  • Enable dynamic mode for VDI

    If this option is enabled, dynamic mode for Virtual Desktop Infrastructure (VDI) will be enabled for Network Agent installed on a virtual machine.

    By default, this option is disabled.

  • Optimize settings for VDI

    If this option is enabled, the following features are disabled in the Network Agent settings:

    • Retrieving information about software installed
    • Retrieving information about hardware
    • Retrieving information about vulnerabilities detected
    • Retrieving information about updates required

    By default, this option is disabled.

  • Allow running the user registration utility after Network Agent installation

    If this option is enabled, the user registration as a device owner utility will run after Network Agent installation. By default, this option is disabled.

Additional components

In this section you can select additional components for concurrent installation with Network Agent.

Tags

The Tags section displays a list of keywords (tags) that can be added to client devices after Network Agent installation. You can add and remove tags from the list, as well as rename them.

If the check box is selected next to a tag, this tag is automatically added to managed devices during Network Agent installation.

If the check box is cleared next to a tag, the tag will not automatically be added to managed devices during Network Agent installation. You can manually add this tag to devices.

When removing a tag from the list, it is automatically removed from all devices to which it was added.

Revision history

In this section, you can view the history of the installation package revisions. You can compare revisions, view revisions, save revisions to a file, and add and edit revision descriptions.

Network Agent installation package settings available to a specific operating system are given in the table below.

Network Agent installation package settings

Property section

Windows

Mac

Linux

General

Included.

Included.

Included.

Settings

Included.

Excluded.

Excluded.

Connection

Included.

Included.

* except the Open Network Agent ports in Microsoft Windows Firewall check box

Included.

* except the Open Network Agent ports in Microsoft Windows Firewall check box

Advanced

Included.

Included.

Included.

Additional components

Included.

Included.

Included.

Tags

Included.

Included.

* except the automatic tagging rules

Included.

* except the automatic tagging rules

Revision history

Included.

Included.

Included.

See also:

Ports used by Kaspersky Security Center Cloud Console

Scenario: Kaspersky applications initial deployment

Page top

[Topic 92479]

Virtual infrastructure

Kaspersky Security Center Cloud Console supports the use of virtual machines. To protect your virtual infrastructure, you need to install Network Agent on each virtual machine.

In this section

Tips on reducing the load on virtual machines

Support of dynamic virtual machines

Support of virtual machines copying

See also:

Initial configuration of Kaspersky Security Center Cloud Console

Page top

[Topic 92480]

Tips on reducing the load on virtual machines

When installing Network Agent on a virtual machine, you are advised to consider disabling some Kaspersky Security Center Cloud Console features that seem to be of little use for virtual machines.

When installing Network Agent on a virtual machine or on a template intended for generation of virtual machines, we recommend the following actions:

  • If you are running a remote installation, in the properties window of the Network Agent installation package, in the Advanced section, select the Optimize settings for VDI option.
  • If you are running an interactive installation through a wizard, in the wizard window, select the Optimize the Network Agent settings for the virtual infrastructure option.

Selecting those options alters the settings of Network Agent so that the following features remain disabled by default (before a policy is applied):

  • Retrieving information about software installed
  • Retrieving information about hardware
  • Retrieving information about vulnerabilities detected
  • Retrieving information about updates required

Usually, those features are not necessary on virtual machines because they use uniform software and virtual hardware.

Disabling the features is invertible. If any of the disabled features is required, you can enable it through the policy of Network Agent, or through the local settings of Network Agent. The local settings of Network Agent are available through the context menu of the relevant device in Administration Console.

See also:

Initial configuration of Kaspersky Security Center Cloud Console

Page top

[Topic 92481]

Support of dynamic virtual machines

Kaspersky Security Center Cloud Console supports dynamic virtual machines. If a virtual infrastructure has been deployed on the organization's network, dynamic (temporary) virtual machines can be used in certain cases. The dynamic VMs are created under unique names based on a template that has been prepared by the administrator. The user works on a VM for a while and then, after being turned off, this virtual machine will be removed from the virtual infrastructure. The virtual machine with installed Network Agent is also added to the Administration Server database. After you turn off this virtual machine, the corresponding entry must also be removed from the database of Administration Server.

To make functional the feature of automatic removal of entries on virtual machines, when installing Network Agent on a template for dynamic virtual machines, select the Enable dynamic mode for VDI option:

Avoid selecting the Enable dynamic mode for VDI option when installing Network Agent on physical devices.

If you want events from dynamic virtual machines to be stored on the Administration Server for a while after you remove those virtual machines, then, in the Administration Server properties window, in the Events repository section, select the Store events after devices are deleted option and specify the maximum storage term for events (in days).

See also:

Initial configuration of Kaspersky Security Center Cloud Console

Page top

[Topic 92482]

Support of virtual machines copying

Kaspersky Security Center Cloud Console supports copying a virtual machine with installed Network Agent or creating one from a template with installed Network Agent.

Network Agent can automatically detect copying of virtual machines in the following cases:

  • The Enable dynamic mode for VDI option was selected when Network Agent was installed—After each restart of the operating system, this virtual machine will be recognized as a new device, regardless of whether it has been copied or not.
  • One of the following hypervisors is in use: VMware, HyperV, or Xen: Network Agent detects the copying of the virtual machine by the changed IDs of the virtual hardware.

Analysis of changes in virtual hardware is not absolutely reliable. Before applying this method widely, you must test it on a small pool of virtual machines for the version of the hypervisor currently used in your organization.

See also:

Initial configuration of Kaspersky Security Center Cloud Console

Page top

[Topic 172012]

Usage of Network Agent for Windows, Linux, and macOS: Comparison

Network Agent for macOS and Linux has several functional limitations compared to Network Agent for Windows. The Network Agent policy and installation package settings also differ depending on the operating system. The table below compares Network Agent features and usage scenarios available for Windows, macOS, and Linux operating systems.

Network Agent feature comparison

Network Agent feature

Windows

Linux

macOS

Installation

 

Automatic installation of updates and patches for Network Agent

Yes

No.

No.

Automatic distributing of a key

Yes

Yes

Yes

Installing manually, by running application installers on devices

Yes

Yes

Yes

Forced synchronization

Yes

Yes

Yes

Distribution point

 

Network polling

Yes

  • IP range polling
  • Windows network polling
  • Domain controller polling (Microsoft Active Directory)

Yes

  • IP range polling
  • Domain controller polling (Microsoft Active Directory, Samba as an Active Directory)

No.

Running KSN proxy service on a distribution point side

Yes

Yes

No.

Downloading updates via Kaspersky update servers to the distribution points repositories that distribute updates to managed devices

Yes

Yes

No.

Distribution point devices running macOS cannot download updates from Kaspersky update servers.

If one or more devices running macOS are within the scope of the Download updates to the repositories of distribution points task, the task completes with the Failed status, even if it has successfully completed on all Windows devices.

Push installation of applications

 

Yes

Restricted: it is not possible to perform push installation on Windows devices by using Linux distribution points.

 

Restricted: it is not possible to perform push installation on Windows devices by using macOS distribution points.

 

Handling third-party applications

 

Remote installation of applications on devices

 

Yes

No.

No.

Software updates

Yes

No.

No.

Configuring operating system updates in a Network Agent policy

Yes

No.

No.

Viewing information about software vulnerabilities

Yes

No.

No.

Scanning applications for vulnerabilities

Yes

No.

No.

Inventory of software installed on devices

Yes

Yes

No.

Virtual machines

 

Installing Network Agent on a virtual machine

Included.

Included.

Included.

Optimization settings for virtual desktop infrastructure (VDI)

Included.

Included.

Included.

Support of dynamic virtual machines

Included.

Included.

Included.

Other

 

Auditing actions on a remote client device by using Windows Desktop Sharing

Yes

No.

No.

Managing device restarts

Yes

No.

No.

Connection Manager

Yes

Yes

Yes

Remotely connecting to the desktop of a client device

Yes

No.

No.

The following sections are displayed in the distribution point properties, but the corresponding features are not supported by Network Agent for macOS:

  • Source of updates
  • KSN proxy server
  • Windows domains
  • Active Directory
  • IP ranges
  • Advanced
  • Statistics

See also:

Scenario: Kaspersky applications initial deployment

Page top

[Topic 212573]

Specifying settings for remote installation on Unix devices

Expand all | Collapse all

When you install an application on a Unix device by using a remote installation task, you can specify Unix-specific settings for the task. These settings are available in the task properties after the task is created.

To specify Unix-specific settings for a remote installation task:

  1. In the main menu, go to Assets (Devices) Tasks.
  2. Click the name of the remote installation task for which you want to specify the Unix-specific settings.

    The task properties window opens.

  3. Go to Application settingsUnix-specific settings.
  4. Specify the following settings:
    • Set a password for the root account (only for deployment through SSH)

      If the sudo command cannot be used on the target device without specifying the password, select this option, and then specify the password for the root account. Kaspersky Security Center Cloud Console transmits the password in an encrypted form to the target device, decrypts the password, and then starts the installation procedure on behalf of the root account with the specified password.

      Kaspersky Security Center Cloud Console does not use the account or the specified password to create an SSH connection.

    • Specify the path to a temporary folder with Execute permissions on the target device (only for deployment through SSH)

      If the /tmp directory on the target device does not have the execute permission, select this option, and then specify the path to the directory with the execute permission. Kaspersky Security Center Cloud Console uses the specified directory as a temporary directory to access via SSH. The application places the installation package in the directory and runs the installation procedure.

  5. Click the Save button.

The specified task settings are saved.

See also:

General task settings and properties

Scenario: Kaspersky applications initial deployment

Scenario: Monitoring and reporting

Page top

[Topic 180093]

Replacing third-party security applications

Installation of Kaspersky security applications through Kaspersky Security Center Cloud Console may require removal of third-party software incompatible with the application being installed. Kaspersky Security Center Cloud Console provides several ways of removing the third-party applications.

Removing incompatible applications when configuring remote installation of an application

You can enable the Uninstall incompatible applications automatically option when you configure remote installation of a security application. You can find this option in the Protection deployment wizard. When this option is enabled, Kaspersky Security Center Cloud Console removes incompatible applications before installing a security application on a managed device.

Removing incompatible applications through a dedicated task

To remove incompatible applications through a task, use the Uninstall application remotely task. This task should be run on devices before the security application installation task. For example, in the installation task you can select On completing another task as the schedule type where the other task is Uninstall application remotely.

This method of uninstallation is useful when the security application installer cannot properly remove an incompatible application.

See also:

Scenario: Kaspersky applications initial deployment

Page top

[Topic 92464]

Options for manual installation of applications

You can install Network Agent on devices locally without involving Kaspersky Security Center Cloud Console. To do this, create a stand-alone installation package for Network Agent as described in the following topic: Creating stand-alone installation packages. Transfer the package to your client device and install it. Once the installation of the Network Agent is completed, you can use the device as a distribution point.

Page top

[Topic 92462]

Forced deployment through the remote installation task of Kaspersky Security Center Cloud Console

If you need to start deploying Network Agents or other applications immediately, without waiting for the next time target devices log in to the domain, or if any target devices that are not members of the Active Directory domain are available, you can force installation of selected installation packages through the remote installation task of Kaspersky Security Center Cloud Console.

In this case, you can specify target devices either explicitly (with a list), or by selecting the Kaspersky Security Center Cloud Console administration group to which they belong, or by creating a selection of devices based on a criterion. The installation start time is defined by the task schedule. If the Run missed tasks setting is enabled in the task properties, the task can be run either immediately after target devices are turned on, or when they are moved to the target administration group.

This type of installation is performed in two steps:

  1. Copying files to the administrative resource (admin$) on each device.
  2. Performing remote registration of supporting services on each device.

The following conditions must be met:

  • Devices must be available from the distribution points.
  • Name resolution for target devices must function properly in the network.
  • The administrative shares (admin$) must be enabled on target devices.
  • The Server system service must be running on target devices (the service runs by default).
  • The following ports must be open on target devices to allow remote access through Windows tools: TCP 139, TCP 445, UDP 137, and UDP 138.
  • Simple File Sharing mode must be disabled on target devices.
  • On target devices, the access sharing and security model must be set as Classic – local users authenticate as themselves, it cannot be Guest only – local users authenticate as Guest.
  • Target devices must be members of the domain, or uniform accounts with administrator rights must be created on target devices in advance.

Devices in workgroups can be adjusted in accordance with the above requirements by using the riprep utility, which is described on Kaspersky Technical Support website.

During installation on new devices that have not yet been allocated to any of the Kaspersky Security Center Cloud Console administration groups, you can open the remote installation task properties and specify the administration group to which devices will be moved after Network Agent installation.

When creating a group task, keep in mind that each group task affects all devices in all nested groups within a selected group. Therefore, you must avoid duplicating installation tasks in subgroups.

Automatic installation is a simplified way to create tasks for forced installation of applications. To do this, open the administration group properties, open the list of installation packages and select the ones that must be installed on devices in this group. As a result, the selected installation packages will be automatically installed on all devices in this group and all of its subgroups. The time interval over which the packages will be installed depends on the network throughput and the total number of networked devices.

Using the remote installation task of Kaspersky Security Center Cloud Console places a significant load on devices acting as distribution points. Therefore, it is recommended that you select devices with high-performance storage units as distribution points. Moreover, the free disk space in the partition with the %ALLUSERSPROFILE%\Application Data\KasperskyLab\adminkit folder must exceed, by many times, the total size of the distribution packages of installed applications.

Page top

[Topic 178756]

Protection deployment wizard

To install Kaspersky applications, you can use the Protection deployment wizard. The Protection deployment wizard enables remote installation of applications either through specially created installation packages or directly from a distribution package.

The Protection deployment wizard performs the following actions:

  • Downloads an installation package for application installation (if it was not created earlier). The installation package is located at Discovery & deploymentDeployment & assignmentInstallation packages. You can use this installation package for the application installation in the future.
  • Creates and runs a remote installation task for specific devices or for an administration group. The newly created remote installation task is stored in the Tasks section. You can later start this task manually. The task type is Install application remotely.

In this section

Starting Protection deployment wizard

Step 1. Selecting the installation package

Step 2. Selecting Network Agent version

Step 3. Selecting devices

Step 4. Specifying the remote installation task settings

Step 5. Restart management

Step 6. Removing incompatible applications before installation

Step 7. Moving devices to Managed devices

Step 8. Selecting accounts to access devices

Step 9. Starting installation

See also:

Scenario: Kaspersky applications initial deployment

Page top

[Topic 178757]

Starting Protection deployment wizard

To start the Protection deployment wizard manually,

In the main menu, go to Discovery & deploymentDeployment & assignmentProtection deployment wizard.

The Protection deployment wizard starts. Proceed through the wizard by using the Next button.

See also:

Protection deployment wizard

Scenario: Kaspersky applications initial deployment

Page top

[Topic 178655]

Step 1. Selecting the installation package

Select the way you want to install the selected installation package:

  • Remote installation by Kaspersky Security Center
  • Remote installation by Microsoft Azure API

After that, select the installation package of the application that you want to install.

If the installation package of the required application is not listed, click the Add button and then select the application from the list.

See also:

Protection deployment wizard

Scenario: Kaspersky applications initial deployment

Page top

[Topic 178658]

Step 2. Selecting Network Agent version

If you selected the installation package of an application other than Network Agent, you also have to install Network Agent, which connects the application with Kaspersky Security Center Administration Server.

Select the latest version of Network Agent.

See also:

Protection deployment wizard

Scenario: Kaspersky applications initial deployment

Page top

[Topic 178657]

Step 3. Selecting devices

Expand all | Collapse all

Specify a list of devices on which the application will be installed:

  • Install on managed devices

    If this option is selected, the remote installation task is created for a group of devices.

  • Select devices for installation

    The task is assigned to devices included in a device selection. You can specify one of the existing selections.

    For example, you may want to use this option to run a task on devices with a specific operating system version.

See also:

Protection deployment wizard

Scenario: Kaspersky applications initial deployment

Page top

[Topic 178659]

Step 4. Specifying the remote installation task settings

Expand all | Collapse all

On the "Remote installation" task settings page, specify the settings for remote installation of the application.

In the Force installation package download settings group, specify how files that are required for the application installation are distributed to client devices:

  • Using Network Agent

    If this option is enabled, installation packages are delivered to client devices by Network Agent installed on those client devices.

    If this option is disabled, installation packages are delivered using the operating system tools of client devices.

    We recommend that you enable this option if the task has been assigned to devices with Network Agents installed.

    By default, this option is enabled.

  • Using operating system resources through distribution points

    If this option is enabled, installation packages are transmitted to client devices using operating system tools through distribution points. You can select this option if there is at least one distribution point on the network.

    If the Using Network Agent option is enabled, the files are delivered using operating system tools only if Network Agent tools are unavailable.

    By default, this option is enabled for remote installation tasks that have been created on a virtual Administration Server.

Define the additional setting:

Do not re-install application if it is already installed

If this option is enabled, the selected application will not be re-installed if it has already been installed on this client device.

If this option is disabled, the application will be installed anyway.

By default, this option is enabled.

Password to uninstall the current Kaspersky application

The Password to uninstall the current Kaspersky application field is only available if you have selected the Using Network Agent option in the Force installation package download settings group.

Enter the password in the Password to uninstall the current Kaspersky application field if you migrate from one Kaspersky application to another and your current application is password-protected. Note that during the migration, your current Kaspersky application will be uninstalled.

To complete the migration scenario successfully, make sure that the following prerequisites are met:

  • You are using the Kaspersky Security Center Network Agent 14.2 for Windows or later.
  • You are installing the application on the devices running Windows.

See also:

Protection deployment wizard

Scenario: Kaspersky applications initial deployment

Page top

[Topic 178660]

Step 5. Restart management

Expand all | Collapse all

Specify the action to be performed if the operating system must be restarted when you install the application:

  • Do not restart the device

    Client devices are not restarted automatically after the operation. To complete the operation, you must restart a device (for example, manually or through a device management task). Information about the required restart is saved in the task results and in the device status. This option is suitable for tasks on servers and other devices where continuous operation is critical.

  • Restart the device

    Client devices are always restarted automatically if a restart is required for completion of the operation. This option is useful for tasks on devices that provide for regular pauses in their operation (shutdown or restart).

  • Prompt user for action

    The restart reminder is displayed on the screen of the client device, prompting the user to restart it manually. Some advanced settings can be defined for this option: text of the message for the user, the message display frequency, and the time interval after which a restart will be forced (without the user's confirmation). This option is most suitable for workstations where users must be able to select the most convenient time for a restart.

    By default, this option is selected.

    • Repeat prompt every (min)

      If this option is enabled, the application prompts the user to restart the operating system with the specified frequency.

      By default, this option is enabled. The default interval is 5 minutes. Available values are between 1 and 1440 minutes.

      If this option is disabled, the prompt is displayed only once.

    • Restart after (min)

      After prompting the user, the application forces restart of the operating system upon expiration of the specified time interval.

      By default, this option is enabled. The default delay is 30 minutes. Available values are between 1 and 1440 minutes.

  • Force closure of applications in blocked sessions

    Running applications may prevent a restart of the client device. For example, if a document is being edited in a word processing application and is not saved, the application does not allow the device to restart.

    If this option is enabled, such applications on a locked device are forced to close before the device restart. As a result, users may lose their unsaved changes.

    If this option is disabled, a locked device is not restarted. The task status on this device states that a device restart is required. Users have to manually close all applications running on locked devices and restart these devices.

    By default, this option is disabled.

See also:

Protection deployment wizard

Scenario: Kaspersky applications initial deployment

Page top

[Topic 178752]

Step 6. Removing incompatible applications before installation

This step is only present if the application that you deploy is known to be incompatible with some other applications.

Select the option if you want Kaspersky Security Center Cloud Console to automatically remove applications that are incompatible with the application you deploy.

The list of incompatible applications is also displayed.

If you do not select this option, the application will only be installed on devices that have no incompatible applications.

See also:

Protection deployment wizard

Scenario: Kaspersky applications initial deployment

Page top

[Topic 178661]

Step 7. Moving devices to Managed devices

Expand all | Collapse all

Specify whether devices must be moved to an administration group after Network Agent installation.

  • Do not move devices

    The devices remain in the groups in which they are currently located. The devices that have not been placed in any group remain unassigned.

  • Move unassigned devices to group

    The devices are moved to the administration group that you select.

The Do not move devices option is selected by default. For security reasons, you might want to move the devices manually.

See also:

Protection deployment wizard

Scenario: Kaspersky applications initial deployment

Page top

[Topic 178753]

Step 8. Selecting accounts to access devices

Expand all | Collapse all

If necessary, add the accounts that will be used to start the remote installation task:

  • No account required (Network Agent installed)

    If this option is selected, you do not have to specify the account under which the application installer will be run. The task will run under the account under which the Administration Server service is running.

    If Network Agent has not been installed on client devices, this option is unavailable.

  • Account required (Network Agent is not used)

    Select this option if Network Agent is not installed on the devices for which you assign the remote installation task. In this case, you can specify a user account or an SSH certificate to install the application.

    • Local Account. If this option is selected, specify the user account under which the application installer will be run. Click the Add button, select Local Account, and then specify the user account credentials.

      You can specify multiple user accounts if, for example, none of them have all the required rights on all devices for which you assign the task. In this case, all added accounts are used for running the task, in consecutive order, top-down.

    • SSH certificate. If you want to install an application on a Linux-based client device, you can specify an SSH certificate instead of a user account. Click the Add button, select SSH certificate, and then specify the private and public keys of the certificate.

      To generate a private key, you can use the ssh-keygen utility. Note that Kaspersky Security Center Cloud Console supports the PEM format of private keys, but the ssh-keygen utility generates SSH keys in the OPENSSH format by default. The OPENSSH format is not supported by Kaspersky Security Center Cloud Console. To create a private key in the supported PEM format, add the -m PEM option in the ssh-keygen command. For example:

      ssh-keygen -m PEM -t rsa -b 4096 -C "<user email>"

See also:

Protection deployment wizard

Scenario: Kaspersky applications initial deployment

Page top

[Topic 178755]

Step 9. Starting installation

This page is the final step of the wizard. At this step, the Remote installation task has been successfully created and configured.

By default, the Run the task after the wizard finishes option is not selected. If you select this option, the Remote installation task will start immediately after you complete the wizard. If you do not select this option, the Remote installation task will not start. You can later start this task manually.

Click OK to complete the final step of the Protection deployment wizard.

See also:

Protection deployment wizard

Scenario: Kaspersky applications initial deployment

Page top

[Topic 255242]

Network settings for interaction with external services

Kaspersky Security Center Cloud Console uses the following network settings for interacting with external services.

Network settings

Network settings

Address

Description

Port: 443

Protocol: HTTPS

activation-v2.kaspersky.com/activationservice/activationservice.svc

Application activation.

Port: 443

Protocol: HTTPS

https://s00.upd.kaspersky.com

https://s01.upd.kaspersky.com

https://s02.upd.kaspersky.com

https://s03.upd.kaspersky.com

https://s04.upd.kaspersky.com

https://s05.upd.kaspersky.com

https://s06.upd.kaspersky.com

https://s07.upd.kaspersky.com

https://s08.upd.kaspersky.com

https://s09.upd.kaspersky.com

https://s10.upd.kaspersky.com

https://s11.upd.kaspersky.com

https://s12.upd.kaspersky.com

https://s13.upd.kaspersky.com

https://s14.upd.kaspersky.com

https://s15.upd.kaspersky.com

https://s16.upd.kaspersky.com

https://s17.upd.kaspersky.com

https://s18.upd.kaspersky.com

https://s19.upd.kaspersky.com

https://cm.k.kaspersky-labs.com

Updating Kaspersky databases, software modules, and applications.

Port: 443

Protocol: HTTPS

https://downloads.upd.kaspersky.com

Port: 80

Protocol: HTTP

http://p00.upd.kaspersky.com

http://p01.upd.kaspersky.com

http://p02.upd.kaspersky.com

http://p03.upd.kaspersky.com

http://p04.upd.kaspersky.com

http://p05.upd.kaspersky.com

http://p06.upd.kaspersky.com

http://p07.upd.kaspersky.com

http://p08.upd.kaspersky.com

http://p09.upd.kaspersky.com

http://p10.upd.kaspersky.com

http://p11.upd.kaspersky.com

http://p12.upd.kaspersky.com

http://p13.upd.kaspersky.com

http://p14.upd.kaspersky.com

http://p15.upd.kaspersky.com

http://p16.upd.kaspersky.com

http://p17.upd.kaspersky.com

http://p18.upd.kaspersky.com

http://p19.upd.kaspersky.com

http://downloads0.kaspersky-labs.com

http://downloads1.kaspersky-labs.com

http://downloads2.kaspersky-labs.com

http://downloads3.kaspersky-labs.com

http://downloads4.kaspersky-labs.com

http://downloads5.kaspersky-labs.com

http://downloads6.kaspersky-labs.com

http://downloads7.kaspersky-labs.com

http://downloads8.kaspersky-labs.com

http://downloads9.kaspersky-labs.com

http://downloads.kaspersky-labs.com

http://cm.k.kaspersky-labs.com

Updating Kaspersky databases, software modules, and applications.

Port: 443

Protocol: HTTPS

ds.kaspersky.com

Using Kaspersky Security Network.

Port: 443, 1443

Protocol: HTTPS

ksn-a-stat-geo.kaspersky-labs.com

ksn-file-geo.kaspersky-labs.com

ksn-verdict-geo.kaspersky-labs.com

ksn-url-geo.kaspersky-labs.com

ksn-a-p2p-geo.kaspersky-labs.com

ksn-info-geo.kaspersky-labs.com

ksn-cinfo-geo.kaspersky-labs.com

Using Kaspersky Security Network.

Protocol: HTTPS

click.kaspersky.com

redirect.kaspersky.com

Following links from the interface.

Port: 80

Protocol: HTTP

http://crl.kaspersky.com

http://ocsp.kaspersky.com

Public Key Infrastructure (PKI).

Port: 443

Protocol: HTTPS

https://ipm-klca.kaspersky.com

Marketing announcements.

Page top

[Topic 251798]

Preparing a device running Astra Linux in the closed software environment mode for installation of Network Agent

Prior to the installation of Network Agent on a device running Astra Linux in the closed software environment mode, you must perform two preparation procedures—the one in the instructions below and general preparation steps for any Linux device.

Before you begin:

  • Make sure that the device on which you want to install Network Agent for Linux is running one of the supported Linux distributions.
  • Download the necessary Network Agent installation file from the Kaspersky website.

Run the commands provided in this instruction under an account with root privileges.

To prepare a device running Astra Linux in the closed software environment mode for installation of Network Agent:

  1. Open the /etc/digsig/digsig_initramfs.conf file, and then specify the following setting:

    DIGSIG_ELF_MODE=1

  2. In the command line, run the following command to install the compatibility package:

    apt install astra-digsig-oldkeys

  3. Create a directory for the application key:

    mkdir -p /etc/digsig/keys/legacy/kaspersky/

  4. Place the application key /opt/kaspersky/ksc64/share/kaspersky_astra_pub_key.gpg in the directory created in the previous step:

    cp kaspersky_astra_pub_key.gpg /etc/digsig/keys/legacy/kaspersky/

    If the Kaspersky Security Center Cloud Console distribution kit does not include the kaspersky_astra_pub_key.gpg application key, you can download it by clicking the link: https://media.kaspersky.com/utilities/CorporateUtilities/kaspersky_astra_pub_key.gpg.

  5. Update the RAM disks:

    update-initramfs -u -k all

    Reboot the system.

  6. Perform the preparation steps common for any Linux device.

The device is prepared. You can now proceed to the installation of Network Agent.

Page top

[Topic 137593]

Preparing a Linux device and installing Network Agent on a Linux device remotely

Network Agent installation comprises two steps:

  • A Linux device preparation
  • Network Agent remote installation

A Linux device preparation

To prepare a device running Linux for remote installation of Network Agent:

  1. Make sure that the following software is installed on the target Linux device:
    • Sudo (for Ubuntu 10.04, Sudo version is 1.7.2p1 or later)
    • Perl language interpreter version 5.10 or later
  2. Test the device configuration:
    1. Check whether you can connect to the device through an SSH client (such as PuTTY).

      If you cannot connect to the device, open the /etc/ssh/sshd_config file and make sure that the following settings have the respective values listed below:

      PasswordAuthentication no

      ChallengeResponseAuthentication yes

      Do not modify the /etc/ssh/sshd_config file if you can connect to the device with no issues; otherwise, you may encounter SSH authentication failure when running a remote installation task.

      Save the file (if necessary) and restart the SSH service by using the sudo service ssh restart command.

    2. Disable the sudo password for the user account under which the device is to be connected.
    3. Use the visudo command in sudo to open the sudoers configuration file.

      In the file you have opened, add the following line to the end of the file: <username> ALL = (ALL) NOPASSWD: ALL. In this case, <username> is the user account which is to be used for the device connection using SSH. If you are using the Astra Linux operating system, in the /etc/sudoers file, add the last line with the following text: %astra-admin ALL=(ALL:ALL) NOPASSWD: ALL

    4. Save the sudoers file and then close it.
    5. Connect to the device again through SSH and make sure that the Sudo service does not prompt you to enter a password; you can do this using the sudo whoami command.
  3. Open the /etc/systemd/logind.conf file, and then do one of the following:
    • Specify 'no' as a value for the KillUserProcesses setting: KillUserProcesses=no.
    • For the KillExcludeUsers setting, type the user name of the account under which the remote installation is to be performed, for example, KillExcludeUsers=root.

    If the target device is running Astra Linux, add export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin string in the /home/<username>/.bashrc file, where <username> is the user account which is to be used for the device connection using SSH.

    To apply the changed setting, restart the Linux device or execute the following command:

    $ sudo systemctl restart systemd-logind.service

  4. If you want to install Network Agent on devices with the SUSE Linux Enterprise Server 15 operating system, install the insserv-compat package first to configure Network Agent.
  5. If you want to install Network Agent on devices with the Astra Linux operating system running in the closed software environment mode, perform additional steps to prepare Astra Linux devices.

Network Agent remote installation

To install Network Agent on Linux devices remotely:

  1. Download and create an installation package:
    1. Before installing the package on the device, make sure that it already has all the dependencies (programs and libraries) installed for this package.

      You can view the dependencies for each package on your own, using utilities that are specific for the Linux distribution on which the package is to be installed. For more details about utilities, refer to your operating system documentation.

    2. Download the Network Agent installation package by using the application interface or from the Kaspersky website.
    3. To create a remote installation package, use the following files:
      • klnagent.kpd
      • akinstall.sh
      • .deb or .rpm package of Network Agent
  2. Create a remote installation task with the following settings:
    • On the Settings page of the New task wizard, select the Using operating system resources through Administration Server check box. Clear all other check boxes.
    • On the Selecting an account to run the task page specify the settings of the user account that is used for device connection through SSH.
  3. Run the remote installation task. Use the option for the su command to preserve the environment: -m, -p, --preserve-environment.

Page top

[Topic 6385]

Installing applications by using a remote installation task

Kaspersky Security Center Cloud Console allows you to install applications on devices remotely, by using remote installation tasks. These tasks are created and assigned to devices through a dedicated wizard. To assign a task more quickly and easily, you can specify devices (up to 1000 devices) in the wizard window in one of the following ways:

  • Select networked devices detected by Administration Server. In this case, the task is assigned to specific devices. The specific devices can include devices in administration groups, as well as unassigned devices.
  • Specify device addresses manually or import addresses from a list. In this case, you can specify DNS names, IP addresses, and IP subnets of devices to which you want to assign the task.
  • Assign task to a device selection. In this case, the task is assigned to devices included in a selection created earlier. You can specify the default selection or a custom one that you created.
  • Assign task to an administration group. In this case, the task is assigned to devices included in an administration group created earlier.

For correct remote installation on a device with no Network Agent installed, the following ports must be opened: a) TCP 139 and 445; b) UDP 137 and 138. By default, these ports are opened on all devices included in the domain. They are opened automatically by the remote installation preparation utility.

In this section

Installing an application remotely

Installing applications on secondary Administration Servers

Page top

[Topic 236055]

Installing an application remotely

Expand all | Collapse all

This article contains information on how to install an application remotely on devices in an administration group, devices with specific addresses, or a selection of devices.

To install an application on specific devices:

  1. In the main menu, go to Assets (Devices)Tasks.
  2. Click Add.

    The New task wizard starts.

  3. In the Task type field, select Install application remotely.
  4. Select one of the following options:
    • Assign task to an administration group

      The task is assigned to devices included in an administration group. You can specify one of the existing groups or create a new one.

      For example, you may want to use this option to run a task of sending a message to users if the message is specific for devices included in a specific administration group.

      If a task is assigned to an administration group, the Security tab is not displayed in the task properties window because group tasks are subject to the security settings of the groups to which they apply.

    • Specify device addresses manually or import addresses from a list

      You can specify NetBIOS names, DNS names, IP addresses, and IP subnets of devices to which you want to assign the task.

      You may want to use this option to execute a task for a specific subnet. For example, you may want to install a certain application on devices of accountants or to scan devices in a subnet that is probably infected.

    • Assign task to a device selection

      The task is assigned to devices included in a device selection. You can specify one of the existing selections.

      For example, you may want to use this option to run a task on devices with a specific operating system version.

    The Install application remotely task is created for the specified devices. If you selected the Assign task to an administration group option, the task is a group one.

  5. At the Task scope step, specify an administration group, devices with specific addresses, or a device selection.

    The available settings depend on the option selected at the previous step.

  6. At the Installation packages step, specify the following settings:
    • Select how you want to install the selected application:
    • In the Select installation package field, select the installation package of an application that you want to install.
    • In the Force installation package download settings group, specify how files that are required for the application installation are distributed to client devices:
      • Using Network Agent

        If this option is enabled, installation packages are delivered to client devices by Network Agent installed on those client devices.

        If this option is disabled, installation packages are delivered using the operating system tools of client devices.

        We recommend that you enable this option if the task has been assigned to devices with Network Agents installed.

        By default, this option is enabled.

      • Using operating system resources through distribution points

        If this option is enabled, installation packages are transmitted to client devices using operating system tools through distribution points. You can select this option if there is at least one distribution point on the network.

        If the Using Network Agent option is enabled, the files are delivered using operating system tools only if Network Agent tools are unavailable.

        By default, this option is enabled for remote installation tasks that have been created on a virtual Administration Server.

    • In the Maximum number of concurrent downloads field, specify the maximum allowed number of client devices to which Administration Server can simultaneously transmit the files.
    • In the Maximum number of installation attempts field, specify the maximum allowed number of installer runs.

      If the number of attempts specified in the parameter is exceeded, Kaspersky Security Center Cloud Console does not start the installer on the device anymore. To restart the Install application remotely task, increase the value of the Maximum number of installation attempts parameter, and then restart the task. Alternatively, you can create a new Install application remotely task.

    • If you migrate from one Kaspersky application to another and your current application is password-protected, enter the password in the Password to uninstall the current Kaspersky application field. Note that during the migration, your current Kaspersky application will be uninstalled.

      The Password to uninstall the current Kaspersky application field is only available if you have selected the Using Network Agent option in the Force installation package download settings group.

      You can use the uninstall password only for the Kaspersky Security for Windows Server to Kaspersky Endpoint Security for Windows migration scenario when installing Kaspersky Endpoint Security for Windows by using the Install application remotely task. Using the uninstall password when installing other applications may cause installation errors.

      To complete the migration scenario successfully, make sure that the following prerequisites are met:

      • You are using Kaspersky Security Center Network Agent 14.2 for Windows or later.
      • You are installing the application on devices running Windows.
    • Define the additional options:
      • Do not re-install application if it is already installed

        If this option is enabled, the selected application will not be re-installed if it has already been installed on this client device.

        If this option is disabled, the application will be installed anyway.

        By default, this option is enabled.

      • Verify operating system type before downloading

        Before transmitting the files to client devices, Kaspersky Security Center Cloud Console checks if the Installation utility settings are applicable to the operating system of the client device. If the settings are not applicable, Kaspersky Security Center Cloud Console does not transmit the files and does not attempt to install the application. For example, to install some application to devices of an administration group that includes devices running various operating systems, you can assign the installation task to the administration group, and then enable this option to skip devices that run an operating system other than the required one.

      • Prompt users to close running applications

        Running applications may prevent a restart of the client device. For example, if a document is being edited in a word processing application and is not saved, the application does not allow the device to restart.

        If this option is enabled, such applications on a locked device are forced to close before the device restart. As a result, users may lose their unsaved changes.

        If this option is disabled, a locked device is not restarted. The task status on this device states that a device restart is required. Users have to manually close all applications running on locked devices and restart these devices.

        By default, this option is disabled.

    • Select on which devices you want to install the application:
      • Install on all devices

        The application will be installed even on devices managed by other Administration Servers.

        This option is selected by default. You do not have to change this setting if you have only one Administration Server in your network.

      • Install only on devices managed through this Administration Server

        The application will be installed only on devices managed by this Administration Server. Select this option if you have more than one Administration Server in your network and want to avoid conflicts between them.

    • Specify whether devices must be moved to an administration group after installation:

      The Do not move devices option is selected by default. For security reasons, you might want to move the devices manually.

  7. At this step of the wizard, specify whether the devices must be restarted during installation of applications:
    • Do not restart the device

      If this option is selected, the device will not be restarted after the security application installation.

    • Restart the device

      If this option is selected, the device will be restarted after the security application installation.

    • Prompt user for action

      The restart reminder is displayed on the screen of the client device, prompting the user to restart it manually. Some advanced settings can be defined for this option: text of the message for the user, the message display frequency, and the time interval after which a restart will be forced (without the user's confirmation). This option is most suitable for workstations where users must be able to select the most convenient time for a restart.

      By default, this option is selected.

      • Repeat prompt every (min)

        If this option is enabled, the application prompts the user to restart the operating system with the specified frequency.

        By default, this option is enabled. The default interval is 5 minutes. Available values are between 1 and 1440 minutes.

        If this option is disabled, the prompt is displayed only once.

      • Restart after (min)

        After prompting the user, the application forces restart of the operating system upon expiration of the specified time interval.

        By default, this option is enabled. The default delay is 30 minutes. Available values are between 1 and 1440 minutes.

    • Force closure of applications in blocked sessions

      Running applications may prevent a restart of the client device. For example, if a document is being edited in a word processing application and is not saved, the application does not allow the device to restart.

      If this option is enabled, such applications on a locked device are forced to close before the device restart. As a result, users may lose their unsaved changes.

      If this option is disabled, a locked device is not restarted. The task status on this device states that a device restart is required. Users have to manually close all applications running on locked devices and restart these devices.

      By default, this option is disabled.

  8. If necessary, at the Select accounts to access devices step, add the accounts that will be used to start the Install application remotely task:
    • No account required (Network Agent installed)

      If this option is selected, you do not have to specify the account under which the application installer will be run. The task will run under the account under which the Administration Server service is running.

      If Network Agent has not been installed on client devices, this option is unavailable.

    • Account required (Network Agent is not used)

      Select this option if Network Agent is not installed on the devices for which you assign the remote installation task. In this case, you can specify a user account or an SSH certificate to install the application.

      • Local Account. If this option is selected, specify the user account under which the application installer will be run. Click the Add button, select Local Account, and then specify the user account credentials.

        You can specify multiple user accounts if, for example, none of them have all the required rights on all devices for which you assign the task. In this case, all added accounts are used for running the task, in consecutive order, top-down.

      • SSH certificate. If you want to install an application on a Linux-based client device, you can specify an SSH certificate instead of a user account. Click the Add button, select SSH certificate, and then specify the private and public keys of the certificate.

        To generate a private key, you can use the ssh-keygen utility. Note that Kaspersky Security Center Cloud Console supports the PEM format of private keys, but the ssh-keygen utility generates SSH keys in the OPENSSH format by default. The OPENSSH format is not supported by Kaspersky Security Center Cloud Console. To create a private key in the supported PEM format, add the -m PEM option in the ssh-keygen command. For example:

        ssh-keygen -m PEM -t rsa -b 4096 -C "<user email>"

  9. At the Finish task creation step, click the Finish button to create the task and close the wizard.

    If you enabled the Open task details when creation is complete option, the task settings window opens. In this window, you can check the task parameters, modify them, or configure a task start schedule, if necessary.

  10. In the task list, select the task you created, and then click Start.

    Alternatively, wait for the task to launch according to the schedule that you specified in the task settings.

When the remote installation task is completed, the selected application is installed on the specified devices.

See also:

Protection deployment wizard

Page top

[Topic 236153]

Installing applications on secondary Administration Servers

To install an application on secondary Administration Servers:

  1. Establish a connection with the Administration Server that controls the relevant secondary Administration Servers.
  2. Make sure that the installation package corresponding to the application being installed is available on each of the selected secondary Administration Servers. If you cannot find the installation package on any of the secondary Servers, distribute it. For this purpose, create a task with the Distribute installation package task type.
  3. Create a task for a remote application installation on secondary Administration Servers. Select the Install application on secondary Administration Server remotely task type.

    The New task wizard creates a task for remote installation of the application selected in the wizard on specific secondary Administration Servers.

  4. Run the task manually or wait for it to launch according to the schedule that you specified in the task settings.

When the remote installation task is complete, the selected application is installed on the secondary Administration Servers.

Page top

[Topic 293238]

Starting and stopping Kaspersky applications

You can use the Start or stop application task for starting and stopping Kaspersky applications on managed devices.

To create the Start or stop application task:

  1. In the main menu, go to Assets (Devices) → Tasks.
  2. Click Add.

    The New task wizard starts. Proceed through the wizard by using the Next button.

  3. In the Application drop-down list, select the application for which you want to create the task.
  4. In the Task type list, select the Application activation task.
  5. In the Task name field, specify the name of the new task.

    The task name cannot be more than 100 characters long and cannot include any special characters ("*<>?\:|).

  6. Select the devices to which the task will be assigned.
  7. In the Applications window, do the following:
    • Select the check boxes next to the names of applications for which you want to create the task.
    • Select the Start application or the Stop application option.
  8. If you want to modify the default task settings, enable the Open task details when creation is complete option at the Finish task creation step. If you do not enable this option, the task is created with the default settings. You can modify the default settings later, at any time.
  9. Click the Finish button.

    The task is created and displayed in the list of tasks.

  10. Click the name of the created task to open the task properties window.
  11. In the task properties window, specify the general task settings according to your needs, and then save the settings.

The task is created and configured.

If you want to run the task, select it in the task list, and then click the Start button.

Page top

[Topic 213746]

Mobile Device Management

Management of mobile device protection through Kaspersky Security Center Cloud Console is carried out by using the Mobile Device Management feature. If you are intending to manage mobile devices owned by employees in your organization, enable and configure Mobile Device Management.

Mobile Device Management enables you to manage Android devices of the employees. The protection is provided by the Kaspersky Security for Mobile app installed on the devices. This mobile app ensures protection of mobile devices against web threats, viruses, and other programs that pose threats.

iOS devices

Kaspersky Device Management for iOS ensures protection and control of mobile devices that are connected to Kaspersky Security Center Cloud Console.

The Kaspersky Security for iOS app offers the following key features:

  • Web Protection. This component blocks malicious websites designed to spread malicious code. Web Protection also blocks fake (phishing) websites designed to steal confidential data of the user (for example, passwords for online banking or e-money systems) and access the user's financial info.
  • Jailbreak detection. When Kaspersky Security for iOS detects a jailbreak, it displays a critical message and informs you about the issue.

For information about protection deployment and management of mobile devices, see Kaspersky Security for Mobile Help.

See also:

Assigning a user as a device owner

Page top

[Topic 224996]

Detection and response capabilities

This section contains information about Kaspersky solutions that can be integrated into Kaspersky Security Center Cloud Console to add the detection and response capabilities to the console.

Page top

[Topic 225015]

About detection and response capabilities

Kaspersky Security Center Cloud Console can integrate features of other Kaspersky solutions into the console interface. For example, you can add the detection and response features to the functionality of Kaspersky Security Center Cloud Console.

The detection and response solutions are designed to protect an organization's IT infrastructure from complex cyberthreats. The solutions' functionality combines automatic threat detection with the ability to respond to these threats to resist complex attacks, including new exploits, ransomware, fileless attacks, and methods that use legitimate system tools.

You can integrate the following solutions:

  • Kaspersky Endpoint Detection and Response Optimum

    After a Kaspersky Endpoint Protection Platform (also referred to as EPP) application detects a threat, Kaspersky Security Center Cloud Console adds a new alert to the alert list. An alert contains detailed information about the detected threat and enables you to analyze and investigate the threat. You can also visualize the threat by creating a threat development chain graph. The graph describes the deployment stages of the detected attack in time.

    As a response, you can choose one of the predefined response actions, for example, isolate an untrusted object, isolate a compromised device from the network, or create an execution prevention rule for an untrusted object.

    For information about the solution activation, see the Kaspersky Endpoint Detection and Response Optimum documentation.

  • Kaspersky Managed Detection and Response

    After a Kaspersky EPP application detects a threat, Kaspersky Security Center Cloud Console adds a new incident to the incident list. An incident contains detailed information about the detected threat. The MDR Security Operation Center (SOC) analysts of Kaspersky or a third-party company investigate the incidents and offer responses to solve the incidents. You can accept or reject the offered measures manually, or enable the option to auto-accept all of the responses.

    For information about the solution activation, see the Kaspersky Managed Detection and Response documentation.

  • Kaspersky Endpoint Detection and Response Expert

    This is a solution for organizations that have a team of SOC analysts. The detected threats are registered as alerts or incidents that can be assigned to SOC analysts for investigation. Kaspersky Endpoint Detection and Response Expert provides you with detailed information on each alert or incident, as well as the tools for alert and incident management, threat hunting, and custom rules development. The SOC analysts or security officers can manually select the response actions, or the predefined automated response measures can be taken.

    For information about the solution activation, see the Kaspersky Endpoint Detection and Response Expert documentation.

Page top

[Topic 225206]

Interface changes after integrating the detection and response features

The following Kaspersky solutions provide detection and response features that can be integrated into the interface of Kaspersky Security Center Cloud Console:

The table below lists the changes that the solutions make in the interface of Kaspersky Security Center Cloud Console after integration.

Interface changes made by integrated Kaspersky solutions

Solution

Changes in Kaspersky Security Center Cloud Console

Kaspersky EDR Optimum

Adds the following elements:

  • Alerts section (Monitoring & reportingAlerts). The alerts detected by this solution are listed on the Optimum tab.
  • A widget on Dashboard (Monitoring & reportingDashboard).

Kaspersky MDR

 

Adds the following elements:

  • MDR section (Monitoring & reportingMDR).
  • The Show MDR features option (SettingsInterface options Show MDR features).
  • A widget on Dashboard (Monitoring & reportingDashboard).

Kaspersky EDR Expert

Adds the following elements:

  • Alerts section (Monitoring & reportingAlerts). The alerts detected by this solution are listed on the Expert tab.
  • Incidents section (Monitoring & reportingIncidents).
  • Threat hunting section (Monitoring & reportingThreat hunting).
  • Custom rules section (Monitoring & reportingCustom rules).
  • General settings of Kaspersky EDR Expert (SettingsIntegrationKaspersky EDR Expert).
  • Widgets on Dashboard (Monitoring & reportingDashboard).

Page top

[Topic 3907]

Discovering networked devices and creating administration groups

This section describes search and discovery of networked devices, as well as creating administration groups for these devices.

Kaspersky Security Center Cloud Console enables you to find devices on the basis of specified criteria. You can save search results to a text file.

The search and discovery feature enables you to find the following devices:

  • Managed devices in administration groups of Kaspersky Security Center Cloud Console Administration Server and its secondary Administration Servers.
  • Unassigned devices managed by Kaspersky Security Center Cloud Console Administration Server and its secondary Administration Servers.

In this section

Scenario: Discovering networked devices

Network polling

Adjustment of distribution points and connection gateways

Creating administration groups

Creating device moving rules

Copying device moving rules

Adding devices to an administration group manually

Moving devices or clusters to an administration group manually

Configuring retention rules for unassigned devices

Page top

[Topic 179028]

Scenario: Discovering networked devices

You must perform device discovery before the initial deployment of the security applications. When all networked devices are discovered, you can get information about them and manage them through policies. Regular network polls are needed to discover if there are any new devices and whether the previously discovered devices are still on the network.

When you complete the scenario, device discovery is set up and will be conducted according to the specified schedule.

Prerequisites

In Kaspersky Security Center Cloud Console, device discovery is performed by distribution points. Before you start, do the following:

  • Decide which devices will act as distribution points.
  • Install Network Agents on the devices that you chose.
  • Manually assign the devices to act as distribution points.

Stages

The scenario proceeds in stages:

  1. Choosing types of discovery

    Decide which type(s) of discovery you want to use regularly.

  2. Configuring polls

    In the properties of each distribution point, enable and configure the types of network polling that you chose: Windows network polling, domain controller polling, or IP range polling. Make sure that the poll schedule meets the needs of your organization.

    If networked devices are included in a domain, it is recommended to use domain controller polling.

  3. Setting up rules for adding discovered devices to administration groups (optional)

    If new devices appear on your network, they are discovered during regular polls and are automatically included in the Unassigned devices group. If you want, you can set up the rules for automatically moving these devices to the Managed devices group. You can also establish retention rules.

    If you skip this rule-setting step, all the newly discovered devices go to the Unassigned devices group and stay there. If you want, you can move these devices to the Managed devices group manually. If you move the devices to the Managed devices group manually, you can analyze information about each device and decide whether you want to move it to an administration group, and, if so, to which group.

When a network polling operation is complete, check that the newly discovered devices are arranged according to the configured rules. If no rules are configured, the devices stay in the Unassigned devices group.

See also:

Network polling

Adjustment of distribution points and connection gateways

Creating administration groups

Creating device moving rules

Copying device moving rules

Adding devices to an administration group manually

Moving devices or clusters to an administration group manually

Configuring retention rules for unassigned devices

Administration groups

Page top

[Topic 3884]

Network polling

Information about the structure of the network and devices on this network is received by Kaspersky Security Center Cloud Console through regular polling of the Windows network, IP ranges, Microsoft Active Directory domain controller and a Samba domain controller. For a Samba domain controller, Samba 4 is used as an Active Directory domain controller. Network polling can be started either manually or automatically according to a schedule.

Based on the results of this polling, Kaspersky Security Center Cloud Console updates the list of unassigned devices. You can also configure rules for newly discovered devices to be moved automatically to administration groups.

Kaspersky Security Center Cloud Console uses the following methods of network polling:

  • IP range polling. Kaspersky Security Center Cloud Console polls the specified IP ranges using Internet Control Message Protocol (ICMP) packets and compiles a complete set of data on devices within those IP ranges.
  • Windows network polling. You can run either of the two Windows network polls: fast or full. During a fast poll, Kaspersky Security Center Cloud Console only retrieves information from the list of the NetBIOS names of devices in all network domains and work groups. During a full poll, the following information is requested from each device: operating system (OS) name, IP address, DNS name, and NetBIOS name.
  • Domain controllers polling. Information about the Active Directory unit structure and about DNS names of the devices from Active Directory groups is recorded to the Kaspersky Security Center Cloud Console database.

Polling results are shown in the Discovery & deploymentDiscovery section separately for the Windows network polling and the Domain controllers polling methods.

Polling results for the IP range polling method are shown in the Discovery & deploymentUnassigned devices section.

One device can be shown in more than one detection area. If a device is detected in the HQ domain and its address is 192.168.0.1, the device will appear in both the Windows domains section and the Unassigned devices section. You can modify network polling settings for each polling method. For example, you may want to modify the polling schedule or to set whether to poll the entire Active Directory forest or only a specific domain.

In this section

Windows network polling

Domain controller polling

IP range polling

Configuring a Samba domain controller

Adding and modifying an IP range

See also:

Creating device moving rules

Scenario: Discovering networked devices

Page top

[Topic 166186]

Windows network polling

About Windows network polling

During a quick poll, the Administration Server only retrieves information from the list of the NetBIOS names of devices in all network domains and workgroups. During a full poll, the following information is requested from each client device:

  • Operating system name
  • IP address
  • DNS name
  • NetBIOS name

Both quick polls and full polls require the following:

  • Ports UDP 137/138, TCP 139 must be available on the network.
  • The Microsoft Computer Browser service must be used, and the primary browser computer must be enabled on the distribution point.
  • The Microsoft Computer Browser service must be used, and the primary browser computer must be enabled on the client devices:
    • On at least one device, if the number of networked devices does not exceed 32.
    • On at least one device for each 32 networked devices.

The full poll can run only if the quick poll has run at least once.

Viewing and modifying the settings for Windows network polling

To modify the properties of Windows network polling:

  1. In the main menu, click the settings icon () next to the name of the required Administration Server.

    The Administration Server properties window opens.

  2. On the General tab, select the Distribution points section.
  3. Click the name of the distribution point that you want to use to poll the network.

    The distribution point properties window opens.

  4. Select the Windows domains polling section.
  5. Enable or disable Windows network polling by using the Enable network polling toggle button.
  6. Configure the schedule for the quick polling and the full polling.
  7. Click the OK button.

The properties are saved and applied to all of the discovered Windows domains and workgroups.

See also:

Network polling

Scenario: Discovering networked devices

Page top

[Topic 166185]

Domain controller polling

Kaspersky Security Center Cloud Console supports polling of a Microsoft Active Directory domain controller and a Samba domain controller only by using a distribution point.

Kaspersky Security Center Cloud Console allows you to poll a Samba domain controller only by using a Linux distribution point. For a Samba domain controller, Samba 4 is used as an Active Directory domain controller.

When you poll a domain controller, a distribution point retrieves information about the domain structure, user accounts, security groups, and DNS names of the devices that are included in the domain. Domain controller polling is performed according to a schedule that you set.

Prerequisites

Before you poll a domain controller, ensure that the following protocols are enabled:

  • Simple Authentication and Security Layer (SASL)
  • Lightweight Directory Access Protocol (LDAP)

Ensure that the following ports are available on the domain controller device:

  • 389 for SASL
  • 636 for TLS

Domain controller polling by using a distribution point

You can also poll a domain controller by using a distribution point. A Windows- or Linux-based managed device can act as a distribution point.

For a Linux distribution point, polling of a Microsoft Active Directory domain controller and a Samba domain controller are supported.
For a Windows distribution point, only polling of a Microsoft Active Directory domain controller is supported.
Polling with a Mac distribution point is not supported.

To configure domain controller polling by using the distribution point:

  1. Open the distribution point properties.
  2. Select the Domain controller polling section.
  3. Select the Enable domain controller polling option.
  4. Select the domain controller that you want to poll.

    If you use a Linux distribution point, in the Poll specified domains section, click Add, and then specify the address and user credentials of the domain controller.

    If you use a Windows distribution point, you can select one of the following options:

    • Poll current domain
    • Poll entire domain forest
    • Poll specified domains
  5. Click the Set polling schedule button to specify the polling schedule options if needed.

    Polling starts only according to the specified schedule. Manual start of polling is not available.

After the polling is completed, the domain structure will be displayed in the Domain controllers section.

If you set up and enabled device moving rules, the newly discovered devices are automatically included in the Managed devices group. If no moving rules have been enabled, the newly discovered devices are automatically included in the Unassigned devices group.

The discovered user accounts can be used for domain authentication in Kaspersky Security Center Cloud Console.

Viewing the results of domain controller polling

To view the results of domain controller polling:

  1. In the main menu, go to Discovery & deployment DiscoveryDomain controllers.

    The list of discovered organizational units is displayed.

  2. Select an organizational unit, and then click the Devices button.

    The list of devices in the organizational unit is displayed.

You can search the list and filter the results.

See also:

Network polling

Scenario: Discovering networked devices

Page top

[Topic 166184]

IP range polling

Kaspersky Security Center Cloud Console attempts to perform reverse name resolution for every address from the specified range to a DNS name using standard DNS requests. If this operation succeeds, the server sends an ICMP ECHO REQUEST (the same as the ping command) to the received name. If the device responds, the information about it is added to the Kaspersky Security Center Cloud Console database. The reverse name resolution is necessary to exclude the network devices that can have an IP address but are not computers, for example, network printers or routers.

This polling method relies upon a correctly configured local DNS service. It must have a reverse lookup zone. If this zone is not configured, IP subnet polling will yield no results. On the networks where Active Directory is used, such a zone is maintained automatically. But on these networks, IP subnet polling does not provide more information than Active Directory polling. Moreover, administrators of small networks often do not configure the reverse lookup zone because it is not necessary for the work of many network services. For these reasons, IP subnet polling is disabled by default.

Initially, Kaspersky Security Center Cloud Console gets IP ranges for polling from the network settings of the distribution point device which is used for network polling. If the device address is 192.168.0.1 and the subnet mask is 255.255.255.0, Kaspersky Security Center Cloud Console includes the network 192.168.0.0/24 in the list of polling address automatically. Kaspersky Security Center Cloud Console polls all addresses from 192.168.0.1 to 192.168.0.254.

It is not recommended to use IP range polling if you use Windows network polling and/or Active Directory polling.

Viewing and modifying the settings for IP range polling

To view and modify the properties of IP range polling:

  1. In the main menu, click the settings icon () next to the name of the required Administration Server.

    The Administration Server properties window opens.

  2. On the General tab, select the Distribution points section.
  3. Click the name of the distribution point that you want to use to poll the network.

    The distribution point properties window opens.

  4. Select the IP range polling section.
  5. Enable or disable IP polling by using the Enable range polling toggle button.
  6. Configure the polling schedule. By default, IP polling runs every 420 minutes (seven hours).
  7. If necessary, add or modify IP ranges to poll.

    When specifying the polling interval, make sure that this setting does not exceed the value of the IP address lifetime parameter. If an IP address is not verified by polling during the IP address lifetime, this IP address is automatically removed from the polling results. By default, the life span of the polling results is 24 hours, because dynamic IP addresses (assigned using Dynamic Host Configuration Protocol (DHCP)) change every 24 hours.

  8. Click the OK button.

The properties are saved and applied to all IP ranges.

See also:

Network polling

Scenario: Discovering networked devices

Page top

[Topic 257889]

Configuring a Samba domain controller

Kaspersky Security Center Cloud Console supports a Linux domain controller running only on Samba 4.

A Samba domain controller supports the same schema extensions as a Microsoft Active Directory domain controller. You can enable full compatibility of a Samba domain controller with a Microsoft Active Directory domain controller by using the Samba 4 schema extension. This is an optional action.

We recommend enabling full compatibility of a Samba domain controller with a Microsoft Active Directory domain controller. This will ensure the correct interaction between Kaspersky Security Center Cloud Console and the Samba domain controller.

To enable full compatibility of a Samba domain controller with a Microsoft Active Directory domain controller:

  1. Execute the following command to use the RFC2307 schema extension:

    samba-tool domain provision --use-rfc2307 --interactive

  2. Enable the schema update in a Samba domain controller. To do this, add the following line to the /etc/samba/smb.conf file:

    dsdb:schema update allowed = true

    If the schema update completes with an error, you need to perform a full restore of the domain controller that acts as a schema master.

If you want to poll a Samba domain controller correctly, you have to specify the netbios name and workgroup parameters in the /etc/samba/smb.conf file.

Page top

[Topic 176003]

Adding and modifying an IP range

Expand all | Collapse all

Initially, Kaspersky Security Center Cloud Console gets IP ranges for polling from the network settings of the distribution point device which is used for network polling. If the device address is 192.168.0.1 and the subnet mask is 255.255.255.0, Kaspersky Security Center Cloud Console includes the network 192.168.0.0/24 in the list of polling address automatically. Kaspersky Security Center Cloud Console polls all addresses from 192.168.0.1 to 192.168.0.254. You can modify the automatically defined IP ranges or add custom IP ranges.

To add a new IP range:

  1. In the main menu, click the settings icon () next to the name of the required Administration Server.

    The Administration Server properties window opens.

  2. On the General tab, select the Distribution points section.
  3. Click the name of the distribution point that you want to use to poll the network.

    The distribution point properties window opens.

  4. Select the IP range polling section.
  5. To add a new IP range, click the Add button.
  6. In the window that opens, specify the following settings:
    • Name

      A name of the IP range. You might want to specify the IP range itself as its name, for example, "192.168.0.0/24".

    • IP interval or subnet address and mask

      Set the IP range by specifying either the start and end IP addresses or the subnet address and subnet mask. You can add as many subnets as you need. Named IP ranges are not allowed to overlap, but unnamed subnets inside an IP range have no such restrictions.

    • IP address lifetime (hours)

      When specifying this parameter make sure that it exceeds the polling interval set in the polling schedule. If an IP address is not verified by polling during the IP address lifetime, this IP address is automatically removed from the polling results. By default, the life span of the polling results is 24 hours, because dynamic IP addresses (assigned using Dynamic Host Configuration Protocol (DHCP)) change every 24 hours.

  7. Click the OK button.

The new IP range is added to the list of IP ranges.

When the polling is complete, you can view the list of discovered devices by using the Devices button. By default, the life span of the polling results is 24 hours and it is equal to the IP address lifetime setting.

See also:

IP range polling

Scenario: Discovering networked devices

Page top

[Topic 92429]

Adjustment of distribution points and connection gateways

A structure of administration groups in Kaspersky Security Center Cloud Console serves the following functions:

  • Sets the scope of policies

    There is an alternate way of applying relevant settings on devices, by using policy profiles. In this case, the scope of policies is set with tags, device locations in Active Directory organizational units, membership in Active Directory security groups, etc.

  • Sets the scope of group tasks

    There is an approach to defining the scope of group tasks that is not based on a hierarchy of administration groups: use of tasks for device selections and tasks for specific devices.

  • Sets access rights to devices and secondary Administration Servers
  • Assigns distribution points

When building the structure of administration groups, you must take into account the topology of the organization's network for the optimum assignment of distribution points. The optimum distribution of distribution points enables you to save traffic in the organization's network.

Depending on the organizational schema and network topology, the following standard configurations can be applied to the structure of administration groups:

  • Single office
  • Multiple small remote offices

Devices functioning as distribution points must be protected, including physical protection, against any unauthorized access.

In this section

Calculating the number and configuration of distribution points

Standard configuration of distribution points: Single office

Standard configuration of distribution points: Multiple small remote offices

Assigning distribution points manually

Modifying the list of distribution points for an administration group

Using a distribution point as a push server

Using the "Do not disconnect from the Administration Server" option to provide continuous connectivity between a managed device and the Administration Server

See also:

Scenario: Discovering networked devices

Scenario: Kaspersky applications initial deployment

Page top

[Topic 154282]

Calculating the number and configuration of distribution points

The more client devices a network contains, the more distribution points it requires. Use the tables below to calculate the number of distribution points required for your network.

Make sure that the devices that you intend to use as distribution points have sufficient volume of free disk space, are not shut down regularly, and have Sleep mode disabled.

Number of exclusively assigned distribution points on a network that contains a single network segment, based on the number of networked devices

Number of client devices in the network segment

Number of distribution points

Less than 300

0 (Do not assign distribution points)

More than 300

Acceptable: (N/10,000 + 1), recommended: (N/5000 + 2), where N is the number of networked devices

Number of exclusively assigned distribution points on a network that contains multiple network segments, based on the number of networked devices

Number of client devices per network segment

Number of distribution points

Less than 10

0 (Do not assign distribution points)

10... 100

1

More than 100

Acceptable: (N/10,000 + 1), recommended: (N/5000 + 2), where N is the number of networked devices

Using standard client devices (workstations) as distribution points

If you plan to use standard client devices (that is, workstations) as distribution points, we recommend that you assign distribution points as shown in the tables below in order to avoid excessive load on the communication channels and on Administration Server:

Number of workstations functioning as distribution points on a network that contains a single network segment, based on the number of networked devices

Number of client devices in the network segment

Number of distribution points

Less than 300

0 (Do not assign distribution points)

More than 300

(N/300 + 1), where N is the number of networked devices; there must be at least 3 distribution points

Number of workstations functioning as distribution points on a network that contains multiple network segments, based on the number of networked devices

Number of client devices per network segment

Number of distribution points

Less than 10

0 (Do not assign distribution points)

10... 30

1

31... 300

2

More than 300

(N/300 + 1), where N is the number of networked devices; there must be at least 3 distribution points

If a distribution point is not available, update Kaspersky databases, software modules, and applications manually or directly from the Kaspersky update servers.

See also:

Adjustment of distribution points and connection gateways

Scenario: Discovering networked devices

Page top

[Topic 92430]

Standard configuration of distribution points: Single office

In a standard "single-office" configuration, all devices are on the organization's network so they can "see" each other. The organization's network may consist of a few separate parts (networks or network segments) linked by narrow channels.

The following methods of building the structure of administration groups are possible:

  • Building the structure of administration groups taking into account the network topology. The structure of administration groups may not reflect the network topology with absolute precision. A match between the separate parts of the network and certain administration groups would be enough.
  • Building the structure of administration groups, without taking the network topology into account. In this case, you must assign one or several devices to act as distribution points for a root administration group in each of the separate parts of the network, for example, for the Managed devices group. All distribution points will be at the same level and will feature the same scope spanning all devices in the organization's network. In this case, each Network Agent will connect to the distribution point that has the shortest route. The route to a distribution point can be traced with the tracert utility.

See also:

Adjustment of distribution points and connection gateways

Scenario: Discovering networked devices

Page top

[Topic 92431]

Standard configuration of distribution points: Multiple small remote offices

This standard configuration provides for a number of small remote offices, which may communicate with the head office over the internet. Each remote office is located behind the NAT, that is, connection from one remote office to another is not possible because offices are isolated from one another.

The configuration must be reflected in the structure of administration groups: a separate administration group must be created for each remote office (groups Office 1 and Office 2 in the figure below).

A Managed devices node includes the Root group of offices folder that contains Administration Servers, and groups Office 1 and Office 2.

Remote offices are included in the administration group structure

One or multiple distribution points must be assigned to each administration group that correspond to an office. Distribution points must be devices at the remote office that have a sufficient amount of free disk space. Devices deployed in the Office 1 group, for example, will access distribution points assigned to the Office 1 administration group.

If some users move between offices physically, with their laptops, you must select two or more devices (in addition to the existing distribution points) in each remote office and assign them to act as distribution points for a top-level administration group (Root group for offices in the figure above).

Example: A laptop is deployed in the Office 1 administration group and then is moved physically to the office that corresponds to the Office 2 administration group. After the laptop is moved, Network Agent attempts to access the distribution points assigned to the Office 1 group, but those distribution points are unavailable. Then, Network Agent starts attempting to access the distribution points that have been assigned to the Root group for offices. Because remote offices are isolated from one another, attempts to access distribution points assigned to the Root group for offices administration group will only be successful when Network Agent attempts to access distribution points in the Office 2 group. That is, the laptop will remain in the administration group that corresponds to the initial office, but the laptop will use the distribution point of the office where it is physically located at the moment.

See also:

Adjustment of distribution points and connection gateways

Requirements for a distribution point

Scenario: Regular updating of Kaspersky databases and applications

Scenario: Discovering networked devices

Page top

[Topic 181511]

Assigning distribution points manually

Expand all | Collapse all

Kaspersky Security Center Cloud Console enables you to manually assign devices to act as distribution points. We recommend that you calculate the number and configuration of distribution points required for your network.

Distribution point devices running macOS cannot download updates from Kaspersky update servers.

If one or more devices running macOS are within the scope of the Download updates to the repositories of distribution points task, the task completes with the Failed status, even if it has successfully completed on all Windows devices.

Devices functioning as distribution points must be protected, including physical protection, against any unauthorized access.

To manually assign a device to act as distribution point:

  1. In the main menu, click the settings icon () next to the name of the required Administration Server.

    The Administration Server properties window opens.

  2. On the General tab, select the Distribution points section.
  3. Click the Assign button.
  4. Select the device that you want to make a distribution point.

    When selecting a device, keep in mind the operation features of distribution points and the requirements set for the device that acts as distribution point.

  5. Select the administration group that you want to include in the scope of the selected distribution point.
  6. Click the Add button.

    The distribution point that you have added will be displayed in the list of distribution points, in the Distribution points section.

  7. Select the newly added distribution point in the list to open its properties window.
  8. Configure the distribution point in the properties window:
    • The General section contains the settings of interaction between the distribution point and client devices:
      • SSL port

        The number of the SSL port for encrypted connection between client devices and the distribution point using SSL.

        By default, port 13000 is used.

      • Use multicast

        If this option is enabled, IP multicasting will be used for automatic distribution of installation packages to client devices within the group.

        IP multicasting decreases the time required to install an application from an installation package to a group of client devices, but increases the installation time when you install an application to a single client device.

      • IP multicast address

        IP address that will be used for multicasting. You can define an IP address in the range of 224.0.0.0 – 239.255.255.255

        By default, Kaspersky Security Center Cloud Console automatically assigns a unique IP multicast address within the given range.

      • IP multicast port number

        Number of the port for IP multicasting.

        By default, the port number is 15001. If the device with Administration Server installed is specified as the distribution point, port 13001 is used for SSL connection by default.

      • Deploy updates

        Updates are distributed to managed devices from the following sources:

        • This distribution point, if this option is enabled.
        • Other distribution points, Administration Server, or Kaspersky update servers, if this option is disabled.

        If you use distribution points to deploy updates, you can save traffic because you reduce the number of downloads. Also, you can relieve the load on the Administration Server and relocate the load between the distribution points. You can calculate the number of distribution points for your network to optimize the traffic and load.

        If you disable this option, the number of update downloads and load on the Administration Server may increase. By default, this option is enabled.

      • Deploy installation packages

        Installation packages are distributed to managed devices from the following sources:

        • This distribution point, if this option is enabled.
        • Other distribution points, Administration Server, or Kaspersky update servers, if this option is disabled.

        If you use distribution points to deploy installation packages, you can save traffic because you reduce the number of downloads. Also, you can relieve the load on the Administration Server and relocate the load between the distribution points. You can calculate the number of distribution points for your network to optimize the traffic and load.

        If you disable this option, the number of installation package downloads and load on the Administration Server may increase. By default, this option is enabled.

      • Run push server

        In Kaspersky Security Center Cloud Console, a distribution point can work as a push server for Windows-based and Linux-based devices that are managed by Network Agent. A push server has the same scope of managed devices as the distribution point on which the push server is enabled. If you have several distribution points assigned for the same administration group, you can enable a push server on each of the distribution points. In this case, Administration Server balances the load between the distribution points.

      • Push server port

        The port number for the push server. You can specify the number of any unoccupied port.

    • In the Scope section, specify the scope to which the distribution point will distribute updates (administration groups and / or network location).

      Only devices running a Windows operating system can determine their network location. Network location cannot be determined for devices running other operating systems.

    • In the KSN Proxy section, you can configure the application to use the distribution point to forward KSN requests from the managed devices:

      Enable KSN Proxy on the distribution point side

      The KSN proxy service is run on the device that is used as a distribution point. Use this feature to redistribute and optimize traffic on the network.

      This feature is not supported by distribution point devices running Linux or macOS.

      The distribution point sends the KSN statistics, which are listed in the Kaspersky Security Network statement, to Kaspersky. By default, the KSN statement is located in %ProgramFiles%\Kaspersky Lab\Kaspersky Security Center\ksneula.

      By default, this option is disabled. Enabling this option takes effect only if the I agree to use Kaspersky Security Network option is enabled in the Administration Server properties window.

      You can assign a node of an active-passive cluster to a distribution point and enable KSN proxy server on this node.

    • Configure the polling of Windows domains, domain controller, and IP ranges by the distribution point:
      • Windows domains polling

        You can enable device discovery for Windows domains and set the schedule for the discovery.

      • Domain controller polling

        You can enable network polling for Active Directory and set the schedule for the poll.

        If you use a Windows distribution point, you can select one of the following options:

        • Poll current Active Directory domain.
        • Poll Active Directory domain forest.
        • Poll selected Active Directory domains only. If you select this option, add one or more Active Directory domains to the list.

        If you use a Linux distribution point with installed Network Agent version 15, you can poll only Active Directory domains for which you specify the address and user credentials. Polling of the current Active Directory domain and the Active Directory domain forest is not available.

        You can enable device discovery for domain controllers.

        If you select the Enable domain controller polling option, you can select domain controllers for polling and also specify the polling schedule for them.

        If you use a Linux distribution point, in the Poll specified domains section, click Add, and then specify the address and user credentials of the domain controller.

        If you use a Windows distribution point, you can select one of the following options:

        • Poll current domain
        • Poll entire domain forest
        • Poll specified domains
      • IP range polling

        You can enable device discovery for IPv4 ranges and IPv6 networks.

        If you enable the Enable range polling option, you can add scanned ranges and set the schedule for them. You can add IP ranges to the list of scanned ranges.

        If you enable the Use Zeroconf to poll IPv6 networks option, the distribution point automatically polls the IPv6 network by using zero-configuration networking (also referred to as Zeroconf). In this case, the specified IP ranges are ignored because the distribution point polls the whole network. The Use Zeroconf to poll IPv6 networks option is available if the distribution point runs Linux. To use Zeroconf IPv6 polling, you must install the avahi-browse utility on the distribution point.

    • In the Advanced section, specify the folder that the distribution point must use to store distributed data:
      • Use default folder

        If you select this option, the application uses the Network Agent installation folder on the distribution point.

      • Use specified folder

        If you select this option, in the field below, you can specify the path to the folder. It can be a local folder on the distribution point, or it can be a folder on any device on the corporate network.

        The user account used on the distribution point to run Network Agent must have read/write access to the specified folder.

  9. Click the OK button.

The selected devices act as distribution points.

See also:

Ports used by Kaspersky Security Center Cloud Console

Scenario: Discovering networked devices

Page top

[Topic 181540]

Modifying the list of distribution points for an administration group

You can view the list of distribution points assigned to a specific administration group and modify the list by adding or removing distribution points.

To view and modify the list of distribution points assigned to an administration group:

  1. In the main menu, go to Assets (Devices) → Groups.
  2. In the administration group structure, select the administration group for which you want to view the assigned distribution points.
  3. Click the Distribution points tab.
  4. Add new distribution points for the administration group by using the Assign button or remove the assigned distribution points by using the Unassign button.

Depending on your modifications, the new distribution points are added to the list or existing distribution points are removed from the list.

See also:

Adjustment of distribution points and connection gateways

Scenario: Discovering networked devices

Page top

[Topic 219573]

Using a distribution point as a push server

In Kaspersky Security Center Cloud Console, a distribution point can work as a push server for Windows-based and Linux-based devices that are managed by Network Agent. A push server has the same scope of managed devices as the distribution point on which the push server is enabled. If you have several distribution points assigned for the same administration group, you can enable a push server on each of the distribution points. In this case, Administration Server balances the load between the distribution points.

You can use distribution points as push servers to ensure that continuous connectivity between a managed device and the Administration Server. Continuous connectivity is needed for some operations, such as running and stopping local tasks, receiving statistics for a managed application, or creating a tunnel. If you use a distribution point as a push server, you do not have to send packets to the UDP port of Network Agent.

To use a distribution point as a push server:

  1. In the main menu, click the settings icon () next to the name of the required Administration Server.

    The Administration Server properties window opens.

  2. On the General tab, select the Distribution points section.
  3. Click the distribution point that you want to use as a push server.
  4. In the property list of the selected distribution point, go to the General section, and then enable the Run push server option.

    The Push server port entry field becomes available.

  5. In the Push server port entry field, specify the port on the distribution point that client devices will use for connection. By default, port 13295 is used.

    To establish connection between the distribution point acting as a push server and a managed device, you must manually add the specified push server port to the Microsoft Windows Firewall exclusion list.

  6. Click OK to exit the distribution point properties window, and then click Save to apply changes.

    After you enable the Run push server option, the Do not disconnect from the Administration Server option is automatically enabled on the distribution point that acts as a push server. This option provides an early connection between Network Agent and the Administration Server.

  7. Open the Network Agent policy settings window.
  8. Go to ConnectivityNetwork, and then enable the Use distribution point to force connection to the Administration Server option. Close the lock for this option.
  9. Also in the Network subsection, you can disable the Use UDP port option. The configured push server will provide continuous connectivity between a managed device and the Administration Server instead of sending packets through the UDP port.
  10. Click OK to exit the window.

The distribution point starts acting as a push server. It can now send push notifications to client devices.

See also:

Ports used by Kaspersky Security Center Cloud Console

Distribution point

Adjustment of distribution points and connection gateways

Page top

[Topic 155179]

Using the "Do not disconnect from the Administration Server" option to provide continuous connectivity between a managed device and the Administration Server

If you do not use push servers, Kaspersky Security Center Cloud Console does not provide continuous connectivity between managed devices and the Administration Server. Network Agents on managed devices periodically establish connections and synchronize with the Administration Server. The interval between those synchronization sessions is defined in a Network Agent policy. If an early synchronization is required, the Administration Server (or a distribution point, if it is in use) sends a signed network packet over an IPv4 or IPv6 network to the UDP port of Network Agent. By default, the port number is 15000. If no connection through UDP is possible between the Administration Server and a managed device, synchronization will run at the next regular connection of Network Agent to the Administration Server within the synchronization interval.

Some operations cannot be performed without an early connection between Network Agent and the Administration Server, such as running and stopping local tasks, receiving statistics for a managed application, or creating a tunnel. To resolve this issue, if you are not using push servers, you can use the Do not disconnect from the Administration Server option to ensure continuous connectivity between a managed device and the Administration Server.

To provide continuous connectivity between a managed device and the Administration Server:

  1. Do one of the following:
    • If the managed device accesses the Administration Server directly (that is, not via a distribution point):
      1. In the main menu, go to DevicesManaged devices.
      2. Click the name of the device with which you want to provide continuous connectivity.

        The property window of the managed device opens.

    • If the managed device accesses the Administration Server through a distribution point running in gateway mode, not directly:
      1. In the main menu, click the settings icon () next to the name of the required Administration Server.

        The Administration Server properties window opens.

      2. On the General tab, select the Distribution points section.
      3. In the distribution point list, click the name of the required distribution point.

        The properties window of the selected distribution point opens.

  2. In the General section of the opened properties window, select the Do not disconnect from the Administration Server option.

Continuous connectivity is established between the managed device and the Administration Server.

The maximum total number of devices with the Do not disconnect from the Administration Server option selected is 300.

See also:

Using a distribution point as a push server

Page top

[Topic 46974]

Creating administration groups

Initially, the hierarchy of administration groups contains the only administration group named Managed devices. When creating a hierarchy of administration groups, you can add devices and virtual machines to the Managed devices group and add subgroups. For each administration group, the properties window contains information about policies, tasks, and devices related to the group.

To create an administration group:

  1. In the main menu, go to Assets (Devices)Hierarchy of groups.
  2. Select the check box next to the administration group for which you want to create a new subgroup.
  3. Click the Add button.
  4. Type a name for the new administration group.
  5. Click the Add button.

A new administration group with the specified name appears in the administration group hierarchy.

The application allows creation of a hierarchy of administration groups based on the structure of Active Directory or on the structure of the domain network. Also, you can create a structure of groups from a text file.

To create a structure of administration groups:

  1. In the main menu, go to Assets (Devices)Hierarchy of groups.
  2. Click the Import button.

The New administration group structure wizard starts. Follow the instructions of the wizard.

See also:

Scenario: Discovering networked devices

Page top

[Topic 175901]

Creating device moving rules

Expand all | Collapse all

You can set up device moving rules, that is, rules that automatically allocate devices to administration groups.

To create a moving rule:

  1. In the main menu, go to Assets (Devices) → Moving rules.
  2. Click Add.
  3. In the window that opens, specify the following information on the General tab:
    • Rule name

      Enter a name for the new rule.

      If you are copying a rule, the new rule gets the same name as the source rule, but an index in () format is added to the name, for example: (1).

    • Administration group

      Select the administration group into which the devices are to be moved automatically.

    • Active rule

      If this option is enabled, the rule is enabled and starts working after it is saved.

      If this option is disabled, the rule is created, but not enabled. It will not work until you enable this option.

    • Move only devices that do not belong to an administration group

      If this option is enabled, only unassigned devices will be moved to the selected group.

      If this option is disabled, devices that already belong to other administration groups, as well as unassigned devices, will be moved to the selected group.

    • Apply rule

      You can select one of the following options:

      • Run once for each device

        The rule is applied once for each device that matches your criteria.

      • Run once for each device, then at every Network Agent reinstallation

        The rule is applied once for each device that matches your criteria, then only when Network Agent is reinstalled on these devices.

      • Apply rule continuously

        The rule is applied according to the schedule which the Administration Server sets up automatically (usually every several hours).

  4. On the Rule conditions tab, specify at least one criterion by which the devices are moved to an administration group.
  5. Click Save.

The moving rule is created. It is displayed in the list of moving rules.

The higher the position is on the list, the higher the priority of the rule. To increase or decrease the priority of a moving rule, move the rule up or down in the list, respectively, using the mouse.

If the Apply rule continuously option is selected, the moving rule is applied regardless of the priority settings. Such rules are applied according to the schedule which the Administration Server sets up automatically.

If the device attributes meet the conditions of multiple rules, the device is moved to the target group of the rule with the highest priority (that is, has the highest rank in the list of rules).

See also:

Adding devices to an administration group manually

Scenario: Discovering networked devices

Page top

[Topic 177040]

Copying device moving rules

Expand all | Collapse all

You can copy moving rules, for example, if you want to have several identical rules for different target administration groups.

To copy an existing a moving rule:

  1. Do one of the following:
    • In the main menu, go to Assets (Devices) → Moving rules.
    • In the main menu, go to Discovery & deploymentDeployment & assignment → Moving rules.

    The list of moving rules is displayed.

  2. Select the check box next to the rule you want to copy.
  3. Click Copy.
  4. In the window that opens, change the following information on the General tab—or make no changes if you only want to copy the rule without changing its settings:
    • Rule name

      Enter a name for the new rule.

      If you are copying a rule, the new rule gets the same name as the source rule, but an index in () format is added to the name, for example: (1).

    • Administration group

      Select the administration group into which the devices are to be moved automatically.

    • Active rule

      If this option is enabled, the rule is enabled and starts working after it is saved.

      If this option is disabled, the rule is created, but not enabled. It will not work until you enable this option.

    • Move only devices that do not belong to an administration group

      If this option is enabled, only unassigned devices will be moved to the selected group.

      If this option is disabled, devices that already belong to other administration groups, as well as unassigned devices, will be moved to the selected group.

    • Apply rule

      You can select one of the following options:

      • Run once for each device

        The rule is applied once for each device that matches your criteria.

      • Run once for each device, then at every Network Agent reinstallation

        The rule is applied once for each device that matches your criteria, then only when Network Agent is reinstalled on these devices.

      • Apply rule continuously

        The rule is applied according to the schedule which the Administration Server sets up automatically (usually every several hours).

  5. On the Rule conditions tab, specify at least one criterion for the devices that you want to be moved automatically.
  6. Click Save.

The new moving rule is created. It is displayed in the list of moving rules.

See also:

Scenario: Discovering networked devices

Page top

[Topic 198761]

Adding devices to an administration group manually

You can move devices to administration groups automatically by creating device moving rules or manually by moving devices from one administration group to another or by adding devices to a selected administration group. This section describes how to manually add devices to an administration group.

To add manually one or more devices to a selected administration group:

  1. In the main menu, go to Assets (Devices) → Managed devices.
  2. Select the administration group to which you want to add the devices:
    • For the root group:

      In this case you can proceed to the next step.

    • For a subgroup:

      Click the Change scope button at the top of the page, and then, in the window that opens, click the name of the subgroup.

      The path to the selected group is displayed at the top of the page. If necessary, you can click a link with the administration group name to go to the group. By default, the last link in the path is inactive.

  3. Click the Add devices button.

    The Move devices wizard starts.

  4. Make a list of the devices that you want to add to the administration group.

    You can add only devices for which information has already been added to the Administration Server database either upon connection of the device or after device discovery.

    Select how you want to add devices to the list:

    • Click the Add devices button, and then specify the devices in one of the following ways:
      • Select devices from the list of devices detected by the Administration Server.
      • Specify a device IP address or an IP range.
      • Specify the NetBIOS name or DNS name of a device.

        The device name field must not contain space characters, backspace characters, or the following prohibited characters: , \ / * ' " ; : & ` ~ ! @ # $ ^ ( ) = + [ ] { } | < > %

    • Click the Import devices from file button to import a list of devices from a .txt file. Each device address or name must be specified on a separate line.

      The file must not contain space characters, backspace characters, or the following prohibited characters: , \ / * ' " ; : & ` ~ ! @ # $ ^ ( ) = + [ ] { } | < > %

  5. View the list of devices to be added to the administration group. You can edit the list by adding or removing devices.
  6. After making sure that the list is correct, click the Next button.

The wizard processes the device list and displays the result. The successfully processed devices are added to the administration group and are displayed in the list of devices under names generated by Administration Server.

See also:

Creating device moving rules

Scenario: Discovering networked devices

Page top

[Topic 3908]

Moving devices or clusters to an administration group manually

You can move devices from one administration group to another, or from the group of unassigned devices to an administration group.

You can also move clusters or server arrays from one administration group to another. When you move a cluster or server array to another group, all of its nodes move with it, because a cluster and any of its nodes always belong to the same administration group. When you select a single cluster node on the Devices tab, the Move to group button becomes unavailable.

To move one or several devices or clusters to a selected administration group:

  1. Open the administration group from which you want to move the devices. To do this, perform one of the following:
    • To open an administration group, in the main menu, go to Assets (Devices) → Groups → <group name> → Managed devices.
    • To open the Unassigned devices group, in the main menu, go to Discovery & deploymentUnassigned devices.
  2. If the administration group contains clusters or server arrays, the Managed devices section is divided into two tabs—the Devices tab and the Clusters and server arrays tab. Open the tab for the object that you want to move.
  3. Select the check boxes next to the devices or clusters that you want to move to a different group.
  4. Click the Move to group button.
  5. In the hierarchy of administration groups, select the check box next to the administration group to which you want to move the selected devices or clusters.
  6. Click the Move button.

The selected devices or clusters are moved to the selected administration group.

See also:

Scenario: Discovering networked devices

Page top

[Topic 174975]

Configuring retention rules for unassigned devices

Expand all | Collapse all

After Windows network polling is complete, the found devices are placed into subgroups of the Unassigned devices administration group. This administration group can be found at Discovery & deploymentDiscoveryWindows domains. The Windows domains folder is the parent group. It contains child groups named after the corresponding domains and workgroups that have been found during the poll. The parent group may also contain the administration group of mobile devices. You can configure the retention rules of the unassigned devices for the parent group and for each of the child groups. The retention rules do not depend on the device discovery settings and work even if the device discovery is disabled.

The device retention rules do not affect the devices that have one or more drives encrypted with full disk encryption. Such devices are not deleted automatically—you can only delete them manually. If you need to delete a device with an encrypted drive, first decrypt the drive, and then delete the device.

To configure retention rules for unassigned devices:

  1. In the main menu, go to Discovery & deploymentDiscoveryWindows domains.
  2. Do one of the following:
    • To configure settings of the parent group, click the Properties button.

      The Windows domain properties window opens.

    • To configure settings of a child group, click its name.

      The child group properties window opens.

  3. Define the following settings:
    • Remove the device from the group if it has been inactive for longer than (days)

      If this option is enabled, you can specify the time interval after which the device is automatically removed from the group. By default, this option is also distributed to the child groups. The default time interval is 7 days.

      By default, this option is enabled.

    • Inherit from parent group

      If this option is enabled, the retention period for the devices in the current group is inherited from the parent group and cannot be changed.

      This option is available only for child groups.

      By default, this option is enabled.

    • Force inheritance in child groups

      The setting values will be distributed to child groups but in the properties of the child groups these settings are locked.

      By default, this option is disabled.

  4. Click the Accept button.

Your changes are saved and applied.

Page top

[Topic 179344]

Scenario: Configuring network protection

The quick start wizard creates policies and tasks with the default settings. These settings may turn out to be sub-optimal or even disallowed by the organization. Therefore, we recommend that you fine-tune these policies and tasks and create other policies and tasks, if they are necessary for your network.

Prerequisites

Before you start, make sure that you have completed the Kaspersky Security Center Cloud Console initial configuration scenario, including the quick start wizard.

When the quick start wizard is running, the following policies and tasks are created in the Managed devices administration group:

  • Policy of Kaspersky Endpoint Security
  • Group task for updating Kaspersky Endpoint Security
  • Policy of Network Agent
  • Find vulnerabilities and required updates (task of Network Agent)

Stages

Configuring network protection proceeds in stages:

  1. Setup and propagation of Kaspersky application policies and policy profiles

    To configure and propagate settings for Kaspersky applications installed on the managed devices, you can use two different security management approaches: device-centric or user-centric. You can also combine these two approaches.

  2. Configuring tasks for remote management of Kaspersky applications

    Check the tasks created with the quick start wizard and fine-tune them, if necessary.

    How-to instructions:

    If necessary, create additional tasks to manage the Kaspersky applications installed on the client devices.

  3. Evaluating and limiting the event load on the database

    Information about events that occur during the operation of managed applications is transferred from a client device and registered in the Administration Server database. To reduce the load on the Administration Server, evaluate and limit the maximum number of events that can be stored in the database.

    How-to instructions: Setting the maximum number of events.

Results

Upon completion of this scenario, your network will be protected by configuration of Kaspersky applications, tasks, and events received by the Administration Server:

  • The Kaspersky applications are configured according to the policies and policy profiles.
  • The applications are managed through a set of tasks.
  • The maximum number of events that can be stored in the database is set.

When the network protection configuration is complete, you can proceed to configuring regular updates to Kaspersky databases and applications.

See also:

About device-centric and user-centric security management approaches

Policy setup and propagation: Device-centric approach

Policy setup and propagation: User-centric approach

Network Agent policy settings

Comparison of Network Agent policy settings by operating systems

Manual setup of the Kaspersky Endpoint Security policy

Manual setup of the group update task for Kaspersky Endpoint Security

Tasks

Managing client devices

Managing administration groups

Policies and policy profiles

Data encryption and protection

Users and user roles

Managing object revisions

Kaspersky Security Network (KSN)

Deletion of objects

Page top

[Topic 179989]

About device-centric and user-centric security management approaches

You can manage security settings from the standpoint of device features and from the standpoint of user roles. The first approach is called device-centric security management and the second is called user-centric security management. To apply different application settings to different devices you can use either or both types of management in combination.

Device-centric security management enables you to apply different security application settings to managed devices depending on device-specific features. For example, you can apply different settings to devices allocated in different administration groups. You can also differentiate the devices by usage of those devices in Active Directory, or their hardware specifications.

User-centric security management enables you to apply different security application settings to different user roles. You can create several user roles, assign an appropriate user role to each user, and define different application settings to the devices owned by users with different roles. For example, you may want to apply different application settings to devices of accountants and human resources (HR) specialists. As a result, when user-centric security management is implemented, each department—accounts department and HR department—has its own settings configuration for Kaspersky applications. A settings configuration defines which application settings can be changed by users and which are forcibly set and locked by the administrator.

By using user-centric security management you can apply specific application settings to individual users. This may be required when an employee has a unique role in the company or when you want to monitor security issues related to devices of a specific person. Depending on the role of this employee in the company, you can expand or limit the rights of this person to change application settings. For example, you might want to expand the rights of a system administrator who manages client devices in a local office.

You can also combine the device-centric and user-centric security management approaches. For example, you can configure a specific application policy for each administration group, and then create policy profiles for one or several user roles of your enterprise. In this case the policies and policy profiles are applied in the following order:

  1. The policies created for device-centric security management are applied.
  2. They are modified by the policy profiles according to the policy profile priorities.
  3. The policies are modified by the policy profiles associated with user roles.

See also:

Scenario: Configuring network protection

Page top

[Topic 177128]

Policy setup and propagation: Device-centric approach

This section provides a scenario for a device-centric approach to the centralized configuration of Kaspersky applications installed on managed devices. When you complete this scenario, the applications will be configured on all of the managed devices in accordance with the application policies and policy profiles that you define.

You might also want to consider user-centric security management as an alternative or additional option to the device-centric approach.

Process

The scenario of device-centric management of Kaspersky applications consists of the following steps:

  1. Configuring application policies

    Configure settings for Kaspersky applications installed on the managed devices by creating a policy for each application. The set of policies will be propagated to the client devices.

    When you configure the protection of your network in quick start wizard, Kaspersky Security Center Cloud Console creates the default policy for Kaspersky Endpoint Security for Windows. If you completed the configuration process by using this wizard, you do not have to create a new policy for this application. Proceed to the manual setup of Kaspersky Endpoint Security policy.

    If you have a hierarchical structure of several administration groups, the child administration groups inherit the policies from the primary Administration Server by default. You can force the inheritance by the child groups to prohibit any modifications of the settings configured in the upstream policy. If you want only part of the settings to be forcibly inherited, you can lock them in the upstream policy. The remaining unlocked settings will be available for modification in the downstream policies. The created hierarchy of policies will allow you to effectively manage devices in the administration groups.

    How-to instructions: Creating a policy

  2. Creating policy profiles (optional)

    If you want devices within a single administration group to run under different policy settings, create policy profiles for those devices. A policy profile is a named subset of policy settings. This subset is distributed on target devices together with the policy, supplementing it under a specific condition called the profile activation condition. Profiles only contain settings that differ from the "basic" policy, which is active on the managed device.

    By using profile activation conditions, you can apply different policy profiles, for example, to the devices located in a specific unit or security group of Active Directory, having a specific hardware configuration, or marked with specific tags. Use tags to filter devices that meet specific criteria. For example, you can create a tag called Windows, mark all devices running Windows operating system with this tag, and then specify this tag as an activation condition for a policy profile. As a result, Kaspersky applications installed on all devices running Windows will be managed by their own policy profile.

    How-to instructions:

  3. Propagating policies and policy profiles to the managed devices

    Kaspersky Security Center Cloud Console automatically synchronizes the Administration Server with the managed devices several times per hour. During the synchronization, the new or changed policies and policy profiles are propagated to the managed devices. You can circumvent auto-synchronization and run the synchronization manually by using the Force synchronization command. When synchronization is complete, the policies and policy profiles are delivered and applied to the installed Kaspersky applications.

    You can check whether the policies and policy profiles were delivered to a device. Kaspersky Security Center Cloud Console specifies the delivery date and time in the properties of the device.

    How-to instructions: Forced synchronization

Results

When the device-centric scenario is complete, the Kaspersky applications are configured according to the settings specified and propagated through the hierarchy of policies.

The configured application policies and policy profiles will be applied automatically to the new devices added to the administration groups.

See also:

Initial configuration of Kaspersky Security Center Cloud Console

Hierarchy of Administration Servers

Administration groups

Policies

Policy profiles

About user roles

Scenario: Configuring network protection

Page top

[Topic 177180]

Policy setup and propagation: User-centric approach

This section describes the scenario of user-centric approach to the centralized configuration of Kaspersky applications installed on the managed devices. When you complete this scenario, the applications will be configured on all of the managed devices in accordance with the application policies and policy profiles that you define.

You might also want to consider device-centric security management as an alternative or additional option to the user-centric approach. Learn more about two management approaches.

Process

The scenario of user-centric management of Kaspersky applications consists of the following steps:

  1. Configuring application policies

    Configure settings for Kaspersky applications installed on the managed devices by creating a policy for each application. The set of policies will be propagated to the client devices.

    When you configure the protection of your network in quick start wizard, Kaspersky Security Center Cloud Console creates the default policy for Kaspersky Endpoint Security. If you completed the configuration process by using this wizard, you do not have to create a new policy for this application. Proceed to the manual setup of Kaspersky Endpoint Security policy.

    If you have a hierarchical structure of several administration groups, the child administration groups inherit the policies from the primary Administration Server by default. You can force the inheritance by the child groups to prohibit any modifications of the settings configured in the upstream policy. If you want only part of the settings to be forcibly inherited, you can lock them in the upstream policy. The remaining unlocked settings will be available for modification in the downstream policies. The created hierarchy of policies will allow you to effectively manage devices in the administration groups.

    How-to instructions: Creating a policy

  2. Specifying owners of the devices

    Assign the managed devices to the corresponding users.

    How-to instructions: Assigning a user as a device owner

  3. Defining user roles typical for your enterprise

    Think about different kinds of work that the employees of your enterprise typically perform. You must divide all employees in accordance with their roles. For example, you can divide them by departments, professions, or positions. After that you will need to create a user role for each group. Keep in mind that each user role will have its own policy profile containing application settings specific for this role.

  4. Creating user roles

    Create and configure a user role for each group of employees that you defined at the previous step or use the predefined user roles. The user roles will contain set of rights of access to the application features.

    How-to instructions: Creating a user role

  5. Defining the scope of each user role

    For each of the created user roles, define users and/or security groups and administration groups. Settings associated with a user role apply only to devices that belong to users who have this role, and only if these devices belong to groups associated with this role, including child groups.

    How-to instructions: Editing the scope of a user role

  6. Creating policy profiles

    Create a policy profile for each user role in your enterprise. The policy profiles define which settings will be applied to the applications installed on users' devices depending on the role of each user.

    How-to instructions: Creating a policy profile

  7. Associating policy profiles with the user roles

    Associate the created policy profiles with the user roles. After that: the policy profile becomes active for a user that has the specified role. The settings configured in the policy profile will be applied to the Kaspersky applications installed on the user's devices.

    How-to instructions: Associating policy profiles with roles

  8. Propagating policies and policy profiles to the managed devices

    Kaspersky Security Center Cloud Console automatically synchronizes the Administration Server with the managed devices several times per hour. During the synchronization, the new or changed policies and policy profiles are propagated to the managed devices. You can circumvent auto-synchronization and run the synchronization manually by using the Force synchronization command. When synchronization is complete, the policies and policy profiles are delivered and applied to the installed Kaspersky applications.

    You can check whether the policies and policy profiles were delivered to a device. Kaspersky Security Center Cloud Console specifies the delivery date and time in the properties of the device.

    How-to instructions: Forced synchronization

Results

When the user-centric scenario is complete, the Kaspersky applications are configured according to the settings specified and propagated through the hierarchy of policies and policy profiles.

For a new user, you will have to create a new account, assign the user one of the created user roles, and assign the devices to the user. The configured application policies and policy profiles will be automatically applied to the devices of this user.

See also:

Initial configuration of Kaspersky Security Center Cloud Console

Hierarchy of Administration Servers

Administration groups

Policies

Policy profiles

About user roles

Scenario: Configuring network protection

Page top

[Topic 219894]

Network Agent policy settings

Expand all | Collapse all

To configure the Network Agent policy:

  1. In the main menu, go to Assets (Devices)Policies & profiles.
  2. Click the name of the Network Agent policy.

    The properties window of the Network Agent policy opens.

See the comparison table detailing how the settings below apply depending on the type of operating system used.

General tab

On this tab you can modify the policy status and specify the inheritance of policy settings:

  • In the Policy status block, you can select one of the policy modes:
    • Active
    • Inactive

      If this option is selected, the policy becomes inactive, but it is still stored in the Policies folder. If required, the policy can be activated.

  • In the Settings inheritance settings group, you can configure the policy inheritance:
    • Inherit settings from parent policy

      If this option is enabled, the policy setting values are inherited from the upper-level group policy and, therefore, are locked.

      By default, this option is enabled.

    • Force inheritance of settings in child policies

      If this option is enabled, after policy changes are applied, the following actions will be performed:

      • The values of the policy settings will be propagated to the policies of administration subgroups, that is, to the child policies.
      • In the Settings inheritance block of the General section in the properties window of each child policy, the Inherit settings from parent policy option will be automatically enabled.

      If this option is enabled, the child policies settings are locked.

      By default, this option is disabled.

Event configuration tab

This tab allows you to configure event logging and event notification. Events are distributed according to importance level in the following sections on the Event configuration tab:

  • Functional failure
  • Warning
  • Info

In each section, the event type list shows the types of events and the default event storage term on the Administration Server (in days). Clicking the Properties button lets you specify the settings of event logging and notifications about events selected in the list. By default, common notification settings specified for the entire Administration Server are used for all event types. However, you can change specific settings for required event types.

Application settings tab

Settings

In the Settings section, you can configure the Network Agent policy:

  • Distribute files through distribution points only

    If this option is enabled, client devices receive updates through distribution points only, not directly from update servers.

    If this option is disabled, client devices can receive updates from various sources: directly from update servers and from a local or network folder.

    By default, this option is disabled.

  • Maximum size of event queue, in MB
  • Application is allowed to retrieve policy's extended data on device

    Network Agent installed on a managed device transfers information about the applied security application policy to the security application (for example, Kaspersky Endpoint Security for Windows). You can view the transferred information in the security application interface.

    Network Agent transfers the following information:

    • Time of the policy delivery to the managed device
    • Name of the active or out-of-office policy at the moment of the policy delivery to the managed device
    • Name and full path to the administration group that contained the managed device at the moment of the policy delivery to the managed device
    • List of active policy profiles

      You can use the information to ensure the correct policy is applied to the device and for troubleshooting purposes. By default, this option is disabled.

  • Protect Network Agent service against unauthorized removal or termination, and prevent changes to the settings

    When this option is enabled, after Network Agent is installed on a managed device, the component cannot be removed or reconfigured without required privileges. The Network Agent service cannot be stopped. This option has no effect on domain controllers.

    Enable this option to protect Network Agent on workstations operated with local administrator rights.

    By default, this option is disabled.

  • Use uninstallation password

    If this option is enabled, by clicking the Modify button you can specify the password for the klmover utility and Network Agent remote uninstallation.

    Note that the klmover utility is used only for moving managed devices under management of a virtual Administration Server.

    By default, this option is disabled.

Repositories

In the Repositories section, you can select the types of objects whose details will be sent from Network Agent to Administration Server. If modification of some settings in this section is prohibited by the Network Agent policy, you cannot modify these settings:

  • Details of installed applications
  • Include information about patches

    Information about patches of applications installed on client devices is sent to the Administration Server. Enabling this option may increase the load on the Administration Server and DBMS, as well as cause increased volume of the database.

    By default, this option is enabled. It is available only for Windows.

  • Details of Windows Update updates

    If this option is enabled, information about Microsoft Windows Update updates that must be installed on client devices is sent to the Administration Server.

    Sometimes, even if the option is disabled, updates are displayed in the device properties in the Available updates section. This might happen if, for example, the devices of the organization had vulnerabilities that could be fixed by these updates.

    By default, this option is enabled. It is available only for Windows.

  • Details of software vulnerabilities and corresponding updates

    If this option is enabled, information about vulnerabilities in third-party software (including Microsoft software), detected on managed devices, and about software updates to fix third-party vulnerabilities (not including Microsoft software) is sent to the Administration Server.

    Selecting this option (Details of software vulnerabilities and corresponding updates) increases the network load, Administration Server disk load, and Network Agent resource consumption.

    By default, this option is enabled. It is available only for Windows.

    To manage software updates of Microsoft software, use the Details of Windows Update updates option.

  • Hardware registry details

Software updates and vulnerabilities

In the Software updates and vulnerabilities section, you can configure search of Windows updates, as well as enable scanning of executable files for vulnerabilities. The settings in the Software updates and vulnerabilities section are available only on devices running Windows:

  • In the Windows Update search mode settings group, you can select the update search mode:
    • Active

      If this option is selected, Administration Server with support from Network Agent initiates a request from Windows Update Agent on the client device to the update source: Windows Update Servers or WSUS. Next, Network Agent passes information received from Windows Update Agent to Administration Server.

      The option takes effect only if Connect to the update server to update data option of the Find vulnerabilities and required updates task is selected.

      By default, this option is selected.

    • Passive

      If you select this option, Network Agent periodically passes Administration Server information about updates retrieved at the last synchronization of Windows Update Agent with the update source. If no synchronization of Windows Update Agent with an update source is performed, information about updates on Administration Server becomes out-of-date.

      Select this option if you want to get updates from the memory cache of the update source.

    • Disabled

      If this option is selected, Administration Server does not request any information about updates.

      Select this option if, for example, you want to test the updates on your local device first.

  • Scan executable files for vulnerabilities when running them

    If this option is enabled, executable files are scanned for vulnerabilities when they are run.

    By default, this option is disabled.

Restart management

In the Restart management section, you can specify the action to be performed if the operating system of a managed device has to be restarted for correct use, installation, or uninstallation of an application:

  • Do not restart the operating system

    Client devices are not restarted automatically after the operation. To complete the operation, you must restart a device (for example, manually or through a device management task). Information about the required restart is saved in the task results and in the device status. This option is suitable for tasks on servers and other devices where continuous operation is critical.

  • Restart the operating system automatically, if necessary

    Client devices are always restarted automatically if a restart is required for completion of the operation. This option is useful for tasks on devices that provide for regular pauses in their operation (shutdown or restart).

  • Prompt user for action

    The restart reminder is displayed on the screen of the client device, prompting the user to restart it manually. Some advanced settings can be defined for this option: text of the message for the user, the message display frequency, and the time interval after which a restart will be forced (without the user's confirmation). This option is most suitable for workstations where users must be able to select the most convenient time for a restart.

    By default, this option is selected.

    • Repeat the prompt every (min)

      If this option is enabled, the application prompts the user to restart the operating system with the specified frequency.

      By default, this option is enabled. The default interval is 5 minutes. Available values are between 1 and 1440 minutes.

      If this option is disabled, the prompt is displayed only once.

    • Force restart after (min)

      After prompting the user, the application forces restart of the operating system upon expiration of the specified time interval.

      By default, this option is enabled. The default delay is 30 minutes. Available values are between 1 and 1440 minutes.

  • Force closure of applications in blocked sessions

    Running applications may prevent a restart of the client device. For example, if a document is being edited in a word processing application and is not saved, the application does not allow the device to restart.

    If this option is enabled, such applications on a locked device are forced to close before the device restart. As a result, users may lose their unsaved changes.

    If this option is disabled, a locked device is not restarted. The task status on this device states that a device restart is required. Users have to manually close all applications running on locked devices and restart these devices.

    By default, this option is disabled.

Windows Desktop Sharing

In the Windows Desktop Sharing section, you can enable and configure the audit of the administrator's actions performed on a remote device when desktop access is shared. The settings in the Windows Desktop Sharing section are available only on devices running Windows:

  • Enable audit

    If this option is enabled, audit of the administrator's actions is enabled on the remote device. Records of the administrator's actions on the remote device are logged:

    • In the event log on the remote device
    • In a file with the syslog extension located in the Network Agent installation folder on the remote device
    • In the event database of Kaspersky Security Center Cloud Console

    Audit of the administrator's actions is available when the following conditions are met:

    • The Vulnerability and patch management license is in use
    • The administrator has the right to start shared access to the desktop of the remote device

    If this option is disabled, the audit of the administrator's actions is disabled on the remote device.

    By default, this option is disabled.

  • Masks of files to monitor when read

    The list contains file masks. When the audit is enabled, the application monitors the administrator's reading files that match the masks and saves information about files read. The list is available if the Enable audit check box is selected. You can edit file masks and add new ones to the list. Each new file mask should be specified in the list on a new line.

    By default, the following file masks are specified:*.txt, *.rtf, *.doc, *.xls, *.docx, *.xlsx, *.odt, *.pdf.

  • Masks of files to monitor when modified

    The list contains masks of files on the remote device. When audit is enabled, the application monitors changes made by the administrator in files that match masks, and saves information about those modifications. The list is available if the Enable audit check box is selected. You can edit file masks and add new ones to the list. Each new file mask should be specified in the list on a new line.

    By default, the following file masks are specified:*.txt, *.rtf, *.doc, *.xls, *.docx, *.xlsx, *.odt, *.pdf.

Manage patches and updates

In the Manage patches and updates section, you can configure download and distribution of updates, as well as installation of patches, on managed devices: enable or disable the Automatically install applicable updates and patches for components that have the Undefined status option.

Connectivity

The Connectivity section includes three subsections:

  • Network
  • Connection profiles
  • Connection schedule

In the Network subsection, you can configure the connection to Administration Server, enable the use of a UDP port, and specify the UDP port number.

  • In the Connection to Administration Server settings group, you can specify the following settings:
  • Use UDP port

    If you need Network Agent to connect to Administration Server through a UDP port, enable the Use UDP port option and specify a UDP port number. By default, this option is enabled. The default UDP port to connect to Administration Server is 15000.

  • UDP port number

    In this field you can enter the UDP port number. The default port number is 15000.

    The decimal system is used for records.

    If the client device runs Windows XP Service Pack 2, the integrated firewall blocks UDP port 15000. This port should be opened manually.

  • Use the distribution point to force a connection to Administration Server

    Select this option if you selected the Run push server option in the distribution point settings window. Otherwise, the distribution point will not act as a push server.

In the Connection profiles subsection, no new items can be added to the Administration Server connection profiles list so the Add button is inactive. The preset connection profiles cannot be modified, either.

In the Connection schedule subsection, you can specify the time intervals during which Network Agent sends data to the Administration Server:

  • Connect when necessary
  • Connect at specified time intervals

In the Connection schedule subsection, you can specify the time intervals during which Network Agent sends data to the Administration Server:

  • Connect when necessary

    If this option is selected, the connection is established when Network Agent has to send data to the Administration Server.

    By default, this option is selected.

  • Connect at specified time intervals

    If this option is selected, Network Agent connects to the Administration Server at a specified time. You can add several connection time periods.

Network polling by distribution points

In the Network polling by distribution points section, you can configure automatic polling of the network. The polling settings are available only on devices running Windows. You can use the following options to enable the polling and set its frequency:

  • Windows network

    If this option is enabled, the distribution point automatically polls the network according to the schedule configured by clicking the Set quick polling schedule and Set full polling schedule links.

    If this option is disabled, the Administration Server does not poll the network.

    By default, this option is enabled.

  • IP ranges

    If this option is enabled, the distribution point automatically polls IP ranges according to the schedule configured by clicking the Set polling schedule link.

    If this option is disabled, the distribution point does not poll IP ranges.

    By default, this option is disabled.

  • Domain controllers

    If the option is enabled, the distribution point automatically polls domain controllers according to the schedule that you configured by clicking the Set polling schedule button.

    If this option is disabled, the distribution point does not poll domain controllers.

    The frequency of domain controller polling for Network Agent versions prior to 10.2 can be configured in the Poll interval (min) field. The field is available if this option is enabled.

    By default, this option is disabled.

Network settings for distribution points

In the Network settings for distribution points section, you can specify the internet access settings:

  • Use proxy server
  • Address
  • Port number
  • Bypass proxy server for local addresses

    If this option is enabled, no proxy server is used to connect to devices on the local network.

    By default, this option is disabled.

  • Proxy server authentication

    If this check box is selected, in the entry fields you can specify the credentials for proxy server authentication.

    By default, this check box is cleared.

  • User name
  • Password

KSN Proxy (distribution points)

In the KSN Proxy (distribution points) section, you can configure the application to use the distribution point to forward KSN requests from the managed devices:

  • Enable KSN Proxy on the distribution point side

    The KSN proxy service is run on the device that is used as a distribution point. Use this feature to redistribute and optimize traffic on the network.

    This feature is not supported by distribution point devices running Linux or macOS.

    The distribution point sends the KSN statistics, which are listed in the Kaspersky Security Network statement, to Kaspersky. By default, the KSN statement is located in %ProgramFiles%\Kaspersky Lab\Kaspersky Security Center\ksneula.

    By default, this option is disabled. Enabling this option takes effect only if the I agree to use Kaspersky Security Network option is enabled in the Administration Server properties window.

    You can assign a node of an active-passive cluster to a distribution point and enable KSN proxy server on this node.

  • Port

    The number of the TCP port that the managed devices will use to connect to KSN proxy server. The default port number is 13111.

  • UDP port

    If you need Network Agent to connect to Administration Server through a UDP port, enable the Use UDP port option and specify a UDP port number. By default, this option is enabled. The default UDP port to connect to Administration Server is 15000.

See also:

Ports used by Kaspersky Security Center Cloud Console

Scenario: Kaspersky applications initial deployment

Page top

[Topic 238367]

Comparison of Network Agent policy settings by operating systems

The table below shows which Network Agent policy settings you can use to configure Network Agent with a specific operating system.

Network Agent policy settings: comparison by operating systems

Policy section

Windows

macOS

Linux

General

Yes.

Yes.

Yes.

Event configuration

Yes.

Yes.

Yes.

Settings

Yes.

Yes.

Except the Use uninstallation password check box.

Yes.

Except the Use uninstallation password check box.

Repositories

Yes.

Yes.

The Hardware registry details option is available.

Yes.

The following options are available:

  • Details of installed applications
  • Hardware registry details

Software updates and vulnerabilities

Yes.

No.

No.

Restart management

Yes.

No.

No.

Windows Desktop Sharing

Yes.

No.

No.

Manage patches and updates

Yes.

No.

No.

ConnectivityNetwork

Yes.

Yes.

Except the Open Network Agent ports in Microsoft Windows Firewall check box.

Yes.

Except the Open Network Agent ports in Microsoft Windows Firewall check box.

ConnectivityConnection schedule

Yes.

Yes.

Yes.

Network polling by distribution points

Yes.

The following options are available:

  • Windows network
  • IP ranges
  • Domain controllers (Microsoft Active Directory)

No.

Yes.

The following options are available:

  • IP ranges
  • Domain controllers (Microsoft Active Directory, Samba as an Active Directory)

Network settings for distribution points

Yes.

Yes.

Yes.

KSN Proxy (distribution points)

Yes.

No.

Yes.

See also:

Usage of Network Agent for Windows, Linux, and macOS: Comparison

Page top

[Topic 179912]

Manual setup of the Kaspersky Endpoint Security policy

This section provides recommendations on how to configure the Kaspersky Endpoint Security policy. You can perform setup in the policy properties window. When you edit a setting, click the lock icon to the right of the relevant group of settings to apply the specified values to a workstation.

In this section

Configuring Kaspersky Security Network

Checking the list of the networks protected by Firewall

Excluding software details from the Administration Server memory

Saving important policy events in the Administration Server database

See also:

Scenario: Configuring network protection

Page top

[Topic 181226]

Configuring Kaspersky Security Network

Kaspersky Security Network (KSN) is the infrastructure of cloud services that has information about the reputation of files, web resources, and software. Kaspersky Security Network enables Kaspersky Endpoint Security for Windows to respond faster to different kinds of threats, enhances the performance of the protection components, and decreases the likelihood of false positives. For more information about Kaspersky Security Network, see the Kaspersky Endpoint Security for Windows Help.

You can configure the Kaspersky Security Network work in the policy properties window of Kaspersky Endpoint Security for Windows, in the Application settingsAdvanced Threat Protection section.

To specify recommended KSN settings:

  1. In the main menu, go to Assets (Devices) → Policies & profiles.
  2. Click the policy of Kaspersky Endpoint Security for Windows.

    The properties window of the selected policy opens.

  3. In the policy properties, go to Application settingsAdvanced Threat ProtectionKaspersky Security Network.
  4. Make sure that the Use Administration Server as a KSN proxy server option is enabled. Using this option helps to redistribute and optimize traffic on the network.

    If you use Managed Detection and Response, you must enable Kaspersky Security Network option for the distribution point and enable extended KSN mode.

  5. Enable use of KSN servers if the KSN proxy service is not available. To do this, enable the Use Kaspersky Security Network servers if the KSN proxy server is unavailable option.

    KSN servers may be located either on the side of Kaspersky (when KSN is used) or on the side of third parties (when KPSN is used).

  6. Click OK.

The recommended KSN settings are specified.

See also:

Scenario: Configuring network protection

Page top

[Topic 179919]

Checking the list of the networks protected by Firewall

Make sure that Kaspersky Endpoint Security for Windows Firewall protects all your networks. By default, Firewall protects networks with the following types of connection:

  • Public network. Security applications, firewalls, or filters do not protect devices in such a network.
  • Local network. Access to files and printers is restricted for devices in this network.
  • Trusted network. Devices in such a network are protected from attacks and unauthorized access to files and data.

If you configured a custom network, make sure that Firewall protects it. For this purpose, check the list of the networks in the Kaspersky Endpoint Security for Windows policy properties. The list may not contain all the networks.

For more information about Firewall, see the Kaspersky Endpoint Security for Windows Help.

To check the list of networks:

  1. In the main menu, go to Assets (Devices) Policies & profiles.
  2. Click the policy of Kaspersky Endpoint Security for Windows.

    The properties window of the selected policy opens.

  3. In the policy properties, go to Application settingsEssential Threat ProtectionFirewall.
  4. Under Available networks, click the Network settings link.

    The Network connections window opens. This window displays the list of networks.

  5. If the list has a missing network, add it.

See also:

Scenario: Configuring network protection

Page top

[Topic 179923]

Excluding software details from the Administration Server memory

We recommend that Administration Server does not save information about software modules that are started on the network devices. As a result, the Administration Server memory does not overrun.

You can disable saving this information in the Kaspersky Endpoint Security for Windows policy properties.

To disable saving information about installed software modules:

  1. In the main menu, go to Assets (Devices) → Policies & profiles.
  2. Click the policy of Kaspersky Endpoint Security for Windows.

    The properties window of the selected policy opens.

  3. In the policy properties, go to Application settingsGeneral SettingsReports and Storage.
  4. Under Data transfer to Administration Server, disable the About started applications check box if it is still enabled in the top-level policy.

    When this check box is selected, the Administration Server database saves information about all versions of all software modules on the networked devices. This information may require a significant amount of disk space in the Kaspersky Security Center Cloud Console database (dozens of gigabytes).

The information about installed software modules is no longer saved to the Administration Server database.

See also:

Scenario: Configuring network protection

Page top

[Topic 181227]

Saving important policy events in the Administration Server database

To avoid the Administration Server database overflow, we recommend that you save only important events to the database.

To configure registration of important events in the Administration Server database:

  1. In the main menu, go to Assets (Devices) → Policies & profiles.
  2. Click the policy of Kaspersky Endpoint Security for Windows.

    The properties window of the selected policy opens.

  3. In the policy properties, open the Event configuration tab.
  4. In the Critical section, click Add event and select check boxes next to the following events only:
    • End User License Agreement violated
    • Application autorun is disabled
    • Activation error
    • Active threat detected. Advanced Disinfection should be started
    • Disinfection impossible
    • Previously opened dangerous link detected
    • Process terminated
    • Network activity blocked
    • Network attack detected
    • Application startup prohibited
    • Access denied (local bases)
    • Access denied (KSN)
    • Local update error
    • Cannot start two tasks at the same time
    • Error in interaction with Kaspersky Security Center
    • Not all components were updated
    • Error applying file encryption / decryption rules
    • Error enabling portable mode
    • Error disabling portable mode
    • Could not load encryption module
    • Policy cannot be applied
    • Error changing application components
  5. Click OK.
  6. In the Functional failure section, click Add event and select check box next to the event Invalid task settings. Settings not applied.
  7. Click OK.
  8. In the Warning section, click Add event and select check boxes next to the following events only:
    • Self-Defense is disabled
    • Protection components are disabled
    • Incorrect reserve key
    • Legitimate software that can be used by intruders to damage your computer or personal data was detected (local bases)
    • Legitimate software that can be used by intruders to damage your computer or personal data was detected (KSN)
    • Object deleted
    • Object disinfected
    • User has opted out of the encryption policy
    • File was restored from quarantine on the Kaspersky Anti Targeted Attack Platform server by the administrator
    • File was quarantined on the Kaspersky Anti Targeted Attack Platform server by the administrator
    • Application startup blockage message to administrator
    • Device access blockage message to administrator
    • Web page access blockage message to administrator
  9. Click OK.
  10. In the Info section, click Add event and select check boxes next to the following events only:
    • A backup copy of the object was created
    • Application startup prohibited in test mode
  11. Click OK.

Registration of important events in the Administration Server database is configured.

See also:

Scenario: Configuring network protection

Page top

[Topic 180029]

Manual setup of the group update task for Kaspersky Endpoint Security

The optimal and recommended schedule option for Kaspersky Endpoint Security is When new updates are downloaded to the repository when the Use automatically randomized delay for task starts check box is selected.

See also:

Scenario: Configuring network protection

Page top

[Topic 165846]

About tasks

Kaspersky Security Center Cloud Console manages Kaspersky security applications installed on devices by creating and running tasks. Tasks are required for installing, launching, and stopping applications, scanning files, updating databases and software modules, and performing other actions on applications. Tasks can be performed on the Administration Server and on devices.

The following types of tasks are performed on devices:

  • Local tasks—Tasks that are performed on a specific device

    Local tasks can be modified either by the administrator, who uses administration tools, or by the user of a remote device (for example, through the security application interface). If a local task has been modified simultaneously by the administrator and the user of a managed device, the changes made by the administrator will take effect because they have a higher priority.

  • Group tasks—Tasks that are performed on all devices of a specific group

    Unless otherwise specified in the task properties, a group task also affects all subgroups of the selected group.

  • Global tasks—Tasks that are performed on a set of devices, regardless of whether they are included in any group

For each application, you can create multiple group tasks, global tasks, or local tasks.

You can make changes to the settings of tasks, view the progress of tasks, and copy, export, import, and delete tasks.

A task is started on a device only if the application for which the task was created is running.

Execution results of tasks are saved in the OS event log on each device and in the Administration Server database.

Do not include private data in task settings. For example, avoid specifying the domain administrator password.

See also:

Tasks

Scenario: Migration without a hierarchy of Administration Servers

Scenario: Configuring network protection

Page top

[Topic 175792]

About task scope

The scope of a task is the set of devices on which the task is performed. The types of scope are as follows:

  • For a local task, the scope is the device itself.
  • For an Administration Server task, the scope is the Administration Server.
  • For a group task, the scope is the list of devices included in the group.

When creating a global task, you can use the following methods to specify its scope:

  • Specifying certain devices manually.

    You can use an IP address (or IP range), NetBIOS name, or DNS name as the device address.

  • Importing a list of devices from a TXT file with the device addresses to be added (each address must be placed on an individual line).

    If you import a list of devices from a file or create a list manually, and if devices are identified by their names, the list can only contain devices for which information has already been entered into the Administration Server database. Moreover, the information must have been entered when those devices were connected or during device discovery.

  • Specifying a device selection.

    Over time, the scope of a task changes as the set of devices included in the selection change. A selection of devices can be made on the basis of device attributes, including software installed on a device, and on the basis of tags assigned to devices. Device selection is the most flexible way to specify the scope of a task.

    Tasks for device selections are always run on a schedule by the Administration Server. These tasks cannot be run on devices that lack connection to the Administration Server. Tasks whose scope is specified by using other methods are run directly on devices and therefore do not depend on the device connection to the Administration Server.

Tasks for device selections are not run on the local time of a device; instead, they are run on the local time of the Administration Server. Tasks whose scope is specified by using other methods are run on the local time of a device.

See also:

Tasks

Page top

[Topic 175983]

Creating a task

You can create a task in the task list. Alternatively, you can select devices in the Managed devices list, and then create a new task assigned to the selected devices.

To create a task in the task list:

  1. In the main menu, go to Assets (Devices) Tasks.
  2. Click Add.

    The New task wizard starts. Follow its instructions.

  3. If you want to modify the default task settings, enable the Open task details when creation is complete option on the Finish task creation page. If you do not enable this option, the task is created with the default settings. You can modify the default settings later, at any time.
  4. Click the Finish button.

The task is created and displayed in the list of tasks.

To create a new task assigned to the selected devices:

In the main menu, go to Assets (Devices) → Managed devices.

The list of managed devices is displayed.

  1. In the list of managed devices, select the check boxes next to the devices to run the task for them. You can use the search and filter functions to find the devices you're looking for.
  2. Click the Run task button, and then select Create new task.

    The New task wizard starts.

    On the first step of the wizard, you can remove the devices selected to include in the task scope. Follow the wizard instructions.

  3. Click the Finish button.

The task is created for the selected devices.

See also:

Tasks

General task settings and properties

Scenario: Kaspersky applications initial deployment

Scenario: Monitoring and reporting

Scenario: Configuring network protection

Page top

[Topic 190998]

Viewing the task list

You can view the list of tasks that are created in Kaspersky Security Center Cloud Console.

To view the list of tasks,

In the main menu, go to Assets (Devices) → Tasks.

The list of tasks is displayed. The tasks are grouped by the names of applications to which they are related. For example, the Uninstall application remotely task is related to the Administration Server, and the Find vulnerabilities and required updates task refers to the Network Agent.

To view properties of a task,

Click the name of the task.

The task properties window is displayed with several named tabs. For example, the Task type is displayed on the General tab, and the task schedule—on the Schedule tab.

See also:

Tasks

Scenario: Configuring network protection

Scenario: Finding and fixing software vulnerabilities

Page top

[Topic 189265]

Starting a task manually

The application starts tasks according to the schedule settings specified in the properties of each task. You can start a task manually at any time from the task list. Alternatively, you can select devices in the Managed devices list, and then start an existing task for them.

To start a task manually:

  1. In the main menu, go to Assets (Devices) → Tasks.
  2. In the task list, select the check box next to the task that you want to start.
  3. Click the Start button.

The task starts. You can check the task status in the Status column or by clicking the Result button.

See also:

Starting a task for selected devices

About tasks

Creating a task

General task settings and properties

Scenario: Configuring network protection

Page top

[Topic 270572]

Starting a task for selected devices

You can select one or more client devices in the list of devices, and then launch a previously created task for them. This allows you to run tasks created earlier for a specific set of devices.

This changes the devices to which the task was assigned to the list of devices that you select when you run the task.

To start a task for selected devices:

  1. In the main menu, go to Assets (Devices) → Managed devices. The list of managed devices is displayed.

    In the list of managed devices, use the check boxes to select the devices to run the task for them. You can use the search and filter functions to find the devices you're looking for.

  2. Click the Run task button, and then select Apply existing task.

    The list of the existing tasks is displayed.
  3. The selected devices are displayed above the task list. If necessary, you can remove a device from this list. You can delete all but one device.
  4. Select the desired task in the list. You can use the search box above the list to search for the desired task by name. Only one task can be selected.
  5. Click Save and start task.

The selected task is immediately started for the selected devices. The scheduled start settings in the task are not changed.

See also:

General task settings and properties

Page top

[Topic 182650]

General task settings and properties

Expand all | Collapse all

This section contains the settings that you can view and configure for most of your tasks. The list of settings available depends on the task you are configuring.

Settings specified during task creation

You can specify the following settings when creating a task. Some of these settings can also be modified in the properties of the created task.

  • Devices to which the task will be assigned:
    • Assign task to an administration group

      The task is assigned to devices included in an administration group. You can specify one of the existing groups or create a new one.

      For example, you may want to use this option to run a task of sending a message to users if the message is specific for devices included in a specific administration group.

      If a task is assigned to an administration group, the Security tab is not displayed in the task properties window because group tasks are subject to the security settings of the groups to which they apply.

    • Specify device addresses manually or import addresses from a list

      The task is assigned to specific devices. You can specify devices by one of the following methods:

      • Specify the IP address, NetBIOS name, or DNS name of the device.
      • Specify the IP range.

        You may want to use this option to execute a task for a specific subnet. For example, you may want to install a certain application on devices of accountants or to scan devices in a subnet that is probably infected.

      • Select devices detected by the Administration Server, including unassigned devices.

        For example, you may want to use this option in a task of installing Network Agent on unassigned devices.

    • Assign task to a device selection

      The task is assigned to devices included in a device selection. You can specify one of the existing selections.

      For example, you may want to use this option to run a task on devices with a specific operating system version.

  • Account settings:
    • Default account

      The task will be run under the same account as the application that performs this task.

      By default, this option is selected.

    • Specify account

      Fill in the Account and Password fields to specify the details of an account under which the task is run. The account must have sufficient rights for this task.

  • Operating system restart settings:
    • Do not restart

      Client devices are not restarted automatically after the operation. To complete the operation, you must restart a device (for example, manually or through a device management task). Information about the required restart is saved in the task results and in the device status. This option is suitable for tasks on servers and other devices where continuous operation is critical.

    • Restart the device

      Client devices are always restarted automatically if a restart is required for completion of the operation. This option is useful for tasks on devices that provide for regular pauses in their operation (shutdown or restart).

    • Prompt user for action

      The restart reminder is displayed on the screen of the client device, prompting the user to restart it manually. Some advanced settings can be defined for this option: text of the message for the user, the message display frequency, and the time interval after which a restart will be forced (without the user's confirmation). This option is most suitable for workstations where users must be able to select the most convenient time for a restart.

      By default, this option is selected.

    • Repeat prompt every (min)

      If this option is enabled, the application prompts the user to restart the operating system with the specified frequency.

      By default, this option is enabled. The default interval is 5 minutes. Available values are between 1 and 1440 minutes.

      If this option is disabled, the prompt is displayed only once.

    • Restart after (min)

      After prompting the user, the application forces restart of the operating system upon expiration of the specified time interval.

      By default, this option is enabled. The default delay is 30 minutes. Available values are between 1 and 1440 minutes.

    • Force closure of applications in blocked sessions

      Running applications may prevent a restart of the client device. For example, if a document is being edited in a word processing application and is not saved, the application does not allow the device to restart.

      If this option is enabled, such applications on a locked device are forced to close before the device restart. As a result, users may lose their unsaved changes.

      If this option is disabled, a locked device is not restarted. The task status on this device states that a device restart is required. Users have to manually close all applications running on locked devices and restart these devices.

      By default, this option is disabled.

Settings specified after task creation

You can specify the following settings only after a task is created.

  • Group task settings:
    • Distribute to subgroups

      This option is only available in the settings of the group tasks.

      When this option is enabled, the task scope includes:

      • The administration group that you selected while creating the task.
      • The administration groups subordinate to the selected administration group at any level down by the group hierarchy.

      When this option is disabled, the task scope includes only the administration group that you selected while creating the task.

      By default, this option is enabled.

    • Distribute to secondary and virtual Administration Servers

      When this option is enabled, the task that is effective on the primary Administration Server is also applied on the secondary Administration Servers (including virtual ones). If a task of the same type already exists on the secondary Administration Server, both tasks are applied on the secondary Administration Server—the existing one and the one that is inherited from the primary Administration Server.

      This option is only available when the Distribute to subgroups option is enabled.

      By default, this option is disabled.

  • Task scheduling settings:
    • Start task setting:
      • Manually

        The task does not run automatically. You can only start it manually.

        By default, this option is selected.

      • Once

        The task runs once, on the specified date and time (by default, on the day when the task was created).

      • Immediately

        The task runs immediately after its settings are saved.

      • Every N minutes

        The task runs regularly, with the specified interval in minutes, starting from the specified time on the day that the task is created.

        By default, the task runs every 30 minutes, starting from the current system time.

      • Every N hours

        The task runs regularly, with the specified interval in hours, starting from the specified date and time.

        By default, the task runs every 6 hours, starting from the current system date and time.

      • Every N days

        The task runs regularly, with the specified interval in days. Additionally, you can specify a date and time of the first task run. These additional options become available, if they are supported by the application for which you create the task.

        By default, the task runs every day, starting from the current system date and time.

      • By days of week

        The task runs regularly, on the specified days of the week, at the specified time.

        By default, the task runs every Friday at 6:00:00 PM.

      • Monthly

        The task runs regularly, on the specified day of the month, at the specified time.

        In months that lack the specified day, the task runs on the last day.

        By default, the task runs on the first day of each month, at the current system time.

      • Every month on specified days of selected weeks

        The task runs regularly, on the specified days of each month, at the specified time.

        By default, no days of month are selected. The default start time is 18:00.

      • When new updates are downloaded to the repository

        When new updates are downloaded to the distribution point repositories, Kaspersky Security Center Cloud Console runs all tasks that have this schedule. Network Agent checks the availability of updates during periodic synchronization between the managed device and the Administration Server (the heartbeat).

        For example, you may want to use this schedule for the Update task related to a security application, such as Kaspersky Endpoint Security.

        If Network Agent on a managed device detects no new updates for 25 hours or longer, then Kaspersky Security Center Cloud Console runs on this device all tasks that have this schedule. These tasks are run every hour until new updates are detected. Kaspersky Security Center Cloud Console also runs these tasks every hour if there is no connection between the managed device and the distribution point that downloads updates to the repository.

      • On virus outbreak

        The task runs after a Virus outbreak event occurs. Select application types that will monitor virus outbreaks. The following application types are available:

        • Anti-virus for workstations and file servers
        • Anti-virus for perimeter defense
        • Anti-virus for mail systems

        By default, all application types are selected.

        You may want to run different tasks depending on the security application type that reports a virus outbreak. In this case, remove the selection of the application types that you do not need.

      • On completing another task

        The current task starts after another task completes. This parameter only works if both tasks are assigned to the same devices. For example, you may want to run the Manage devices task with the Turn on the device option and, after it completes, run the Virus scan task as a triggering task.

        You have to select the triggering task from the table and the status with which this task must complete (Completed successfully or Failed).

        If necessary, you can search, sort, and filter the tasks in the table as follows:

        • Enter the task name in the search field, to search the task by its name.
        • Click the sort icon to sort the tasks by name.

          By default, the tasks are sorted in alphabetical ascending order.

        • Click the filter icon, and in the window that opens, filter the tasks by group, and then click the Apply button.

      The scheduling settings may depend on the local time zone of the device operating system.

      Correlation between the local time zone of the device operating system and the task start time

      Task schedule

      Local time is used

      Once

      No

      Every N minutes

      No

      Every N hours

      No

      Every N days

      Yes

      By days of week

      Yes

      Monthly

      Yes

      Every month on specified days of selected weeks

      Yes

      When new updates are downloaded to the repository

      Another trigger for running the task (corresponds to the schedule name)

      On virus outbreak

      Another trigger for running the task (corresponds to the schedule name)

      On completing another task

      Another trigger for running the task (corresponds to the schedule name)

      Immediately

      Another trigger for running the task (corresponds to the schedule name)

      Manually

      Another trigger for running the task (corresponds to the schedule name)

    • Run missed tasks

      This option determines the behavior of a task if a client device is not visible on the network when the task is about to start.

      If this option is enabled, the system attempts to start the task the next time the Kaspersky application is run on the client device. If the task schedule is Manually, Once or Immediately, the task is started immediately after the device becomes visible on the network or immediately after the device is included in the task scope.

      If this option is disabled, only scheduled tasks run on client devices. For Manually, Once and Immediately schedule, tasks run only on those client devices that are visible on the network. For example, you may want to disable this option for a resource-consuming task that you want to run only outside of business hours.

      By default, this option is disabled.

    • Use automatically randomized delay for task starts

      If this option is enabled, the task is started on client devices randomly within a specified time interval, that is, distributed task start. A distributed task start helps to avoid a large number of simultaneous requests by client devices to the Administration Server when a scheduled task is running.

      The distributed start time is calculated automatically when a task is created, depending on the number of client devices to which the task is assigned. Later, the task is always started on the calculated start time. However, when task settings are edited or the task is started manually, the calculated value of the task start time changes.

      If this option is disabled, the task starts on client devices according to the schedule.

    • Use automatically randomized delay for task starts within an interval of

      If this option is enabled, the task is started on client devices randomly within the specified time interval. A distributed task start helps to avoid a large number of simultaneous requests by client devices to the Administration Server when a scheduled task is running.

      If this option is disabled, the task starts on client devices according to the schedule.

      By default, this option is disabled. The default time interval is one minute.

    • Turn on devices by using the Wake-on-LAN function before starting the task

      The operating system on the device starts at the specified time before the task is started. The default time period is five minutes.

      Enable this option if you want the task to run on all of the client devices from the task scope, including those devices that are turned off when the task is about to start.

      If you want the device to be automatically turned off after the task is completed, enable the Shut down the devices after completing the task option. This option can be found in the same window.

      By default, this option is disabled.

    • Shut down the devices after completing the task

      For example, you may want to enable this option for an install update task that installs updates to client devices each Friday after business hours, and then turns off these devices for the weekend.

      By default, this option is disabled.

    • Stop the task if it runs longer than

      After the specified time period expires, the task is stopped automatically, whether it is completed or not.

      Enable this option if you want to interrupt (or stop) tasks that take too long to execute.

      By default, this option is disabled. The default task execution time is 120 minutes.

  • Notifications:
    • Store task history block:
      • Save all events
      • Save events related to task progress
      • Save only task execution results
      • Store in the Administration Server database for (days)

        Application events related to execution of the task on all client devices from the task scope are stored on the Administration Server during the specified number of days. When this period elapses, the information is deleted from the Administration Server.

        By default, this option is enabled.

      • Store in the OS event log on device

        Application events related to execution of the task are stored locally in Windows Event Log of each client device.

        By default, this option is disabled.

    • Notify of errors only
    • Notify by email
  • Task scope settings
  • Exclusions from scope

    You can specify groups of devices to which the task is not applied. Groups to be excluded can only be subgroups of the administration group to which the task is applied.

  • Revision history

See also:

Tasks

Scenario: Configuring network protection

Page top

[Topic 240599]

Exporting a task

Kaspersky Security Center Cloud Console allows you to save a task and its settings to a KLT file. You can use this KLT file to import the saved task both to Kaspersky Security Center Windows and Kaspersky Security Center Linux.

To export a task:

  1. In the main menu, go to Assets (Devices) Tasks.
  2. Select the check box next to the task that you want to export.

    You cannot export multiple tasks at the same time. If you select more than one task, the Export button will be disabled. Administration Server tasks are also unavailable for export.

  3. Click the Export button.
  4. In the opened Save as window, specify the task file name and path. Click the Save button.

    The Save as window is displayed only if you use Google Chrome, Microsoft Edge, or Opera. If you use another browser, the task file is automatically saved in the Downloads folder.

Page top

[Topic 240815]

Importing a task

Expand all | Collapse all

Kaspersky Security Center Cloud Console allows you to import a task from a KLT file. The KLT file contains the exported task and its settings.

To import a task:

  1. In the main menu, go to Assets (Devices) → Tasks.
  2. Click the Import button.
  3. Click the Browse button to choose a task file that you want to import.
  4. In the opened window, specify the path to the KLT task file, and then click the Open button. Note that you can select only one task file.

    The task processing starts.

  5. After the task is processed successfully, select the devices to which you want to assign the task. To do this, select one of the following options:
    • Assign task to an administration group

      The task is assigned to devices included in an administration group. You can specify one of the existing groups or create a new one.

      For example, you may want to use this option to run a task of sending a message to users if the message is specific for devices included in a specific administration group.

      If a task is assigned to an administration group, the Security tab is not displayed in the task properties window because group tasks are subject to the security settings of the groups to which they apply.

    • Specify device addresses manually or import addresses from a list

      You can specify NetBIOS names, DNS names, IP addresses, and IP subnets of devices to which you want to assign the task.

      You may want to use this option to execute a task for a specific subnet. For example, you may want to install a certain application on devices of accountants or to scan devices in a subnet that is probably infected.

    • Assign task to a device selection

      The task is assigned to devices included in a device selection. You can specify one of the existing selections.

      For example, you may want to use this option to run a task on devices with a specific operating system version.

  6. Specify the task scope.
  7. Click the Complete button to finish the task import.

The notification with the import results appears. If the task is imported successfully, you can click the Details link to view the task properties.

After a successful import, the task is displayed in the task list. The task settings and schedule are also imported. The task will be started according to its schedule.

If the newly imported task has an identical name to an existing task, the name of the imported task is expanded with the (<next sequence number>) index, for example: (1), (2).

Page top

[Topic 3794]

Viewing task run results stored on the Administration Server

Kaspersky Security Center Cloud Console allows you to view the results for group tasks, tasks for specific devices, and Administration Server tasks.

To view the task results:

  1. In the task properties window, select the General section.
  2. Click the Results link to open the Task results window.

See also:

Scenario: Configuring network protection

Page top

[Topic 177914]

Managing client devices

Kaspersky Security Center Cloud Console allows you to manage client devices:

You can use administration groups to combine client devices in a set that can be managed as a single unit. A client device can be included in only one administration group. Devices can be allocated to a group automatically based on Rule conditions:

You can use device selections to filter devices based on a condition. You can also tag devices for creating selections, for finding devices, and for distributing devices among administration groups.

In this section

Settings of a managed device

Device selections

Viewing and configuring the actions when devices show inactivity

About device statuses

Configuring the switching of device statuses

Changing the Administration Server for client devices

Avoiding conflicts between multiple Administration Servers

Creating Administration Server connection profiles

About clusters and server arrays

Properties of a cluster or server array

Device tags

Quarantine and Backup

Remote diagnostics of client devices

Remotely connecting to the desktop of a client device

Connecting to devices through Windows Desktop Sharing

Triggering of rules in Smart Training mode

See also:

Scenario: Configuring network protection

Page top

[Topic 201874]

Settings of a managed device

Expand all | Collapse all

To view the settings of a managed device:

  1. In the main menu, go to Assets (Devices)Managed devices.

    The list of managed devices is displayed.

  2. In the list of managed devices, click the link with the name of the required device.

The properties window of the selected device is displayed.

The following tabs are displayed in the upper part of the properties window representing the main groups of the settings:

  • General

    This tab comprises the following sections:

    • The General section displays general information about the client device. Information is provided on the basis of data received during the last synchronization of the client device with the Administration Server:
      • Name

        In this field, you can view and modify the client device name in the administration group.

      • Description

        In this field, you can enter an additional description for the client device.

      • Device status

        Status of the client device assigned on the basis of the criteria defined by the administrator for the status of anti-virus protection on the device and the activity of the device on the network.

      • Device owner

        Name of the device owner. You can assign or remove a user as a device owner by clicking the Manage device owner link.

      • Full group name

        Administration group, which includes the client device.

      • Last update of anti-virus databases

        Date the anti-virus databases or applications were last updated on the device.

      • Connected to Administration Server

        Date and time Network Agent installed on the client device last connected to the Administration Server.

      • Last visible

        Date and time the device was last visible on the network.

      • Network Agent version

        Version of the installed Network Agent.

      • Created

        Date of the device creation within Kaspersky Security Center Cloud Console.

      • Do not disconnect from the Administration Server

        If this option is enabled, continuous connectivity between the managed device and the Administration Server is maintained. You may want to use this option if you are not using push servers, which provide such connectivity.

        If this option is disabled and push servers are not in use, the managed device only connects to the Administration Server to synchronize data or to transmit information.

        The maximum total number of devices with the Do not disconnect from the Administration Server option selected is 300.

        This option is disabled by default on managed devices. This option is enabled by default on the device where the Administration Server is installed and stays enabled even if you try to disable it.

      • Sessions

        This section contains a table with information about the users currently logged in to the device. The table displays the following data in the corresponding columns:

        • User name
        • SAM account name
        • User principal name
        • Email address

        To correctly display information about domain users' sessions, you must use domain controller polling.

    • The Network section displays the following information about the network properties of the client device:
    • The System section provides information about the operating system installed on the client device:
      • Operating system
      • CPU architecture
      • Operating system vendor
      • Operating system folder
      • Device name
      • Virtual machine type

        The virtual machine manufacturer.

      • Dynamic virtual machine as part of VDI

        This row displays whether the client device is a dynamic virtual machine as part of VDI.

      • Operating system build
    • The Protection section provides the following information about the current status of anti-virus protection on the client device:
      • Visible

        Visibility status of the client device.

      • Device status

        Status of the client device assigned on the basis of the criteria defined by the administrator for the status of anti-virus protection on the device and the activity of the device on the network.

      • Status description

        Status of the client device protection and connection to Administration Server.

      • Protection status

        This field shows the current status of real-time protection on the client device.

        When the status changes on the device, the new status is displayed in the device properties window only after the client device is synchronized with the Administration Server.

      • Last full scan

        Date and time the last malware scan was performed on the client device.

      • Virus detected

        Total number of threats detected on the client device since installation of the security application (first scan), or since the last reset of the threat counter.

      • Objects that have failed disinfection

        Number of unprocessed files on the client device.

        This field ignores the number of unprocessed files on mobile devices.

      • Disk encryption status

        The current status of file encryption on the local drives of the device. For a description of the statuses, see the Kaspersky Endpoint Security for Windows Help.

    • The Device status defined by application section provides information about the device status that is defined by the managed application installed on the device. This device status can differ from the one defined by Kaspersky Security Center Cloud Console.
  • Applications

    This tab lists all Kaspersky applications installed on the client device.This tab contains the Start and Stop buttons that allow you to start and stop the selected Kaspersky application (excluding Network Agent). You can use these buttons if port 15000 UDP is available on the managed device for receipt push-notifications from Administration Server. If the managed device is unavailable for push-notifications, but the mode of continuous connection to Administration Server is enabled (the Do not disconnect from the Administration Server option in the General section is enabled), the Start and Stop buttons are available too. Otherwise, when you try to start or stop the application, an error message is displayed. Also you can click the application name to view general information about the application, a list of events that have occurred on the device, and the application settings.

  • Active policies and policy profiles

    This tab lists the policies and policy profiles that are currently assigned to the managed device.

  • Tasks

    On the Tasks tab, you can manage client device tasks: view the list of existing tasks, create new ones, remove, start and stop tasks, modify their settings, and view execution results. The list of tasks is provided based on data received during the last session of client synchronization with the Administration Server. The Administration Server requests the task status details from the client device. If port 15000 UDP is available on the managed device for receipt push-notifications from Administration Server, the task status is displayed and buttons for managing the task are enabled. If the managed device is unavailable for push-notifications, but the mode of continuous connection to Administration Server is enabled (the Do not disconnect from the Administration Server option in the General section is enabled), the actions with tasks are available too.

    If connection is not established, the status is not displayed and buttons are disabled.

  • Events

    The Events tab displays events logged on the Administration Server for the selected client device.

  • Security issues

    In the Security issues tab, you can view, edit, and create security issues for the client device. Security issues can be created either automatically, through managed Kaspersky applications installed on the client device, or manually by the administrator. For example, if some users regularly move malware from their removable drives to devices, the administrator can create a security issue. The administrator can provide a brief description of the case and recommended actions (such as disciplinary actions to be taken against a user) in the text of the security issue, and can add a link to the user or users.

    A security issue for which all of the required actions have been taken is called processed. The presence of unprocessed security issues can be chosen as the condition for a change of the device status to Critical or Warning.

    This section contains a list of security issues that have been created for the device. Security issues are classified by severity level and type. The type of a security issue is defined by the Kaspersky application, which creates the security issue. You can highlight processed security issues in the list by selecting the check box in the Processed column.

  • Tags

    In the Tags tab, you can manage the list of keywords that are used for finding client devices: view the list of existing tags, assign tags from the list, configure auto-tagging rules, add new tags and rename old tags, and remove tags.

  • Advanced

    This tab comprises the following sections:

    • Applications registry. In this section, you can view the registry of applications installed on the client device and their updates; you can also set up the display of the applications registry.

      Information about installed applications is provided if Network Agent installed on the client device sends required information to the Administration Server. You can configure sending of information to the Administration Server in the properties window of Network Agent or its policy, in the Repositories section.

      Clicking an application name opens a window that contains the application details and a list of the update packages installed for the application.

    • Executable files. This section displays executable files found on the client device.
    • Distribution points. This section provides a list of distribution points with which the device interacts.
      • Export to file

        Click the Export to file button to save to a file a list of distribution points with which the device interacts. By default, the application exports the list of devices to a CSV file.

      • Properties

        Click the Properties button to view and configure the distribution point with which the device interacts.

    • Hardware registry. In this section, you can view information about hardware installed on the client device.

      If Network Agent is installed on a device running Windows, it sends to the Administration Server the following information about the device hardware:

      • RAM
      • Mass storage devices
      • Motherboard
      • CPU
      • Network adapters
      • Monitors
      • Video adapter
      • Sound card

      If Network Agent is installed on a device running Linux or macOS, it sends to the Administration Server the following information about the device hardware, if this information is provided by the operating system:

      • Total RAM volume
      • Total volume of mass storage devices
      • Motherboard
      • CPU
      • Network adapters
    • Available updates. This section displays a list of software updates found on this device but not installed yet.
    • Software vulnerabilities. This section provides information about vulnerabilities in third-party applications installed on client devices.

      To save the vulnerabilities to a file, select the check boxes next to the vulnerabilities that you want to save, and then click the Export to CSV button or Export to TXT button.

      The section contains the following settings:

      • Show only vulnerabilities that can be fixed

        If this option is enabled, the section displays vulnerabilities that can be fixed by using a patch.

        If this option is disabled, the section displays both vulnerabilities that can be fixed by using a patch, and vulnerabilities for which no patch has been released.

        By default, this option is enabled.

      • Vulnerability properties

        Click a software vulnerability name in the list to view the properties of the selected software vulnerability in a separate window. In the window, you can do the following:

        • Ignore software vulnerability on this managed device (in Administration Console or in Kaspersky Security Center Cloud Console).
        • View the list of recommended fixes for the vulnerability.
        • Manually specify the software updates to fix the vulnerability (in Administration Console or in Kaspersky Security Center Cloud Console).
        • View vulnerability instances.
        • View the list of existing tasks to fix vulnerability and create new tasks to fix vulnerability.

    • Remote diagnostics. In this section, you can perform remote diagnostics of client devices.

Page top

[Topic 166012]

Device selections

Device selections are a tool for filtering devices according to specific conditions. You can use device selections to manage several devices: for example, to view a report about only these devices or to move all of these devices to another group.

Kaspersky Security Center Cloud Console provides a broad range of predefined selections (for example, Devices with Critical status, Protection is disabled, Active threats are detected). Predefined selections cannot be deleted. You can also create and configure additional user-defined selections.

In user-defined selections, you can set the search scope and select all devices, managed devices, or unassigned devices. Search parameters are specified in the conditions. In the device selection you can create several conditions with different search parameters. For example, you can create two conditions and specify different IP ranges in each of them. If several conditions are specified, a selection displays the devices that meet any of the conditions. By contrast, search parameters within a condition are superimposed. If both an IP range and the name of an installed application are specified in a condition, only those devices will be displayed where both the application is installed and the IP address belongs to the specified range.

In this section

Viewing the device list from a device selection

Creating a device selection

Configuring a device selection

Exporting the device list from a device selection

Removing devices from administration groups in a selection

See also:

Using event selections

Scenario: Migration without a hierarchy of Administration Servers

Scenario: Configuring network protection

Page top

[Topic 243445]

Viewing the device list from a device selection

Kaspersky Security Center Cloud Console allows you to view the list of devices from a device selection.

To view the device list from the device selection:

  1. In the main menu, go to the Assets (Devices) Device selections or Discovery & deployment Device selections section.
  2. In the selection list, click the name of the device selection.

    The page displays a table with information about the devices included in the device selection.

  3. You can group and filter the data of the device table as follows:
    • Click the settings icon (The Setting icon.), and then select the columns to be displayed in the table.
    • Click the filter icon (The Filter icon.), and then specify and apply the filter criterion in the invoked menu.

      The filtered table of devices is displayed.

You can select one or several devices in the device selection and click the New task button to create a task that will be applied to these devices.

To move the selected devices of the device selection to another administration group, click the Move to group button, and then select the target administration group.

Page top

[Topic 209938]

Creating a device selection

To create a device selection:

  1. In the main menu, go to Assets (Devices) → Device selections.

    A page with a list of device selections is displayed.

  2. Click the Add button.

    The Device selection settings window opens.

  3. Enter the name of the new selection.
  4. Specify the group that contains the devices to be included in the device selection:
    • Find any devices—Searching for devices that meet the selection criteria and included in the Managed Devices or Unassigned devices group.
    • Find managed devices—Searching for devices that meet the selection criteria and included in the Managed Devices group.
    • Find unassigned devices—Searching for devices that meet the selection criteria and included in the Unassigned devices group.

    You can enable the Include data from secondary Administration Servers check box to enable searching for devices that meet the selection criteria and managed by secondary Administration Servers.

  5. Click the Add button.
  6. In the window that opens, specify conditions that must be met for including devices in this selection, and then click the OK button.
  7. Click the Save button.

The device selection is created and added to the list of device selections.

Page top

[Topic 209943]

Configuring a device selection

Expand all | Collapse all

To configure a device selection:

  1. In the main menu, go to Assets (Devices) → Device selections.

    A page with a list of device selections is displayed.

  2. Select the relevant user-defined device selection, and click the Properties button.

    The Device selection settings window opens.

  3. On the General tab, click the New condition link.
  4. Specify conditions that must be met for including devices in this selection.
  5. Click the Save button.

The settings are applied and saved.

Below are descriptions of the conditions for assigning devices to a selection. Conditions are combined by using the OR logical operator: the selection will contain devices that comply with at least one of the listed conditions.

General

In the General section, you can change the name of the selection condition and specify whether that condition must be inverted:

Invert selection condition

If this option is enabled, the specified selection condition will be inverted. The selection will include all devices that do not meet the condition.

By default, this option is disabled.

Network infrastructure

In the Network subsection, you can specify the criteria that will be used to include devices in the selection according to their network data:

  • Device name

    Windows network name (NetBIOS name) of the device, or the IPv4 or IPv6 address.

  • Domain

    Displays all devices included in the specified Windows domain.

  • Administration group

    Displays devices included in the specified administration group.

  • Description

    Text in the device properties window: In the Description field of the General section.

    To describe text in the Description field, you can use the following characters:

    • Within a word:
      • *. Replaces any string with any number of characters.

      Example:

      To describe words such as Server or Server's, you can enter Server*.

      • ?. Replaces any single character.

      Example:

      To describe words such as Window or Windows, you can enter Windo?.

      Asterisk (*) or question mark (?) cannot be used as the first character in the query.

    • To find several words:
      • Space. Displays all the devices whose descriptions contain any of the listed words.

      Example:

      To find a phrase that contains Secondary or Virtual words, you can include Secondary Virtual line in your query.

      • +. When a plus sign precedes a word, all search results will contain this word.

      Example:

      To find a phrase that contains both Secondary and Virtual, enter the +Secondary+Virtual query.

      • -. When a minus sign precedes a word, no search results will contain this word.

      Example:

      To find a phrase that contains Secondary and does not contain Virtual, enter the +Secondary-Virtual query.

      • "<some text>". Text enclosed in quotation marks must be present in the text.

      Example:

      To find a phrase that contains Secondary Server word combination, you can enter "Secondary Server" in the query.

  • IP range

    If this option is enabled, you can enter the initial and final IP addresses of the IP range in which the relevant devices must be included.

    By default, this option is disabled.

  • Managed by a different Administration Server

    Select one of the following values:

    • Yes. A device moving rule only applies to client devices managed by other Administration Servers. These Servers are different from the Server on which you configure the device moving rule.
    • No. The device moving rule only applies to client devices managed by the current Administration Server.
    • No value is selected. The condition does not apply.

In the Active Directory subsection, you can configure criteria for including devices into a selection based on their Active Directory data:

In the Network activity subsection, you can specify the criteria that will be used to include devices in the selection according to their network activity:

  • Acts as a distribution point

    In the drop-down list, you can set up the criterion for including devices in the selection when performing search:

    • Yes. The selection includes devices that act as distribution points.
    • No. Devices that act as distribution points are not included in the selection.
    • No value is selected. The criterion will not be applied.
  • Do not disconnect from the Administration Server

    In the drop-down list, you can set up the criterion for including devices in the selection when performing search:

    • Enabled. The selection will include devices on which the Do not disconnect from the Administration Server check box is selected.
    • Disabled. The selection will include devices on which the Do not disconnect from the Administration Server check box is cleared.
    • No value is selected. The criterion will not be applied.
  • Connection profile switched

    In the drop-down list, you can set up the criterion for including devices in the selection when performing search:

    • Yes. The selection will include devices that connected to the Administration Server after the connection profile was switched.
    • No. The selection will not include devices that connected to the Administration Server after the connection profile was switched.
    • No value is selected. The criterion will not be applied.
  • Last connected to Administration Server

    You can use this check box to set a search criterion for devices according to the time they last connected to the Administration Server.

    If this check box is selected, in the entry fields you can specify the time interval (date and time) during which the last connection was established between Network Agent installed on the client device and the Administration Server. The selection will include devices that fall within the specified interval.

    If this check box is cleared, the criterion will not be applied.

    By default, this check box is cleared.

  • New devices detected by network poll

    Searches for new devices that have been detected by network polling over the last few days.

    If this option is enabled, the selection only includes new devices that have been detected by device discovery over the number of days specified in the Detection period (days) field.

    If this option is disabled, the selection includes all devices that have been detected by device discovery.

    By default, this option is disabled.

  • Device is visible

    In the drop-down list, you can set up the criterion for including devices in the selection when performing search:

    • Yes. The application includes in the selection devices that are currently visible in the network.
    • No. The application includes in the selection devices that are currently invisible in the network.
    • No value is selected. The criterion will not be applied.

In the Cloud segments subsection, you can configure criteria for including devices in a selection according to their respective cloud segments:

  • Device is in a cloud segment

    If this option is enabled, you can choose devices from the AWS, Azure, and Google cloud segments.

    If the Include child objects option is also enabled, the search is run on all child objects of the selected segment.

    Search results include only devices from the selected segment.

  • Device discovered by using the API

    In the drop-down list, you can select whether a device is detected by API tools:

    • Yes. The device is detected by using the AWS, Azure, or Google API.
    • No. The device cannot be detected by using the AWS, Azure, or Google API. That is, the device is either outside the cloud environment or it is in the cloud environment but it cannot be detected by using an API.
    • No value. This condition does not apply.

Device statuses

In the Managed device status subsection, you can configure criteria for including devices into a selection based on the description of the devices status from a managed application:

  • Device status

    Drop-down list in which you can select one of the device statuses: OK, Critical, or Warning.

  • Real-time protection status

    Drop-down list, in which you can select the real-time protection status. Devices with the specified real-time protection status are included in the selection.

  • Device status description

    In this field, you can select the check boxes next to conditions that, if met, assign one of the following statuses to the device: OK, Critical, or Warning.

In the Status of components in managed applications subsection, you can configure criteria for including devices in a selection according to the statuses of components in managed applications:

In the Status-affecting problems in managed applications subsection, you can specify the criteria that will be used to include devices in the selection according to the list of possible problems detected by a managed application. If at least one problem that you select exists on a device, the device will be included in the selection. When you select a problem listed for several applications, you have the option to select this problem in all of the lists automatically.

You can select check boxes for descriptions of statuses from the managed application; upon receipt of these statuses, the devices will be included in the selection. When you select a status listed for several applications, you have the option to select this status in all of the lists automatically.

System details

In the Operating system section, you can specify the criteria that will be used to include devices in the selection according to their operating system type.

  • Platform type

    If the check box is selected, you can select an operating system from the list. Devices with the specified operating systems installed are included in the search results.

  • Operating system service pack version

    In this field, you can specify the package version of the operating system (in the X.Y format), which will determine how the moving rule is applied to the device. By default, no version value is specified.

  • Operating system bit size

    In the drop-down list, you can select the architecture for the operating system, which will determine how the moving rule is applied to the device (Unknown, x86, AMD64, or IA64). By default, no option is selected in the list so that the operating system's architecture is not defined.

  • Operating system build

    This setting is applicable to Windows operating systems only.

    The build number of the operating system. You can specify whether the selected operating system must have an equal, earlier, or later build number. You can also configure searching for all build numbers except the specified one.

  • Operating system release number

    This setting is applicable to Windows operating systems only.

    The release identifier (ID) of the operating system. You can specify whether the selected operating system must have an equal, earlier, or later release ID. You can also configure searching for all release ID numbers except the specified one.

In the Virtual machines section, you can set up the criteria to include devices in the selection according to whether these are virtual machines or part of virtual desktop infrastructure (VDI):

  • This is a virtual machine

    In the drop-down list, you can select the following options:

    • Undefined.
    • No. Find devices that are not virtual machines.
    • Yes. Find devices that are virtual machines.
  • Virtual machine type

    In the drop-down list, you can select the virtual machine manufacturer.

    This drop-down list is available if the Yes or Not important value is selected in the This is a virtual machine drop-down list.

  • Part of Virtual Desktop Infrastructure

    In the drop-down list, you can select the following options:

    • Undefined.
    • No. Find devices that are not part of Virtual Desktop Infrastructure.
    • Yes. Find devices that are part of the Virtual Desktop Infrastructure (VDI).

In the Hardware registry subsection, you can configure criteria for including devices into a selection based on their installed hardware:

Ensure that the lshw utility is installed on Linux devices from which you want to fetch hardware details. Hardware details fetched from virtual machines may be incomplete depending on the hypervisor used.

  • Device

    In the drop-down list, you can select a unit type. All devices with this unit are included in the search results.

    The field supports the full-text search.

  • Vendor

    In the drop-down list, you can select the name of a unit manufacturer. All devices with this unit are included in the search results.

    The field supports the full-text search.

  • Device name

    Name of the device in the Windows network. The device with the specified name is included in the selection.

  • Description

    Description of the device or hardware unit. Devices with the description specified in this field are included in the selection.

    A device's description in any format can be entered in the properties window of that device. The field supports the full-text search.

  • Device vendor

    Name of the device manufacturer. Devices produced by the manufacturer specified in this field are included in the selection.

    You can enter the manufacturer's name in the properties window of a device.

  • Serial number

    All hardware units with the serial number specified in this field will be included in the selection.

  • Inventory number

    Equipment with the inventory number specified in this field will be included in the selection.

  • User

    All hardware units of the user specified in this field will be included in the selection.

  • Location

    Location of the device or hardware unit (for example, at the HQ or a branch office). Computers or other devices that are deployed at the location specified in this field will be included in the selection.

    You can describe the location of a device in any format in the properties window of that device.

  • CPU clock rate, in MHz, from

    The minimum clock rate of a CPU. Devices with a CPU that matches the clock rate range specified in the entry fields (inclusive) will be included in the selection.

  • CPU clock rate, in MHz, to

    The maximum clock rate of a CPU. Devices with a CPU that matches the clock rate range specified in the entry fields (inclusive) will be included in the selection.

  • Number of virtual CPU cores, from

    The minimum number of virtual CPU cores. Devices with a CPU that matches the range of the virtual cores number specified in the entry fields (inclusive) will be included in the selection.

  • Number of virtual CPU cores, to

    The maximum number of virtual CPU cores. Devices with a CPU that matches the range of the virtual cores number specified in the entry fields (inclusive) will be included in the selection.

  • Hard drive volume, in GB, from

    The minimum volume of the hard drive on the device. Devices with a hard drive that matches the volume range specified in the entry fields (inclusive) will be included in the selection.

  • Hard drive volume, in GB, to

    The maximum volume of the hard drive on the device. Devices with a hard drive that matches the volume range specified in the entry fields (inclusive) will be included in the selection.

  • RAM size, in MB, from

    The minimum size of the device RAM. Devices with RAM that matches the size range specified in the entry fields (inclusive) will be included in the selection.

  • RAM size, in MB, to

    The maximum size of the device RAM. Devices with RAM that matches the size range specified in the entry fields (inclusive) will be included in the selection.

Third-party software details

In the Applications registry subsection, you can set up the criteria to search for devices according to applications installed on them:

  • Application name

    Drop-down list in which you can select an application. Devices on which the specified application is installed, are included in the selection.

  • Application version

    Entry field in which you can specify the version of selected application.

  • Vendor

    Drop-down list in which you can select the manufacturer of an application installed on the device.

  • Application status

    A drop-down list in which you can select the status of an application (Installed, Not installed). Devices on which the specified application is installed or not installed, depending on the selected status, will be included in the selection.

  • Find by update

    If this option is enabled, search will be performed using the details of updates for applications installed on the relevant devices. After you select the check box, the Application name, Application version, and Application status fields change to Update name, Update version, and Status respectively.

    By default, this option is disabled.

  • Name of incompatible security application

    Drop-down list in which you can select third-party security applications. During the search, devices on which the specified application is installed, are included in the selection.

  • Application tag

    In the drop-down list, you can select the application tag. All devices that have installed applications with the selected tag in the description are included in the device selection.

  • Apply to devices without the specified tags

    If this option is enabled, the selection includes devices with descriptions that contain none of the selected tags.

    If this option is disabled, the criterion is not applied.

    By default, this option is disabled.

In the Vulnerabilities and updates subsection, you can specify the criteria that will be used to include devices in the selection according to their Windows Update source:

WUA is switched to Administration Server

You can select one of the following search options from the drop-down list:

  • Yes. If this option is selected, the search results will include devices that receive updates through Windows Update from the Administration Server.
  • No. If this option is selected, the results will include devices that receive updates through Windows Update from another sources.

Details of Kaspersky applications

In the Kaspersky applications subsection, you can configure criteria for including devices in a selection based on the selected managed application:

  • Application name

    In the drop-down list, you can set a criterion for including devices in a selection when search is performed by the name of a Kaspersky application.

    The list provides only the names of applications with management plug-ins installed on the administrator's workstation.

    If no application is selected, the criterion will not be applied.

  • Application version

    In the entry field, you can set a criterion for including devices in a selection when search is performed by the version number of a Kaspersky application.

    If no version number is specified, the criterion will not be applied.

  • Critical update name

    A drop-down list in which you can select the status of an application (Installed, Not installed). Devices on which the specified application is installed or not installed, depending on the selected status, will be included in the selection.

    In the entry field, you can set a criterion for including devices in a selection when search is performed by application name or by update package number.

    If the field is left blank, the criterion will not be applied.

  • Select the period of the last update of modules

    You can use this option to set a criterion for searching devices by time of the last update of modules of applications installed on those devices.

    If this check box is selected, in the entry fields you can specify the time interval (date and time) during which the last update of modules of applications installed on those devices was performed.

    If this check box is cleared, the criterion will not be applied.

    By default, this check box is cleared.

  • Device is managed through Administration Server

    In the drop-down list, you can include in the selection the devices managed through Kaspersky Security Center Cloud Console:

    • Yes. The application includes in the selection devices managed through Kaspersky Security Center Cloud Console.
    • No. The application includes devices in the selection if they are not managed through Kaspersky Security Center Cloud Console.
    • No value is selected. The criterion will not be applied.
  • Security application is installed

    In the drop-down list, you can include in the selection all devices with the security application installed:

    • Yes. The application includes in the selection all devices with the security application installed.
    • No. The application includes in the selection all devices with no security application installed.
    • No value is selected. The criterion will not be applied.

In the Anti-virus protection subsection, you can set up the criteria for including devices in a selection based on their protection status:

  • Databases released

    If this option is selected, you can search for client devices by anti-virus database release date. In the entry fields you can set the time interval, on the basis of which the search is performed.

    By default, this option is disabled.

  • Database records count

    If this option is enabled, you can search for client devices by number of database records. In the entry fields you can set the lower and upper threshold values for anti-virus database records.

    By default, this option is disabled.

  • Last scanned

    If this check option is enabled, you can search for client devices by time of the last malware scan. In the entry fields you can specify the time period within which the last malware scan was performed.

    By default, this option is disabled.

  • Threats detected

    Advanced Encryption Standard (AES) symmetrical block cipher algorithm. In the drop-down list, you can select the encryption key size (56-bit, 128-bit, 192-bit, or 256-bit).

    Available values: AES56, AES128, AES192, and AES256.

    If this option is enabled, you can search for client devices by number of viruses detected. In the entry fields you can set the lower and upper threshold values for the number of viruses found.

    By default, this option is disabled.

The Application components subsection contains the list of components of those applications that have corresponding management plug-ins installed in Kaspersky Security Center Cloud Console.

In the Application components subsection, you can specify criteria for including devices in a selection according to the statuses and version numbers of the components that refer to the application that you select:

  • Status

    Search for devices according to the component status sent by an application to the Administration Server. You can select one of the following statuses: N/A, Stopped, Paused, Starting, Running, Failed, Not installed, Not supported by license. If the selected component of the application installed on a managed device has the specified status, the device is included in the device selection.

    Statuses sent by applications:

    • Stopped—The component is disabled and not working at the moment.
    • Paused—The component is suspended, for example, after the user has paused protection in the managed application.
    • Starting—The component is currently in the process of initialization.
    • Running—The component is enabled and working properly.
    • Failed—An error has occurred during the component operation.
    • Not installed—The user did not select the component for installation when configuring custom installation of the application.
    • Not supported by license—The license does not cover the selected component.

    Unlike other statuses, the N/A status is not sent by applications. This option shows that the applications have no information about the selected component status. For example, this can happen when the selected component does not belong to any of the applications installed on the device, or when the device is turned off.

  • Version

    Search for devices according to the version number of the component that you select in the list. You can type a version number, for example 3.4.1.0, and then specify whether the selected component must have an equal, earlier, or later version. You can also configure searching for all versions except the specified one.

Tags

In the Tags section, you can configure criteria for including devices into a selection based on key words (tags) that were previously added to the descriptions of managed devices:

Apply if at least one specified tag matches

If this option is enabled, the search results will show devices with descriptions that contain at least one of the selected tags.

If this option is disabled, the search results will only show devices with descriptions that contain all the selected tags.

By default, this option is disabled.

To add tags to the criterion, click the Add button, and select tags by clicking the Tag entry field. Specify whether to include or exclude the devices with the selected tags in the device selection.

  • All devices that have this tag

    If this option is selected, the search results will display the devices whose descriptions contain the selected tag. To find devices, you can use the asterisk, which stands for any string with any number of characters.

    By default, this option is selected.

  • All devices that do not have this tag

    If this option is selected, the search results will display the devices whose descriptions do not contain the selected tag. To find devices, you can use the asterisk, which stands for any string with any number of characters.

Users

In the Users section, you can set up the criteria to include devices in the selection according to the accounts of users who have logged in to the operating system.

  • Last user who logged in to the system

    If this option is enabled, you can select the user account for configuring the criterion. Note that the user list is filtered and displays internal users. The search results will include devices on which the selected user performed the last login to the system.

  • User who logged in to the system at least once

    If this option is enabled, you can select the user account for configuring the criterion. Note that the user list is filtered and displays internal users. The search results will include devices on which the specified user logged in to the system at least once.

Page top

[Topic 251033]

Exporting the device list from a device selection

Kaspersky Security Center Cloud Console allows you to save information about devices from a device selection and export it as a CSV or a TXT file.

To export the device list from the device selection:

  1. Open the table with the devices from the device selection.
  2. Use one of the following ways to select the devices that you want to export:
    • To select particular devices, select the check boxes next to them.
    • To select all devices from the current table page, select the check box in the device table header, and then select the Select all on current page check box.
    • To select all devices from the table, select the check box in the device table header, and then select the Select all check box.

Click the Export to CSV or Export to TXT button. All information about the selected devices included in the table will be exported.

Note that if you applied a filter criterion to the device table, only the filtered data from the displayed columns will be exported.

Page top

[Topic 251146]

Removing devices from administration groups in a selection

When working with a device selection, you can remove devices from administration groups right in this selection, without switching to the administration groups from which these devices must be removed.

To remove devices from administration groups:

  1. In the main menu, go to Assets (Devices) Device selections or Discovery & deployment Device selections.
  2. In the selection list, click the name of the device selection.

    The page displays a table with information about the devices included in the device selection.

  3. Select the devices that you want to remove, and then click Delete.

    The selected devices are removed from their respective administration groups.

Page top

[Topic 179988]

Viewing and configuring the actions when devices show inactivity

Expand all | Collapse all

If client devices within a group are inactive, you can get notifications about it. You can also automatically delete such devices.

To view or configure the actions when the devices in the group show inactivity:

  1. In the main menu, go to Assets (Devices)Hierarchy of groups.
  2. Click the name of the required administration group.

    The administration group properties window opens.

  3. In the properties window, go to the Settings tab.
  4. In the Inheritance section, enable or disable the following options:
    • Inherit from parent group

      The settings in this section will be inherited from the parent group in which the client device is included. If this option is enabled, the settings under Device activity on the network are locked from any changes.

      This option is available only if the administration group has a parent group.

      By default, this option is enabled.

    • Force inheritance of settings in child groups

      The setting values will be distributed to child groups but in the properties of the child groups these settings are locked.

      By default, this option is disabled.

  5. In the Device activity section, enable or disable the following options:
  6. Click Save.

Your changes are saved and applied.

Page top

[Topic 191051]

About device statuses

Kaspersky Security Center Cloud Console assigns a status to each managed device. The particular status depends on whether the conditions defined by the user are met. In some cases, when assigning a status to a device, Kaspersky Security Center Cloud Console takes into consideration the device's visibility flag on the network (see the table below). If Kaspersky Security Center Cloud Console does not find a device on the network within two hours, the visibility flag of the device is set to Not Visible.

The statuses are the following:

  • Critical or Critical/Visible
  • Warning or Warning/Visible
  • OK or OK/Visible

The table below lists the default conditions that must be met to assign the Critical or Warning status to a device, with all possible values.

Conditions for assigning a status to a device

Condition

Condition description

Available values

Security application is not installed

Network Agent is installed on the device, but a security application is not installed.

  • Toggle button is on.
  • Toggle button is off.

Too many viruses detected

Some viruses have been found on the device by a task for virus detection, for example, the Virus scan task, and the number of viruses found exceeds the specified value.

More than 0.

Real-time protection level differs from the level set by the Administrator

The device is visible on the network, but the real-time protection level differs from the level set (in the condition) by the administrator for the device status.

  • Stopped.
  • Paused.
  • Running.

Malware scan has not been performed in a long time

The device is visible on the network and a security application is installed on the device, but neither the Malware scan task nor a local scan task has been run within the specified time interval. The condition is applicable only to devices that were added to the Administration Server database 7 days ago or earlier.

More than 1 day.

Databases are outdated

The device is visible on the network and a security application is installed on the device, but the anti-virus databases have not been updated on this device within the specified time interval. The condition is applicable only to devices that were added to the Administration Server database 1 day ago or earlier.

More than 1 day.

Not connected in a long time

Network Agent is installed on the device, but the device has not connected to an Administration Server within the specified time interval, because the device was turned off.

More than 1 day.

Active threats are detected

The number of unprocessed objects in the Active threats folder exceeds the specified value.

More than 0 items.

Restart is required

The device is visible on the network, but an application requires the device restart longer than the specified time interval and for one of the selected reasons.

More than 0 minutes.

Incompatible applications are installed

The device is visible on the network, but software inventory performed through Network Agent has detected incompatible applications installed on the device.

  • Toggle button is off.
  • Toggle button is on.

Software vulnerabilities have been detected

The device is visible on the network and Network Agent is installed on the device, but the Find vulnerabilities and required updates task has detected vulnerabilities with the specified severity level in applications installed on the device.

  • Critical.
  • High.
  • Medium.
  • Ignore if the vulnerability cannot be fixed.
  • Ignore if an update is assigned for installation.

License expired

The device is visible on the network, but the license has expired.

  • Toggle button is off.
  • Toggle button is on.

License expires soon

The device is visible on the network, but the license will expire on the device in less than the specified number of days.

More than 0 days.

Check for Windows Update updates has not been performed in a long time

The device is visible on the network, but the Perform Windows Update synchronization task has not been run within the specified time interval.

More than 1 day.

Invalid encryption status

Network Agent is installed on the device, but the device encryption result is equal to the specified value.

  • Does not comply with the policy due to the user's refusal (for external devices only).
  • Does not comply with the policy due to an error.
  • Restart is required when applying the policy.
  • No encryption policy is specified.
  • Not supported.
  • When applying the policy.

Mobile device settings do not comply with the policy

The mobile device settings are other than the settings that were specified in the Kaspersky Endpoint Security for Android policy during the check of compliance rules.

  • Toggle button is off.
  • Toggle button is on.

Unprocessed security issues detected

Some unprocessed security issues have been found on the device. Security issues can be created either automatically, through managed Kaspersky applications installed on the client device, or manually by the administrator.

  • Toggle button is off.
  • Toggle button is on.

Device status defined by application

The status of the device is defined by the managed application.

  • Toggle button is off.
  • Toggle button is on.

Device is out of disk space

Free disk space on the device is less than the specified value or the device could not be synchronized with the Administration Server. The Critical or Warning status is changed to the OK status when the device is successfully synchronized with the Administration Server and free space on the device is greater than or equal to the specified value.

More than 0 MB

Device has become unmanaged

During device discovery, the device was recognized as visible on the network, but more than three attempts to synchronize with the Administration Server failed.

  • Toggle button is off.
  • Toggle button is on.

Protection is disabled

The device is visible on the network, but the security application on the device has been disabled for longer than the specified time interval.

In this case, the state of the security application is stopped or failure, and differs from the following: starting, running, or suspended.

More than 0 minutes.

Security application is not running

The device is visible on the network and a security application is installed on the device but is not running.

  • Toggle button is off.
  • Toggle button is on.

Kaspersky Security Center Cloud Console enables you to set up automatic switching of the status of a device in an administration group when specified conditions are met. When specified conditions are met, the client device is assigned one of the following statuses: Critical or Warning. When specified conditions are not met, the client device is assigned the OK status.

Different statuses may correspond to different values of one condition. For example, by default, if the Databases are outdated condition has the More than 3 days value, the client device is assigned the Warning status; if the value is More than 7 days, the Critical status is assigned.

When Kaspersky Security Center Cloud Console assigns a status to a device, for some conditions (see the Condition description column) the visibility flag is taken into consideration. For example, if a managed device was assigned the Critical status because the Databases are outdated condition was met, and later the visibility flag was set for the device, then the device is assigned the OK status.

See also:

Managing client devices

Configuring the switching of device statuses

Scenario: Configuring network protection

Page top

[Topic 181770]

Configuring the switching of device statuses

You can change conditions to assign the Critical or Warning status to a device.

To enable changing the device status to Critical:

  1. In the main menu, go to Assets (Devices)Hierarchy of groups.
  2. In the list of groups that opens, click the link with the name of a group for which you want to change switching the device statuses.
  3. In the properties window that opens, select the Device status tab.
  4. In the left pane, select Critical.
  5. In the right pane, in the Set to Critical if these are specified section, enable the condition to switch a device to the Critical status.

    You can change only settings that are not locked in the parent policy.

  6. Select the radio button next to the condition in the list.
  7. In the upper-left corner of the list, click the Edit button.
  8. Set the required value for the selected condition.

    Values cannot be set for every condition.

  9. Click OK.

When specified conditions are met, the managed device is assigned the Critical status.

To enable changing the device status to Warning:

  1. In the main menu, go to Assets (Devices)Hierarchy of groups.
  2. In the list of groups that opens, click the link with the name of a group for which you want to change switching the device statuses.
  3. In the properties window that opens, select the Device status tab.
  4. In the left pane, select Warning.
  5. In the right pane, in the Set to Warning if these are specified section, enable the condition to switch a device to the Warning status.

    You can change only settings that are not locked in the parent policy.

  6. Select the radio button next to the condition in the list.
  7. In the upper-left corner of the list, click the Edit button.
  8. Set the required value for the selected condition.

    Values cannot be set for every condition.

  9. Click OK.

When specified conditions are met, the managed device is assigned the Warning status.

See also:

Managing client devices

About device statuses

Scenario: Monitoring and reporting

Scenario: Configuring network protection

Page top

[Topic 218291]

Changing the Administration Server for client devices

Expand all | Collapse all

You can change the Administration Server that manages client devices to a different Server using the Change Administration Server task. After the task completion, the selected client devices will be put under the management of the Administration Server that you specify. You can switch the device management between the following Administration Servers:

  • Primary Administration Server and one of its virtual Administration Servers
  • Two virtual Administration Servers of the same primary Administration Server

To change the Administration Server that manages client devices to a different Server:

  1. In the main menu, go to Assets (Devices)Tasks.
  2. Click Add.

    The New task wizard starts. Proceed through the wizard by using the Next button.

  3. At the New task settings step, specify the following settings:
    1. In the Application drop-down list, select Kaspersky Security Center Cloud Console.
    2. In the Task type field, select Change Administration Server.
    3. In the Task name field, specify the name for the task that you are creating.

      A task name cannot be more than 100 characters long and cannot include any special characters ("*<>?\:|).

    4. Select devices to which the task will be assigned:
      • Assign task to an administration group

        The task is assigned to devices included in an administration group. You can specify one of the existing groups or create a new one.

        For example, you may want to use this option to run a task of sending a message to users if the message is specific for devices included in a specific administration group.

        If a task is assigned to an administration group, the Security tab is not displayed in the task properties window because group tasks are subject to the security settings of the groups to which they apply.

      • Specify device addresses manually or import addresses from a list

        You can specify NetBIOS names, DNS names, IP addresses, and IP subnets of devices to which you want to assign the task.

        You may want to use this option to execute a task for a specific subnet. For example, you may want to install a certain application on devices of accountants or to scan devices in a subnet that is probably infected.

      • Assign task to a device selection

        The task is assigned to devices included in a device selection. You can specify one of the existing selections.

        For example, you may want to use this option to run a task on devices with a specific operating system version.

  4. At the Task scope step, specify an administration group, devices with specific addresses, or a device selection.
  5. At the next step, confirm that you agree to the terms of changing the Administration Server for client devices.
  6. At the next step, select the virtual Administration Server that you want to use to manage the selected devices.
  7. At the Selecting an account to run the task step, specify the account settings:
    • Default account

      The task will be run under the same account as the application that performs this task.

      By default, this option is selected.

    • Specify account

      Fill in the Account and Password fields to specify the details of an account under which the task is run. The account must have sufficient rights for this task.

      • Account

        Account under which the task is run.

      • Password

        Password of the account under which the task will be run.

  8. If on the Finish task creation page you enable the Open task details when creation is complete option, you can modify the default task settings.

    If you do not enable this option, the task is created with the default settings. You can modify the default settings later, at any time.

  9. Click the Finish button.

    The task is created and displayed in the list of tasks.

  10. Click the name of the created task to open the task properties window.
  11. In the task properties window, specify the general task settings according to your needs.
  12. Click the Save button.

    The task is created and configured.

  13. Run the created task.

After the task is complete, the client devices for which it was created are put under the management of the Administration Server specified in the task settings.

See also:

Managing client devices

Scenario: Configuring network protection

Page top

[Topic 175419]

Avoiding conflicts between multiple Administration Servers

If you have more than one Administration Server on your network, they can see the same client devices. This may result, for example, in remote installation of the same application to one and the same device from more than one Server and other conflicts. To avoid such a situation, Kaspersky Security Center Cloud Console allows you to prevent an application from being installed on a device managed by another Administration Server.

You can also use the Managed by a different Administration Server property as a criterion for the following purposes:

Kaspersky Security Center Cloud Console uses heuristics to determine whether a client device is managed by the Administration Server you are working with or by a different Administration Server.

Page top

[Topic 231207]

Creating Administration Server connection profiles

To allow out-of-office users to change the method of connecting Network Agent to Administration Server, you have to configure Administration Server connection profiles.

Connection profiles are supported only for devices running Windows and macOS.

To create a connection profile:

  1. In the main menu, go to Assets (Devices), and do one of the following:
    • If you want to create a connection profile for a group of managed devices, click Policies & profiles, and then click Kaspersky Security Center Network Agent.
    • If you want to create a connection profile for a specific managed device, click Managed devices, and then click the name of the device. In the window that opens, go to the Applications tab, and then click Kaspersky Security Center Network Agent.

    The properties window of the Network Agent policy opens.

  2. Go to the Application settings tab, and then go to the Connectivity section.
  3. In the Connection profiles section, click the Settings button.

    The Administration Server connection profiles subsection displays the table of connection profiles.

    You cannot view, modify, or delete the Home Administration Server and Offline mode connection profiles.

  4. Click the Add button, and then in the window that opens, specify the profile name.

    The name must be unique. You cannot use the same name for several profiles.

  5. If necessary, select the check boxes in the following fields:
    • Enable out-of-office mode when Administration Server is not available.
    • Use proxy server.

      If you select this option, do the following:

      • Specify information in the Address and the Port number fields.
      • If necessary, select the Proxy server authentication check box, and then specify the user name and the password in the corresponding fields.
  6. Click the Save button.

The new profile is displayed in the table of connection profiles. You can use it when configuring the Network location settings.

Network location settings define the characteristics of the network to which the client device is connected and specify rules for Network Agent switching from one Administration Server connection profile to another when those network characteristics are altered.

You can edit and delete connection profiles.

To edit a connection profile:

  1. In the table of connection profiles click the name of the connection profile that you want to edit.
  2. Make all necessary changes, and then click the Save button.

The changes are applied to the connection profile.

To delete a connection profile:

  1. In the table of connection profiles select the check boxes next to the connection profiles that you want to delete.
  2. Click the Delete button.

The selected connection profiles are deleted.

Page top

[Topic 246554]

About clusters and server arrays

Kaspersky Security Center Cloud Console supports cluster technology. If Network Agent sends information to Administration Server confirming that an application installed on a client device is part of a server array, this client device becomes a cluster node.

If an administration group contains clusters or server arrays, the Managed devices page displays two tabs—one for individual devices, and one for clusters and server arrays. After the managed devices are detected as cluster nodes, the cluster is added as an individual object to the Clusters and server arrays tab.

The cluster or server array nodes are listed on the Devices tab, along with other managed devices. You can view properties of the nodes as individual devices and perform other operations, but you cannot delete a cluster node or move it to another administration group separately from its cluster. You can only delete or move an entire cluster.

You can perform the following operations with clusters or server arrays:

  • View properties
  • Move the cluster or server array to another administration group

    When you move a cluster or server array to another group, all of its nodes move with it, because a cluster and any of its nodes always belong to the same administration group.

  • Delete

    It is reasonable to delete a cluster or server array only when the cluster or server array does not exist in the organization network any longer. If a cluster is still visible on your network and Network Agent and the Kaspersky security application are still installed on the cluster nodes, Kaspersky Security Center Cloud Console returns the deleted cluster and its nodes back to the list of managed devices automatically.

See also:

Moving devices or clusters to an administration group manually

Properties of a cluster or server array

Page top

[Topic 246991]

Properties of a cluster or server array

Expand all | Collapse all

To view the settings of a cluster or server array:

  1. In the main menu, go to Assets (Devices)Managed devicesClusters and server arrays.

    The list of clusters and server arrays is displayed.

  2. Click the name of the required cluster or server array.

The properties window of the selected cluster or server array is displayed.

General

The General section displays general information about the cluster or server array. Information is provided on the basis of data received during the last synchronization of the cluster nodes with the Administration Server:

  • Name
  • Description
  • Windows domain

    Windows domain or workgroup, which contains the cluster or server array.

  • NetBIOS name

    Windows network name of the cluster or server array.

  • DNS name

    Name of the DNS domain of the cluster or server array.

Tasks

In the Tasks tab, you can manage the tasks assigned to the cluster or server array: view the list of existing tasks; create new ones; remove, start, and stop tasks; modify task settings; and view execution results. The listed tasks relate to the Kaspersky security application installed on the cluster nodes. Kaspersky Security Center Cloud Console receives the task list and the task status details from the cluster nodes. If a connection is not established, the status is not displayed.

Nodes

This tab displays a list of nodes included into the cluster or server array. You can click a node name to view the device properties window.

Kaspersky application

The properties window may also contain additional tabs with the information and settings related to the Kaspersky security application installed on the cluster nodes.

See also:

About clusters and server arrays

Moving devices or clusters to an administration group manually

Page top

[Topic 175848]

Device tags

Kaspersky Security Center Cloud Console enables you to tag devices. A tag is the label of a device that can be used for grouping, describing, or finding devices. Tags assigned to devices can be used for creating selections, for finding devices, and for distributing devices among administration groups.

You can tag devices manually or automatically. You may use manual tagging when you want to tag an individual device. Auto-tagging is performed by Kaspersky Security Center Cloud Console in accordance with the specified tagging rules.

Devices are tagged automatically when specified rules are met. An individual rule corresponds to each tag. Rules are applied to the network properties of the device, operating system, applications installed on the device, and other device properties. For example, if your network includes devices running Windows, Linux, and macOS, you can set up a rule that will assign the [Linux] tag to all Linux-based devices. Then, you can use this tag when creating a device selection; this will help you sort all Linux-based devices and assign them a task. A tag is automatically removed from a device in the following cases:

  • When the device stops meeting conditions of the rule that assigns the tag.
  • When the rule that assigns the tag is disabled or deleted.

The list of tags and the list of rules on each Administration Server are independent of all other Administration Servers, including a primary Administration Server or subordinate virtual Administration Servers. A rule is applied only to devices from the same Administration Server on which the rule is created.

See also:

Managing client devices

Scenario: Configuring network protection

Page top

[Topic 175850]

Creating a device tag

To create a device tag:

  1. In the main menu, go to Assets (Devices)TagsDevice tags.
  2. Click Add.

    A new tag window opens.

  3. In the Tag field, enter the tag name.
  4. Click Save to save the changes.

The new tag appears in the list of device tags.

Page top

[Topic 175855]

Renaming a device tag

To rename a device tag:

  1. In the main menu, go to Assets (Devices)TagsDevice tags.
  2. Click the name of the tag that you want to rename.

    A tag properties window opens.

  3. In the Tag field, change the tag name.
  4. Click Save to save the changes.

The updated tag appears in the list of device tags.

Page top

[Topic 175856]

Deleting a device tag

To delete a device tag:

  1. In the main menu, go to Assets (Devices)TagsDevice tags.
  2. In the list, select the device tag that you want to delete.
  3. Click the Delete button.
  4. In the window that opens, click Yes.

The device tag is deleted. The deleted tag is automatically removed from all of the devices to which it was assigned.

The tag that you have deleted is not removed automatically from auto-tagging rules. After the tag is deleted, it will be assigned to a new device only when the device first meets the conditions of a rule that assigns the tag.

The deleted tag is not removed automatically from the device if this tag is assigned to the device by an application or Network Agent. To remove the tag from your device, use the klscflag utility.

Page top

[Topic 175859]

Viewing devices to which a tag is assigned

To view devices to which a tag is assigned:

  1. In the main menu, go to Assets (Devices)TagsDevice tags.
  2. Click the View devices link next to the tag for which you want to view assigned devices.

    You will be redirected to the Managed devices section of the main menu, with the devices filtered by the tag for which you clicked the View devices link.

  3. If you want to return to the list of device tags, click the Back button of your browser.

After you view the devices to which the tag is assigned, you can either create and assign a new tag or assign the existing tag to other devices. In this case, you have to remove the filter by tag, select the devices, and then assign the tag.

Page top

[Topic 175862]

Viewing tags assigned to a device

To view tags assigned to a device:

  1. In the main menu, go to Assets (Devices) → Managed devices.
  2. Click the name of the device whose tags you want to view.
  3. In the device properties window that opens, select the Tags tab.

The list of tags assigned to the selected device is displayed. In the Tag assigned column you can view how the tag was assigned.

You can assign another tag to the device or remove an already assigned tag. You can also view all device tags that exist on the Administration Server.

You can also view tags assigned to a device in the command line, by using the klscflag utility.

To view tags assigned to a device in the command line, run the following command:

klscflag -ssvget -pv 1103/1.0.0.0 -s KLNAG_SECTION_TAGS_INFO -n KLCONN_HOST_TAGS -svt ARRAY_T -ss "|ss_type = \"SS_PRODINFO\";"

Page top

[Topic 175860]

Tagging devices manually

To assign a tag to a device:

  1. View tags assigned to the device to which you want to assign another tag.
  2. Click Add.
  3. In the window that opens, do one of the following:
    • To create and assign a new tag, select Create new tag, and then specify the name of the new tag.
    • To select an existing tag, select Assign existing tag, and then select the necessary tag in the drop-down list.
  4. Click OK to apply the changes.
  5. Click Save to save the changes.

The selected tag is assigned to the device.

To assign a tag to several devices:

  1. In the main menu, go to Assets (Devices) Managed devices.
  2. Select the devices to which you want to assign a tag.
  3. Click Tags, and then select Assign from the drop-down list.
  4. In the window that opens, select a tag from the drop-down list.

    If necessary, you can select several tags.

    You can also do the following:

    • Edit the name of a tag by clicking the Edit (A pencil.) icon.

      Specify the new name of the tag, and then click the Save button.

      Note that the tag will also be renamed in the list of device tags.

    • Delete a tag by clicking the Delete (Trash can.) icon.

      In the window that opens, click Delete.

      Note that the tag will also be deleted from the Administration Server.

  5. Click the Save button.

The tags are assigned to the selected devices. You can remove the assigned tags.

Page top

[Topic 175861]

Removing assigned tags from devices

The unassigned device tag is not deleted. If you want, you can delete it manually.

You cannot manually remove tags assigned to the device by applications or Network Agent. To remove these tags, use the klscflag utility.

To remove a tag from a device:

  1. In the main menu, go to Assets (Devices) → Managed devices.
  2. Click the name of the device whose tags you want to view.
  3. In the device properties window that opens, select the Tags tab.
  4. Select the check box next to the tag that you want to remove.
  5. At the top of the list, click the Unassign tag? button.
  6. In the window that opens, click Yes.

The tag is removed from the device.

To remove tags from several devices:

  1. In the main menu, go to Assets (Devices) Managed devices.
  2. Select the devices whose tags you want to remove.
  3. Click Tags, and then select Unassign from the drop-down list.
  4. In the window that opens, select the check boxes next to the tags that you want to remove.

    The window displays all tags assigned to all the devices that you selected at step 2.

  5. Click the Save button.

The tags are removed from the devices.

Page top

[Topic 175849]

Viewing rules for tagging devices automatically

To view rules for tagging devices automatically,

Do any of the following:

  • In the main menu, go to Assets (Devices) → TagsAuto-tagging rules.
  • In the main menu, go to Assets (Devices) → TagsDevice tags, and then click the Set up auto-tagging rules link.
  • View tags assigned to a device and then click the Settings button.

The list of rules for auto-tagging devices appears.

Page top

[Topic 175967]

Editing a rule for tagging devices automatically

To edit a rule for tagging devices automatically:

  1. View rules for tagging devices automatically.
  2. Click the name of the rule that you want to edit.

    A rule settings window opens.

  3. Edit the general properties of the rule:
    1. In the Rule name field, change the rule name.

      The name cannot be more than 256 characters long.

    2. Do any of the following:
      • Enable the rule by switching the toggle button to Rule enabled.
      • Disable the rule by switching the toggle button to Rule disabled.
  4. Do any of the following:
    • If you want to add a new condition, click the Add button, and specify the settings of the new condition in the window that opens.
    • If you want to edit an existing condition, click the name of the condition that you want to edit, and then edit the condition settings.
    • If you want to delete a condition, select the check box next to the name of the condition that you want to delete, and then click Delete.
  5. Click OK in the conditions settings window.
  6. Click Save to save the changes.

The edited rule is shown in the list.

Page top

[Topic 175878]

Creating a rule for tagging devices automatically

To create a rule for tagging devices automatically:

  1. View rules for tagging devices automatically.
  2. Click Add.

    A new rule settings window opens.

  3. Configure the general properties of the rule:
    1. In the Rule name field, enter the rule name.

      The name cannot be more than 256 characters long.

    2. Do one of the following:
      • Enable the rule by switching the toggle button to Rule enabled.
      • Disable the rule by switching the toggle button to Rule disabled.
    3. In the Tag field, enter the new device tag name or select one of the existing device tags from the list.

      The name cannot be more than 256 characters long.

  4. In the conditions section, click the Add button to add a new condition.

    A new condition settings window open.

  5. Enter the condition name.

    The name cannot be more than 256 characters long. The name must be unique within a rule.

  6. Set up the triggering of the rule according to the following conditions. You can select multiple conditions.
    • Network—Network properties of the device, such as the device name on the Windows network, or device inclusion in a domain or an IP subnet.

      If case sensitive collation is set for the database that you use for Kaspersky Security Center Cloud Console, keep case when you specify a device DNS name. Otherwise, the auto-tagging rule will not work.

    • Applications—Presence of Network Agent on the device, operating system type, version, and architecture.
    • Virtual machines—Device belongs to a specific type of virtual machine.
    • Active Directory—Presence of the device in an Active Directory organizational unit and membership of the device in an Active Directory group.
    • Applications registry—Presence of applications of different vendors on the device.
  7. Click OK to save the changes.

    If necessary, you can set multiple conditions for a single rule. In this case, the tag will be assigned to a device if it meets at least one condition.

  8. Click Save to save the changes.

The newly created rule is enforced on devices managed by the selected Administration Server. If the settings of a device meet the rule conditions, the device is assigned the tag.

Later, the rule is applied in the following cases:

  • Automatically and periodically, depending on the server workload
  • After you edit the rule
  • When you run the rule manually
  • After the Administration Server detects a change in the settings of a device that meets the rule conditions or the settings of a group that contains such device

You can create multiple tagging rules. A single device can be assigned multiple tags if you have created multiple tagging rules and if the respective conditions of these rules are met simultaneously. You can view the list of all assigned tags in the device properties.

Page top

[Topic 175974]

Running rules for auto-tagging devices

When a rule is run, the tag specified in properties of this rule is assigned to devices that meet conditions specified in properties of the same rule. You can run only active rules.

To run rules for auto-tagging devices:

  1. View rules for tagging devices automatically.
  2. Select check boxes next to active rules that you want to run.
  3. Click the Run rule button.

The selected rules are run.

Page top

[Topic 175976]

Deleting a rule for tagging devices automatically

To delete a rule for tagging devices automatically:

  1. View rules for tagging devices automatically.
  2. Select the check box next to the rule that you want to delete.
  3. Click Delete.
  4. In the window that opens, click Delete again.

The selected rule is deleted. The tag that was specified in properties of this rule is unassigned from all of the devices that it was assigned to.

The unassigned device tag is not deleted. If you want, you can delete it manually.

Page top

[Topic 12429]

Quarantine and Backup

Kaspersky anti-virus applications installed on client devices may place files in Quarantine or Backup during device scan.

Quarantine is a special repository for storing files that are probably infected with viruses and files that cannot be disinfected at the time when they are detected.

Backup is designed for storing backup copies of files that have been deleted or modified during the disinfection process.

Kaspersky Security Center Cloud Console creates a summarized list of files placed in Quarantine or Backup by Kaspersky applications on the devices. Network Agents on client devices transmit information about the files in Quarantine and Backup to the Administration Server.

Kaspersky Security Center Cloud Console does not copy files from repositories to Administration Server. All files are stored in repositories on the devices.

In this section

Downloading a file from repositories

Deleting files from repositories

See also:

Managing client devices

Scenario: Configuring network protection

Page top

[Topic 12592]

Downloading a file from repositories

Kaspersky Security Center Cloud Console enables you to download copies of files that a security application placed in Quarantine or Backup on a client device. Files are copied to the destination that you specify.

You can download files only if one of the following conditions is met: the Do not disconnect from the Administration Server option is enabled in the settings of the device, a push server is in use, or a connection gateway is in use. Otherwise, downloading is not possible.

The maximum total number of devices with the Do not disconnect from the Administration Server option selected is 300.

To save a copy of file from Quarantine or Backup to a hard drive:

  1. Do one of the following:
    • If you want to save a copy of file from Quarantine, in the main menu, go to Operations RepositoriesQuarantine.
    • If you want to save a copy of file from Backup, in the main menu, go to Operations RepositoriesBackup.
  2. In the window that opens, select a file that you want to download and click Download.

The download starts. A copy of the file that had been placed in Quarantine on the client device is saved to the specified folder.

See also:

Quarantine and Backup

Scenario: Configuring network protection

Page top

[Topic 12431]

Deleting files from repositories

To delete a file from Quarantine or Backup:

  1. Do one of the following:
    • If you want to save a copy of file from Quarantine, in the main menu, go to Operations RepositoriesQuarantine.
    • If you want to save a copy of file from Backup, in the main menu, go to Operations RepositoriesBackup.
  2. In the window that opens, select a file that you want to delete and click Delete.
  3. Confirm that you want to delete the file.

The security application on the client device that had placed files in the repository (Quarantine or Backup) deletes the same files from this repository.

See also:

Quarantine and Backup

Scenario: Configuring network protection

Page top

[Topic 197041]

Remote diagnostics of client devices

You can use remote diagnostics for remote execution of the following operations on Windows-based and Linux-based client devices:

  • Enabling and disabling tracing, changing the tracing level, and downloading the trace file
  • Downloading system information and application settings
  • Downloading event logs
  • Generating a dump file for an application
  • Starting diagnostics and downloading diagnostics reports
  • Starting, stopping, and restarting applications

You can use event logs and diagnostics reports downloaded from a client device to troubleshoot problems on your own. Also, if you contact Kaspersky Technical Support, a Technical Support specialist might ask you to download trace files, dump files, event logs, and diagnostics reports from a client device for further analysis at Kaspersky.

In this section

Opening the remote diagnostics window

Enabling and disabling tracing for applications

Downloading trace files of an application

Deleting trace files

Downloading application settings

Downloading system information from a client device

Downloading event logs

Starting, stopping, restarting the application

Running the remote diagnostics of an application and downloading the results

Running an application on a client device

Generating a dump file for an application

Page top

[Topic 197042]

Opening the remote diagnostics window

To perform remote diagnostics on Windows-based and Linux-based client devices, you first have to open the remote diagnostics window.

To open the remote diagnostics window:

  1. To select the device for which you want to open the remote diagnostics window, perform one of the following:
    • If the device belongs to an administration group, in the main menu, go to Assets (Devices) → Groups → <group name> → Managed devices.
    • If the device belongs to the Unassigned devices group, in the main menu, go to Discovery & deploymentUnassigned devices.
  2. Click the name of the required device.
  3. In the device properties window that opens, select the Advanced tab.
  4. On the Advanced tab, click Remote diagnostics.

    This opens the Remote diagnostics window of a client device. If connection between Administration Server and the client device is not established, the error message is displayed.

Alternatively, if you need to obtain all diagnostic information about a Linux-based client device at once, you can run the collect.sh script on this device.

Page top

[Topic 197056]

Enabling and disabling tracing for applications

Expand all | Collapse all

You can enable and disable tracing for applications, including Xperf tracing.

Enabling and disabling tracing

To enable or disable tracing on a remote device:

  1. Open the remote diagnostics window of a client device.
  2. In the remote diagnostics window, select the Kaspersky applications tab.

    In the Application management section, the list of Kaspersky applications installed on the device displays.

  3. In the application list, select the application for which you want to enable or disable tracing.

    The list of remote diagnostics options opens.

  4. If you want to enable tracing:
    1. In the Tracing section, click Enable tracing.
    2. In the Modify tracing level window that opens, we recommend that you keep the default values of the settings. When required, a Technical Support specialist will guide you through the configuration process. The following settings are available:
      • Tracing level

        The tracing level defines the amount of detail that the trace file contains.

      • Rotation-based tracing

        The application overwrites the tracing information to prevent excessive increase in the size of the trace file. Specify the maximum number of files to be used to store the tracing information, and the maximum size of each file. If the maximum number of trace files of the maximum size are written, the oldest trace file is deleted so that a new trace file can be written.

        This setting is available for Kaspersky Endpoint Security only.

    3. Click Save.

    The tracing is enabled for the selected application. In some cases, the security application and its task must be restarted in order to enable tracing.

    On Linux-based client devices, tracing for the Updater of Kaspersky Security Agent component is regulated by the Network Agent settings. Therefore, the Enable tracing and Modify tracing level options are disabled for this component on client devices running Linux.

  5. If you want to disable tracing for the selected application, click Disable tracing.

    The tracing is disabled for the selected application.

Enabling Xperf tracing

For Kaspersky Endpoint Security, a Technical Support specialist may ask you to enable Xperf tracing for information about the system performance.

To enable and configure Xperf tracing or disable it:

  1. Open the remote diagnostics window of a client device.
  2. In the remote diagnostics window, select the Kaspersky applications tab.

    In the Application management section, the list of Kaspersky applications installed on the device displays.

  3. In the list of applications, select Kaspersky Endpoint Security for Windows.

    The list of remote diagnostics options for Kaspersky Endpoint Security for Windows displays.

  4. In the Xperf tracing section, click Enable Xperf tracing.

    If Xperf tracing is already enabled, the Disable Xperf tracing button is displayed instead. Click this button if you want to disable Xperf tracing for Kaspersky Endpoint Security for Windows.

  5. In the Change Xperf tracing level window that opens, depending on the request from the Technical Support specialist, do the following:
    1. Select one of the following tracing levels:
      • Light level

        A trace file of this type contains the minimum amount of information about the system.

        By default, this option is selected.

      • Deep level

        A trace file of this type contains more detailed information than trace files of the Light type and may be requested by Technical Support specialists when a trace file of the Light type is not enough for the performance evaluation. A Deep trace file contains technical information about the system including information about hardware, operating system, list of started and finished processes and applications, events used for performance evaluation, and events from Windows System Assessment Tool.

    2. Select one of the following Xperf tracing types:
      • Basic type

        The tracing information is received during operation of the Kaspersky Endpoint Security application.

        By default, this option is selected.

      • On-restart type

        The tracing information is received when the operating system starts on the managed device. This tracing type is effective when the issue that affects the system performance occurs after the device is turned on and before Kaspersky Endpoint Security starts.

      You may also be asked to enable the Rotation file size, in MB option to prevent excessive increase in the size of the trace file. Then specify the maximum size of the trace file. When the file reaches the maximum size, the oldest tracing information is overwritten with new information.

    3. Define the rotation file size.
    4. Click Save.

    Xperf tracing is enabled and configured.

  6. If you want to disable Xperf tracing for Kaspersky Endpoint Security for Windows, click Disable Xperf tracing in the Xperf tracing section.

    Xperf tracing is disabled.

Page top

[Topic 197112]

Downloading trace files of an application

You can download trace files from a client device only if one of the following conditions is met: the Do not disconnect from the Administration Server option is enabled in the settings of the device, a push server is in use, or a connection gateway is in use. Otherwise, downloading is not possible.

The maximum total number of devices with the Do not disconnect from the Administration Server option selected is 300.

To download a trace file of an application:

  1. Open the remote diagnostics window of a client device.
  2. In the remote diagnostics window, select the Kaspersky applications tab.

    In the Application management section, the list of Kaspersky applications installed on the device displays.

  3. In the list of applications, select the application for which you want to download a trace file.
  4. In the Tracing section, click the Trace files button.

    This opens the Device tracing logs window, where a list of trace files is displayed.

  5. In the list of trace files, select the file that you want to download.
  6. Do one of the following:
    • Download the selected file by clicking the Download. You can select one or several files for downloading.
    • Download a portion of the selected file:
      1. Click Download a portion.

        You cannot download portions of several files at the same time. If you select more than one trace file, the Download a portion button will be disabled.

      2. In the window that opens, specify the name and the file portion to download, according to your needs.

        For Linux-based devices, editing the file portion name is not available.

      3. Click Download.

The selected file, or its portion, is downloaded to the location that you specify.

Page top

[Topic 198282]

Deleting trace files

You can delete trace files that are no longer needed.

To delete a trace file:

  1. Open the remote diagnostics window of a client device.
  2. In the remote diagnostics window that opens, select the Event logs tab.
  3. In the Trace files section, click Windows Update logs or Remote installation logs, depending on which trace files you want to delete.

    This opens the Device tracing logs window, where a list of trace files is displayed.

  4. In the list of trace files, select one or several files that you want to delete.
  5. Click the Remove button.

The selected trace files are deleted.

Page top

[Topic 197067]

Downloading application settings

You can download application settings from a client device only if one of the following conditions is met: the Do not disconnect from the Administration Server option is enabled in the settings of the device, a push server is in use, or a connection gateway is in use. Otherwise, downloading is not possible.

The maximum total number of devices with the Do not disconnect from the Administration Server option selected is 300.

To download application settings from a client device:

  1. Open the remote diagnostics window of a client device.
  2. In the remote diagnostics window, select the Kaspersky applications tab.
  3. In the Application settings section, click the Download button to download information about the settings of the applications installed on the client device.

The ZIP archive with information is downloaded to the specified location.

Page top

[Topic 249394]

Downloading system information from a client device

You can download system information to your device from a client device only if one of the following conditions is met: the Do not disconnect from the Administration Server option is enabled in the settings of the device, a push server is in use, or a connection gateway is in use. Otherwise, downloading is not possible.

The maximum total number of devices with the Do not disconnect from the Administration Server option selected is 300.

To download system information from a client device:

  1. Open the remote diagnostics window of a client device.
  2. In the remote diagnostics window, select the System information tab.
  3. Click the Download button to download the system information about the client device.

The file with information is downloaded to the specified location.

Page top

[Topic 197068]

Downloading event logs

You can download event logs to your device from a client device only if one of the following conditions is met: the Do not disconnect from the Administration Server option is enabled in the settings of the device, a push server is in use, or a connection gateway is in use. Otherwise, downloading is not possible.

The maximum total number of devices with the Do not disconnect from the Administration Server option selected is 300.

To download an event log from a remote device:

  1. Open the remote diagnostics window of a client device.
  2. In the remote diagnostics window, on the Event logs tab, click All device logs.
  3. In the All device logs window, select one or several relevant logs.
  4. Do one of the following:
    • Download the selected log by clicking Download entire file.
    • Download a portion of the selected log:
      1. Click Download a portion.

        You cannot download portions of several logs at the same time. If you select more than one event log, the Download a portion button will be disabled.

      2. In the window that opens, specify the name and the log portion to download, according to your needs.
      3. Click Download.

The selected event log, or a portion of it, is downloaded to the specified location.

Page top

[Topic 197117]

Starting, stopping, restarting the application

You can start, stop, and restart applications on a client device.

To start, stop, or restart an application:

  1. Open the remote diagnostics window of a client device.
  2. In the remote diagnostics window, select the Kaspersky applications tab.

    In the Application management section, the list of Kaspersky applications installed on the device displays.

  3. In the list of applications, select the application that you want to start, stop, or restart.
  4. Select an action by clicking one of the following buttons:
    • Stop application

      This button is available only if the application is currently running.

    • Restart application

      This button is available only if the application is currently running.

    • Start application

      This button is available only if the application is not currently running.

Depending on the action that you have selected, the required application is started, stopped, or restarted on the client device.

If you restart the Network Agent, a message is displayed stating that the current connection of the device to the Administration Server will be lost.

Page top

[Topic 197886]

Running the remote diagnostics of an application and downloading the results

To start diagnostics for an application on a remote device and download the results:

  1. Open the remote diagnostics window of a client device.
  2. In the remote diagnostics window, select the Kaspersky applications tab.

    In the Application management section, the list of Kaspersky applications installed on the device displays.

  3. In the list of applications, select the application for which you want to run remote diagnostics.

    The list of remote diagnostics options opens.

  4. In the Diagnostics report section, click the Run diagnostics button.

    This starts the remote diagnostics process and generates a diagnostics report. When the diagnostics process is complete, the Download diagnostics report button becomes available.

  5. Click the Download diagnostics report button to download the report.

The report is downloaded to the specified location.

Page top

[Topic 198283]

Running an application on a client device

You may have to run an application on the client device, if a Kaspersky support specialist requests it. You do not have to install the application on that device.

To run an application on the client device:

  1. Open the remote diagnostics window of a client device.
  2. In the remote diagnostics window, select the Running a remote application tab.
  3. In the Object type field, select the type of object that you want to upload:
    • Select File to upload the executable file.
    • Select Folder to upload the folder containing the application that you want to run on the client device.

      If you select this object type, the Name of the executable file to be run field appears. In this field, specify the name of the executable file in the folder. You can also specify the relative path to the file.

    • Select Archive to upload the ZIP archive containing the application that you want to run on the client device.

      If you select this object type, the Name of the executable file to be run field appears. In this field, specify the name of the file in the folder that you want to run on the client device. You can also specify the relative path to the file.

      The ZIP archive must include the utility folder. This folder contains the executable file to be run on a remote device.

  4. Upload the object by selecting it in the system window, or dragging it to the upload field.
  5. If necessary, in the Command line arguments field, specify the command line arguments to be passed when running the executable file.
  6. In the Running a remote application section, click the Upload button to select a ZIP archive containing the application that you want to run on the client device.
  7. Click the Upload and run button to run the selected application on a client device.
  8. After the application execution is completed successfully, download the execution results by clicking the Download application execution results button.

    The application execution results are stored until you run a new diagnostic or close the window.

Remote diagnostics of the client device by using the application is completed.

Page top

[Topic 249403]

Generating a dump file for an application

An application dump file allows you to view parameters of the application running on a client device at a point in time. This file also contains information about modules that were loaded for an application.

Generating dump files is available only for 32-bit processes running on Windows-based client devices. For client devices running Linux and for 64-bit processes this feature is not supported.

To create a dump file for an application:

  1. Open the remote diagnostics window of a client device.
  2. In the remote diagnostics window, select click the Running a remote application tab.
  3. In the Generating the process dump file section, specify the executable file of the application for which you want to generate a dump file.
  4. Click the Download button to save the dump file for the specified application.

    If the specified application is not running on the client device, the error message will be displayed.

Page top

[Topic 195218]

Remotely connecting to the desktop of a client device

You can obtain remote access to the desktop of a client device through a Network Agent installed on the device. Remote connection to a device through the Network Agent is possible even if the TCP and UDP ports of the client device are closed.

Upon establishing the connection with the device, you gain full access to information stored on this device and can manage applications installed on it.

Remote connection must be allowed in the operating system settings of the target managed device. For example, in Windows 10, this option is called Allow Remote Assistance connections to this computer (you can find this option at Control PanelSystem and SecuritySystemRemote settings). If you have a license for the Vulnerability and patch management feature, you can enable this option forcibly when you establish connection to a managed device. If you do not have the license, enable this option locally on the target managed device. If this option is disabled, remote connection is not possible.

To establish remote connection to a device, you must have two utilities:

  • Kaspersky utility named klsctunnel. This utility must be stored on your workstation. You use this utility for tunneling the connection between a client device and the Administration Server.

    Kaspersky Security Center Cloud Console allows tunneling TCP connections from Administration Console via the Administration Server and then via Network Agent to a specified port on a managed device. Tunneling is designed for connecting a client application on a device with Administration Console installed to a TCP port on a managed device—if no direct connection is possible between Administration Console and the target device.

    Connection tunneling between a remote client device and Administration Server is required if the port used for connection to Administration Server is not available on the device. The port on the device may be unavailable in the following cases:

    • The remote device is connected to a local network that uses the NAT mechanism.
    • The remote device is part of the local network of Administration Server, but its port is closed by a firewall.
  • Standard Microsoft Windows component named Remote Desktop Connection. Connection to a remote desktop is established through the standard Windows utility mstsc.exe in accordance with the utility's settings.

    Connection to the current remote desktop session of the user is established without the user's knowledge. Once you connect to the session, the device user is disconnected from the session without an advance notification.

To connect to the desktop of a client device, one of the following conditions must be met:

  • Client device is a member of an administration group that has a distribution point with the Do not disconnect from the Administration Server option enabled.
  • In the client device settings, the Do not disconnect from the Administration Server option is enabled.

    The maximum total number of client devices with the Do not disconnect from the Administration Server option enabled is 300.

To connect to the desktop of a client device:

  1. In the main menu, go to Assets (Devices) → Managed devices.
  2. Select the check box next to the name of the device to which you want to obtain access.
  3. Click the Connect to Remote Desktop button.

    The Connect to Remote Desktop window opens.

  4. Click the Download button to download the klsctunnel utility.
  5. Click the Copy to clipboard button to copy the text from the text field. This text is a Binary Large Object (BLOB) that contains settings required to establish connection between the Administration Server and the managed device.

    A BLOB is valid for 3 minutes. If it has expired, reopen the Connect to Remote Desktop window to generate a new BLOB.

  6. Run the klsctunnel utility.

    The utility window opens.

  7. Paste the copied text into the text field.
  8. If you use a proxy server, select the Use proxy server check box, and then specify the proxy server connection settings.
  9. Click the Open port button.

    The Remote Desktop Connection login window opens.

  10. Specify the credentials of the account under which you are currently logged in to Kaspersky Security Center Cloud Console.
  11. Click the Connect button.

When connection to the device is established, the desktop is available in the Remote Desktop Connection window of Microsoft Windows.

See also:

Managing client devices

Scenario: Configuring network protection

Page top

[Topic 198907]

Connecting to devices through Windows Desktop Sharing

You can obtain remote access to the desktop of a client device through a Network Agent installed on the device. Remote connection to a device through the Network Agent is possible even if the TCP and UDP ports of the client device are closed.

You can connect to an existing session on a client device without disconnecting the user in this session. In this case, you and the session user on the device share access to the desktop.

To establish remote connection to a device, you must have two utilities:

  • Kaspersky utility named klsctunnel. This utility must be stored on your workstation. You use this utility for tunneling the connection between a client device and the Administration Server.

    Kaspersky Security Center Cloud Console allows tunneling TCP connections from Administration Console via the Administration Server and then via Network Agent to a specified port on a managed device. Tunneling is designed for connecting a client application on a device with Administration Console installed to a TCP port on a managed device—if no direct connection is possible between Administration Console and the target device.

    Connection tunneling between a remote client device and Administration Server is required if the port used for connection to Administration Server is not available on the device. The port on the device may be unavailable in the following cases:

    • The remote device is connected to a local network that uses the NAT mechanism.
    • The remote device is part of the local network of Administration Server, but its port is closed by a firewall.
  • Windows Desktop Sharing. When connecting to an existing session of the remote desktop, the session user on the device receives a connection request from you. No information about remote activity on the device and its results will be saved in reports created by Kaspersky Security Center Cloud Console.

    You can configure an audit of user activity on a remote client device. During the audit, the application saves information about files on the client device that have been opened and/or modified by the administrator.

To connect to the desktop of a client device through Windows Desktop Sharing, the following conditions must be met:

  • Microsoft Windows Vista or later is installed on your workstation.

    To check whether the Windows Desktop Sharing feature is included in your Windows edition, make sure that CLSID {32BE5ED2-5C86-480F-A914-0FF8885A1B3F} is included in the 32-bit registry.

  • Microsoft Windows Vista or later is installed on the client device.
  • Kaspersky Security Center Cloud Console uses a license for Vulnerability and patch management.
  • The client device is a member of an administration group that has a distribution point with the Do not disconnect from the Administration Server option enabled, or this option is enabled in the client device settings.

    Note that the maximum total number of client devices with the Do not disconnect from the Administration Server option enabled is 300.

To connect to the desktop of a client device through Windows Desktop Sharing:

  1. In the main menu, go to Assets (Devices) → Managed devices.
  2. Select the check box next to the name of the device to which you want to obtain access.
  3. Click the Windows Desktop Sharing button.

    The Windows Desktop Sharing wizard opens.

  4. Click the Download button to download the klsctunnel utility, and wait for the download process to complete.

    If you already have the klsctunnel utility, skip this step.

  5. Click the Next button.
  6. Select the session on the device to which you want to connect, and then click the Next button.
  7. On the target device, in the dialog box that opens, the user must allow a desktop sharing session. Otherwise, the session is not possible.

    After the device user confirms the desktop sharing session, the next page of the wizard opens.

  8. Click the Copy to clipboard button to copy the text from the text field. This text is a Binary Large Object (BLOB) that contains settings required to establish connection between the Administration Server and the managed device.

    A BLOB is valid for 3 minutes. If it has expired, generate a new BLOB.

  9. Run the klsctunnel utility.

    The utility window opens.

  10. Paste the copied text into the text field.
  11. If you use a proxy server, select the Use proxy server check box, and then specify the proxy server connection settings.
  12. Click the Open port button.

Desktop sharing starts in a new window. If you want to interact with the device, click the menu icon () in the upper-left corner of the window, and then select Interactive mode.

See also:

Managing client devices

Ports used by Kaspersky Security Center Cloud Console

Scenario: Configuring network protection

Page top

[Topic 172869]

Triggering of rules in Smart Training mode

This section provides information about the detections performed by the Adaptive Anomaly Control rules in Kaspersky Endpoint Security for Windows on client devices.

The rules detect anomalous behavior on client devices and may block it. If the rules work in Smart Training mode, they detect anomalous behavior and send reports about every such occurrence to Kaspersky Security Center Cloud Console Administration Server. This information is stored as a list in the Rule triggers in Smart Training state subfolder of the Repositories folder. You can confirm detections as correct or add them as exclusions, so that this type of behavior is not considered anomalous anymore.

Information about detections is stored in the event log on the Administration Server (along with other events) and in the Adaptive Anomaly Control report.

For more information about Adaptive Anomaly Control, the rules, their modes and statuses, refer to Kaspersky Endpoint Security Help.

In this section

Viewing the list of detections performed using Adaptive Anomaly Control rules

Adding exclusions from the Adaptive Anomaly Control rules

See also:

Managing client devices

Scenario: Configuring network protection

Page top

[Topic 172650]

Viewing the list of detections performed using Adaptive Anomaly Control rules

Expand all | Collapse all

To view the list of detections performed by Adaptive Anomaly Control rules:

  1. In the main menu, go to Operations → Repositories.
  2. Click the Rule triggers in Smart Training state link.

    The list displays the following information about detections performed using Adaptive Anomaly Control rules:

    • Administration group

      The name of the administration group where the device belongs.

    • Device name

      The name of the client device where the rule was applied.

    • Name

      The name of the rule that was applied.

    • Status

      Excluding—If the Administrator processed this item and added it as an exclusion to the rules. This status remains till the next synchronization of the client device with the Administration Server; after the synchronization, the item disappears from the list.

      Confirming—If the Administrator processed this item and confirmed it. This status remains till the next synchronization of the client device with the Administration Server; after the synchronization, the item disappears from the list.

      Empty—If the Administrator did not process this item.

    • User name

      The name of the client device user who run the process that generated the detect.

    • Processed

      Date when the anomaly was detected.

    • Source process path

      Path to the source process, i.e. to the process that performs the action (for more information, refer to the Kaspersky Endpoint Security help).

    • Source process hash

      SHA256 hash of the source process file (for more information, refer to the Kaspersky Endpoint Security help).

    • Source object path

      Path to the object that started the process (for more information, refer to the Kaspersky Endpoint Security help).

    • Source object hash

      SHA256 hash of the source file (for more information, refer to the Kaspersky Endpoint Security help).

    • Target process path

      Path to the target process (for more information, refer to the Kaspersky Endpoint Security help).

    • Target process hash

      SHA256 hash of the target file (for more information, refer to the Kaspersky Endpoint Security help).

    • Target object path

      Path to the target object (for more information, refer to the Kaspersky Endpoint Security help).

    • Target object hash

      SHA256 hash of the target file (for more information, refer to the Kaspersky Endpoint Security help).

To view properties of each information element:

  1. In the main menu, go to Operations → Repositories.
  2. Click the Rule triggers in Smart Training state link.
  3. In the window that opens, select the object that you want.
  4. Click the Properties link.

The properties window of the object opens and displays information about the selected element.

You can confirm or add to exclusions any element in the list of detections of Adaptive Anomaly Control rules.

To confirm an element,

Select an element (or several elements) in the list of detections and click the Confirm button.

The status of the element(s) will be changed to Confirming.

Your confirmation will contribute to the statistics used by the rules (for more information, refer to Kaspersky Endpoint Security for Windows documentation).

To add an element as an exclusion,

Select an element (or several elements) in the list of detections and click the Exclude button.

The Add exclusion wizard starts. Follow the instructions of the wizard.

If you reject or confirm an element, it will be excluded from the list of detections after the next synchronization of the client device with the Administration Server, and will no longer appear in the list.

See also:

Triggering of rules in Smart Training mode

Scenario: Configuring network protection

Page top

[Topic 173182]

Adding exclusions from the Adaptive Anomaly Control rules

The Add exclusion wizard enables you to add exclusions from the Adaptive Anomaly Control rules for Kaspersky Endpoint Security for Windows.

To start the Add exclusion wizard through the Adaptive Anomaly Control node:

  1. In the main menu, go to Operations → Repositories → Rule triggers in Smart Training state.
  2. In the window that opens, select an element (or several elements) in the list of detections, and then click the Exclude button.

    You can add up to 1000 exclusions at a time. If you select more elements and try to add them to exclusions, an error message is displayed.

The Add exclusion wizard starts. Proceed through the wizard by using the Next button.

See also:

Triggering of rules in Smart Training mode

Scenario: Configuring network protection

Page top

[Topic 46974_2]

Managing administration groups

This section provides information about how to manage administration groups.

You can perform the following actions on administration groups:

  • Add any number of nested groups at any level of hierarchy to administration groups.
  • Add devices to administration groups.
  • Change the hierarchy of administration groups by moving individual devices and entire groups to other groups.
  • Remove nested groups and devices from administration groups.
  • Add secondary and virtual Administration Servers to administration groups.
  • Move devices from the administration groups of an Administration Server to those of another Server.
  • Define which Kaspersky applications will be automatically installed on devices included in a group.

You can perform these actions only if you have the Modify permission in the Management of administration groups area for the administration groups you want to manage or for the Administration Server to which these groups belong.

In this section

Creating administration groups

Automatic installation of applications on devices in an administration group

Moving administration groups

Deleting administration groups

Page top

[Topic 3181]

Creating administration groups

Initially, the hierarchy of administration groups contains only one administration group called Managed devices group. You can add devices and subgroups into the Managed devices group.

To create an administration group:

  1. In the main menu, go to Assets (Devices)Hierarchy of groups.
  2. In the hierarchy, select the administration group that is to include the new administration group.
  3. Click the Add button.
  4. In the window that opens, enter a name for the group and click Add.

A new administration group with the specified name appears in the administration group hierarchy.

The application allows creating a hierarchy of administration groups based on the structure of Active Directory or the domain network's structure. Also, you can create a structure of groups from a text file.

To create a structure of administration groups:

  1. In the main menu, go to Assets (Devices)Hierarchy of groups.
  2. Click the Import button.

The New administration group structure wizard starts. Follow the instructions of the wizard.

See also:

Adjustment of distribution points and connection gateways

Modifying the list of distribution points for an administration group

Standard configuration of distribution points: Single office

Standard configuration of distribution points: Multiple small remote offices

Administration groups

Page top

[Topic 4626]

Automatic installation of applications on devices in an administration group

You can specify which installation packages must be used for automatic remote installation of Kaspersky applications to client devices in an administration group.

To configure automatic installation of applications on the devices in an administration group:

  1. In the main menu, go to Assets (Devices) → Hierarchy of groups, and click the name of the required administration group.
  2. In the properties window that opens, go to the Automatic installation tab.
  3. Select the installation packages of the applications to be installed on the devices, and then click the Save button.

    If you select several installation packages of the same application that differ only in their versions, the installation package with the latest version is saved.

After you select the installation packages, a group tasks for installation of the applications on the devices in the administration group is created for each of the application. These tasks are run on the client devices immediately after they are added to the administration group.

Page top

[Topic 4616]

Moving administration groups

You can move nested administration groups within the groups hierarchy.

An administration group is moved together with all nested groups, secondary Administration Servers, devices, group policies, and tasks. The application applies to the group all the settings that correspond to its new position in the hierarchy of administration groups.

The name of the group must be unique within one level of the hierarchy. If a group with the same name already exists in the folder into which you move the administration group, you must change the name of the latter. If you have not changed the name of the moved group, an index in (<next sequence number>) format is automatically added to its name when it is moved, for example: (1), (2).

You cannot rename and move the Managed devices group.

To move an administration group to another level of the administration groups hierarchy:

  1. In the main menu, go to Assets (Devices) → Hierarchy of groups, and then select the check box next to the administration group that you want to move.
  2. On the toolbar, click the Move button.
  3. In the window that opens, select where you want to move the administration group, and then click the Move button.

The window is closed, and the administration group is moved to another level of the groups hierarchy.

Page top

[Topic 51393]

Deleting administration groups

If you delete an administration group that contains secondary Administration Servers, nested groups, client devices, group tasks, or policies created for this group, all of them will also be deleted.

Before deleting an administration group, you must delete all secondary Administration Servers, nested groups, and client devices from that group.

To delete an administration group:

  1. In the main menu, go to Assets (Devices) → Hierarchy of groups, and then select the check box next to the administration group that you want to delete.
  2. On the toolbar, click the Delete button.

The administration group is deleted.

Page top

[Topic 165762]

Policies and policy profiles

In Kaspersky Security Center Cloud Console, you can create policies for Kaspersky applications. This section describes policies and policy profiles, and provides instructions for creating and modifying them.

In this section

About policies

About lock and locked settings

Inheritance of policies and policy profiles

Managing policies

Managing policy profiles

See also:

Scenario: Configuring network protection

Page top

[Topic 165742]

About policies

A policy is a set of Kaspersky application settings that are applied to an administration group and its subgroups. You can install several Kaspersky applications on the devices of an administration group. Kaspersky Security Center Cloud Console provides a single policy for each Kaspersky application in an administration group. A policy has one of the following statuses (see the table below):

The status of the policy

Status

Description

Active

The current policy that is applied to the device. Only one policy may be active for a Kaspersky application in each administration group. Devices apply the settings values of an active policy for a Kaspersky application.

Inactive

A policy that is not currently applied to a device.

Out-of-office

If this option is selected, the policy becomes active when the device leaves the corporate network.

Policies function according to the following rules:

  • Multiple policies with different values can be configured for a single application.
  • Only one policy can be active for the current application.
  • You can activate an inactive policy when a specific event occurs. For example, you can enforce stricter anti-virus protection settings during virus outbreaks.
  • A policy can have child policies.

Generally, you can use policies as preparations for emergency situations, such as a virus attack. For example, if there is an attack via flash drives, you can activate a policy that blocks access to flash drives. In this case, the current active policy automatically becomes inactive.

In order to prevent maintaining multiple policies, for example, when different occasions assume changing of several settings only, you may use policy profiles.

A policy profile is a named subset of policy settings values that replaces the settings values of a policy. A policy profile affects the effective settings formation on a managed device. Effective settings are a set of policy settings, policy profile settings, and local application settings that are currently applied for the device.

Policy profiles function according to the following rules:

  • A policy profile takes an effect when a specific activation condition occurs.
  • Policy profiles contain values of settings that differ from the policy settings.
  • Activation of a policy profile changes the effective settings of the managed device.
  • A policy can include a maximum of 100 policy profiles.

You cannot create an Administration Server policy.

See also:

Inheritance of policies and policy profiles

Scenario: Configuring network protection

Page top

[Topic 167068]

About lock and locked settings

Each policy setting has a lock button icon (The lock icon.). The table below shows lock button statuses:

Lock button statuses

Status

Description

An opened lock icon and the toggle button with text “Undefined” is off.

If an open lock is displayed next to a setting and the toggle button is disabled, the setting is not specified in the policy. A user can change these settings in the managed application interface. These type of settings are called unlocked.

A closed lock icon and the toggle button with text “Enforce” is on.

If a closed lock is displayed next to a setting and the toggle button is enabled, the setting is applied to the devices where the policy is enforced. A user cannot modify the values of these settings in the managed application interface. These type of settings are called locked.

We highly recommend that you close locks for the policy settings that you want to apply on the managed devices. The unlocked policy settings can be reassigned by Kaspersky application settings on a managed device.

You can use a lock button for performing the following actions:

  • Locking settings for an administration subgroup policy
  • Locking settings of a Kaspersky application on a managed device

Thus, a locked setting is used for implementing effective settings on a managed device.

A process of effective settings implementation includes the following actions:

  • Managed device applies settings values of Kaspersky application.
  • Managed device applies locked settings values of a policy.

A policy and managed Kaspersky application contain the same set of settings. When you configure policy settings, the Kaspersky application settings change values on a managed device. You cannot adjust locked settings on a managed device (see the figure below):

Administrator sets value and closes a lock. A user cannot change it. The user can change settings with an opened lock.

Locks and Kaspersky application settings

See also:

Policy profiles in a hierarchy of policies

Hierarchy of policies

Page top

[Topic 165771]

Inheritance of policies and policy profiles

This section provides information about the hierarchy and inheritance of policies and policy profiles.

In this section

Hierarchy of policies

Policy profiles in a hierarchy of policies

How settings are implemented on a managed device

Page top

[Topic 165770]

Hierarchy of policies

If different devices need different settings, you can organize devices into administration groups.

You can specify a policy for a single administration group. Policy settings can be inherited. Inheritance means receiving policy settings values in subgroups (child groups) from a policy of a higher-level (parent) administration group.

Hereinafter, a policy for a parent group is also referred to as a parent policy. A policy for a subgroup (child group) is also referred to as a child policy.

By default, at least one managed devices group exists on Administration Server. If you want to create custom groups, they are created as subgroups (child groups) within the managed devices group.

Policies of the same application act on each other, according to a hierarchy of administration groups. Locked settings from a policy of a higher-level (parent) administration group will reassign policy settings values of a subgroup (see the figure below).

Unlocked parent policy settings can be reassigned and locked in child policy. Locked policy settings cannot be changed.

Hierarchy of policies

Page top

[Topic 175793]

Policy profiles in a hierarchy of policies

Policy profiles have the following priority assignment conditions:

  • A profile's position in a policy profile list indicates its priority. You can change a policy profile priority. The highest position in a list indicates the highest priority (see the figure below).

    The Policy profile 1 has the highest priority, the Policy profile 100 has the lowest priority.

    Priority definition of a policy profile

  • Activation conditions of policy profiles do not depend on each other. Several policy profiles can be activated simultaneously. If several policy profiles affect the same setting, the device takes the setting value from the policy profile with the highest priority (see the figure below).

    Target device configuration fulfills the activation conditions of several policy profiles.

    Managed device configuration fulfills activation conditions of several policy profiles

Policy profiles in a hierarchy of inheritance

Policy profiles from different hierarchy level policies comply with the following conditions:

  • A lower-level policy inherits policy profiles from a higher-level policy. A policy profile inherited from a higher-level policy obtains higher priority than the original policy profile's level.
  • You cannot change a priority of an inherited policy profile (see the figure below).

    A child policy inherits profiles of the parent policy and they obtain higher priority than the child policy profiles.

    Inheritance of policy profiles

Policy profiles with the same name

If there are two policies with the same names in different hierarchy levels, these policies function according to the following rules:

  • Locked settings and the profile activation condition of a higher-level policy profile changes the settings and profile activation condition of a lower-level policy profile (see the figure below).

    Profile names of parent and child policies are the same. Changes in parent policy profile transfer to child policy profile.

    Child profile inherits settings values from a parent policy profile

  • Unlocked settings and the profile activation condition of a higher-level policy profile do not change the settings and profile activation condition of a lower-level policy profile.

See also:

Ports used by Kaspersky Security Center Cloud Console

Policy setup and propagation: Device-centric approach

Page top

[Topic 209754]

How settings are implemented on a managed device

Implementation of effective settings on a managed device can be described as follows:

  • The values of all settings that have not been locked are taken from the policy.
  • Then they are overwritten with the values of managed application settings.
  • And then the locked settings values from the effective policy are applied. Locked settings values change the values of unlocked effective settings.

See also:

About policies

About lock and locked settings

Hierarchy of policies

Policy profiles in a hierarchy of policies

Page top

[Topic 208004]

Managing policies

This section describes managing policies and provides information about viewing the list of policies, creating a policy, modifying a policy, copying a policy, moving a policy, forced synchronization, viewing the policy distribution status chart, and deleting a policy.

In this section

Viewing the list of policies

Creating a policy

Modifying a policy

General policy settings

Enabling and disabling a policy inheritance option

Copying a policy

Moving a policy

Exporting a policy

Importing a policy

Viewing the policy distribution status chart

Activating a policy automatically at the Virus outbreak event

Forced synchronization

Deleting a policy

Page top

[Topic 176804]

Viewing the list of policies

You can view lists of policies created for the Administration Server or for any administration group.

To view a list of policies:

  1. In the main menu, go to Assets (Devices) → Hierarchy of groups.
  2. In the administration group structure, select the administration group for which you want to view the list of policies.

The list of policies appears in tabular format. If there are no policies, the table is empty. You can show or hide the columns of the table, change their order, view only lines that contain a value that you specify, or use search.

See also:

Scenario: Configuring network protection

Page top

[Topic 166295]

Creating a policy

You can create policies; you can also modify and delete existing policies.

You cannot create an Administration Server policy.

To create a policy:

  1. In the main menu, go to Assets (Devices) → Policies & profiles.
  2. Click Add.

    The Select application window opens.

  3. Select the application for which you want to create a policy.
  4. Click Next.

    The new policy settings window opens with the General tab selected.

  5. If you want, change the default name, default status, and default inheritance settings of the policy.
  6. Click the Application settings tab.

    Or, you can click Save and exit. The policy will appear in the list of policies, and you can edit its settings later.

  7. On the Application settings tab, in the left pane select the category that you want and in the results pane on the right, edit the settings of the policy. You can edit policy settings in each category (section).

    The application settings depend on the application for which you create a policy. For details, refer to the following:

    For details about settings of other security applications, refer to the documentation for the corresponding application.

    When editing the settings, you can click Cancel to cancel the last operation.

  8. Click Save to save the policy.

The policy will appear in the list of policies.

See also:

Scenario: Kaspersky applications initial deployment

Scenario: Configuring network protection

Page top

[Topic 177380]

Modifying a policy

To modify a policy:

  1. In the main menu, go to Assets (Devices) → Policies & profiles.
  2. Click the policy that you want to modify.

    The policy settings window opens.

  3. Specify the general settings and settings of the application for which you create a policy. For details, refer to the following:

    For details about settings of other security applications, refer to the documentation for that application.

  4. Click Save.

The changes made to the policy will be saved in the policy properties, and will appear in the Revision history section.

See also:

Scenario: Configuring network protection

Page top

[Topic 177410]

General policy settings

Expand all | Collapse all

General

On the General tab, you can modify the policy status and specify the inheritance of policy settings:

  • In the Policy status block, you can select one of the policy modes:
    • Active
    • Out-of-office

      If this option is selected, the policy becomes active when the device leaves the corporate network.

    • Inactive

      If this option is selected, the policy becomes inactive, but it is still stored in the Policies folder. If required, the policy can be activated.

  • In the Settings inheritance settings group, you can configure the policy inheritance:
    • Inherit settings from parent policy

      If this option is enabled, the policy setting values are inherited from the upper-level group policy and, therefore, are locked.

      By default, this option is enabled.

    • Force inheritance of settings in child policies

      If this option is enabled, after policy changes are applied, the following actions will be performed:

      • The values of the policy settings will be propagated to the policies of administration subgroups, that is, to the child policies.
      • In the Settings inheritance block of the General section in the properties window of each child policy, the Inherit settings from parent policy option will be automatically enabled.

      If this option is enabled, the child policies settings are locked.

      By default, this option is disabled.

Event configuration

The Event configuration tab enables you to configure event logging and event notification. Events are distributed by importance level on the following tabs:

  • Critical

    The Critical section is not displayed in the Network Agent policy properties.

  • Functional failure
  • Warning
  • Info

In each section, the list shows the types of events and the default event storage term on the Administration Server (in days). Clicking an event type lets you specify the following settings:

  • Event registration

    You can specify how many days to store the event and select where to store the event:

    • Store in the Administration Server database for (days)
    • Store in the OS event log on device
  • Event notifications

    You can select if you want to be notified about the event by email.

    By default, the notification settings specified on the Administration Server properties tab (such as recipient address) are used. If you want, you can change these settings on the Email tab.

Revision history

The Revision history tab enables you to view the list of the policy revisions and roll back changes made to the policy, if necessary.

See also:

Scenario: Configuring network protection

Page top

[Topic 209023]

Enabling and disabling a policy inheritance option

To enable or disable the inheritance option in a policy:

  1. Open the required policy.
  2. Open the General tab.
  3. Enable or disable policy inheritance:
    • If you enable Inherit settings from parent policy in a child policy and an administrator locks some settings in the parent policy, then you cannot change these settings in the child policy.
    • If you disable Inherit settings from parent policy in a child policy, then you can change all of the settings in the child policy, even if some settings are locked in the parent policy.
    • If you enable Force inheritance of settings in child policies in the parent group, this enables the Inherit settings from parent policy option for each child policy. In this case, you cannot disable this option for any child policy. All of the settings that are locked in the parent policy are forcibly inherited in the child groups, and you cannot change these settings in the child groups.
  4. Click the Save button to save changes or click the Cancel button to reject changes.

By default, the Inherit settings from parent policy option is enabled for a new policy.

If a policy has profiles, all of the child policies inherit these profiles.

See also:

Hierarchy of policies

Scenario: Configuring network protection

Page top

[Topic 171683]

Copying a policy

You can copy policies from one administration group to another.

To copy a policy to another administration group:

  1. In the main menu, go to Assets (Devices) → Policies & profiles.
  2. Select the check box next to the policy (or policies) that you want to copy.
  3. Click the Copy button.

    On the right side of the screen, the tree of the administration groups appears.

  4. In the tree, select the target group, that is, the group to which you want to copy the policy (or policies).
  5. Click the Copy button at the bottom of the screen.
  6. Click OK to confirm the operation.

The policy (policies) will be copied to the target group with all its profiles. The status of each copied policy in the target group will be Inactive. You can change the status to Active at any time.

If a policy with the name identical to that of the newly moved policy already exists in the target group, the name of the newly moved policy is expanded with the (<next sequence number>) index, for example: (1).

See also:

Scenario: Configuring network protection

Page top

[Topic 171323]

Moving a policy

You can move policies from one administration group to another. For example, you want to delete a group, but you want to use its policies for another group. In this case, you may want move the policy from the old group to the new one before deleting the old group.

To move a policy to another administration group:

  1. In the main menu, go to Assets (Devices) → Policies & profiles.
  2. Select the check box next to the policy (or policies) that you want to move.
  3. Click the Move button.

    On the right side of the screen, the tree of the administration groups appears.

  4. In the tree, select the target group, that is, the group to which you want to move the policy (or policies).
  5. Click the Move button at the bottom of the screen.
  6. Click OK to confirm the operation.

If a policy is not inherited from the source group, it is moved to the target group with all its profiles. The status of the policy in the target group is Inactive. You can change the status to Active at any time.

If a policy is inherited from the source group, it remains in the source group. It is copied to the target group with all its profiles. The status of the policy in the target group is Inactive. You can change the status to Active at any time.

If a policy with the name identical to that of the newly moved policy already exists in the target group, the name of the newly moved policy is expanded with the (<next sequence number>) index, for example: (1).

See also:

Scenario: Configuring network protection

Page top

[Topic 240595]

Exporting a policy

Kaspersky Security Center Cloud Console allows you to save a policy, its settings, and the policy profiles to a KLP file. You can use this KLP file to import the saved policy both to Kaspersky Security Center Windows and Kaspersky Security Center Linux.

To export a policy:

  1. In the main menu, go to Assets (Devices) → Policies & profiles.
  2. Select the check box next to the policy that you want to export.

    You cannot export multiple policies at the same time. If you select more than one policy, the Export button will be disabled.

  3. Click the Export button.
  4. In the opened Save as window, specify the policy file name and path. Click the Save button.

    The Save as window is displayed only if you use Google Chrome, Microsoft Edge, or Opera. If you use another browser, the policy file is automatically saved in the Downloads folder.

Page top

[Topic 240597]

Importing a policy

Kaspersky Security Center Cloud Console allows you to import a policy from a KLP file. The KLP file contains the exported policy, its settings, and the policy profiles.

To import a policy:

  1. In the main menu, go to Assets (Devices) → Policies & profiles.
  2. Click the Import button.
  3. Click the Browse button to choose a policy file that you want to import.
  4. In the opened window, specify the path to the KLP policy file, and then click the Open button. Note that you can select only one policy file.

    The policy processing starts.

  5. After the policy is processed successfully, select the administration group to which you want to apply the policy.
  6. Click the Complete button to finish the policy import.

The notification with the import results appears. If the policy is imported successfully, you can click the Details link to view the policy properties.

After a successful import, the policy is displayed in the policy list. The settings and profiles of the policy are also imported. Regardless of the policy status that was selected during the export, the imported policy is inactive. You can change the policy status in the policy properties.

If the newly imported policy has a name identical to that of an existing policy, the name of the imported policy is expanded with the (<next sequence number>) index, for example: (1), (2).

Page top

[Topic 203532]

Viewing the policy distribution status chart

In Kaspersky Security Center Cloud Console, you can view the status of policy application on each device in a policy distribution status chart.

To view the policy distribution status on each device:

  1. In the main menu, go to Assets (Devices) → Policies & profiles.
  2. Select check box next to the name of the policy for which you want to view the distribution status on devices.
  3. In the menu that appears, click the Distribution link.

    The <Policy name> distribution results window opens.

  4. In the <Policy name> distribution results window that opens, the Status description (if available) of the policy is displayed.

You can change number of results displayed in the list with policy distribution. The maximum number of devices is 100,000.

To change the number of devices displayed in the list with policy distribution results:

  1. In the main menu, go to your account settings, and then select Interface options.
  2. In the Maximum number of devices displayed in policy distribution results, enter the number of devices (up to 100,000).

    By default, the number is 5000.

  3. Click Save.

The settings are saved and applied.

See also:

Scenario: Configuring network protection

Page top

[Topic 181204]

Activating a policy automatically at the Virus outbreak event

To make a policy perform automatic activation at a Virus outbreak event:

  1. In the main menu, click the settings icon () next to the name of the required Administration Server.

    The Administration Server properties window opens, with the General tab selected.

  2. Select the Virus outbreak section.
  3. In the right pane, click the Configure policies to activate when a virus outbreak event occurs link.

    The Policy activation window opens.

  4. In the section relating to the component that detects a virus outbreak—Anti-Virus for workstations and file servers, Anti-Virus for mail servers, or Anti-Virus for perimeter defense—select the option button next to the entry you want, and then click Add.

    A window opens with the Managed devices administration group.

  5. Click the chevron icon () next to Managed devices.

    A hierarchy of administration groups and their policies is displayed.

  6. In the hierarchy of administration groups and their policies, click the name of a policy or policies that are activated when a virus outbreak is detected.

    To select all policies in the list or in a group, select the check box next to the required name.

  7. Click the Save button.

    The window with the hierarchy of administration groups and their policies is closed.

The selected policies are added to the list of policies that are activated when a virus outbreak is detected. The selected policies are activated at the virus outbreak, independent whether they are active or inactive.

If a policy has been activated on the Virus outbreak event, you can return to the previous policy only by using the manual mode.

See also:

Scenario: Monitoring and reporting

Scenario: Configuring network protection

Page top

[Topic 175431]

Forced synchronization

Although Kaspersky Security Center Cloud Console automatically synchronizes the status, settings, tasks, and policies for managed devices, in some cases you need to know for certain, at a given moment, whether synchronization has already been performed for a specified device.

Synchronizing a single device

To force synchronization between the Administration Server and a managed device:

  1. In the main menu, go to Assets (Devices) → Managed devices.
  2. Click the name of the device that you want to synchronize with the Administration Server.

    A property window opens with the General section selected.

  3. Click the Force synchronization button.

The application synchronizes the selected device with the Administration Server.

Synchronizing multiple devices

To force synchronization between the Administration Server and multiple managed devices:

  1. Open the device list of an administration group or a device selection:
    • In the main menu, go to Assets (Devices) → Managed devices → Groups, and then select the administration group that contains devices to synchronize.
    • Run a device selection to view the device list.
  2. Select the check boxes next to the devices that you want to synchronize with the Administration Server.
  3. Click the Force synchronization button.

    The application synchronizes the selected devices with the Administration Server.

  4. In the device list, check that the time of last connection to the Administration Server has changed, for the selected devices, to the current time. If the time has not changed, update the page content by clicking the Refresh button.

The selected devices are synchronized with the Administration Server.

Viewing the time of a policy delivery

After changing a policy for a Kaspersky application on the Administration Server, you can check whether the changed policy has been delivered to a specific managed device. A policy can be delivered during a regular synchronization or a forced synchronization.

To view the date and time that an application policy was delivered to a managed device:

  1. In the main menu, go to Assets (Devices) → Managed devices.
  2. Click the name of the device that you want to synchronize with the Administration Server.

    A property window opens with the General section selected.

  3. Click the Applications tab.
  4. Select the application for which you want to view the policy synchronization date.

The application policy window opens with the General section selected and the policy delivery date and time displayed.

See also:

Scenario: Configuring network protection

Page top

[Topic 171525]

Deleting a policy

You can delete a policy if you do not need it anymore. You can delete only a policy that is not inherited in the specified administration group. If a policy is inherited, you can only delete it in the upper-level group for which it was created.

To delete a policy:

  1. In the main menu, go to Assets (Devices) → Policies & profiles.
  2. Select the check box next to the policy that you want to delete, and click Delete.

    The Delete button becomes unavailable (dimmed) if you select an inherited policy.

  3. Click OK to confirm the operation.

The policy is deleted together with all its profiles.

See also:

Scenario: Configuring network protection

Page top

[Topic 208033]

Managing policy profiles

This section describes managing policy profiles and provides information about viewing the profiles of a policy, changing a policy profile priority, creating a policy profile, modifying a policy profile, copying a policy profile, creating a policy profile activation rule, and deleting a policy profile.

In this section

Viewing the profiles of a policy

Changing a policy profile priority

Creating a policy profile

Modifying a policy profile

Copying a policy profile

Creating a policy profile activation rule

Deleting a policy profile

Page top

[Topic 175403]

Viewing the profiles of a policy

To view profiles of a policy:

  1. In the main menu, go to Assets (Devices) → Policies & profiles.
  2. Click the name of the policy whose profiles you want to view.

    The policy properties window opens with the General tab selected.

  3. Open the Policy profiles tab.

The list of policy profiles appears in tabular format. If the policy does not have profiles, an empty table appears.

See also:

Scenario: Configuring network protection

Page top

[Topic 171313]

Changing a policy profile priority

To change a policy profile priority:

  1. Proceed to the list of profiles of a policy that you want.

    The list of policy profiles appears.

  2. On the Policy profiles tab, select the check box next to the policy profile for which you want to change priority.
  3. Set a new position of the policy profile in the list by clicking Prioritize or Deprioritize.

    The higher a policy profile is located in the list, the higher its priority.

  4. Click the Save button.

Priority of the selected policy profile is changed and applied.

See also:

Policy profiles in a hierarchy of policies

Inheritance of policies and policy profiles

Scenario: Configuring network protection

Page top

[Topic 166297]

Creating a policy profile

To create a policy profile:

  1. Proceed to the list of profiles of the policy that you want.

    The list of policy profiles appears. If the policy does not have profiles, an empty table appears.

  2. Click Add.
  3. If you want, change the default name and default inheritance settings of the profile.
  4. Select the Application settings tab.

    Alternatively, you can click Save and exit. The profile that you have created appears in the list of policy profiles, and you can edit its settings later.

  5. On the Application settings tab, in the left pane, select the category that you want and in the results pane on the right, edit the settings for the profile. You can edit policy profile settings in each category (section).

    When editing the settings, you can click Cancel to cancel the last operation.

  6. Click Save to save the profile.

The profile will appear in the list of policy profiles.

See also:

Policy setup and propagation: Device-centric approach

Scenario: Configuring network protection

Page top

[Topic 177486]

Modifying a policy profile

The capability to edit a policy profile is only available for policies of Kaspersky Endpoint Security for Windows.

To modify a policy profile:

  1. Proceed to the list of profiles of a policy that you want.

    The list of policy profiles appears.

  2. On the Policy profiles tab, click the policy profile that you want to modify.

    The policy profile properties window opens.

  3. Configure the profile in the properties window:
    • If necessary, on the General tab, change the profile name and enable or disable the profile.
    • Edit the profile activation rules.
    • Edit the application settings.

    For details about settings of security applications, please see the documentation of the corresponding application.

  4. Click Save.

The modified settings will take effect either after the device is synchronized with the Administration Server (if the policy profile is active), or after an activation rule is triggered (if the policy profile is inactive).

See also:

Scenario: Configuring network protection

Page top

[Topic 175400]

Copying a policy profile

You can copy a policy profile to the current policy or to another, for example, if you want to have identical profiles for different policies. You can also use copying if you want to have two or more profiles that differ in only a small number of settings.

To copy a policy profile:

  1. Proceed to the list of profiles of a policy that you want.

    The list of policy profiles appears. If the policy does not have profiles, an empty table appears.

  2. On the Policy profiles tab, select the policy profile that you want to copy.
  3. Click Copy.
  4. In the window that opens, select the policy to which you want to copy the profile.

    You can copy a policy profile to the same policy or to a policy that you specify.

  5. Click Copy.

The policy profile is copied to the policy that you selected. The newly copied profile gets the lowest priority. If you copy the profile to the same policy, the name of the newly copied profile will be expanded with the () index, for example: (1), (2).

Later, you can change the settings of the profile, including its name and its priority; the original policy profile will not be changed in this case.

See also:

Scenario: Configuring network protection

Page top

[Topic 177498]

Creating a policy profile activation rule

Expand all | Collapse all

To create a policy profile activation rule:

  1. Proceed to the list of profiles of a policy that you want.

    The list of policy profiles appears.

  2. On the Policy profiles tab, click the policy profile for which you need to create an activation rule.

    If the list of policy profiles is empty, you can create a policy profile.

  3. On the Activation rules tab, click the Add button.

    The window with policy profile activation rules opens.

  4. Specify a name for the rule.
  5. Select the check boxes next to the conditions that must affect activation of the policy profile that you are creating:
    • General rules for policy profile activation

      Select this check box to set up policy profile activation rules on the device depending on the status of the device offline mode, rule for connection to Administration Server, and tags assigned to the device.

      For this option, specify at the next step:

      • Device status

        Defines the condition for device presence on the network:

        • Online—The device is on the network, and so the Administration Server is available.
        • Offline—The device is on an external network, which means that the Administration Server is not available.
        • N/A—The criterion will not be applied.
      • Rule for Administration Server connection is active on this device

        Choose the condition of policy profile activation (whether the rule is executed or not) and select the rule name.

        The rule defines the network location of the device for connection to the Administration Server, whose conditions must be met (or must not be met) for activation of the policy profile.

        A network location description of devices for connection to an Administration Server can be created or configured in a Network Agent switching rule.

    • Rules for specific device owner

      For this option, specify at the next step:

      • Device owner

        Enable this option to configure and enable the rule for profile activation on the device according to its owner. In the drop-down list under the check box, you can select a criterion for the profile activation:

        • The device belongs to the specified owner ("=" sign).
        • The device does not belong to the specified owner ("≠" sign).

          Note that the user list is filtered and displays device owners who are internal users.

          If this option is enabled, the profile is activated on the device in accordance with the criterion configured. You can specify the device owner when the option is enabled. If this option is disabled, the profile activation criterion is not applied. By default, this option is disabled.

      • Device owner is included in an internal security group

        Enable this option to configure and enable the rule of profile activation on the device by the owner's membership in an internal security group of Kaspersky Security Center Cloud Console. In the drop-down list under the check box, you can select a criterion for the profile activation:

        • The device owner is a member of the specified security group ("=" sign).
        • The device owner is not a member of the specified security group ("≠" sign).

          Note that the user list is filtered and displays device owners who are internal users.

          If this option is enabled, the profile is activated on the device in accordance with the criterion configured. You can specify a security group of Kaspersky Security Center Cloud Console. If this option is disabled, the profile activation criterion is not applied. By default, this option is disabled.

    • Rules for hardware specifications

      Select this check box to set up rules for policy profile activation on the device depending on the memory volume and the number of logical processors.

      For this option, specify at the next step:

      • RAM size, in MB

        Enable this option to configure and enable the rule of profile activation on the device by the RAM volume available on that device. In the drop-down list under the check box, you can select a criterion for the profile activation:

        • The device RAM size is less than the specified value ("<" sign).
        • The device RAM size is greater than the specified value (">" sign).

        If this option is enabled, the profile is activated on the device in accordance with the criterion configured. You can specify the RAM volume on the device. If this option is disabled, the profile activation criterion is not applied. By default, this option is disabled.

      • Number of logical processors

        Enable this option to configure and enable the rule of profile activation on the device by the number of logical processors on that device. In the drop-down list under the check box, you can select a criterion for the profile activation:

        • The number of logical processors on the device is less than or equal to the specified value ("<" sign).
        • The number of logical processors on the device is greater than or equal to the specified value (">" sign).

        If this option is enabled, the profile is activated on the device in accordance with the criterion configured. You can specify the number of logical processors on the device. If this option is disabled, the profile activation criterion is not applied. By default, this option is disabled.

    • Rules for role assignment

      For this option, specify at the next step:

      Activate policy profile by specific role of device owner

      Select this option to configure and enable the rule of profile activation on the device depending on the owner's role. Add the role manually from the list of existing roles.

      If this option is enabled, the profile is activated on the device in accordance with the criterion configured.

    • Rules for tag usage

      Select this check box to set up rules for policy profile activation on the device depending on the tags assigned to the device. You can activate the policy profile to the devices that either have the selected tags or do not have them.

      For this option, specify at the next step:

      • Tag

        In the list of tags, specify the rule for device inclusion in the policy profile by selecting the check boxes next to the relevant tags.

        You can add new tags to the list by entering them in the field over the list and clicking the Add button.

        The policy profile includes devices with descriptions containing all the selected tags. If check boxes are cleared, the criterion is not applied. By default, these check boxes are cleared.

      • Apply to devices without the specified tags

        Enable this option if you have to invert your selection of tags.

        If this option is enabled, the policy profile includes devices with descriptions that contain none of the selected tags. If this option is disabled, the criterion is not applied.

        By default, this option is disabled.

    • Rules for Active Directory usage

      Select this check box to set up rules for policy profile activation on the device depending on the presence of the device in an Active Directory organizational unit (OU), or on membership of the device (or its owner) in an Active Directory security group.

      For this option, specify at the next step:

      • Device owner's membership in an Active Directory security group

        If this option is enabled, the policy profile is activated on the device whose owner is a member of the specified security group. If this option is disabled, the profile activation criterion is not applied. By default, this option is disabled.

      • Device membership in Active Directory security group

        If this option is enabled, the policy profile is activated on the device. If this option is disabled, the profile activation criterion is not applied. By default, this option is disabled.

      • Device allocation in Active Directory organizational unit

        If this option is enabled, the policy profile is activated on the device which is included in the specified Active Directory organizational unit (OU). If this option is disabled, the profile activation criterion is not applied.

        By default, this option is disabled.

    The number of additional pages of the wizard depends on the settings that you select at the first step. You can modify policy profile activation rules later.

  6. Check the list of the configured parameters. If the list is correct, click Create.

The profile will be saved. The profile will be activated on the device when activation rules are triggered.

Policy profile activation rules created for the profile are displayed in the policy profile properties on the Activation rules tab. You can modify or remove any policy profile activation rule.

Multiple activation rules can be triggered simultaneously.

See also:

Policy setup and propagation: Device-centric approach

Scenario: Configuring network protection

Page top

[Topic 176807]

Deleting a policy profile

To delete a policy profile:

  1. Proceed to the list of profiles of a policy that you want.

    The list of policy profiles appears.

  2. On the Policy profiles tab, select the check box next to the policy profile that you want to delete, and click Delete.
  3. In the window that opens, click Delete again.

The policy profile is deleted. If the policy is inherited by a lower-level group, the profile remains in that group, but becomes the policy profile of that group. This is done to eliminate significant change in settings of the managed applications installed on the devices of lower-level groups.

See also:

Scenario: Configuring network protection

Page top

[Topic 195124]

Data encryption and protection

Data encryption reduces the risk of unintentional leakage in case your laptop or hard drive is stolen or lost, or upon access by unauthorized users and applications.

The following Kaspersky applications support encryption:

  • Kaspersky Endpoint Security for Windows
  • Kaspersky Endpoint Security for Mac

You can show or hide some of the interface elements related to the encryption management feature by using the user interface settings.

Encryption of data in Kaspersky Endpoint Security for Windows

You can manage the BitLocker Drive Encryption technology on devices running a Windows operating system for servers or workstations.

By using these components of Kaspersky Endpoint Security for Windows, you can, for example, enable or disable encryption, view the list of encrypted drives, or generate and view reports about encryption.

You configure encryption by defining policies of Kaspersky Endpoint Security for Windows in Kaspersky Security Center Cloud Console. Kaspersky Endpoint Security for Windows performs encryption and decryption according to the active policy. For detailed instructions on how to configure rules and a description of encryption features, see the Kaspersky Endpoint Security for Windows Help.

Encryption of data in Kaspersky Endpoint Security for Mac

You can use FileVault encryption on devices running macOS. While working with Kaspersky Endpoint Security for Mac, you can enable or disable this encryption.

You configure encryption by defining policies of Kaspersky Endpoint Security for Mac in Kaspersky Security Center Cloud Console. Kaspersky Endpoint Security for Mac performs encryption and decryption according to the active policy. For a detailed description of encryption features, see the Kaspersky Endpoint Security for Mac Help.

In this section

Viewing the list of encrypted drives

Creating and viewing encryption reports

Granting access to an encrypted drive in offline mode

See also:

Licenses and the minimum number of devices for each license

Compatible Kaspersky applications and solutions

Scenario: Configuring network protection

Page top

[Topic 195125]

Viewing the list of encrypted drives

In Kaspersky Security Center Cloud Console, you can view details about encrypted drives and devices that are encrypted at the drive level. After the information on a drive is decrypted, the drive is automatically removed from the list.

To view the list of encrypted drives,

In the main menu, go to OperationsData encryption and protectionEncrypted drives.

If the section is not on the menu, this means that it is hidden. In the user interface settings, enable the Show data encryption and protection option to display the section.

You can export the list of encrypted drives to a CSV or TXT file. To do this, click the Export to CSV or Export to TXT button.

See also:

Scenario: Configuring network protection

Page top

[Topic 195130]

Creating and viewing encryption reports

You can generate the following reports:

  • Report on encryption status of managed devices. This report provides details about the data encryption of various managed devices. For example, the report shows the number of devices to which the policy with configured encryption rules applies. Also, you can find out, for instance, how many devices need to be rebooted. The report also contains information about the encryption technology and algorithm for every device.
  • Report on encryption status of mass storage devices. This report contains similar information as the report on the encryption status of managed devices, but it provides data only for mass storage devices and removable drives.
  • Report on rights to access encrypted drives. This report shows which user accounts have access to encrypted drives.
  • Report on file encryption errors. This report contains information about errors that occurred when the data encryption or decryption tasks were run on devices.
  • Report on blockage of access to encrypted files. This report contains information about blocking application access to encrypted files. This report is helpful if an unauthorized user or application tries to access encrypted files or drives.

You can generate any report in the Monitoring & reportingReports section. Alternatively, in the OperationsData encryption and protection section, you can generate the following encryption reports:

  • Report on encryption status of mass storage devices
  • Report on rights to access encrypted drives
  • Report on file encryption errors

To generate an encryption report in the Data encryption and protection section:

  1. Make sure that you enabled the Show data encryption and protection option in the Interface options.
  2. In the main menu, go to OperationsData encryption and protection.
  3. Open the Encrypted drives section to generate the report on encryption status of mass storage devices or the report on rights to access encrypted drives.
  4. Click the name of the report that you want to generate.

The report generation starts.

See also:

Scenario: Configuring network protection

Page top

[Topic 195131]

Granting access to an encrypted drive in offline mode

A user can request access to an encrypted device, for example, when Kaspersky Endpoint Security for Windows is not installed on the managed device. After you receive the request, you can create an access key file and send it to the user. All of the use cases and detailed instructions are provided in the Kaspersky Endpoint Security for Windows Help.

To grant access to an encrypted drive in offline mode:

  1. Get a request access file from a user (a file with the FDERTC extension). Follow the instructions in the Kaspersky Endpoint Security for Windows Help to generate the file in Kaspersky Endpoint Security for Windows.
  2. In the main menu, go to OperationsData encryption and protectionEncrypted drives.

    A list of encrypted drives appears.

  3. Select the drive to which the user requested access.
  4. Click the Grant access to the device in offline mode button.
  5. In the window that opens, select the plug-in corresponding to the Kaspersky application that was used to encrypt the selected drive.

    If a drive is encrypted with a Kaspersky application that is not supported by Kaspersky Security Center Cloud Console, use Microsoft Management Console-based Administration Console to grant the offline access.

  6. Follow the instructions provided in the Kaspersky Endpoint Security for Windows Help (see expanding blocks at the end of the section).

After that, the user applies the received file to access the encrypted drive and read data stored on the drive.

See also:

Scenario: Configuring network protection

Page top

[Topic 225606]

About user accounts

Kaspersky Security Center Cloud Console allows you to manage user accounts and groups of accounts. The application supports two types of accounts:

  • Accounts of organization employees. Administration Server retrieves data of the accounts of those local users when polling the organization's network.
  • Accounts of internal users of Kaspersky Security Center Cloud Console. You can create accounts of internal users. These accounts are used only within Kaspersky Security Center Cloud Console.

To view tables of user accounts and security groups:

  1. In the main menu, go to Users & rolesUsers & groups.
  2. Select the Users or the Groups tab.

The table of users or security groups opens. By default, the opened table is filtered by the Subtype and Has assigned roles columns. The table displays internal users or groups that have assigned roles.

If you want to view the table with only the accounts of local users, set the Subtype filter criteria to Local.

If you switch to a secondary Administration Server version 14.2 or earlier, and then open the list of users or security groups, the opened table will be filtered only by the Subtype column. The filter by the Has assigned roles column will not be applied by default. The filtered table will contain all internal users or security groups with the assigned role and without it.

Page top

[Topic 89265]

Adding an account of an internal user

If you want, you can add internal users of your workspace on the portal. After you add an internal user, you can assign a role to him or her in the Kaspersky Security Center Cloud Console.

Page top

[Topic 165864]

About user roles

A user role (also referred to as a role) is an object containing a set of rights and privileges. A role can be associated with settings of Kaspersky applications installed on a user device. You can assign a role to a set of users or to a set of security groups at any level in the hierarchy of administration groups, Administration Servers, or at the level of specific objects.

If you manage devices through a hierarchy of Administration Servers that includes virtual Administration Servers, note that you can create, modify, or delete user roles only from a physical Administration Server. Then, you can propagate the user roles to secondary Administration Servers, including virtual ones.

You can associate user roles with policy profiles. If a user is assigned a role, this user gets security settings necessary to perform job functions.

A user role can be associated with users of devices in a specific administration group.

User role scope

A user role scope is a combination of users and administration groups. Settings associated with a user role apply only to devices that belong to users who have this role, and only if these devices belong to groups associated with this role, including child groups.

Advantage of using roles

An advantage of using roles is that you do not have to specify security settings for each of the managed devices or for each of the users separately. The number of users and devices in a company may be quite large, but the number of different job functions that require different security settings is considerably smaller.

Differences from using policy profiles

Policy profiles are properties of a policy that is created for each Kaspersky application separately. A role is associated with many policy profiles created for different applications. Therefore, a role is a method of uniting settings for a certain user type in one place.

See also:

Scenario: Configuring network protection

Page top

[Topic 203717]

Configuring access rights to application features. Role-based access control

Kaspersky Security Center Cloud Console provides facilities for role-based access to the features of Kaspersky Security Center Cloud Console and of managed Kaspersky applications.

You can configure access rights to application features for Kaspersky Security Center Cloud Console users in one of the following ways:

  • By configuring the rights for each user or group of users individually.
  • By creating standard user roles with a predefined set of rights and assigning those roles to users depending on their scope of duties.

Application of user roles is intended to simplify and shorten routine procedures of configuring users' access rights to application features. Access rights within a role are configured in accordance with the standard tasks and the users' scope of duties.

User roles can be assigned names that correspond to their respective purposes. You can create an unlimited number of roles in the application.

You can use the predefined user roles with already configured set of rights, or create new roles and configure the required rights yourself.

In this section

Access rights to application features

Predefined user roles

Assigning access rights to specific objects

Assigning access rights to users and security groups

See also:

Scenario: Configuring network protection

Page top

[Topic 203748]

Access rights to application features

The table below shows the Kaspersky Security Center Cloud Console features with the access rights to manage the associated tasks, reports, settings, and perform the associated user actions.

To perform the user actions listed in the table, a user has to have the right specified next to the action.

Read, Write, and Execute rights are applicable to any task, report, or setting. In addition to these rights, a user has to have the Perform operations on device selections right to manage tasks, reports, or settings on device selections.

The General features: Access objects regardless of their ACLs functional area is intended for audit purposes. When users are granted Read rights in this functional area, they get full Read access to all objects and are able to execute any created tasks on selections of devices connected to the Administration Server via Network Agent with local administrator rights (root for Linux). We recommend granting these rights carefully and to a limited set of users who need them to perform their official duties.

All tasks, reports, settings, and installation packages that are missing in the table belong to the General features: Basic functionality functional area.

Access rights to application features

Functional area

Right

User action: right required to perform the action

Task

Report

Other

General features: Management of administration groups

Write

  • Add device to an administration group: Write
  • Delete device from an administration group: Write
  • Add an administration group to another administration group: Write
  • Delete an administration group from another administration group: Write

None

None

None

General features: Access objects regardless of their ACLs

Read

Get read access to all objects: Read

None

None

Access is granted regardless of other rights, even if they prohibit read access to specific objects.

General features: Basic functionality

  • Read
  • Write
  • Execute
  • Perform operations on device selections
  • Device moving rules (create, modify, or delete) for the virtual Server: Write, Perform operations on device selections
  • Get Mobile (LWNGT) protocol custom certificate: Read
  • Set Mobile (LWNGT) protocol custom certificate: Write
  • Get NLA-defined network list: Read
  • Add, modify, or delete NLA-defined network list: Write
  • View Access Control List of groups: Read
  • View the Kaspersky Event Log: Read
  • "Download updates to the Administration Server repository"
  • "Deliver reports"
  • "Distribute installation package"
  • "Install application on secondary Administration Servers remotely"
  • "Report on protection status"
  • "Report on threats"
  • "Report on most heavily infected devices"
  • "Report on status of anti-virus databases"
  • "Report on errors"
  • "Report on network attacks"
  • "Summary report on mail system protection applications installed"
  • "Summary report on perimeter defense applications installed"
  • "Summary report on types of applications installed"
  • "Report on users of infected devices"
  • "Report on security issues"
  • "Report on events"
  • "Report on activity of distribution points"
  • "Report on Secondary Administration Servers"
  • "Report on Device Control events"
  • "Report on vulnerabilities"
  • "Report on prohibited applications"
  • "Report on Web Control"
  • "Report on encryption status of managed devices"
  • "Report on encryption status of mass storage devices"
  • "Report on file encryption errors"
  • "Report on blockage of access to encrypted files"
  • "Report on rights to access encrypted devices"
  • "Report on effective user permissions"
  • "Report on rights"

None

General features: Deleted objects

  • Read
  • Write
  • View deleted objects in the Recycle Bin: Read
  • Delete objects from the Recycle Bin: Write

None

None

None

General features: Event processing

  • Delete events
  • Edit event notification settings
  • Edit event logging settings
  • Write
  • Change events registration settings: Edit event logging settings
  • Change events notification settings: Edit event notification settings
  • Delete events: Delete events

None

None

Settings:

  • Virus outbreak settings: number of virus detections required to create a virus outbreak event
  • Virus outbreak settings: period of time for evaluation of virus detections
  • The maximum number of events stored in the database
  • Period of time for storing events from the deleted devices

General features: Kaspersky software deployment

  • Manage Kaspersky patches
  • Read
  • Write
  • Execute
  • Perform operations on device selections

Approve or decline installation of the patch: Manage Kaspersky patches

None

  • "Report on license key usage by virtual Administration Server"
  • "Report on Kaspersky software versions"
  • "Report on incompatible applications"
  • "Report on versions of Kaspersky software module updates"
  • "Report on protection deployment"

Installation package: "Kaspersky"

General features: License key management

  • Export key file
  • Write
  • Export key file: Export key file
  • Modify Administration Server license key settings: Write

None

None

None

General features: Enforced report management

  • Read
  • Write
  • Create reports regardless of their ACLs: Write
  • Execute reports regardless of their ACLs: Read

None

None

None

General features: Hierarchy of Administration Servers

Configure hierarchy of Administration Servers

Register, update, or delete secondary Administration Servers: Configure hierarchy of Administration Servers

None

None

None

General features: User permissions

Modify object ACLs

  • Change Security properties of any object: Modify object ACLs
  • Manage user roles: Modify object ACLs
  • Manage internal users: Modify object ACLs
  • Manage security groups: Modify object ACLs
  • Manage aliases: Modify object ACLs

None

None

None

General features: Virtual Administration Servers

  • Manage virtual Administration Servers
  • Read
  • Write
  • Execute
  • Perform operations on device selections
  • Get list of virtual Administration Servers: Read
  • Get information on the virtual Administration Server: Read
  • Create, update, or delete a virtual Administration Server: Manage virtual Administration Servers
  • Move a virtual Administration Server to another group: Manage virtual Administration Servers
  • Set administration virtual Server permissions: Manage virtual Administration Servers

None

"Report on results of installation of third-party software updates"

None

General features: Encryption Key Management

Write

Import the encryption keys: Write

None

None

None

System management: Connectivity

  • Start RDP sessions
  • Connect to existing RDP sessions
  • Initiate tunneling
  • Save files from devices to the administrator's workstation
  • Read
  • Write
  • Execute
  • Perform operations on device selections
  • Create desktop sharing session: The right to create desktop sharing session
  • Create RDP session: Connect to existing RDP sessions
  • Create tunnel: Initiate tunneling
  • Save content network list: Save files from devices to the administrator's workstation

None

"Report on device users"

None

System management: Hardware inventory

  • Read
  • Write
  • Execute
  • Perform operations on device selections
  • Get or export hardware inventory object: Read
  • Add, set or delete hardware inventory object: Write

None

  • "Report on hardware registry"
  • "Report on configuration changes"
  • "Report on hardware"

None

System management: Network access control

  • Read
  • Write
  • View CISCO settings: Read
  • Change CISCO settings: Write

None

None

None

System management: Operating system deployment

  • Deploy PXE servers
  • Read
  • Write
  • Execute
  • Perform operations on device selections
  • Deploy PXE servers: Deploy PXE servers
  • View a list of PXE servers: Read
  • Start or stop the installation process on PXE clients: Execute
  • Manage drivers for WinPE and operating system images: Write

"Create installation package upon reference device OS image"

None

Installation package: "OS Image"

System management: Vulnerability and patch management

 

 

  • Read
  • Write
  • Execute
  • Perform operations on device selections
  • View third-party patch properties: Read
  • Change third-party patch properties: Write
  • "Perform Windows Update synchronization"
  • "Install Windows Update updates"
  • "Fix vulnerabilities"
  • "Install required updates and fix vulnerabilities"

"Report on software updates"

None

System management: Remote installation

  • Read
  • Write
  • Execute
  • Perform operations on device selections
  • View third-party Vulnerability and patch management based installation package properties: Read
  • Change third-party Vulnerability and patch management based installation package properties: Write

None

None

Installation packages:

  • "Custom application"
  • "VAPM package"

System management: Software inventory

  • Read
  • Write
  • Execute
  • Perform operations on device selections

None

None

  • "Report on installed applications"
  • "Report on applications registry history"
  • "Report on status of licensed applications groups"
  • "Report on third-party software license keys"

None

See also:

Scenario: Configuring network protection

Page top

[Topic 203750]

Predefined user roles

User roles assigned to Kaspersky Security Center Cloud Console users provide them with sets of access rights to application features.

Users created on a virtual Server cannot be assigned a role on the Administration Server.

You can use the predefined user roles with already configured set of rights, or create new roles and configure the required rights yourself. Some of the predefined user roles available in Kaspersky Security Center Cloud Console can be associated with specific job positions, for example, Auditor, Security Officer, Supervisor (these roles are present in Kaspersky Security Center Cloud Console starting from the version 11). Access rights of these roles are pre-configured in accordance with the standard tasks and scope of duties of the associated positions. The table below shows how roles can be associated with specific job positions.

Examples of roles for specific job positions

Role

Comment

Auditor

Permits all operations with all types of reports, all viewing operations, including viewing deleted objects (grants the Read and Write permissions in the Deleted objects area). Does not permit other operations. You can assign this role to a person who performs the audit of your organization.

Supervisor

Permits all viewing operations; does not permit other operations. You can assign this role to a security officer and other managers in charge of the IT security in your organization.

Security Officer

Permits all viewing operations, permits reports management; grants limited permissions in the System management: Connectivity area. You can assign this role to an officer in charge of the IT security in your organization.

The table below shows the access rights assigned to each predefined user role.

Access rights of predefined user roles

Role

Description

Administration Server Administrator

Permits all operations in the following functional areas:

  • General features:
    • Basic functionality
    • Event processing
    • Hierarchy of Administration Servers
    • Virtual Administration Servers
  • System management:
    • Connectivity
    • Hardware inventory
    • Software inventory

Grants the Read and Write rights in the General features: Encryption key management functional area.

Administration Server Operator

Grants the Read and Execute rights in all of the following functional areas:

  • General features:
    • Basic functionality
    • Virtual Administration Servers
  • System management:
    • Connectivity
    • Hardware inventory
    • Software inventory

Auditor

Permits all operations in the following functional areas, in General features:

  • Access objects regardless of their ACLs
  • Deleted objects
  • Enforced report management

You can assign this role to a person who performs the audit of your organization.

Installation Administrator

Permits all operations in the following functional areas:

  • General features:
    • Basic functionality
    • Kaspersky software deployment
    • License key management
  • System management:
    • Operating system deployment
    • Vulnerability and patch management
    • Remote installation
    • Software inventory

Grants Read and Execute rights in the General features: Virtual Administration Servers functional area.

Installation Operator

Grants the Read and Execute rights in all of the following functional areas:

  • General features:
    • Basic functionality
    • Kaspersky software deployment (also grants the Manage Kaspersky patches right in this area)
    • Virtual Administration Servers
  • System management:
    • Operating system deployment
    • Vulnerability and patch management
    • Remote installation
    • Software inventory

Kaspersky Endpoint Security Administrator

Permits all operations in the following functional areas:

  • General features: Basic functionality
  • Kaspersky Endpoint Security area, including all features

Grants the Read and Write rights in the General features: Encryption key management functional area.

Kaspersky Endpoint Security Operator

Grants the Read and Execute rights in all of the following functional areas:

  • General features: Basic functionality
  • Kaspersky Endpoint Security area, including all features

Main Administrator

Permits all operations in functional areas, except for the following areas in General features:

  • Access objects regardless of their ACLs
  • Enforced report management

Grants the Read and Write rights in the General features: Encryption key management functional area.

Main Operator

Grants the Read and Execute (where applicable) rights in all of the following functional areas:

  • General features:
    • Basic functionality
    • Deleted objects
    • Operations on Administration Server
    • Kaspersky application deployment
    • Virtual Administration Servers
  • Mobile Device Management: General
  • System management, including all features
  • Kaspersky Endpoint Security area, including all features

Mobile Device Management Administrator

Permits all operations in the following functional areas:

  • General features: Basic functionality
  • Mobile Device Management: General

Mobile Device Management Operator

Grants the Read and Execute rights in the General features: Basic functionality functional area.

Grants Read and Send only information commands to mobile devices in the Mobile Device Management: General functional area.

Security Officer

 

Permits all operations in the following functional areas, in General features:

  • Access objects regardless of their ACLs
  • Enforced report management

Grants the Read, Write, Execute, Save files from devices to the administrator's workstation, and Perform operations on device selections rights in the System management: Connectivity functional area.

You can assign this role to an officer in charge of the IT security in your organization.

Senior Security Analyst

Grants the Read right in the General features: Basic functionality functional area.

Grants the Read, Write, Execute, Save files from devices to the administrator's workstation, and Perform operations on device selections rights in the System management: Connectivity functional area.

Grants the access rights to the Kaspersky Endpoint Detection and Response Expert solution.

Self Service Portal User

Permits all operations in the Mobile Device Management: Self Service Portal functional area. This feature is not supported in Kaspersky Security Center 11 and later.

Supervisor

Grants the Read right in the General features: Access objects regardless of their ACLs and General features: Enforced report management functional area.

You can assign this role to a security officer and other managers in charge of the IT security in your organization.

Vulnerability and patch management administrator

Permits all operations in the General features: Basic functionality and System management (including all features) functional areas.

Vulnerability and patch management operator

Grants the Read and Execute (where applicable) rights in the General features: Basic functionality and System management (including all features) functional areas.

See also:

Scenario: Configuring network protection

Page top

[Topic 237474]

Assigning access rights to specific objects

In addition to assigning access rights at the server level, you can configure access to specific objects, for example, to a specific task. The application allows you to specify access rights to the following object types:

  • Administration groups
  • Tasks
  • Reports
  • Device selections
  • Event selections

To assign access rights to a specific object:

  1. Depending on the object type, in the main menu, go to the corresponding section:
    • Assets (Devices) → Hierarchy of groups
    • Assets (Devices) Tasks
    • Monitoring & reporting Reports
    • Assets (Devices) → Device selections
    • Monitoring & reporting Event selections
  2. Open the properties of the object to which you want to configure access rights.

    To open the properties window of an administration group or a task, click the object name. Properties of other objects can be opened by using the button on the toolbar.

  3. In the properties window, open the Access rights section.

    The user list opens. The listed users and security groups have access rights to the object. By default, if you use a hierarchy of administration groups or Servers, the list and access rights are inherited from the parent administration group or primary Server.

  4. To be able to modify the list, enable the Use custom permissions option.
  5. Configure access rights:
    • Use the Add and Delete buttons to modify the list.
    • Specify access rights for a user or security group. Do one of the following:
      • If you want to specify access rights manually, select the user or security group, click the Access rights button, and then specify the access rights.
      • If you want to assign a user role to the user or security group, select the user or security group, click the Roles button, and then select the role to assign.
  6. Click the Save button.

The access rights to the object are configured.

See also:

Configuring access rights to application features. Role-based access control

Access rights to application features

Predefined user roles

Page top

[Topic 256412]

Assigning access rights to users and security groups

You can give users and security groups access rights to use different features of Administration Server, for example, Kaspersky Endpoint Security for Linux.

To assign access rights to a user or a security group:

  1. In the main menu, click the settings icon () next to the name of the required Administration Server.

    The Administration Server properties window opens.

  2. On the Access rights tab, select the check box next to the name of the user or the security group to whom to assign rights, and then click the Access rights button.

    You cannot select multiple users or security groups at the same time. If you select more than one item, the Access rights button will be disabled.

  3. Configure the set of rights for the user or group:
    1. Expand the node with features of Administration Server or other Kaspersky application.
    2. Select the Allow or Deny check box next to the feature or the access right that you want.

      Example 1: Select the Allow check box next to the Application integration node to grant all available access rights to the Application integration feature (Read, Write, and Execute) for a user or group.

      Example 2: Expand the Encryption key management node, and then select the Allow check box next to the Write permission to grant the Write access right to the Encryption key management feature for a user or group.

  4. After you configure the set of access rights, click OK.

The set of rights for the user or group of users will be configured.

The permissions of the Administration Server (or the administration group) are divided into the following areas:

  • General features:
    • Management of administration groups
    • Access objects regardless of their ACLs
    • Basic functionality
    • Deleted objects
    • Encryption Key Management
    • Event processing
    • Operations on Administration Server (only in the property window of Administration Server)
    • Device tags
    • Kaspersky application deployment
    • License key management
    • Application integration
    • Enforced report management
    • Hierarchy of Administration Servers
    • User permissions
    • Virtual Administration Servers
  • Mobile Device Management:
    • General
    • Self Service Portal
  • System Management:
    • Connectivity
    • Execute scripts remotely
    • Hardware inventory
    • Network Access Control
    • Operating system deployment
    • Vulnerability and patch management
    • Remote installation
    • Software inventory

If neither Allow nor Deny is selected for an access right, then the access right is considered undefined: it is denied until it is explicitly denied or allowed for the user.

The rights of a user are the sum of the following:

  • User's own rights
  • Rights of all the roles assigned to this user
  • Rights of all the security group to which the user belongs
  • Rights of all the roles assigned to the security groups to which the user belongs

If at least one of these sets of rights has Deny for a permission, then the user is denied this permission, even if other sets allow it or leave it undefined.

You can also add users and security groups to the scope of a user role to use different features of Administration Server. Settings associated with a user role will only apply only to devices that belong to users who have this role, and only if these devices belong to groups associated with this role, including child groups.

Page top

[Topic 89269]

Assigning a role to a user or a security group

To assign a role to a user or a security group:

  1. In the main menu, go to Users & rolesUsers & groups, and then select the Users or the Groups tab.
  2. Select the name of the user or the security group to whom to assign a role.

    You can select multiple names.

  3. On the menu line, click the Assign role button.

    The Role assignment wizard starts.

  4. Follow the instructions of the wizard: select the role that you want to assign to the selected users or security groups, and then select the scope of role.

    A user role scope is a combination of users and administration groups. Settings associated with a user role apply only to devices that belong to users who have this role, and only if these devices belong to groups associated with this role, including child groups.

The role with a set of rights for working with Administration Server is assigned to the user (or users, or the security group). In the list of users or security groups, a check box appears in the Has assigned roles column.

Page top

[Topic 176121]

Creating a user role

To create a user role:

  1. In the main menu, go to Users & roles → Roles.
  2. Click Add.
  3. In the New role name window that opens, enter the name of the new role.
  4. Click OK to apply the changes.
  5. In the role properties window that opens, change the settings of the role:
    • On the General tab, edit the role name.

      You cannot edit the name of a predefined role.

    • On the Settings tab, edit the role scope and policies and profiles associated with the role.
    • On the Access rights tab, edit the rights for access to Kaspersky applications.
  6. Click Save to save the changes.

The new role appears in the list of user roles.

See also:

Scenario: Configuring network protection

Page top

[Topic 176250]

Editing a user role

To edit a user role:

  1. In the main menu, go to Users & roles → Roles.
  2. Click the name of the role that you want to edit.
  3. In the role properties window that opens, change the settings of the role:
    • On the General tab, edit the role name.

      You cannot edit the name of a predefined role.

    • On the Settings tab, edit the role scope and policies and profiles associated with the role.
    • On the Access rights tab, edit the rights for access to Kaspersky applications.
  4. Click Save to save the changes.

The updated role appears in the list of user roles.

See also:

Scenario: Configuring network protection

Page top

[Topic 176256]

Editing the scope of a user role

A user role scope is a combination of users and administration groups. Settings associated with a user role apply only to devices that belong to users who have this role, and only if these devices belong to groups associated with this role, including child groups.

To add users, user groups, and administration groups to the scope of a user role, you can use either of the following methods:

Method 1:

  1. In the main menu, go to Users & rolesUsers & groups, and then select the Users or the Groups tab.
  2. Select check boxes next to the users or user groups that you want to add to the user role scope.
  3. Click the Assign role button.

    The Role assignment wizard starts. Proceed through the wizard by using the Next button.

  4. On the Select role step, select the user role that you want to assign.
  5. On the Define scope step, select the administration group that you want to add to the user role scope.
  6. Click the Assign role button to close the window.

The selected users or user groups and the selected administration group are added to the scope of the user role.

Method 2:

  1. In the main menu, go to Users & roles → Roles.
  2. Click the name of the role for which you want to define the scope.
  3. In the role properties window that opens, select the Settings tab.
  4. In the Role scope section, click Add.

    The Role assignment wizard starts. Proceed through the wizard by using the Next button.

  5. On the Define scope step, select the administration group that you want to add to the user role scope.
  6. On the Select users step, select users and user groups that you want to add to the user role scope.
  7. Click the Assign role button to close the window.
  8. Close the role properties window.

The selected users or user groups and the selected administration group are added to the scope of the user role.

Method 3:

  1. In the main menu, click the settings icon () next to the name of the required Administration Server.

    The Administration Server properties window opens.

  2. On the Access rights tab, select the check box next to the name of the user or the security group that you want to add to the user role scope, and then click the Roles button.

    You cannot select multiple users or security groups at the same time. If you select more than one item, the Roles button will be disabled.

  3. In the Roles window, select the user role that you want to assign, and then click OK and save changes.

    The selected users or security groups are added to the scope of the user role.

See also:

Scenario: Configuring network protection

Page top

[Topic 176252]

Deleting a user role

To delete a user role:

  1. In the main menu, go to Users & roles → Roles.
  2. Select the check box next to the name of the role that you want to delete.
  3. Click Delete.
  4. In the window that opens, click OK.

The user role is deleted.

See also:

Scenario: Configuring network protection

Page top

[Topic 166091]

Associating policy profiles with roles

You can associate user roles with policy profiles. In this case, the activation rule for this policy profile is based on the role: the policy profile becomes active for a user that has the specified role.

For example, the policy bars any GPS navigation software on all devices in an administration group. GPS navigation software is necessary only on a single device in the Users administration group—the device owned by a courier. In this case, you can assign a "Courier" role to its owner, and then create a policy profile allowing GPS navigation software to run only on the devices whose owners are assigned the "Courier" role. All the other policy settings are preserved. Only the user with the role "Courier" will be allowed to run GPS navigation software. Later, if another worker is assigned the "Courier" role, the new worker also can run navigation software on your organization's device. Running GPS navigation software will still be prohibited on other devices in the same administration group.

To associate a role with a policy profile:

  1. In the main menu, go to Users & roles → Roles.
  2. Click the name of the role that you want to associate with a policy profile.

    The role properties window opens with the General tab selected.

  3. Select the Settings tab, and scroll down to the Policies & profiles section.
  4. Click Edit.
  5. To associate the role with:
    • An existing policy profile—Click the chevron icon () next to the required policy name, and then select the check box next to the profile with which you want to associate the role.
    • A new policy profile:
      1. Select the check box next to the policy for which you want to create a profile.
      2. Click New policy profile.
      3. Specify a name for the new profile and configure the profile settings.
      4. Click the Save button.
      5. Select the check box next to the new profile.
  6. Click Assign to role.

The profile is associated with the role and appears in the role properties. The profile applies automatically to any device whose owner is assigned the role.

See also:

Scenario: Configuring network protection

Page top

[Topic 176021]

Creating a security group

To create a security group:

  1. In the main menu, go to Users & rolesUsers & groups, and then select the Groups tab.
  2. Click New group.
  3. In the New group window, specify the following settings for the new security group:
    • Name
    • Description
  4. Click OK to save the changes.

A new security group is added to the security group list.

See also:

Scenario: Configuring network protection

Page top

[Topic 176112]

Editing a security group

To edit a security group:

  1. In the main menu, go to Users & rolesUsers & groups, and then select the Groups tab.
  2. Click the name of the security group that you want to edit.
  3. In the group settings window that opens, change the settings of the security group:
    • On the General tab, you can change the Name and Description settings. These settings are available only for internal security groups.
    • On the Users tab, you can add users to the security group. This setting is available only for internal users and internal security groups.
    • On the Roles tab, you can assign a role to the security group.
  4. Click Save to save the changes.

The changes are applied to the security group.

See also:

Scenario: Configuring network protection

Page top

[Topic 176304]

Adding user accounts to an internal group

You can add only accounts of internal users to an internal group.

To add user accounts to an internal group:

  1. In the main menu, go to Users & rolesUsers & groups, and then select the Users tab.
  2. Select check boxes next to user accounts that you want to add to a group.
  3. Click the Assign group button.
  4. In the Assign group window that opens, select the group to which you want to add user accounts.
  5. Click the Assign button.

The user accounts are added to the group. You can also add internal users to a group by using the group settings.

See also:

Scenario: Configuring network protection

Page top

[Topic 176022]

Deleting a security group

You can delete only internal security groups.

To delete a user group:

  1. In the main menu, go to Users & rolesUsers & groups, and then select the Groups tab.
  2. Select the check box next to the user group that you want to delete.
  3. Click Delete, and then confirm the deletion in the opened window.

The user group is deleted.

See also:

Scenario: Configuring network protection

Page top

[Topic 218655]

Configuring ADFS integration

Expand all | Collapse all

To allow the users registered in Active Directory (AD) in your organization to sign in to Kaspersky Security Center Cloud Console, you must configure integration with Active Directory Federation Services (ADFS).

Kaspersky Security Center Cloud Console supports ADFS 3 (Windows Server 2016) or a later version. ADFS must be published and available on the internet. As the service communication certificate ADFS uses publicly trusted certificate.

To change ADFS integration settings, you must have the access right to change user permissions.

Before you proceed, make sure that you completed Active Directory polling.

To configure ADFS integration:

  1. In the main menu, click the settings icon () next to the name of the Administration Server.

    The Administration Server properties window opens.

  2. On the General tab, select the ADFS integration settings section.
  3. Copy the callback URL.

    You will need this URL to configure the integration in ADFS Management Console.

  4. In ADFS Management Console, add a new application group, and then add a new application by selecting the Server application template (the names of the Microsoft interface elements are provided in English.).

    ADFS Management Console generates client ID for the new application. You will need the client ID to configure the integration in Kaspersky Security Center Cloud Console.

  5. As a redirect URI, specify the callback URL that you copied in the Administration Server properties window.
  6. Generate a client secret. You will need the client secret to configure the integration in Kaspersky Security Center Cloud Console.
  7. Save the properties of the added application.
  8. Add a new application to the created application group. This time select the Web API template.
  9. On the Identifiers tab, to the Relying party identifiers list, add the client ID of the server application that you added before.
  10. On the Client Permissions tab, in the Permitted scopes list, select the allatclaims and openid scopes.
  11. On the Issuance Transform Rules tab, add a new rule by selecting the Send LDAP Attributes as Claims template:
    1. Name the rule. For example, you can name it 'Group SID'.
    2. Select Active Directory as an attribute store, and then map Token-Groups as SIDs as a LDAP attribute to 'Group SID' as an outgoing claim type.
  12. On the Issuance Transform Rules tab, add a new rule by selecting the Send Claims Using a Custom Rule template:
    1. Name the rule. For example, you can name it 'ActiveDirectoryUserSID'.
    2. In the Custom rule field, type:

      c:[Type == "http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsaccountname", Issuer == "AD AUTHORITY"] => issue(store = "Active Directory", types = ("http://schemas.microsoft.com/ws/2008/06/identity/claims/primarysid"), query = ";objectSID;{0}", param = c.Value);

  13. In Kaspersky Security Center Cloud Console, open again the ADFS integration settings section.
  14. Switch the toggle button to the ADFS integration Enabled position.
  15. Click the Settings link, and then specify the file that contains the certificate or several certificates for the federation server.
  16. Click the ADFS integration settings link, and then specify the following settings:
    • Issuer URL

      The URL address of the federation server working in your organization.

      In particular, Kaspersky Security Center Cloud Console adds '/.well-known/openid-configuration' to the issuer URL address and tries to open the resulting URL address (issuer_URL/.well-known/openid-configuration) to discover the issuer configuration automatically.

    • Client ID

      Client ID that the federation server generates to identify Kaspersky Security Center Cloud Console. You can find the Client ID in ADFS Management Console in the properties window of the server application that corresponds to Kaspersky Security Center Cloud Console.

    • Client secret

      You generate a client secret in ADFS Management Console when you specify the properties of the server application that corresponds to Kaspersky Security Center Cloud Console.

    • Domain to authenticate users from

      The members of the domain that you select will be able to sign in to Kaspersky Security Center Cloud Console with their domain account credentials. The domain names appear in the list after you complete the network polling.

    • Field name for user SID in ID token

      Name of the field that refers to the user SID in the ID token. The field name is required to identify the user in Kaspersky Security Center Cloud Console. By default, this field in the ID token is called 'primarysid'.

    • Field name for array of SIDs of user's groups in ID token

      Name of the field that refers to the array of SIDs of Active Directory security groups in which the user is included. By default, this field in the ID token is called 'groupsid'.

  17. Click the Save button.

The integration with ADFS is complete. To sign in to Kaspersky Security Center Cloud Console with an AD account credentials, use the link provided in the ADFS integration settings section (Login link to Kaspersky Security Center Cloud Console with ADFS).

When you sign in to Kaspersky Security Center Cloud Console through ADFS for the first time, the console might respond with a delay.

Page top

[Topic 271549]

Configuring integration with Microsoft Entra ID

You have to configure integration with Microsoft Entra ID to allow the users in your organization to sign in to Kaspersky Security Center Cloud Console with their Microsoft Entra ID account credentials.

Integration with Microsoft Entra ID is available for the primary Administration Server only. You cannot configure the integration for secondary or virtual Administration Servers.

To configure integration with Microsoft Entra ID:

  1. In the main menu, click the settings icon () next to the name of the Administration Server.

    The Administration Server properties window opens.

  2. On the General tab, select the Microsoft Entra ID section.
  3. Turn on the Microsoft Entra ID integration toggle button.
  4. Copy the links from the following fields:
    • Callback URL
    • Front-channel logout URL

      You will need these URLs to register Kaspersky Security Center Cloud Console in the Microsoft Entra ID tenant.

    • Login URL

      You will need this URL to allow users to sign in to the Kaspersky Security Center Cloud Console workspace with their Microsoft Entra ID credentials after the integration with Microsoft Entra ID is complete.

  5. Sign in to the Microsoft Entra admin center, and then select the tenant of your organization.

    You must have the Global administrator or the Application administrator role in the tenant.

  6. In the main menu, go to IdentityApplicationsApp registrations, and then click the New registration button.
  7. In the window that opens, do the following:
    • Specify a name for the Kaspersky Security Center Cloud Console application.
    • In the Supported account types section, select the Accounts in this organizational directory only (<tenant_name> only - Single tenant) option.
    • In the Redirect URI section, select Web from the drop-down list, and then enter the callback URL that you copied from Kaspersky Security Center Cloud Console at step 4.
  8. Click the Register button.

    The Kaspersky Security Center Cloud Console application is registered in Microsoft Entra ID, and the application overview page opens.

  9. If necessary, add Kaspersky Security Center Cloud Console to the list of applications.

    The users will be able to open Kaspersky Security Center Cloud Console by clicking its name in the list of applications in My Apps and Office 365 Launcher, without using the login URL.

  10. Copy the Application (client) ID and the Directory (tenant) ID, and save them in any convenient way.

    You will need these IDs when filling in the mandatory fields in Kaspersky Security Center Cloud Console at step 14.

  11. In the menu of the Kaspersky Security Center Cloud Console application, go to the Authentication section, and then enter the URLs that you copied from Kaspersky Security Center Cloud Console at step 4:
    • In the Web section, click the Add URI button, and then enter the login URL.
    • In the Front-channel logout URL section, enter the front-channel logout URL.
  12. In the menu of the Kaspersky Security Center Cloud Console application, go to the Certificates & secrets section, and then do the following:
    1. Go to the Client secrets tab, and then click the New client secret button.
    2. In the window that opens, specify any description for the client secret, and then select the period after which the secret expires.

    We recommend that you copy the date after which the secret expires, in any convenient way, to rotate the secrets in a timely manner.

    1. Click the Add button.

      The created secret is displayed on the Client secrets tab.

    2. Copy the information from the Value column.

      We strongly recommend that you copy the information immediately after creating the client secret.

  13. In the menu of the Kaspersky Security Center Cloud Console application, go to the Token configuration section, and then do the following:
    • Add the onprem_sid optional claim:
      1. Click the Add optional claim button.
      2. In the window that opens, select the ID token type, and then in the Claim column, select the check box next to the onprem_sid.
      3. Click the Add button.

      The onprem_sid optional claim is displayed on the Optional claims page.

    • Add the preferred_username optional claim:
      1. Click the Add optional claim button.
      2. In the window that opens, select the Access token type, and then in the Claim column, select the check box next to the preferred_username.
      3. Click the Add button.

      The preferred_username optional claim is displayed on the Optional claims page.

  14. In the menu of the Kaspersky Security Center Cloud Console application, go to the API permissions section, and then add the permissions:
    • User.Read.All
    • User.Export.All
    • GroupMember.Read.All
    • Directory.Read.All

    To add a permission, do the following:

    1. Click the Add a permission button, and then select the Microsoft APIs tab.
    2. Select Microsoft GraphApplication permissions, and then select the permission you want to add.
    3. Click the Add permission button.

      The four permissions are added and displayed on the Configured permissions page.

    4. Click the Grant admin consent for <tenant_name> button, and then in the window that opens, click Yes to confirm the granting of consent for the permissions you added.
  15. Go back to Kaspersky Security Center Cloud Console, and on the General tab, fill in the following mandatory fields:
    • Tenant ID. The Directory (tenant) ID that you copy at step 10.
    • Client ID. The Application (client) ID that you copy at step 10.
    • Client secret. The value that you copy at step 12.
  16. Click the Check connection button to check if the settings are correct, and then after the Connected status is displayed, click the Save button.

The integration settings are saved, and the integration with Microsoft Entra ID is configured.

After you configure the integration with Microsoft Entra ID, you have to do the following:

  1. In the Kaspersky Security Center Cloud Console main menu, go to Users & rolesUsers & groups to make sure that the users and groups from Microsoft Entra ID are added to Kaspersky Security Center Cloud Console.

    If the users and groups in your Microsoft Entra ID tenant are synchronized from the Active Directory of your organization, and Active Directory polling is configured, then the users and groups are already added to Kaspersky Security Center Cloud Console as a result of Active Directory polling.

    Otherwise, you have to enable and run Microsoft Entra ID polling to add the users and groups from your Microsoft Entra ID tenant to Kaspersky Security Center Cloud Console.

  2. Assign necessary roles to the users and groups.

    When assigning roles to a user on a virtual Administration Server, in the main menu, go to Users & rolesUsers & groups, and then select the Users tab. If you select the Groups tab, and then assign roles to the group where the user is a member, the user will not be able to log in to Kaspersky Security Center Cloud Console.

  3. Send the login URL that you copied at step 4 to the users. They will enter this URL to sign in to the Kaspersky Security Center Cloud Console workspace by using their Microsoft Entra ID credentials.

    When a user signs out of the Microsoft Entra ID account that was used for authentication in Kaspersky Security Center Cloud Console, and Kaspersky Security Center Cloud Console is open on a different tab or window of the same browser, the session also ends for Kaspersky Security Center Cloud Console and the user signs out of the console automatically.

    If Kaspersky Security Center Cloud Console is open in a different browser or on different devices, the session continues when the user signs out of the Microsoft Entra ID account.

To sign in to Kaspersky Security Center Cloud Console with Microsoft Entra ID account credentials, users must be able to sign in to their Microsoft Entra ID account.

Page top

[Topic 272463]

Enabling Microsoft Entra ID polling

You have to enable Microsoft Entra ID polling to add the users from your Microsoft Entra ID to Kaspersky Security Center Cloud Console.

To enable Microsoft Entra ID polling:

  1. In the main menu, click the settings icon () next to the name of the Administration Server.

    The Administration Server properties window opens.

  2. On the General tab, select the Microsoft Entra ID section.
  3. In the User discovery section, turn on the Microsoft Entra ID polling toggle button.
  4. If you want to change the default polling schedule, click the Schedule settings button, specify the polling frequency and time in the window that opens, and then click the Save button.

    Microsoft Entra ID polling will run according to the schedule that you configure.

  5. If you want to run Microsoft Entra ID polling immediately, click the Run now button.

    The users are loading. When the users are loaded, the Microsoft Entra ID polling is finished.

  6. Click the Save button.

The Microsoft Entra ID polling is complete, and the users from your Microsoft Entra ID are added to Kaspersky Security Center Cloud Console.

Page top

[Topic 273318]

Adding Kaspersky Security Center Cloud Console to the list of applications

You can allow users to open Kaspersky Security Center Cloud Console by clicking its name in the list of applications, without entering the login URL. The application list is available in My Apps and Office 365 Launcher.

To add Kaspersky Security Center Cloud Console to the list of applications:

  1. In the Microsoft Entra admin center main menu, go to IdentityApplicationsApp registrations, and then on the All applications tab, select the Kaspersky Security Center Cloud Console application that you have previously registered in Microsoft Entra ID.
  2. In the menu of Kaspersky Security Center Cloud Console, select the Branding & properties section, and then do the following:
    1. In the Home page URL field, enter the login URL.
    2. If necessary, in the Upload new logo field, add an image that will be used as the application icon in the list of applications.
    3. Click the Save button.
  3. In the Microsoft Entra admin center main menu, go to IdentityApplicationsEnterprise applications, and then select Kaspersky Security Center Cloud Console.

    The application overview page opens.

  4. In the menu of Kaspersky Security Center Cloud Console, select the Properties section, and then do the following:
    1. Set the following options to Yes:
      • Enabled for users to sign-in?

        This action is necessary only if the option is not set to Yes by default.

      • Visible to users?
    2. Click the Save button.
  5. In the menu of Kaspersky Security Center Cloud Console, select the Users and groups section, and then do the following:
    1. Click the Add user/group button, and then click the link below Users and groups.
    2. In the window that opens, select users and groups, and then click the Save button.

      The window is closed.

    3. Click the Assign button.

Kaspersky Security Center Cloud Console is available in My Apps and Office 365 Launcher for the selected users. The users can open Kaspersky Security Center Cloud Console by clicking its name in the list, without entering the login URL.

Page top

[Topic 176311]

Assigning a user as a device owner

For information about assigning a user as a mobile device owner, see Kaspersky Security for Mobile Help.

To assign a user as a device owner:

  1. If you want to assign an owner of a device connected to a virtual Administration Server, first switch to the virtual Administration Server:
    1. In the main menu, click the chevron icon (The chevron icon.) to the right of the current Administration Server name.
    2. Select the required Administration Server.
  2. In the main menu, go to Users & rolesUsers & groups, and then select the Users tab.

    A user list opens. If you are currently connected to a virtual Administration Server, the list includes users from the current virtual Administration Server and the primary Administration Server.

  3. Click the name of the user account that you want to assign as a device owner.
  4. In the user settings window that opens, select the Devices tab.
  5. Click Add.
  6. From the device list, select the device that you want to assign to the user.
  7. Click OK.

The selected device is added to the list of devices assigned to the user.

You can perform the same operation at Assets (Devices)Managed devices, by clicking the name of the device that you want to assign, and then clicking the Manage device owner link.

See also:

Scenario: Configuring network protection

Page top

[Topic 267905]

Assigning a user as a Linux device owner after installation of Network Agent

To allow the user to register as a Linux device owner:

  1. In the Kaspersky Security Center Cloud Console, go to Discovery & deploymentDeployment & assignmentInstallation packages.

    The list of installation packages opens.

  2. Click on the installation package of Network Agent.

    The properties window of the installation package opens.

  3. In the installation package properties window, click SettingsAdvanced.
  4. In the User registration as a device owner (Linux only) section, turn on the Allow running the user registration utility after Network Agent installation option and click Save.

The utility for registering the user as a device owner can be run via the command line on the client device.

To register a user as a Linux device owner on the client device:

  1. Execute the following command in the command line on the client device:
    $ /opt/kaspersky/klnagent64/bin/nagregister -set_owner
  2. Enter the login and password, if prompted.

    If the login and the password are included in the answer file or installation package of Network Agent, execute the following command in the command line on the client device:
    $ /opt/kaspersky/klnagent64/bin/nagregister -set_owner -unattended

If the user is included in an internal security group, the login must contain the user name.

If the user is included in an Active Directory security group, the login must contain the user name and domain name.

If two-step verification is turned on for the user, you have to enter the time-based one-time password (TOTP) from the app.

The user will be registered as a device owner.

Page top

[Topic 145580]

Managing object revisions

This section contains information about object revision management. Kaspersky Security Center Cloud Console allows you to track object modification. Every time you save changes made to an object, a revision is created. Each revision has a number.

Objects that support revision management include:

  • Administration Server properties
  • Policies
  • Tasks
  • Administration groups
  • User accounts
  • Installation packages

You can perform the following actions on object revisions:

In the properties window of any object that supports revision management, the Revision history section displays a list of object revisions with the following details:

  • Revision—Object revision number.
  • Time—Date and time the object was modified.
  • User—Name of the user who modified the object.
  • User device IP address—IP address of the device from which the object was modified.
  • Web Console IP address—IP address of Kaspersky Security Center Cloud Console with which the object was modified.
  • Action—Action performed on the object.
  • DescriptionDescription of the revision related to the change made to the object settings.

    By default, the object revision description is blank. To add a description to a revision, select the relevant revision and click the Edit description button. In the opened window, enter some text for the revision description.

In this section

Rolling back changes

Adding a revision description

Viewing and saving a policy revision

See also:

Scenario: Configuring network protection

Page top

[Topic 145598]

Rolling back changes

You can roll back changes made to an object, if necessary. For example, you may have to revert the settings of a policy to their state on a specific date.

To roll back changes made to an object:

  1. In the object's properties window, open the Revision history tab.
  2. In the list of object revisions, select the number of the revision to which you have to roll back changes.
  3. Click the Roll back button.
  4. Click OK to confirm the operation.

The object is now rolled back to the selected revision. The list of object revisions displays a record of the action that was taken. The revision description displays information about the number of the revision to which you reverted the object.

See also:

Managing object revisions

Scenario: Configuring network protection

Page top

[Topic 147001]

Adding a revision description

You can add a description for the revision to simplify the search for revisions in the list.

To add a description for a revision:

  1. In the object's properties window, open the Revision history tab.
  2. In the list of object revisions, select the revision for which you need to add a description.
  3. Click the Edit description button.

    The Description window opens.

  4. In the Description window, enter some text for the revision description.

    By default, the object revision description is blank.

  5. Save the revision description.

The description is added for the revision of the object.

See also:

Managing object revisions

Scenario: Configuring network protection

Page top

[Topic 274565]

Viewing and saving a policy revision

Kaspersky Security Center Cloud Console allows you to view which modifications were made to a policy over a certain period, as well as save information about these modifications in a file.

Viewing and saving a policy revision are available if the corresponding management web plug-in supports this functionality.

To view a policy revision:

  1. In the main menu, go to Assets (Devices)Policies & profiles.
  2. Click the policy for the revision that you want to view, and then go to the Revision history section.
  3. In the list of policy revisions, click the number of the revision that you want to view.

    If the revision size is more than 10 MB, you will not be able to view it by using Kaspersky Security Center Cloud Console. You will be prompted to save the selected revision to a JSON file.

    If the revision size does not exceed 10 MB, a report in the HTML format with the settings of the selected policy revision is displayed. Since the report is displayed in a pop-up window, ensure that pop-ups are allowed in your browser.

To save a policy revision to a JSON file,

In the list of policy revisions, select the revision that you want to save, and then click Save to file.

The revision is saved to a JSON file.

Page top

[Topic 89310]

Kaspersky Security Network (KSN)

This section describes how to use an online service infrastructure named Kaspersky Security Network (KSN). The section provides the details on KSN, as well as instructions on how to enable KSN, configure access to KSN, and view the statistics of the use of KSN proxy server.

Updates functionality (including providing anti-virus signature updates and codebase updates), as well as KSN functionality may not be available in the software in the U.S.

In this section

About KSN

Enabling and disabling KSN

Viewing the accepted KSN Statement

Accepting an updated KSN Statement

Checking whether the distribution point works as KSN proxy server

Page top

[Topic 89311]

About KSN

Kaspersky Security Network (KSN) is an online service infrastructure that provides access to the online Knowledge Base of Kaspersky, which contains information about the reputation of files, web resources, and software. The use of data from Kaspersky Security Network ensures faster responses by Kaspersky applications to threats, improves the effectiveness of some protection components, and reduces the risk of false positives. KSN enables you to use Kaspersky reputation databases to retrieve information about applications installed on client devices.

If you participate in KSN, you agree to send to Kaspersky, in automatic mode, information about the operation of Kaspersky applications installed on client devices that are managed through Kaspersky Security Center Cloud Console. Information is transferred in accordance with the current KSN access settings. Kaspersky analysts additionally analyze received information, and include it in the reputation and statistical databases of Kaspersky Security Network.

The application prompts you to join KSN while running the Quick Start Wizard. You can start or stop using KSN at any moment when using the application.

You use KSN in accordance with the KSN Statement that you read and accept when you enable KSN. If the KSN Statement is updated, it is displayed to you when you update or upgrade Administration Server. You can accept the updated KSN Statement or decline it. If you decline it, you keep using KSN in accordance with the previous version of KSN Statement that you accepted before.

When KSN is enabled, Kaspersky Security Center Cloud Console checks if the KSN servers are accessible. If access to the servers using system DNS is not possible, the application uses public DNS servers. This is necessary to make sure the level of security is maintained for the managed devices.

Client devices managed by the Administration Server interact with KSN through KSN proxy server. KSN proxy server provides the following features:

  • Client devices can send requests to KSN and transfer information to KSN even if they do not have direct access to the internet.
  • The KSN proxy server caches processed data, thus reducing the load on the outbound channel and the time period spent for waiting for information requested by a client device.

You can enable KSN proxy server on the distribution point side to make the device act as a KSN proxy server. In this case, the KSN proxy service (ksnproxy) is run on the device.

Page top

[Topic 213009]

Enabling and disabling KSN

To enable KSN:

  1. In the main menu, click the settings icon () next to the name of the required Administration Server.

    The Administration Server properties window opens.

  2. On the General tab, select the KSN settings section.
  3. Switch the toggle button to the Use Kaspersky Security Network Enabled position.

    KSN is enabled.

    If the toggle button is enabled, client devices send patch installation results to Kaspersky. When enabling this toggle button, you should read and accept the terms of the KSN Statement.

  4. Click the Save button.

To disable KSN:

  1. In the main menu, click the settings icon () next to the name of the required Administration Server.

    The Administration Server properties window opens.

  2. On the General tab, select the KSN settings section.
  3. Switch the toggle button to the Use Kaspersky Security Network Disabled position.

    KSN is disabled.

    If this toggle button is disabled, client devices will send no patch installation results to Kaspersky.

  4. Click the Save button.
Page top

[Topic 213010]

Viewing the accepted KSN Statement

When you enable Kaspersky Security Network (KSN), you must read and accept the KSN Statement. You can view the accepted KSN Statement at any time.

To view the accepted KSN Statement:

  1. In the main menu, click the settings icon () next to the name of the Administration Server.

    The Administration Server properties window opens.

  2. On the General tab, select the KSN settings section.
  3. Click the View Kaspersky Security Network Statement link.

In the window that opens, you can view the text of the accepted KSN Statement.

Page top

[Topic 213147]

Accepting an updated KSN Statement

You use KSN in accordance with the KSN Statement that you read and accept when you enable KSN. If the KSN Statement is updated, it is automatically displayed when you open Kaspersky Security Center Cloud Console. You can accept the updated KSN Statement or decline it. If you decline it, you will continue using KSN in accordance with the version of the KSN Statement that you previously accepted. You can view and accept the updated KSN Statement later.

To view, and then accept or decline an updated KSN Statement:

  1. Click the View notifications link in the upper-right corner of the main application window.

    The Notifications window opens.

  2. Click the View the updated KSN Statement link.

    The Kaspersky Security Network Statement update window opens.

  3. Read the KSN Statement, and then make your decision by clicking one of the following buttons:
    • I accept the updated KSN Statement
    • Use KSN under the old Statement

Depending on your choice, KSN keeps working in accordance with the terms of the current or updated KSN Statement. You can view the text of the accepted KSN Statement in the properties of Administration Server at any time.

Page top

[Topic 178325]

Checking whether the distribution point works as KSN proxy server

On a managed device assigned to work as a distribution point, you can enable KSN proxy server. A managed device works as KSN proxy server when the ksnproxy service is running on the device. You can check, turn on, or turn off this service on the device locally.

You can assign a Windows-based or a Linux-based device as a distribution point. The method of distribution point checking depends on the operating system of this distribution point.

To check whether the Windows-based distribution point works as KSN proxy server:

  1. On the distribution point device, in Windows, open Services (All ProgramsAdministrative Tools Services).
  2. In the list of services, check whether the ksnproxy service is running.

    If the ksnproxy service is running, then Network Agent on the device participates in Kaspersky Security Network and works as KSN proxy server for the managed devices included in the scope of the distribution point.

If you want, you may turn off the ksnproxy service. In this case, Network Agent on the distribution point stops participating in Kaspersky Security Network. This requires local administrator rights.

To check whether the Linux-based distribution point works as KSN proxy server:

  1. On the distribution point device, display the list of running processes.
  2. In the list of running processes, check whether the /opt/kaspersky/ksc64/sbin/ksnproxy process is running.

If /opt/kaspersky/ksc64/sbin/ksnproxy process is running, then Network Agent on the device participates in Kaspersky Security Network and works as the KSN proxy server for the managed devices included in the scope of the distribution point.

Page top

[Topic 171696]

Deletion of objects

You can delete objects, including the following:

  • Policies
  • Tasks
  • Installation packages
  • Virtual Administration Servers
  • Users
  • Security groups
  • Administration groups

When you delete an object, information about it remains in the database. The storage term for information about the deleted objects is the same as the storage term for object revisions (the recommended term is 90 days). You can change the storage term only if you have the Modify permission in the Deleted objects area of rights.

About deletion of client devices

When you delete a managed device from an administration group, the application moves the device to the Unassigned devices group. After device deletion, the installed Kaspersky applications—Network Agent and any security application, for example Kaspersky Endpoint Security—remain on the device.

Kaspersky Security Center Cloud Console handles the devices in the Unassigned devices group according to the following rules:

  • If you have configured device moving rules and a device meets the criteria of a moving rule, the device is automatically moved to an administration group according to the rule.
  • The device is stored in the Unassigned devices group and automatically removed from the group according to the device retention rules.

    The device retention rules do not affect the devices that have one or more drives encrypted with full disk encryption. Such devices are not deleted automatically—you can only delete them manually. If you need to delete a device with an encrypted drive, first decrypt the drive, and then delete the device.

    When you delete a device with encrypted drive, the data required to decrypt the drive is also deleted. If you select the I understand the risk and want to delete device(s) check box in the confirmation window that opens when you delete such devices (either from the Unassigned devices or the Managed Devices group), it means that you are aware of the subsequent data deletion.

    To decrypt the drive, the following conditions must be met:

    • The device is reconnected to Administration Server to restore the data required to decrypt the drive.
    • The device user remembers the decryption password.
    • The security application that was used to encrypt the drive, for example Kaspersky Endpoint Security for Windows, is still installed on the device.

    If the drive was encrypted by Kaspersky Disk Encryption technology, you can also try recovering data by using the FDERT Restore Utility.

When you delete a device from the Unassigned devices group manually, the application removes the device from the list. After device deletion, the installed Kaspersky applications (if any) remain on the device. Then, if the device is still visible to Administration Server and you have configured regular network polling, Kaspersky Security Center Cloud Console discovers the device during the network polling and adds it back to the Unassigned devices group. Therefore, it is reasonable to delete a device manually only if the device is invisible to Administration Server.

See also:

Scenario: Configuring network protection

Page top

[Topic 180689]

Scenario: Regular updating of Kaspersky databases and applications

This section provides a scenario for regular updating of Kaspersky databases, software modules, and applications. After you complete the Configuring network protection scenario, you must maintain the reliability of the protection system. This maintenance ensures that protection of the managed devices remains firm against a range of threats, including viruses, network attacks, and phishing attacks.

There are several schemes that you can use to install updates to Kaspersky Security Center Cloud Console components and security applications. Choose one or more schemes that meet the requirements of your network best.

The scenario below describes the update scheme that implies downloading updates to the distribution point repositories. If the managed devices do not have a connection to the distribution points, consider updating Kaspersky databases, software modules, and applications manually or directly from the Kaspersky update servers.

When you complete this scenario, the following results occur:

  • Kaspersky Security Center Cloud Console components are updated automatically or only when you designate the Approved status for the updates.
  • Kaspersky security applications, Kaspersky databases, and software modules are updated according to the schedule that you specified. By default, Kaspersky security applications install only those updates that you approve.

You can configure the update process to download and install updates in either of two ways:

  • Automatically

    In this case you have to perform this scenario only once. You will have to schedule the Download updates to the repositories of distribution points task (if any) and the Update tasks for the Kaspersky security applications, and keep the default update settings that are in the Network Agent properties.

  • Manually

    You can configure the update process to run the Download updates to the repositories of distribution points task (if any) and the Update tasks for the Kaspersky security applications manually. You can also configure Network Agent to install updates for the Kaspersky Security Center Cloud Console components only when you designate the Approved status for the updates.

Prerequisites

Before you start, make sure that you have done the following:

  1. Deployed the Kaspersky security applications to the managed devices according to the scenario of deploying Kaspersky applications through Kaspersky Security Center Cloud Console. When performing that scenario, you assigned an appropriate amount of distribution points in accordance with the number of managed devices and the network topology.
  2. Created and configured all required policies, policy profiles, and tasks according to the scenario of configuring network protection.

Stages

Configuration of regular updating of Kaspersky databases and applications proceeds in stages:

  1. Creating the task for downloading updates to the repositories of distribution points

    Create the Download updates to the repositories of distribution points task. When this task is run, Kaspersky Security Center Cloud Console downloads the updates to the distribution points directly from Kaspersky update servers.

    How-to instructions: Creating the task for downloading updates to the repositories of distribution points

  2. Configuring distribution points

    Make sure that the Deploy updates option is enabled in the properties of all required distribution points. When this option is disabled for a distribution point, the devices included in the scope of the distribution point can download updates only from a local resource or directly from Kaspersky update servers.

    If you want the managed devices to receive updates only from the distribution points, enable the Distribute files through distribution points only option in the Network Agent policy.

  3. Optimizing the update process by using diff files (optional)

    Enabling this feature results in decrease in the traffic between the distribution points and the managed devices. To use this feature, enable the Download diff files option in the properties of the Download updates to the repositories of distribution points task.

    How-to instructions: Using diff files for updating Kaspersky databases and software modules

  4. Defining which updates to install

    By default, the downloaded software updates have the Undefined status. Change the status to Approved or Declined to define if this update should be installed on networked devices. The approved updates are always installed. The undefined updates can only be installed on Network Agent and other Kaspersky Security Center Cloud Console components in accordance with the Network Agent policy settings. The updates for which you set Declined status will not be installed on devices.

    How-to instructions:

  5. Configuring automatic installation of updates and patches for Kaspersky Security Center Cloud Console components

    By default, the downloaded updates and patches for Network Agent and other Kaspersky Security Center Cloud Console components are installed automatically. If you have left the Automatically install applicable updates and patches for components that have the Undefined status option enabled in the Network Agent properties, then all updates will be installed automatically after they are downloaded to the repository (or several repositories). If this option is disabled, Kaspersky patches that have been downloaded and tagged with the Undefined status will be installed only after you change their status to Approved.

    How-to instructions: Enabling and disabling automatic updating and patching for Kaspersky Security Center Cloud Console components

  6. Configuring automatic installation of updates for the security applications

    Create the Update tasks for the managed applications to provide timely updates to the applications, software modules and Kaspersky databases, including anti-virus databases. We recommend that you select the When new updates are downloaded to the repository option when configuring the task schedule. This will ensure that new updates are installed as soon as possible.

    By default, updates for the managed applications are installed only after you change the update status to Approved. For Kaspersky Endpoint Security for Windows, you can change the update settings in the Update task.

    If an update requires reviewing and accepting the terms of the End User License Agreement, then you first need to accept the terms. After that the update can be propagated to the managed devices.

    How-to instructions: Automatic installation of Kaspersky Endpoint Security updates on devices

  7. Approving and declining updates of managed Kaspersky applications

    By default, the downloaded software updates have the Undefined status. You can change the status to Approved or Declined. The approved updates are always installed. If an update of a managed Kaspersky application requires reviewing and accepting the terms of the End User License Agreement, then you first need to accept the terms. After that the update can be propagated to the managed devices. The updates for which you set Declined status will not be installed on devices. If a declined update for a managed application was previously installed, Kaspersky Security Center Cloud Console will try to uninstall the update from all devices.

    Approving and declining updates is available only for Network Agent and managed Kaspersky applications installed on the Windows-based and Linux-based client devices. Seamless updating of Administration Server, Kaspersky Security Center Cloud Console, and management web plug-ins is not supported.

    How-to instructions: Approving and declining software updates

Upon completion of the scenario, you can proceed to monitoring the network status.

Page top

[Topic 46875]

About updating Kaspersky databases, software modules, and applications

To be sure that the protection of your managed devices is up-to-date, you must provide timely updates of the following:

  • Kaspersky databases and software modules

    Before downloading Kaspersky databases and software modules, Kaspersky Security Center Cloud Console checks if Kaspersky servers are accessible. If access to the servers using system DNS is not possible, the application uses public DNS servers. This is necessary to make sure anti-virus databases are updated and the level of security is maintained for the managed devices.

  • Installed Kaspersky applications, including Kaspersky Security Center Cloud Console components and security applications

    Kaspersky Security Center Cloud Console allows you to update Network Agent and Kaspersky applications installed on Windows-based and Linux-based client devices automatically. Seamless updating of Administration Server, Kaspersky Security Center Cloud Console, and management web plug-ins is not supported. To update these components, you have to download the latest versions from the Kaspersky website, and then install them manually.

Depending on the configuration of your network, you can use the following schemes of downloading and distributing the required updates to the managed devices:

  • Using the Download updates to the repositories of distribution points task
  • Manually through a local folder, a shared folder, or an FTP server
  • Directly from Kaspersky update servers to the security applications on the managed devices

Using the Download updates to the repositories of distribution points task

In this scheme, Kaspersky Security Center Cloud Console downloads updates through the Download updates to the repositories of distribution points task. The managed devices included in the scope of a distribution point download the updates from the repository of the distribution point (see figure below).

Distribution point devices running macOS cannot download updates from Kaspersky update servers.

If one or more devices running macOS are within the scope of the Download updates to the repositories of distribution points task, the task completes with the Failed status, even if it has successfully completed on all Windows devices.

Updating hosted distribution points.

Updating by using the Download updates to the repositories of distribution points task

When the Download updates to the repositories of distribution points task is complete, the following updates are downloaded to the distribution point repository:

Each Kaspersky application requests required updates from Administration Server. Administration Server aggregates these requests and downloads to the distribution point repositories only those updates that are requested by any application. This ensures that the same updates are not downloaded multiple times and that unnecessary updates are not downloaded at all. When running the Download updates to the repositories of distribution points task, Administration Server sends the following information to Kaspersky update servers automatically in order to ensure the downloading of relevant versions of Kaspersky databases and software modules:

  • Application ID and version
  • Application installation ID
  • Active key ID
  • Download task run ID

None of the transmitted information contains personal or other confidential data. AO Kaspersky Lab protects information in accordance with requirements established by law.

Manually through a local folder, a shared folder, or an FTP server

If the client devices do not have a connection to a distribution point, you can use a local folder or a shared resource as a source for updating Kaspersky databases, software modules, and applications. In this scheme, you have to copy required updates from a distribution point repository to a removable drive, and then copy the updates to the local folder or the shared resource specified as an update source in the settings of Kaspersky Endpoint Security for Windows (see figure below).

Update using a local folder or a shared resource.

Updating through a local folder, a shared folder, or an FTP server

Directly from Kaspersky update servers to Kaspersky Endpoint Security for Windows on the managed devices

On the managed devices, you can configure Kaspersky Endpoint Security for Windows to receive updates directly from Kaspersky update servers (see figure below).

Direct update from update servers.

Updating security applications directly from Kaspersky update servers

In this scheme, the security application does not use the repositories provided by Kaspersky Security Center Cloud Console. To receive updates directly from Kaspersky update servers, specify Kaspersky update servers as an update source in the interface of the security application. For a full description of these settings, please refer to the Kaspersky Endpoint Security for Windows documentation.

See also:

Scenario: Regular updating of Kaspersky databases and applications

Page top

[Topic 180731]

Creating the task for downloading updates to the repositories of distribution points

Expand all | Collapse all

Distribution point devices running macOS cannot download updates from Kaspersky update servers.

If one or more devices running macOS are within the scope of the Download updates to the repositories of distribution points task, the task completes with the Failed status, even if it has successfully completed on all Windows devices.

You can create the Download updates to the repositories of distribution points task for an administration group. This task will run for distribution points included in the specified administration group.

This task is required to download updates from Kaspersky update servers to the repositories of distribution points. The list of updates includes:

  • Updates to databases and software modules for Kaspersky security applications
  • Updates to Kaspersky Security Center Cloud Console components
  • Updates to Kaspersky security applications

After the updates are downloaded, they can be propagated to the managed devices.

To create the Download updates to the repositories of distribution points task, for a selected administration group:

  1. In the main menu, go to Assets (Devices) → Tasks.
  2. Click the Add button.

    The New task wizard starts. Follow the steps of the wizard.

  3. For the Kaspersky Security Center Cloud Console application, in the Task type field select Download updates to the repositories of distribution points.
  4. Specify the name for the task that you are creating. A task name cannot be more than 100 characters long and cannot include any special characters ("*<>?\:|).
  5. Select an option button to specify the administration group, the device selection, or the devices to which the task applies.
  6. At the Finish task creation step, if you enable the Open task details when creation is complete option, you can modify the default task settings. If you do not enable this option, the task is created with the default settings. You can modify the default settings later, at any time.
  7. Click the Create button.

    The task is created and displayed in the list of tasks.

  8. Click the name of the created task to open the task properties window.
  9. On the Application settings tab of the task properties window, specify the following settings:
    • Sources of updates

      The following resources can be used as a source of updates for the distribution point:

      • Kaspersky update servers

        HTTP(S) servers at Kaspersky from which Kaspersky applications download database and application module updates.

        This option is selected by default.

      • Primary Administration Server

        This resource applies to tasks created for a secondary or virtual Administration Server.

      • Local or network folder

        A local or network folder that contains the latest updates. A network folder can be an FTP or HTTP server, or an SMB share. If a network folder requires authentication, only the SMB protocol is supported. When selecting a local folder, you must specify a folder on the device that has Administration Server installed.

        An FTP or HTTP server or a network folder used by an update source must contain a folders structure (with updates) that matches the structure created when using Kaspersky update servers.

    • Folder for storing updates

      The path to the specified folder for storing saved updates. You can copy the specified folder path to a clipboard. You cannot change the path to a specified folder for a group task.

    • Download diff files

      This option enables the downloading diff files feature.

      By default, this option is disabled.

    • Download updates by using the old scheme

      Kaspersky Security Center Cloud Console downloads updates of databases and software modules by using the new scheme. For the application to download updates by using the new scheme, the update source must contain the update files with the metadata compatible with the new scheme. If the update source contains the update files with the metadata compatible with the old scheme only, enable the Download updates by using the old scheme option. Otherwise, the update download task will fail.

      For example, you must enable this option when a local or network folder is specified as an update source and the update files in this folder were downloaded by one of the following applications:

      • Kaspersky Update Utility

        This utility downloads updates by using the old scheme.

      • Kaspersky Security Center 13.2 or earlier version

      For example, a distribution point is configured to take the updates from a local or network folder. In this case, you may download updates by using an Administration Server that has an internet connection, and then place the updates to the local folder on the distribution point. If the Administration Server has version 13.2 or earlier, enable the Download updates by using the old scheme option in the Download updates to the repositories of distribution points task.

      By default, this option is disabled.

  10. Create a schedule for task start. If necessary, specify the following settings:
    • Start task

      Select the schedule according to which the task runs, and configure the selected schedule.

      • Manually (selected by default)

        The task does not run automatically. You can only start it manually.

        By default, this option is selected.

      • Every N minutes

        The task runs regularly, with the specified interval in minutes, starting from the specified time on the day that the task is created.

        By default, the task runs every 30 minutes, starting from the current system time.

      • Every N hours

        The task runs regularly, with the specified interval in hours, starting from the specified date and time.

        By default, the task runs every 6 hours, starting from the current system date and time.

      • Every N days

        The task runs regularly, with the specified interval in days. Additionally, you can specify a date and time of the first task run. These additional options become available, if they are supported by the application for which you create the task.

        By default, the task runs every day, starting from the current system date and time.

      • Every N weeks

        The task runs regularly, with the specified interval in weeks, on the specified day of week and at the specified time.

        By default, the task runs every Monday at the current system time.

      • Daily (daylight saving time is not supported)

        The task runs regularly, with the specified interval in days. This schedule does not support observance of daylight saving time (DST). It means that when clocks jump one hour forward or backward at the beginning or ending of DST, the actual task start time does not change.

        We do not recommend that you use this schedule. It is needed for backward compatibility of Kaspersky Security Center Cloud Console.

        By default, the task starts every day at the current system time.

      • Weekly

        The task runs every week on the specified day and at the specified time.

      • By days of week

        The task runs regularly, on the specified days of the week, at the specified time.

        By default, the task runs every Friday at 6:00:00 PM.

      • Monthly

        The task runs regularly, on the specified day of the month, at the specified time.

        In months that lack the specified day, the task runs on the last day.

        By default, the task runs on the first day of each month, at the current system time.

      • Every month on specified days of selected weeks

        The task runs regularly, on the specified days of each month, at the specified time.

        By default, no days of month are selected. The default start time is 18:00.

      • On virus outbreak

        The task runs after a Virus outbreak event occurs. Select application types that will monitor virus outbreaks. The following application types are available:

        • Anti-virus for workstations and file servers
        • Anti-virus for perimeter defense
        • Anti-virus for mail systems

        By default, all application types are selected.

        You may want to run different tasks depending on the security application type that reports a virus outbreak. In this case, remove the selection of the application types that you do not need.

      • On completing another task

        The current task starts after another task completes. This parameter only works if both tasks are assigned to the same devices. For example, you may want to run the Manage devices task with the Turn on the device option and, after it completes, run the Virus scan task as a triggering task.

        You have to select the triggering task from the table and the status with which this task must complete (Completed successfully or Failed).

        If necessary, you can search, sort, and filter the tasks in the table as follows:

        • Enter the task name in the search field, to search the task by its name.
        • Click the sort icon to sort the tasks by name.

          By default, the tasks are sorted in alphabetical ascending order.

        • Click the filter icon, and in the window that opens, filter the tasks by group, and then click the Apply button.
    • Run missed tasks

      This option determines the behavior of a task if a client device is not visible on the network when the task is about to start.

      If this option is enabled, the system attempts to start the task the next time the Kaspersky application is run on the client device. If the task schedule is Manually, Once or Immediately, the task is started immediately after the device becomes visible on the network or immediately after the device is included in the task scope.

      If this option is disabled, only scheduled tasks run on client devices. For Manually, Once and Immediately schedule, tasks run only on those client devices that are visible on the network. For example, you may want to disable this option for a resource-consuming task that you want to run only outside of business hours.

      By default, this option is disabled.

    • Use automatically randomized delay for task starts

      If this option is enabled, the task is started on client devices randomly within a specified time interval, that is, distributed task start. A distributed task start helps to avoid a large number of simultaneous requests by client devices to the Administration Server when a scheduled task is running.

      The distributed start time is calculated automatically when a task is created, depending on the number of client devices to which the task is assigned. Later, the task is always started on the calculated start time. However, when task settings are edited or the task is started manually, the calculated value of the task start time changes.

      If this option is disabled, the task starts on client devices according to the schedule.

    • Use automatically randomized delay for task starts within an interval of

      If this option is enabled, the task is started on client devices randomly within the specified time interval. A distributed task start helps to avoid a large number of simultaneous requests by client devices to the Administration Server when a scheduled task is running.

      If this option is disabled, the task starts on client devices according to the schedule.

      By default, this option is disabled. The default time interval is one minute.

  11. Click the Save button.

The task is created and configured.

In addition to the settings that you specify during task creation, you can change other properties of a created task.

When the Download updates to the repositories of distribution points task is performed, updates for databases and software modules are downloaded from the update source and stored in the shared folder. Downloaded updates will only be used by distribution points that are included in the specified administration group and that have no update download task explicitly set for them.

See also:

Scenario: Regular updating of Kaspersky databases and applications

Page top

[Topic 188882]

Configuring managed devices to receive updates only from distribution points

Managed devices can retrieve updates of Kaspersky databases, software modules, and Kaspersky applications from various sources: directly from update servers, from distribution points, or from a local or network folder. You can specify distribution points as the only possible source of updates.

To configure managed devices to receive updates only from distribution points:

  1. In the main menu, go to Assets (Devices)Policies & profiles.
  2. Click the Network Agent policy.
  3. In the policy properties window, open the Application settings tab.
  4. In the Settings section, turn on the Distribute files through distribution points only toggle button.
  5. Set the lock (The lock icon.) for this toggle button.
  6. Click the Save button.

The policy will be applied to the selected devices, and the devices will receive updates only from distribution points.

See also:

Scenario: Regular updating of Kaspersky databases and applications

Page top

[Topic 180747]

Enabling and disabling automatic updating and patching for Kaspersky Security Center Cloud Console components

Automatic installation of updates and patches for Kaspersky Security Center Cloud Console components is enabled by default during Network Agent installation on the device. You can disable it during Network Agent installation, or you can disable it later by using a policy.

To disable automatic updating and patching for Kaspersky Security Center Cloud Console components during local installation of Network Agent on a device:

  1. Start local installation of Network Agent on the device.
  2. At the Advanced settings step, clear the Automatically install applicable updates and patches for components that have Undefined status check box.
  3. Follow the instructions of the wizard.

Network Agent with disabled automatic updating and patching for Kaspersky Security Center Cloud Console components will be installed on the device. You can enable automatic updating and patching later by using a policy.

To disable automatic updating and patching for Kaspersky Security Center Cloud Console components during Network Agent installation on the device through an installation package:

  1. In the main menu, go to OperationsRepositories → Installation packages.
  2. Click the Kaspersky Security Center Network Agent <version number> package.
  3. In the properties window, select the Settings tab.
  4. Turn off the Automatically install applicable updates and patches for components that have the Undefined status toggle button.

Network Agent with disabled automatic updating and patching for Kaspersky Security Center Cloud Console components will be installed from this package. You can enable automatic updating and patching later by using a policy.

If the check box in step 4 was selected (or cleared) during Network Agent installation on the device, you can subsequently enable (or disable) automatic updating by using the Network Agent policy.

To enable or disable automatic updating and patching for Kaspersky Security Center Cloud Console components by using the Network Agent policy:

  1. In the main menu, go to Assets (Devices)Policies & profiles.
  2. Click the Network Agent policy.
  3. In the policy properties window, select the Application settings tab.
  4. In the Manage patches and updates section, turn on or off the Automatically install applicable updates and patches for components that have the Undefined status toggle button to enable or disable, respectively, automatic updating and patching.
  5. Make sure to set (Enforce) the lock (The lock icon.) for this toggle button.

The policy will be applied to the selected devices, and automatic updating and patching for Kaspersky Security Center Cloud Console components will be enabled (or disabled) on these devices.

See also:

Scenario: Regular updating of Kaspersky databases and applications

Page top

[Topic 180749]

Automatic installation of updates for Kaspersky Endpoint Security for Windows

You can configure automatic updates of databases and software modules of Kaspersky Endpoint Security for Windows on client devices.

To configure download and automatic installation of updates of Kaspersky Endpoint Security for Windows on devices:

  1. In the main menu, go to Assets (Devices) Tasks.
  2. Click the Add button.

    The New task wizard starts. Follow the steps of the wizard.

  3. For the Kaspersky Endpoint Security for Windows application, select Update as the task subtype.
  4. Specify the name for the task that you are creating. A task name cannot be more than 100 characters long and cannot include any special characters ("*<>?\:|).
  5. Choose the task scope.
  6. Specify the administration group, the device selection, or the devices to which the task applies.
  7. At the Finish task creation step, if you enable the Open task details when creation is complete option, you can modify the default task settings. If you do not enable this option, the task is created with the default settings. You can modify the default settings later, at any time.
  8. Click the Create button.

    The task is created and displayed in the list of tasks.

  9. Click the name of the created task to open the task properties window.
  10. On the Application settings tab of the task properties window, define the update task settings in local or mobile mode:
    • Local mode: The settings on this tab define how the device receives updates when connection is established between the device and the Administration Server.
    • Mobile mode: The settings on this tab define how the device receives updates when no connection is established between Kaspersky Security Center Cloud Console and the device (for example, when the device is not connected to the internet).
  11. Enable the update sources that you want to use to update databases and application modules for Kaspersky Endpoint Security for Windows. If required, change the positions of the sources in the list by using the Move up and Move down buttons. If several update sources are enabled, Kaspersky Endpoint Security for Windows tries to connect to them one after another, starting from the top of the list, and performs the update task by retrieving the update package from the first available source.

    When Kaspersky Security Center Cloud Console is set as an update source, the updates are downloaded from a distribution point repository, not from the Administration Server repository. Ensure that you assigned distribution points and created the Download updates to the repositories of distribution points task.

  12. Enable the Install approved application module updates option to download and install software module updates together with the application databases.

    If the option is enabled, Kaspersky Endpoint Security for Windows notifies the user about available software module updates and includes software module updates in the update package when running the update task. Kaspersky Endpoint Security for Windows installs only those updates for which you have set the Approved status; they will be installed locally through the application interface or through Kaspersky Security Center Cloud Console.

    You can also enable the Automatically install critical application module updates option. If any updates are available for software modules, Kaspersky Endpoint Security for Windows automatically installs those that have Critical status; the remaining updates will be installed after you approve them.

    If updating the software module requires reviewing and accepting the terms of the License Agreement and Privacy Policy, the application installs updates after the terms of the License Agreement and Privacy Policy have been accepted by the user.

  13. Select the Copy updates to folder check box in order for the application to save downloaded updates to a folder, and then specify the folder path.
  14. Schedule the task. To ensure timely updates, we recommend that you select the When new updates are downloaded to the repository option.
  15. Click Save.

When the Update task is running, the application sends requests to Kaspersky update servers.

Some updates require installation of the latest versions of management plug-ins.

See also:

Scenario: Regular updating of Kaspersky databases and applications

Page top

[Topic 189899]

About update statuses

Status is an attribute of software updates that defines whether a particular software update must be installed on a networked device.

An update can have the following statuses:

  • Undefined

    By default, the downloaded software updates have the Undefined status. The undefined updates can only be installed on Network Agent and other Kaspersky Security Center Cloud Console components in accordance with the Network Agent policy settings.

  • Approved

    The approved updates are always installed. If an update requires reviewing and accepting the terms of the End User License Agreement, then you first need to accept the terms.

  • Declined

    The updates for which you set Declined status will not be installed on devices.

You can change statuses of updates for the following software:

  • Network Agent and other Kaspersky Security Center Cloud Console components

    By default, the downloaded updates and patches for Kaspersky Security Center Cloud Console components are installed automatically. If you have left the Automatically install applicable updates and patches for components that have the Undefined status option enabled in the Network Agent properties, then all updates will be installed automatically after they are downloaded to the repository (or several repositories). If this option is disabled, Kaspersky patches that have been downloaded and tagged with the Undefined status will be installed only after you change their status to Approved.

    Updates for Kaspersky Security Center Cloud Console components cannot be uninstalled, even if you set an update the Declined status.

  • Kaspersky security applications

    By default, updates for the managed applications are installed only after you change the update status to Approved. If a declined update for a security application was previously installed, Kaspersky Security Center Cloud Console will try to uninstall the update from all devices.

See also:

Scenario: Regular updating of Kaspersky databases and applications

Page top

[Topic 180195]

Approving and declining software updates

The settings of an update installation task may require approval of updates that are to be installed. You can approve updates that must be installed and decline updates that must not be installed.

For example, you may want to first check the installation of updates in a test environment and make sure that they do not interfere with the operation of devices, and only then allow the installation of these updates on client devices.

Approving and declining updates is available only for Network Agent and managed applications installed on the Windows-based and Linux-based client devices. Seamless updating of Administration Server, Kaspersky Security Center Cloud Console, and management web plug-ins is not supported. To update these components, you have to download the latest versions from the Kaspersky website, and then install them manually.

To approve or decline one or several updates:

  1. In the main menu, go to OperationsKaspersky applicationsSeamless updates.

    A list of available updates appears.

    Updates of managed applications may require a specific minimum version of Kaspersky Security Center to be installed. If this version is later than your current version, these updates are displayed but cannot be approved. Also, no installation packages can be created from such updates until you upgrade Kaspersky Security Center. You are prompted to upgrade your Kaspersky Security Center instance to the required minimum version.

  2. If necessary, accept EULA by clicking the View and accept License Agreements button.
  3. Select the updates that you want to approve or decline.
  4. Click Approve to approve the selected updates or Decline to decline the selected updates.

    The default value is Undefined.

The updates to which you assign Approved status are placed in a queue for installation.

The updates to which you assign Declined status are uninstalled (if possible) from all devices on which they were previously installed. Also, they will not be installed on other devices in future.

Some updates for Kaspersky applications cannot be uninstalled. If you set Declined status for them, Kaspersky Security Center Cloud Console will not uninstall these updates from the devices on which they were previously installed. However, these updates will never be installed on other devices in future.

If you set Declined status for third-party software updates, these updates will not be installed on devices for which they were planned but have not yet been installed. Updates will remain on devices on which they were already installed. If you have to delete the updates, you can manually delete them locally.

See also:

Scenario: Regular updating of Kaspersky databases and applications

Page top

[Topic 175487]

Using diff files for updating Kaspersky databases and software modules

A diff file describes the differences between two versions of a file of a database or software module. The usage of diff files limits traffic on your company's network because diff files occupy less space than entire files of databases and software modules. If the Downloading diff files feature is enabled on a distribution point, the diff files are saved on this distribution point. As a result, devices that take updates from this distribution point can use the saved diff files to update their databases and software modules.

To optimize the usage of diff files, we recommend that you synchronize the update schedule of devices with the update schedule of the distribution point from which the devices take updates. However, the traffic can be saved even if devices are updated several times less often than is the distribution point from which the devices take updates.

Distribution points do not use IP multicasting for automatic distribution of diff files.

To enable the Downloading diff files feature:

  1. In the main menu, go to Assets (Devices) Tasks.
  2. Click the Download updates to the repositories of distribution points task to open the task properties.
  3. On the Application settings tab, enable the Download diff files option.
  4. Click the Save button.

The Downloading diff files feature is enabled. Diff files of updates will be downloaded in addition to the update files each time the Download updates to the repositories of distribution points task is run.

To check that the Downloading diff files feature is successfully enabled, you can measure the internal traffic before and after you perform the scenario.

See also:

Scenario: Regular updating of Kaspersky databases and applications

Page top

[Topic 180902]

Updating Kaspersky databases and software modules on offline devices

Updating Kaspersky databases and software modules on managed devices is an important task for maintaining protection of the devices against viruses and other threats. Administrators usually configure regular updates through usage of the repositories of distribution points.

When you need to update databases and software modules on a device (or a group of devices) that is not connected to a distribution point or the internet, you have to use alternative sources of updates, such as an FTP server or a local folder. In this case you have to deliver the files of the required updates by using a mass storage device, such as a flash drive or an external hard drive.

You can copy the required updates from the following sources:

  • Distribution point.

    To be sure the distribution point repository contains the updates required for the security application installed on an offline device, at least one of the managed online devices in the scope of the distribution point must have the same security application installed. This application must be configured to receive the updates from the distribution point repository through the Download updates to the repositories of distribution points task.

  • Any device that has the same security application installed and configured to receive the updates from a distribution point repository or directly from the Kaspersky update servers.

Below is an example of configuring updates of databases and software modules by copying them from a distribution point repository.

To update Kaspersky databases and software modules on offline devices:

  1. Connect the removable drive to the distribution point device.
  2. Copy the updates files to the removable drive.

    By default, the updates are located at: %ALLUSERSPROFILE%\Application Data\KasperskyLab\adminkit\1103\Updates.

  3. On offline devices, configure the security application (for example, Kaspersky Endpoint Security for Windows) to receive updates from a local folder or a shared resource, such as an FTP server or a shared folder.
  4. Copy the updates files from the removable drive to the local folder or the shared resource that you want to use as an update source.
  5. On the offline device that requires update installation, start the update task of Kaspersky Endpoint Security for Windows.

After the update task is complete, the Kaspersky databases and software modules are up-to-date on the device.

See also:

Scenario: Regular updating of Kaspersky databases and applications

Page top

[Topic 203765]

Updating Kaspersky Security for Windows Server databases

You can install Kaspersky Security for Windows Server on managed devices and you might want to launch this application's Real-Time File Protection task. However, the application comes without the databases that are needed for it to work correctly. The databases are downloaded to the managed device only after the Download updates to the repositories of distribution points task has completed.

If you want to start the Real-Time File Protection task on a managed device right after Kaspersky Security for Windows Server is installed on it, you must make sure that the databases for that application are downloaded and are up to date. Otherwise, the task might work incorrectly.

To make sure that Kaspersky Security for Windows Server databases are up to date:

  1. Make sure that the Download updates to the repositories of distribution points task has completed on Administration Server.
  2. Do one of the following:
    • In the settings of the Real-Time File Protection task, set the start to At application launch, and then restart the managed device.
    • In the settings of the Real-Time File Protection task, manually set the start time to the time you want.

The Real-Time File Protection task in Kaspersky Security for Windows Server is ready to work correctly.

See also:

Scenario: Regular updating of Kaspersky databases and applications

Page top

[Topic 196148]

Limitations of Vulnerability and patch management

The Vulnerability and patch management feature has a number of limitations, depending on the license that you use and the mode in which Kaspersky Security Center Cloud Console is working.

The following licenses do not support Vulnerability and patch management:

  • Kaspersky Endpoint Security for Business Select
  • Kaspersky Hybrid Cloud Security

The following licenses support Vulnerability and patch management:

  • Kaspersky Endpoint Security for Business Advanced
  • Kaspersky Endpoint Detection and Response Optimum
  • Kaspersky Total Security for Business
  • Kaspersky Hybrid Cloud Security Enterprise

The table below compares limitations of Kaspersky Security Center Cloud Console in the trial mode, under licenses that do not support Vulnerability and patch management, and under licenses that support Vulnerability and patch management.

Limitations of Vulnerability and patch management

 

Limitation

Trial mode

Commercial mode: licenses that do not support Vulnerability and patch management

Commercial mode: licenses that support Vulnerability and patch management

Maximum number of the Install Windows Update updates tasks or the Fix vulnerabilities tasks

4

4

0 (new tasks of these types cannot be created)

Maximum number of the Install required updates and fix vulnerabilities tasks

2

Not supported

4

Maximum number of rules in all of the Install required updates and fix vulnerabilities tasks

10

Not supported

50

Maximum number of software updates that can have the Approved status at the same time, across all servers including virtual ones

100

Not supported

1000

Maximum number of software updates that can be manually added to a task, across all servers including virtual ones

500

1000

1000

Maximum number of software vulnerabilities that can be manually added to a task, across all servers including virtual ones

500

1000

1000

See also:

Scenario: Finding and fixing software vulnerabilities

Page top

[Topic 212470]

Availability of Vulnerability and patch management features in trial and commercial mode and under various licensing options

The availability of Vulnerability and patch management features in Kaspersky Security Center Cloud Console depends on whether you use it in trial or commercial mode, as well as on the licensing option that you selected. Use the table to check which Vulnerability and patch management features are available.

Availability of Vulnerability and patch management features

Vulnerability and patch management feature

Trial mode

Commercial mode: Kaspersky Endpoint Security for Business Select

Commercial mode: Kaspersky Endpoint Security for Business Advanced, Kaspersky Endpoint Detection and Response Optimum, Kaspersky Total Security for Business

Manual fixing of vulnerabilities in Microsoft software on managed devices that are running Windows

Creating the Fix vulnerabilities task

Yes.

Yes.

No.

Manual installation of updates in Microsoft software on managed devices that are running Windows

Installing third-party software updates through the Install Windows Update updates task

No.

Yes.

Yes.

Automatic rule-based installing third-party software updates and fixing of third-party software vulnerabilities

Creating the Install required updates and fix vulnerabilities task and installing updates

Adding rules for update installation

Yes.

No.

Yes.

See also:

Scenario: Finding and fixing software vulnerabilities

Page top

[Topic 222479]

About third-party applications

Kaspersky Security Center Cloud Console can help you to update third-party software, installed on client devices, and fix the vulnerabilities of the third-party software. Kaspersky Security Center Cloud Console can update third-party software from the current version to the latest version only.

The list of third-party software can be updated and extended with new applications. You can check whether you can update the third-party software (installed on users' devices) with Kaspersky Security Center Cloud Console by viewing the list of available updates in the Kaspersky Security Center Cloud Console.

To view the list of third-party software that you can update with Kaspersky Security Center Cloud Console, do the following:

  1. In the main menu, go to Assets (Devices)Tasks.
  2. Click Add.

    The New task wizard starts. Proceed through the wizard by using the Next button.

  3. At the New task settings step of the wizard, specify the following settings:
    1. In the Application drop-down list, select Kaspersky Security Center Cloud Console.
    2. In the Task type field, select Install required updates and fix vulnerabilities.
    3. In the Task name field, specify the name for the task that you are creating.

      A task name cannot be more than 100 characters long and cannot include any special characters ("*<>?\:|).

    4. Select the devices to which the task will be assigned.
  4. At the Specify rules for installing updates step of the wizard, click the Add button.

    The Rule creation wizard starts. Proceed through the wizard by using the Next button.

  5. At the Select rule type step of the wizard, select the Rule for third-party updates option.
  6. At the General criteria step of the wizard, select the Install all updates (except declined) option, and then click Next.

The list of third-party software is displayed.

See also:

Scenario: Updating third-party software

Scenario: Finding and fixing software vulnerabilities

Third-party software updates

Page top

[Topic 183832]

Third-party software updates

Kaspersky Security Center Cloud Console enables you to manage updates of third-party software installed on managed devices and fix vulnerabilities in Microsoft applications and other software makers' products through installation of required updates.

Kaspersky Security Center Cloud Console searches for updates through the Find vulnerabilities and required updates task. When this task is complete, Administration Server receives the lists of detected vulnerabilities and required updates for the third-party software installed on the devices that you specified in the task properties. After viewing information about available updates, you can install them on devices.

Kaspersky Security Center Cloud Console updates some applications by removing the previous version of the application and installing the new one.

A user interaction may be required when you update a third-party application or fix a vulnerability in a third-party application on a managed device. For example, the user may be prompted to close the third-party application if it is currently open.

For security reasons, any third-party software updates that you install by using the Vulnerability and patch management feature are automatically scanned for malware by Kaspersky technologies. These technologies are used for automatic file checks and include virus scanning, static analysis, dynamic analysis, behavior analysis in the sandbox environment, and machine learning.

Kaspersky experts do not perform manual analysis of third-party software updates that can be installed by using the Vulnerability and patch management feature. In addition, Kaspersky experts do not search for vulnerabilities (known or unknown) or undocumented features in such updates, nor do they perform other types of analysis of the updates other than those specified in the paragraph above.

Tasks for installation of third party software updates

When metadata of the third-party software updates is downloaded to the repository, you can install the updates on client devices by using the following tasks:

  • The Install required updates and fix vulnerabilities task

    This task is used to install updates for Microsoft applications, including the updates provided by the Windows Update service, and updates of other vendors' software.

    When this task is complete, the updates are installed on the managed devices automatically. When metadata of new updates is downloaded to the Administration Server repository, Kaspersky Security Center Cloud Console checks whether the updates meet the criteria specified in the update rules. All new updates that meet the criteria will be downloaded and installed automatically at the next task run.

  • The Install Windows Update updates task

    This task can be used to install Windows Update updates only.

    When this task is complete, only those updates that are specified in the task properties are installed. In future, if you want to install new updates, you must add the required updates to the list of updates in the existing task or create an Install Windows Update updates task.

The software update installation tasks have a number of limitations. These limitations depend on the license under which you are using Kaspersky Security Center Cloud Console and on the mode in which Kaspersky Security Center Cloud Console is working.

In this section

Scenario: Updating third-party software

Installing third-party software updates

Creating the Find vulnerabilities and required updates task

Find vulnerabilities and required updates task settings

Creating the Install required updates and fix vulnerabilities task

Adding rules for update installation

Creating the Install Windows Update updates task

Viewing information about available third-party software updates

Exporting the list of available software updates to a file

Approving and declining third-party software updates

Updating third-party applications automatically

See also:

About third-party applications

Scenario: Updating third-party software

Page top

[Topic 183968]

Scenario: Updating third-party software

This section provides a scenario for updating third-party software installed on the client devices. The third-party software includes applications from Microsoft and other software vendors. Updates for Microsoft applications are provided by the Windows Update service.

Stages

Updating third-party software proceeds in stages:

  1. Searching for required updates

    To find the third-party software updates required for the managed devices, run the Find vulnerabilities and required updates task. When this task is complete, Kaspersky Security Center Cloud Console receives the lists of detected vulnerabilities and required updates for the third-party software installed on the devices that you specified in the task properties.

    The Find vulnerabilities and required updates task is created automatically by the Administration Server quick start wizard. If you did not run the wizard, create the task or run the quick start wizard now.

    How-to instructions:

  2. Analyzing the list of found updates

    View the Software updates list and decide which updates you want to install. To view detailed information about each update, click the update name in the list. For each update in the list, you can view the statistics about the update installation on managed devices. For example, you can view the number of devices on which the selected update is not installed, will be installed, or on which the update installation has failed.

    How-to instructions: Viewing information about available third-party software updates

  3. Configuring installation of updates

    When Kaspersky Security Center Cloud Console received the list of the third-party software updates, you can install them on client devices by using the Install required updates and fix vulnerabilities task or the Install Windows Update updates task. Create one of these tasks. You can create these tasks on the Tasks tab or by using the Software updates list.

    The Install required updates and fix vulnerabilities task is used to install updates for Microsoft applications, including the updates provided by the Windows Update service, and updates of other vendors' software.

    The Install Windows Update updates task can be used to install Windows Update updates only.

    The software update installation tasks have a number of limitations. These limitations depend on the license under which you are using Kaspersky Security Center Cloud Console and on the mode in which Kaspersky Security Center Cloud Console is working.

    To install some software updates you must accept the End User License Agreement (EULA) for the installation software. If you decline the EULA, the software update will not be installed.

    How-to instructions:

  4. Scheduling the tasks

    To be sure that the update list is always up-to-date, schedule the Find vulnerabilities and required updates task to run the task automatically from time to time. The default frequency is once a week.

    If you have created the Install required updates and fix vulnerabilities task, you can schedule it to run with the same frequency as the Find vulnerabilities and required updates task or less often. When scheduling the Install Windows Update updates task, note that for this task you must define the list of updates every time before starting this task.

    When scheduling the tasks, make sure that a task to fix vulnerability starts after the Find vulnerabilities and required updates task is complete.

    How-to instructions: General task settings

  5. Approving and declining software updates (optional)

    If you have created the Install required updates and fix vulnerabilities task, you can specify rules for update installation in the task properties. If you have created the Install Windows Update updates task, skip this step.

    For each rule, you can define the updates to install depending on the update status: Undefined, Approved or Declined. For example, you may want to create a specific task for servers and set a rule for this task to allow installation of only Windows Update updates and only those ones that have Approved status. After that you manually set the Approved status for those updates that you want to install. In this case the Windows Update updates that have the Undefined or Declined status will not be installed on the servers that you specified in the task.

    By default, the downloaded software updates have the Undefined status. You can change the status to Approved or Declined in the Software updates list (OperationsPatch managementSoftware updates).

    How-to instructions: Approving and declining third-party software updates

  6. Running an update installation task

    Start the Install required updates and fix vulnerabilities task or the Install Windows Update updates task. When you start these tasks, updates are downloaded and installed on managed devices. After the task is complete, make sure that it has the Completed successfully status in the task list.

    How-to instructions: Starting a task manually

  7. Create the report on results of update installation of third-party software (optional)

    To make sure that the task is created and the updates are installed, create the Report on results of installation of third-party software updates and view detailed statistics on the update installation in this report.

    How-to instructions: Generating and viewing a report

Page top

[Topic 183925]

Installing third-party software updates

Expand all | Collapse all

You can install third-party software updates on managed devices by creating and running one of the following tasks:

The software update installation tasks have a number of limitations. These limitations depend on the license under which you are using Kaspersky Security Center Cloud Console and on the mode in which Kaspersky Security Center Cloud Console is working.

A user interaction may be required when you update a third-party application or fix a vulnerability in a third-party application on a managed device. For example, the user may be prompted to close the third-party application if it is currently open.

As an option, you can create a task to install the required updates in the following ways:

  • By opening the update list and specifying which updates to install.

    As a result, a new task to install the selected updates is created. As an option, you can add the selected updates to an existing task.

  • By running the Update installation wizard.

    The availability of the Update installation wizard depends on the Kaspersky Security Center Cloud Console mode and your current license.

    The wizard simplifies creation and configuration of an update installation task, and enables you to eliminate the creation of redundant tasks that contain the same updates to install.

Installing third-party software updates by using the update list

To install third-party software updates by using the list of updates:

  1. Open one of the lists of updates:
    • To open the general update list, in the main menu, go to OperationsPatch managementSoftware updates.
    • To open the update list for a managed device, in the main menu, go to Assets (Devices)Managed devices<device name>AdvancedAvailable updates.
    • To open the update list for a specific application, in the main menu, go to OperationsThird-party applications → Applications registry<application name>Available updates.

    A list of available updates appears.

  2. Select the check boxes next to the updates that you want to install.
  3. Click the Install updates button.

    To install some software updates, you must accept the End User License Agreement (EULA). If you decline the EULA, the software update will not be installed.

  4. Select one of the following options:
    • New task

      The New task wizard starts. The Install required updates and fix vulnerabilities task or the Install Windows Update updates task is preselected, depending on the Kaspersky Security Center Cloud Console mode and your current license. Follow the steps of the wizard to complete the task creation.

    • Install update (add rule to specified task)

      Select a task to which you want to add the selected updates. Select an Install required updates and fix vulnerabilities task or an Install Windows Update updates task. If you select an Install required updates and fix vulnerabilities task, a new rule to install the selected updates will be automatically added to the selected task. If you select an Install Windows Update updates task, the selected updates will be added to the task properties.

      The task properties window opens. Click the Save button to save the changes.

If you have chosen to create a task, the task is created and displayed in the task list at Assets (Devices)Tasks. If you have chosen to add the updates to an existing task, the updates are saved in the task properties.

To install third-party software updates, start the Install required updates and fix vulnerabilities task or the Install Windows Update updates task. You can start any of these tasks manually or specify schedule settings in the properties of the task that you start. When specifying the task schedule, make sure that the update installation task starts after the Find vulnerabilities and required updates task is complete.

Installing third-party software updates by using the Update installation wizard

The availability of this feature depends on the Kaspersky Security Center Cloud Console mode and your current license.

To create a task to install third-party software updates by using the Update installation wizard:

  1. In the main menu, go to OperationsPatch managementSoftware updates.

    A list of available updates appears.

  2. Select the check box next to the update that you want to install.
  3. Click the Run Update installation wizard button.

    The Update installation wizard starts. The Select the update installation task page displays the list of all existing tasks of the following types:

    • Install required updates and fix vulnerabilities
    • Install Windows Update updates
    • Fix vulnerabilities

    You cannot modify the tasks of the last two types to install new updates. To install new updates, you can only use the Install required updates and fix vulnerabilities tasks.

  4. If you want the wizard to display only those tasks that install the update that you selected, then enable the Show only tasks that install this update option.
  5. Choose what you want to do:
    • To start a task, select the check box next to the task name, and then click the Start button.
    • To add a new rule to an existing task:
      1. Select the check box next to the task name, and then click the Add rule button.
      2. On the page that opens, configure the new rule:
        • Installation rule for updates of this importance level

          Sometimes software updates may impair the user experience with the software. In such cases, you may decide to install only those updates that are critical for the software operation and to skip other updates.

          If this option is enabled, the updates fix only those vulnerabilities for which the severity level set by Kaspersky is equal to or higher than the severity of the selected update (Medium, High, or Critical). Vulnerabilities with a severity level lower than the selected value are not fixed.

          If this option is disabled, the updates fix all vulnerabilities regardless of their severity level.

          By default, this option is disabled.

        • Installation rule for updates of this importance level according to MSRC (available only for Windows Update updates)

          Sometimes software updates may impair the user experience with the software. In such cases, you may decide to install only those updates that are critical for the software operation and to skip other updates.

          If this option is enabled (available only for Windows Update updates), the updates fix only those vulnerabilities for which the severity level set by Microsoft Security Response Center (MSRC) is equal to or higher than the value selected in the list (Low, Medium, High, or Critical). Vulnerabilities with a severity level lower than the selected value are not fixed.

          If this option is disabled, the updates fix all vulnerabilities regardless of their severity level.

          By default, this option is disabled.

        • Installation rule for updates by this vendor (available only for updates of third-party applications)

          This option is available only for updates of third-party applications. Kaspersky Security Center Cloud Console installs only those updates that relate to the applications made by the same vendor as the selected update. Declined updates and updates to the applications made by other vendors are not installed.

          By default, this option is disabled.

        • Installation rule for updates of the type
        • Installation rule for the selected update
        • Approve selected updates

          The selected update will be approved for installation. Enable this option if some applied rules of update installation allow installation of approved updates only.

          By default, this option is disabled.

        • Automatically install all previous application updates that are required to install the selected updates

          Keep this option enabled if you agree with the installation of interim application versions when this is required for installing the selected updates.

          If this option is disabled, only the selected versions of applications are installed. Disable this option if you want to update applications in a straightforward manner, without attempting to install successive versions incrementally. If installing the selected updates is not possible without installing previous versions of applications, the updating of the application fails.

          For example, you have version 3 of an application installed on a device and you want to update it to version 5, but version 5 of this application can be installed only over version 4. If this option is enabled, the software first installs version 4, and then installs version 5. If this option is disabled, the software fails to update the application.

          By default, this option is enabled.

      3. Click the Add button.
    • To create a task:
      1. Click the New task button.
      2. On the page that opens, configure the new rule:
        • Installation rule for updates of this importance level

          Sometimes software updates may impair the user experience with the software. In such cases, you may decide to install only those updates that are critical for the software operation and to skip other updates.

          If this option is enabled, the updates fix only those vulnerabilities for which the severity level set by Kaspersky is equal to or higher than the severity of the selected update (Medium, High, or Critical). Vulnerabilities with a severity level lower than the selected value are not fixed.

          If this option is disabled, the updates fix all vulnerabilities regardless of their severity level.

          By default, this option is disabled.

        • Installation rule for updates of this importance level according to MSRC (available only for Windows Update updates)

          Sometimes software updates may impair the user experience with the software. In such cases, you may decide to install only those updates that are critical for the software operation and to skip other updates.

          If this option is enabled (available only for Windows Update updates), the updates fix only those vulnerabilities for which the severity level set by Microsoft Security Response Center (MSRC) is equal to or higher than the value selected in the list (Low, Medium, High, or Critical). Vulnerabilities with a severity level lower than the selected value are not fixed.

          If this option is disabled, the updates fix all vulnerabilities regardless of their severity level.

          By default, this option is disabled.

        • Installation rule for updates by this vendor (available only for updates of third-party applications)

          This option is available only for updates of third-party applications. Kaspersky Security Center Cloud Console installs only those updates that relate to the applications made by the same vendor as the selected update. Declined updates and updates to the applications made by other vendors are not installed.

          By default, this option is disabled.

        • Installation rule for updates of the type
        • Installation rule for the selected update
        • Approve selected updates

          The selected update will be approved for installation. Enable this option if some applied rules of update installation allow installation of approved updates only.

          By default, this option is disabled.

        • Automatically install all previous application updates that are required to install the selected updates

          Keep this option enabled if you agree with the installation of interim application versions when this is required for installing the selected updates.

          If this option is disabled, only the selected versions of applications are installed. Disable this option if you want to update applications in a straightforward manner, without attempting to install successive versions incrementally. If installing the selected updates is not possible without installing previous versions of applications, the updating of the application fails.

          For example, you have version 3 of an application installed on a device and you want to update it to version 5, but version 5 of this application can be installed only over version 4. If this option is enabled, the software first installs version 4, and then installs version 5. If this option is disabled, the software fails to update the application.

          By default, this option is enabled.

      3. Click the Add button.

If you have chosen to start a task, you can close the wizard. The task will complete in background mode. No further actions are required.

If you have chosen to add a rule to an existing task, the task properties window opens. The new rule is already added to the task properties. You can view or modify the rule or other task settings. Click the Save button to save the changes.

If you have chosen to create a task, you continue to create the task in the New task wizard. The new rule that you added in the Update installation wizard is displayed in the New task wizard. When you complete the New task wizard, the Install required updates and fix vulnerabilities task is added to the task list.

See also:

Scenario: Updating third-party software

Page top

[Topic 183915]

Creating the Find vulnerabilities and required updates task

Expand all | Collapse all

Through the Find vulnerabilities and required updates task, Kaspersky Security Center Cloud Console receives the lists of detected vulnerabilities and required updates for the third-party software installed on the managed devices.

The Find vulnerabilities and required updates task is created automatically when the quick start wizard is running. If you did not run the wizard, you can create the task manually.

To create the Find vulnerabilities and required updates task:

  1. In the main menu, go to Assets (Devices)Tasks.
  2. Click Add.

    The New task wizard starts. Follow the steps of the wizard.

  3. For the Kaspersky Security Center Cloud Console application, select the Find vulnerabilities and required updates task type.
  4. Specify the name for the task that you are creating. A task name cannot be more than 100 characters long and cannot include any special characters ("*<>?\:|).
  5. Select devices to which the task will be assigned.
  6. If you want to modify the default task settings, enable the Open task details when creation is complete option on the Finish task creation page. If you do not enable this option, the task is created with the default settings. You can modify the default settings later, at any time.
  7. Click the Create button.

    The task is created and displayed in the list of tasks.

  8. Click the name of the created task to open the task properties window.
  9. In the task properties window, specify the general task settings.
  10. On the Application settings tab, specify the following settings:
    • Search for vulnerabilities and updates listed by Microsoft

      When searching for vulnerabilities and updates, Kaspersky Security Center Cloud Console uses the information about applicable Microsoft updates from the source of Microsoft updates, which are available at the present moment.

      For example, you may want to disable this option if you have different tasks with different settings for Microsoft updates and updates of third-party applications.

      By default, this option is enabled.

    • Connect to the update server to update data

      Windows Update Agent on a managed device connects to the source of Microsoft updates. The following servers can act as a source of Microsoft updates:

      • Kaspersky Security Center Cloud Console Administration Server (see the settings of Network Agent policy)
      • Windows Server with Microsoft Windows Server Update Services (WSUS) deployed in your organization's network
      • Microsoft Updates servers

      If this option is enabled, Windows Update Agent on a managed device connects to the source of Microsoft updates to refresh the information about applicable Microsoft Windows updates.

      If this option is disabled, Windows Update Agent on a managed device uses the information about applicable Microsoft Windows updates that was received from the source of Microsoft updates earlier.

      Connecting to the source of Microsoft updates can be resource-consuming. You might want to disable this option if you set regular connection to this source of updates in another task or in the properties of Network Agent policy, in the section Software updates and vulnerabilities. If you do not want to disable this option, then, to reduce the Server overload, you can configure the task schedule to randomize delay for task starts within 360 minutes.

      By default, this option is enabled.

      Combination of the following options of the settings of Network Agent policy defines the mode of getting updates:

      • Windows Update Agent on a managed device connects to the Update Server to get updates only if the Connect to the update server to update data option is enabled in the properties of the Find vulnerabilities and required updates task and the Windows Update search mode option is set to Active in the settings of Network Agent policy.
      • If you do not need Network Agent to initiate a connection to the Microsoft Windows update source and download updates when performing the Vulnerability scan task, you can set the Windows Update search mode option to Passive, while the Connect to the update server to update data option must remain enabled. This allows for you to save resources and use previously received Windows updates to scan for vulnerabilities. You can use the passive mode if you configure receiving Microsoft Windows updates in a different way. If receiving Microsoft Windows updates is not configured in another way, do not set the Windows Update search mode option to Passive, because in this case, information about updates will never be received.
      • Irrespective of the Connect to the update server to update data option's status (enabled or disabled), if the Windows Update search mode option is set to Disabled, Kaspersky Security Center Cloud Console does not request any information about updates.
    • Search for third-party vulnerabilities and updates listed by Kaspersky

      If this option is enabled, Kaspersky Security Center Cloud Console searches for vulnerabilities and required updates for third-party applications (applications made by software vendors other than Kaspersky and Microsoft) in Windows Registry and in the folders specified under Specify paths for advanced search of applications in file system. The full list of supported third-party applications is managed by Kaspersky.

      If this option is disabled, Kaspersky Security Center Cloud Console does not search for vulnerabilities and required updates for third-party applications. For example, you may want to disable this option if you have different tasks with different settings for Microsoft Windows updates and updates of third-party applications.

      By default, this option is enabled.

    • Specify paths for advanced search of applications across the file system

      The folders in which Kaspersky Security Center Cloud Console searches for third-party applications that require vulnerability fix and update installation. You can use system variables.

      Specify the folders to which applications are installed. By default, the list is empty.

    • Enable advanced diagnostics

      If this feature is enabled, Network Agent writes traces even if tracing is disabled for Network Agent in Kaspersky Security Center Cloud Console Remote Diagnostics Utility. Traces are written to two files in turn; the total size of both files is determined by the Maximum size, in MB, of advanced diagnostics files value. When both files are full, Network Agent starts writing to them again. The files with traces are stored in the %WINDIR%\Temp folder. These files are accessible in the remote diagnostics utility, you can download or delete them there.

      If this feature is disabled, Network Agent writes traces according to the settings in Kaspersky Security Center Cloud Console Remote Diagnostics Utility. No additional traces are written.

      When creating a task, you do not have to enable advanced diagnostics. You may want to use this feature later if, for example, a task run fails on some of the devices and you want to get additional information during another task run.

      By default, this option is disabled.

    • Maximum size, in MB, of advanced diagnostics files

      The default value is 100 MB, and available values are between 1 MB and 2048 MB. You may be asked to change the default value by Kaspersky Technical Support specialists when information in the advanced diagnostics files sent by you is not enough to troubleshoot the problem.

  11. Click the Save button.

The task is created and configured.

If the task results contain a warning of the 0x80240033 "Windows Update Agent error 80240033 ("License terms could not be downloaded.")" error, you can resolve this issue through the Windows Registry.

See also:

Scenario: Finding and fixing software vulnerabilities

Scenario: Updating third-party software

Page top

[Topic 182643]

Find vulnerabilities and required updates task settings

Expand all | Collapse all

The Find vulnerabilities and required updates task is created automatically when the quick start wizard is running. If you did not run the wizard, you can create the task manually.

In addition to the general task settings, you can specify the following settings when creating the Find vulnerabilities and required updates task or later, when configuring the properties of the created task:

  • Search for vulnerabilities and updates listed by Microsoft

    When searching for vulnerabilities and updates, Kaspersky Security Center Cloud Console uses the information about applicable Microsoft updates from the source of Microsoft updates, which are available at the present moment.

    For example, you may want to disable this option if you have different tasks with different settings for Microsoft updates and updates of third-party applications.

    By default, this option is enabled.

  • Connect to the update server to update data

    Windows Update Agent on a managed device connects to the source of Microsoft updates. The following servers can act as a source of Microsoft updates:

    • Kaspersky Security Center Cloud Console Administration Server (see the settings of Network Agent policy)
    • Windows Server with Microsoft Windows Server Update Services (WSUS) deployed in your organization's network
    • Microsoft Updates servers

    If this option is enabled, Windows Update Agent on a managed device connects to the source of Microsoft updates to refresh the information about applicable Microsoft Windows updates.

    If this option is disabled, Windows Update Agent on a managed device uses the information about applicable Microsoft Windows updates that was received from the source of Microsoft updates earlier.

    Connecting to the source of Microsoft updates can be resource-consuming. You might want to disable this option if you set regular connection to this source of updates in another task or in the properties of Network Agent policy, in the section Software updates and vulnerabilities. If you do not want to disable this option, then, to reduce the Server overload, you can configure the task schedule to randomize delay for task starts within 360 minutes.

    By default, this option is enabled.

    Combination of the following options of the settings of Network Agent policy defines the mode of getting updates:

    • Windows Update Agent on a managed device connects to the Update Server to get updates only if the Connect to the update server to update data option is enabled in the properties of the Find vulnerabilities and required updates task and the Windows Update search mode option is set to Active in the settings of Network Agent policy.
    • If you do not need Network Agent to initiate a connection to the Microsoft Windows update source and download updates when performing the Vulnerability scan task, you can set the Windows Update search mode option to Passive, while the Connect to the update server to update data option must remain enabled. This allows for you to save resources and use previously received Windows updates to scan for vulnerabilities. You can use the passive mode if you configure receiving Microsoft Windows updates in a different way. If receiving Microsoft Windows updates is not configured in another way, do not set the Windows Update search mode option to Passive, because in this case, information about updates will never be received.
    • Irrespective of the Connect to the update server to update data option's status (enabled or disabled), if the Windows Update search mode option is set to Disabled, Kaspersky Security Center Cloud Console does not request any information about updates.
  • Search for third-party vulnerabilities and updates listed by Kaspersky

    If this option is enabled, Kaspersky Security Center Cloud Console searches for vulnerabilities and required updates for third-party applications (applications made by software vendors other than Kaspersky and Microsoft) in Windows Registry and in the folders specified under Specify paths for advanced search of applications in file system. The full list of supported third-party applications is managed by Kaspersky.

    If this option is disabled, Kaspersky Security Center Cloud Console does not search for vulnerabilities and required updates for third-party applications. For example, you may want to disable this option if you have different tasks with different settings for Microsoft Windows updates and updates of third-party applications.

    By default, this option is enabled.

  • Specify paths for advanced search of applications across the file system

    The folders in which Kaspersky Security Center Cloud Console searches for third-party applications that require vulnerability fix and update installation. You can use system variables.

    Specify the folders to which applications are installed. By default, the list is empty.

  • Enable advanced diagnostics

    If this feature is enabled, Network Agent writes traces even if tracing is disabled for Network Agent in Kaspersky Security Center Cloud Console Remote Diagnostics Utility. Traces are written to two files in turn; the total size of both files is determined by the Maximum size, in MB, of advanced diagnostics files value. When both files are full, Network Agent starts writing to them again. The files with traces are stored in the %WINDIR%\Temp folder. These files are accessible in the remote diagnostics utility, you can download or delete them there.

    If this feature is disabled, Network Agent writes traces according to the settings in Kaspersky Security Center Cloud Console Remote Diagnostics Utility. No additional traces are written.

    When creating a task, you do not have to enable advanced diagnostics. You may want to use this feature later if, for example, a task run fails on some of the devices and you want to get additional information during another task run.

    By default, this option is disabled.

  • Maximum size, in MB, of advanced diagnostics files

    The default value is 100 MB, and available values are between 1 MB and 2048 MB. You may be asked to change the default value by Kaspersky Technical Support specialists when information in the advanced diagnostics files sent by you is not enough to troubleshoot the problem.

Recommendations on the task schedule

When scheduling the Find vulnerabilities and required updates task, make sure that two options—Run missed tasks and Use automatically randomized delay for task starts—are enabled.

By default, the Find vulnerabilities and required updates task is set to start manually. If the organization's workplace rules provide for shutting down all devices at this time, the Find vulnerabilities and required updates task will run after the devices are turned on again, that is, in the morning of the next day. Such activity may be undesirable because a vulnerability scan may increase the load on CPUs and disk subsystems. You must set up the most convenient schedule for the task based on the workplace rules adopted in the organization.

See also:

Scenario: Finding and fixing software vulnerabilities

Scenario: Configuring network protection

Scenario: Updating third-party software

Page top

[Topic 182671]

Creating the Install required updates and fix vulnerabilities task

Expand all | Collapse all

The availability of the Install required updates and fix vulnerabilities task depends on the Kaspersky Security Center Cloud Console mode and your current license.

The Install required updates and fix vulnerabilities task is used to update and fix vulnerabilities in third-party software, including Microsoft software, installed on the managed devices. This task enables you to install multiple updates and fix multiple vulnerabilities according to certain rules.

To install updates or fix vulnerabilities by using the Install required updates and fix vulnerabilities task, you can do one of the following:

The software update installation tasks have a number of limitations. These limitations depend on the license under which you are using Kaspersky Security Center Cloud Console and on the mode in which Kaspersky Security Center Cloud Console is working.

To create the Install required updates and fix vulnerabilities task:

  1. In the main menu, go to Assets (Devices)Tasks.
  2. Click Add.

    The New task wizard starts. Follow the steps of the wizard.

  3. For the Kaspersky Security Center Cloud Console application, select the Install required updates and fix vulnerabilities task type.
  4. Specify the name for the task that you are creating. A task name cannot be more than 100 characters long and cannot include any special characters ("*<>?\:|).
  5. Select devices to which the task will be assigned.
  6. Specify the rules for update installation, and then specify the following settings:
    • Start installation at device restart or shutdown

      If this option is enabled, updates are installed when the device is restarted or shut down. Otherwise, updates are installed according to a schedule.

      Use this option if installing the updates might affect the device performance.

      By default, this option is disabled.

    • Install the required general system components

      If this option is enabled, before installing an update the application automatically installs all general system components (prerequisites) that are required to install the update. For example, these prerequisites can be operating system updates.

      If this option is disabled, you may have to install the prerequisites manually.

      By default, this option is disabled.

    • Allow installation of new application versions during updates

      If this option is enabled, updates are allowed when they result in installation of a new version of a software application.

      If this option is disabled, the software is not upgraded. You can then install new versions of the software manually or through another task. For example, you may use this option if your company infrastructure is not supported by a new software version or if you want to check an upgrade in a test infrastructure.

      By default, this option is enabled.

      Upgrading an application may cause malfunction of dependent applications installed on client devices.

    • Download updates to the device without installing them

      If this option is enabled, the application downloads updates to the device but does not install them automatically. You can then Install downloaded updates manually.

      Microsoft updates are downloaded to the system Windows storage. Updates of third-party applications (applications made by software vendors other than Kaspersky and Microsoft) are downloaded to the folder specified in the Download updates to field.

      If this option is disabled, the updates are installed to the device automatically.

      By default, this option is disabled.

    • Download updates to

      This folder is used to download updates of third-party applications (applications made by software vendors other than Kaspersky and Microsoft).

    • Enable advanced diagnostics

      If this feature is enabled, Network Agent writes traces even if tracing is disabled for Network Agent in Kaspersky Security Center Cloud Console Remote Diagnostics Utility. Traces are written to two files in turn; the total size of both files is determined by the Maximum size, in MB, of advanced diagnostics files value. When both files are full, Network Agent starts writing to them again. The files with traces are stored in the %WINDIR%\Temp folder. These files are accessible in the remote diagnostics utility, you can download or delete them there.

      If this feature is disabled, Network Agent writes traces according to the settings in Kaspersky Security Center Cloud Console Remote Diagnostics Utility. No additional traces are written.

      When creating a task, you do not have to enable advanced diagnostics. You may want to use this feature later if, for example, a task run fails on some of the devices and you want to get additional information during another task run.

      By default, this option is disabled.

    • Maximum size, in MB, of advanced diagnostics files

      The default value is 100 MB, and available values are between 1 MB and 2048 MB. You may be asked to change the default value by Kaspersky Technical Support specialists when information in the advanced diagnostics files sent by you is not enough to troubleshoot the problem.

  7. Specify operating system restart settings:
    • Do not restart the device

      Client devices are not restarted automatically after the operation. To complete the operation, you must restart a device (for example, manually or through a device management task). Information about the required restart is saved in the task results and in the device status. This option is suitable for tasks on servers and other devices where continuous operation is critical.

    • Restart the device

      Client devices are always restarted automatically if a restart is required for completion of the operation. This option is useful for tasks on devices that provide for regular pauses in their operation (shutdown or restart).

    • Prompt user for action

      The restart reminder is displayed on the screen of the client device, prompting the user to restart it manually. Some advanced settings can be defined for this option: text of the message for the user, the message display frequency, and the time interval after which a restart will be forced (without the user's confirmation). This option is most suitable for workstations where users must be able to select the most convenient time for a restart.

      By default, this option is selected.

    • Repeat prompt every (min)

      If this option is enabled, the application prompts the user to restart the operating system with the specified frequency.

      By default, this option is enabled. The default interval is 5 minutes. Available values are between 1 and 1440 minutes.

      If this option is disabled, the prompt is displayed only once.

    • Restart after (min)

      After prompting the user, the application forces restart of the operating system upon expiration of the specified time interval.

      By default, this option is enabled. The default delay is 30 minutes. Available values are between 1 and 1440 minutes.

    • Wait time before forced closure of applications in blocked sessions (min)

      Applications are forced to close when the user's device goes locked (automatically after a specified interval of inactivity, or manually).

      If this option is enabled, applications are forced to close on the locked device upon expiration of the time interval specified in the entry field.

      If this option is disabled, applications do not close on the locked device.

      By default, this option is disabled.

  8. If on the Finish task creation page you enable the Open task details when creation is complete option, you can modify the default task settings. If you do not enable this option, the task is created with the default settings. You can modify the default settings later, at any time.
  9. Click the Finish button.

    The task is created and displayed in the list of tasks.

  10. Click the name of the created task to open the task properties window.
  11. In the task properties window, specify the general task settings according to your needs.
  12. Click the Save button.

    The task is created and configured.

If the task results contain a warning of the 0x80240033 "Windows Update Agent error 80240033 ("License terms could not be downloaded.")" error, you can resolve this issue through the Windows Registry.

See also:

Scenario: Updating third-party software

Page top

[Topic 182798]

Adding rules for update installation

Expand all | Collapse all

The availability of this feature depends on the Kaspersky Security Center Cloud Console mode and your current license.

When installing software updates or fixing software vulnerabilities by using the Install required updates and fix vulnerabilities task, you must specify rules for the update installation. These rules determine the updates to install and the vulnerabilities to fix.

The exact settings depend on whether you add a rule for all updates, for Windows Update updates, or for updates of third-party applications (applications made by software vendors other than Kaspersky and Microsoft). When adding a rule for Windows Update updates or updates of third-party applications, you can select specific applications and application versions for which you want to install updates. When adding a rule for all updates, you can select specific updates that you want to install and vulnerabilities that you want to fix by means of installing updates.

You can add a rule for update installation in the following ways:

To add a new rule for all updates:

  1. Click the Add button.

    The Rule creation wizard starts. Proceed through the wizard by using the Next button.

  2. On the Rule type page, select Rule for all updates.
  3. On the General criteria page, use the drop-down lists to specify the following settings:
    • Set of updates to install

      Select the updates that must be installed on client devices:

      • Install approved updates only. This installs only approved updates.
      • Install all updates (except declined). This installs updates with the Approved or Undefined approval status.
      • Install all updates (including declined). This installs all updates, regardless of their approval status. Select this option with caution. For example, use this option if you want to check installation of some declined updates in a test infrastructure.
    • Fix vulnerabilities with a severity level equal to or higher than

      Sometimes software updates may impair the user experience with the software. In such cases, you may decide to install only those updates that are critical for the software operation and to skip other updates.

      If this option is enabled, the updates fix only those vulnerabilities for which the severity level set by Kaspersky is equal to or higher than the value selected in the list (Medium, High, or Critical). Vulnerabilities with a severity level lower than the selected value are not fixed.

      If this option is disabled, the updates fix all vulnerabilities regardless of their severity level.

      By default, this option is disabled.

  4. On the Updates page, select the updates to be installed:
    • Install all suitable updates

      Install all software updates that meet the criteria specified on the General criteria page of the wizard. Selected by default.

    • Install only updates from the list

      Install only software updates that you select manually from the list. This list contains all available software updates.

      For example, you may want to select specific updates in the following cases: to check their installation in a test environment, to update only critical applications, or to update only specific applications.

    • Automatically install all previous application updates that are required to install the selected updates

      Keep this option enabled if you agree with the installation of interim application versions when this is required for installing the selected updates.

      If this option is disabled, only the selected versions of applications are installed. Disable this option if you want to update applications in a straightforward manner, without attempting to install successive versions incrementally. If installing the selected updates is not possible without installing previous versions of applications, the updating of the application fails.

      For example, you have version 3 of an application installed on a device and you want to update it to version 5, but version 5 of this application can be installed only over version 4. If this option is enabled, the software first installs version 4, and then installs version 5. If this option is disabled, the software fails to update the application.

      By default, this option is enabled.

  5. On the Vulnerabilities page, select vulnerabilities that will be fixed by installing the selected updates:
    • Fix all vulnerabilities that match other criteria

      Fix all vulnerabilities that meet the criteria specified on the General criteria page of the wizard. Selected by default.

    • Fix only vulnerabilities from the list

      Fix only vulnerabilities that you select manually from the list. This list contains all detected vulnerabilities.

      For example, you may want to select specific vulnerabilities in the following cases: to check their fix in a test environment, to fix vulnerabilities only in critical applications, or to fix vulnerabilities only in specific applications.

  6. On the Name page, specify the name for the rule that you are adding. You can later change this name in the Settings section of the properties window of the created task.

After the Rule creation wizard completes its operation, the new rule is added and displayed in the rule list in the New task wizard or in the task properties.

To add a new rule for Windows Update updates:

  1. Click the Add button.

    The Rule creation wizard starts. Proceed through the wizard by using the Next button.

  2. On the Rule type page, select Rule for Windows Update.
  3. On the General criteria page, specify the following settings:
    • Set of updates to install

      Select the updates that must be installed on client devices:

      • Install approved updates only. This installs only approved updates.
      • Install all updates (except declined). This installs updates with the Approved or Undefined approval status.
      • Install all updates (including declined). This installs all updates, regardless of their approval status. Select this option with caution. For example, use this option if you want to check installation of some declined updates in a test infrastructure.
    • Fix vulnerabilities with a severity level equal to or higher than

      Sometimes software updates may impair the user experience with the software. In such cases, you may decide to install only those updates that are critical for the software operation and to skip other updates.

      If this option is enabled, the updates fix only those vulnerabilities for which the severity level set by Kaspersky is equal to or higher than the value selected in the list (Medium, High, or Critical). Vulnerabilities with a severity level lower than the selected value are not fixed.

      If this option is disabled, the updates fix all vulnerabilities regardless of their severity level.

      By default, this option is disabled.

    • Fix vulnerabilities with an MSRC severity level equal to or higher than

      Sometimes software updates may impair the user experience with the software. In such cases, you may decide to install only those updates that are critical for the software operation and to skip other updates.

      If this option is enabled, the updates fix only those vulnerabilities for which the severity level set by Microsoft Security Response Center (MSRC) is equal to or higher than the value selected in the list (Low, Medium, High, or Critical). Vulnerabilities with a severity level lower than the selected value are not fixed.

      If this option is disabled, the updates fix all vulnerabilities regardless of their severity level.

      By default, this option is disabled.

  4. On the Applications page, select the applications and application versions for which you want to install updates. By default, all applications are selected.
  5. On the Categories of updates page, select the categories of updates to be installed. These categories are the same as in Microsoft Update Catalog. By default, all categories are selected.
  6. On the Name page, specify the name for the rule that you are adding. You can later change this name in the Settings section of the properties window of the created task.

After the Rule creation wizard completes its operation, the new rule is added and displayed in the rule list in the New task wizard or in the task properties.

To add a new rule for updates of third-party applications:

  1. Click the Add button.

    The Rule creation wizard starts. Proceed through the wizard by using the Next button.

  2. On the Rule type page, select Rule for third-party updates.
  3. On the General criteria page, specify the following settings:
    • Set of updates to install

      Select the updates that must be installed on client devices:

      • Install approved updates only. This installs only approved updates.
      • Install all updates (except declined). This installs updates with the Approved or Undefined approval status.
      • Install all updates (including declined). This installs all updates, regardless of their approval status. Select this option with caution. For example, use this option if you want to check installation of some declined updates in a test infrastructure.
    • Fix vulnerabilities with a severity level equal to or higher than

      Sometimes software updates may impair the user experience with the software. In such cases, you may decide to install only those updates that are critical for the software operation and to skip other updates.

      If this option is enabled, the updates fix only those vulnerabilities for which the severity level set by Kaspersky is equal to or higher than the value selected in the list (Medium, High, or Critical). Vulnerabilities with a severity level lower than the selected value are not fixed.

      If this option is disabled, the updates fix all vulnerabilities regardless of their severity level.

      By default, this option is disabled.

  4. On the Applications page, select the applications and application versions for which you want to install updates. By default, all applications are selected.
  5. On the Name page, specify the name for the rule that you are adding. You can later change this name in the Settings section of the properties window of the created task.

After the Rule creation wizard completes its operation, the new rule is added and displayed in the rule list in the New task wizard or in the task properties.

See also:

Scenario: Finding and fixing software vulnerabilities

Page top

[Topic 183852]

Creating the Install Windows Update updates task

Expand all | Collapse all

The Install Windows Update updates task enables you to install software updates provided by the Windows Update service on client devices.

The software update installation tasks have a number of limitations. These limitations depend on the license under which you are using Kaspersky Security Center Cloud Console and on the mode in which Kaspersky Security Center Cloud Console is working.

To create the Install Windows Update updates task:

  1. In the main menu, go to Assets (Devices)Tasks.
  2. Click Add.

    The New task wizard starts. Proceed through the wizard by using the Next button.

  3. For the Kaspersky Security Center Cloud Console application, select the Install Windows Update updates task type.
  4. Specify the name for the task that you are creating.

    A task name cannot be more than 100 characters long and cannot include any special characters ("*<>?\:|).

  5. Select devices to which the task will be assigned.
  6. Click the Add button.

    The list of updates opens.

  7. Select the Windows Update updates that you want to install, and then click OK.
  8. Specify the operating system restart settings:
    • Do not restart the device

      Client devices are not restarted automatically after the operation. To complete the operation, you must restart a device (for example, manually or through a device management task). Information about the required restart is saved in the task results and in the device status. This option is suitable for tasks on servers and other devices where continuous operation is critical.

    • Restart the device

      Client devices are always restarted automatically if a restart is required for completion of the operation. This option is useful for tasks on devices that provide for regular pauses in their operation (shutdown or restart).

    • Prompt user for action

      The restart reminder is displayed on the screen of the client device, prompting the user to restart it manually. Some advanced settings can be defined for this option: text of the message for the user, the message display frequency, and the time interval after which a restart will be forced (without the user's confirmation). This option is most suitable for workstations where users must be able to select the most convenient time for a restart.

      By default, this option is selected.

    • Repeat prompt every (min)

      If this option is enabled, the application prompts the user to restart the operating system with the specified frequency.

      By default, this option is enabled. The default interval is 5 minutes. Available values are between 1 and 1440 minutes.

      If this option is disabled, the prompt is displayed only once.

    • Restart after (min)

      After prompting the user, the application forces restart of the operating system upon expiration of the specified time interval.

      By default, this option is enabled. The default delay is 30 minutes. Available values are between 1 and 1440 minutes.

    • Force closure of applications in blocked sessions

      Running applications may prevent a restart of the client device. For example, if a document is being edited in a word processing application and is not saved, the application does not allow the device to restart.

      If this option is enabled, such applications on a locked device are forced to close before the device restart. As a result, users may lose their unsaved changes.

      If this option is disabled, a locked device is not restarted. The task status on this device states that a device restart is required. Users have to manually close all applications running on locked devices and restart these devices.

      By default, this option is disabled.

  9. Specify the account settings:
    • Default account

      The task will be run under the same account as the application that performs this task.

      By default, this option is selected.

    • Specify account

      Fill in the Account and Password fields to specify the details of an account under which the task is run. The account must have sufficient rights for this task.

    • Account

      Account under which the task is run.

    • Password

      Password of the account under which the task will be run.

  10. If you want to modify the default task settings, enable the Open task details when creation is complete option on the Finish task creation page. If you do not enable this option, the task is created with the default settings. You can modify the default settings later, at any time.
  11. Click the Finish button.

    The task is created and displayed in the list of tasks.

  12. Click the name of the created task to open the task properties window.
  13. In the task properties window, specify the general task settings according to your needs.
  14. Click the Save button.

The task is created and configured.

See also:

Creating the Install required updates and fix vulnerabilities task

Viewing information about available third-party software updates

Page top

[Topic 183789]

Viewing information about available third-party software updates

Expand all | Collapse all

You can view the list of available updates for third-party software, including Microsoft software, installed on client devices.

To view a list of available updates for third-party applications installed on client devices,

In the main menu, go to OperationsPatch managementSoftware updates.

A list of available updates appears.

You can specify a filter to view the list of software updates. Click the Filter icon () in the upper right corner of the software updates list to manage the filter. You can also select one of preset filters from the Preset filters drop-down list above the software vulnerabilities list.

To view the properties of an update:

  1. Click the name of the required software update.
  2. The properties window of the update opens, displaying information grouped on the following tabs:
    • General

      This tab displays general details of the selected update:

      • Update approval status (can be changed manually by selecting a new status in the drop-down list)
      • Windows Server Update Services (WSUS) category to which the update belongs
      • Date and time the update was registered
      • Date and time the update was created
      • Importance level of the update
      • Installation requirements imposed by the update
      • Application family to which the update belong
      • Application to which the update applies
      • Number of the update revision
    • Attributes

      This tab displays a set of attributes that you can use to obtain more information about the selected update. This set differs depending on whether the update is published by Microsoft or by a third-party vendor.

      The tab displays the following information for a Microsoft update:

      • Importance level of the update according to the Microsoft Security Response Center (MSRC)
      • Link to the article in the Microsoft Knowledge Base describing the update
      • Link to the article in the Microsoft Security Bulletin describing the update
      • Update identifier (ID)

      The tab displays the following information for a third-party update:

      • Whether the update is a patch or a full distribution package
      • Localization language of the update
      • Whether the update is installed automatically or manually
      • Whether the update was revoked after being applied
      • Link for downloading the update
    • Devices

      This tab displays a list of devices on which the selected update has been installed.

    • Fixed vulnerabilities

      This tab displays a list of vulnerabilities that the selected update can fix.

    • Crossover of updates

      This tab displays possible crossovers between various updates published for the same application, that is, whether the selected update can supersede other updates or, vice versa, be superseded by other updates (available for Microsoft updates only).

    • Tasks to install this update

      This tab displays a list of tasks whose scope includes installation of the selected update. The tab also enables you to create a new remote installation task for the update.

To view the statistics of an update installation:

  1. Select the check box next to the required software update.
  2. Click the Statistics of update installation statuses button.

The diagram of the update installation statuses is displayed. Clicking a status opens a list of devices on which the update has the selected status.

You can view information about available software updates for third-party software, including Microsoft software, installed on the selected managed device running Windows.

To view a list of available updates for third-party software installed on the selected managed device:

  1. In the main menu, go to Assets (Devices)Managed devices.

    The list of managed devices is displayed.

  2. In the list of managed devices, click the link with the name of the device for which you want to view third-party software updates.

    The properties window of the selected device is displayed.

  3. In the properties window of the selected device, select the Advanced tab.
  4. In the left pane, select the Available updates section. If you want to view only installed updates, enable the Show installed updates option.

The list of available third-party software updates for the selected device is displayed.

See also:

Scenario: Updating third-party software

Page top

[Topic 187095]

Exporting the list of available software updates to a file

You can export the list of updates for third-party software, including Microsoft software, that is displayed at the moment to the CSV or TXT files. You can use these files, for example, to send them to your information security manager or to store them for purposes of statistics.

To export to a text file the list of available updates for third-party software installed on all managed devices:

  1. In the main menu, go to Operations → Patch management → Software updates.

    The page displays a list of available updates for third-party software installed on all managed devices.

  2. Click the Export to TXT or Export to CSV button, depending on the format you prefer for export.

The file containing the list of available updates for third-party software, including Microsoft software, is downloaded to the device that you use at the moment.

To export to a text file the list of available updates for third-party software installed on the selected managed device:

  1. Open the list of available third-party software updates on the selected managed device.
  2. Select the software updates you want to export.

    Skip this step if you want to export a complete list of software updates.

    If you want to export a complete list of software updates, only updates displaying on the current page will be exported.

    If you want to export only installed updates, select the Show installed updates check box.

  3. Click the Export to TXT or Export to CSV button, depending on the format you prefer for export.

The file containing the list of updates for third-party software, including Microsoft software, installed on the selected managed device is downloaded to the device you are using at the moment.

See also:

Scenario: Updating third-party software

Page top

[Topic 183775]

Approving and declining third-party software updates

When you configure the Install required updates and fix vulnerabilities task, you can create a rule that requires a specific status of updates that are to be installed. For example, an update rule can allow installation of the following:

  • Only approved updates
  • Only approved and undefined updates
  • All updates irrespective of the update statuses

You can approve updates that must be installed and decline updates that must not be installed.

The usage of the Approved status to manage update installation is efficient for a small amount of updates. To install multiple updates, use the rules that you can configure in the Install required updates and fix vulnerabilities task. We recommend that you set the Approved status for only those specific updates that do not meet the criteria specified in the rules. When you manually approve a large amount of updates, performance of Administration Server decreases and may lead to Administration Server overload.

To approve or decline one or several updates:

  1. In the main menu, go to OperationsPatch managementSoftware updates.

    A list of available updates appears.

  2. Select the updates that you want to approve or decline.
  3. Click Approve to approve the selected updates or Decline to decline the selected updates.

    The default value is Undefined.

The selected updates have the statuses that you defined.

As an option, you can change the approval status in the properties of a specific update.

To approve or decline an update in its properties:

  1. In the main menu, go to OperationsPatch managementSoftware updates.

    A list of available updates appears.

  2. Click the name of the update that you want to approve or decline.

    The update properties window opens.

  3. In the General section, select a status for the update by changing the Update approval status option. You can select the Approved, Declined, or Undefined status.
  4. Click the Save button to save the changes.

The selected update has the status that you defined.

If you set Declined status for third-party software updates, these updates will not be installed on devices for which they were planned but have not yet been installed. Updates will remain on devices on which they were already installed. If you have to delete them, you can manually delete them locally.

See also:

Scenario: Updating third-party software

Creating the Install required updates and fix vulnerabilities task

Page top

[Topic 181247]

Updating third-party applications automatically

Some third-party applications can be updated automatically. The application vendor defines whether or not the application supports the auto-update feature. If a third-party application installed on a managed device supports auto-update, you can specify the auto-update setting in the application properties. After you change the auto-update setting, Network Agents apply the new setting on each managed device on which the application is installed.

The auto-update setting is independent of the other objects and settings of the Vulnerability and patch management feature. For example, this setting does not depend on an update approval status or the update installation tasks, such as Install required updates and fix vulnerabilities, Install Windows Update updates, and Fix vulnerabilities.

To configure the auto-update setting for a third-party application:

  1. In the main menu, go to OperationsThird-party applications → Applications registry.
  2. Click the name of the application for which you want to change the auto-update setting.

    To simplify the search, you can filter the list by the Automatic Updates status column.

    The application properties window opens.

  3. In the General section, select a value for the following setting:

    Automatic Updates status

    Select one of the following options:

    • Undefined

      The auto-update feature is disabled. Kaspersky Security Center Cloud Console installs third-party application updates by using the tasks: Install required updates and fix vulnerabilities, Install Windows Update updates, and Fix vulnerabilities.

    • Allowed

      After the vendor releases an update for the application, this update is installed on the managed devices automatically. No additional actions are required.

    • Blocked

      The application updates are not installed automatically. Kaspersky Security Center Cloud Console installs third-party application updates by using the tasks: Install required updates and fix vulnerabilities, Install Windows Update updates, and Fix vulnerabilities.

  4. Click the Save button to save the changes.

The auto-update setting is applied to the selected application.

See also:

Scenario: Updating third-party software

Page top

[Topic 183975]

Finding and fixing software vulnerabilities

Kaspersky Security Center Cloud Console detects and fixes software

on managed devices running Microsoft Windows families operating systems. Vulnerabilities are detected in the operating system and in third-party software, including Microsoft software.

Updates functionality (including providing anti-virus signature updates and codebase updates), as well as KSN functionality may not be available in the software in the U.S.

Finding software vulnerabilities

To find software vulnerabilities Kaspersky Security Center Cloud Console uses characteristics from the database of known vulnerabilities and Windows Update Database. The database of known vulnerabilities is created and maintained by Kaspersky specialists. It contains information about vulnerabilities, such as vulnerability description, vulnerability detect date, vulnerability severity level. You can find the details of software vulnerabilities on Kaspersky website.

Kaspersky Security Center Cloud Console uses the Find vulnerabilities and required updates task to find software vulnerabilities.

Fixing software vulnerabilities

To fix software vulnerabilities, Kaspersky Security Center Cloud Console uses software updates issued by the software vendors. You can view the list of software vulnerabilities at any time. The software updates metadata is downloaded to the Administration Server repository automatically and to the repositories of distribution points as a result of the Download updates to the repositories of distribution points task run. You can create this task by the Kaspersky Security Center Cloud Console quick start wizard or manually.

Software updates to fix vulnerabilities can be represented as full distribution packages or patches. Software updates that fix software vulnerabilities are named fixes. In Kaspersky Security Center Cloud Console, you fix vulnerabilities by using recommended fixes. Recommended fixes are software updates that are recommended for installation by Kaspersky specialists.

Depending on the Kaspersky Security Center Cloud Console mode and your current license, you can use Install required updates and fix vulnerabilities task or the Fix vulnerabilities task to fix software vulnerabilities.

The Install required updates and fix vulnerabilities task automatically fixes multiple vulnerabilities installing recommended fixes. For this task, you can manually configure certain rules to fix multiple vulnerabilities.

By means of the Fix vulnerabilities task, you can fix vulnerabilities by installing recommended fixes for Microsoft software.

For security reasons, any third-party software updates that you install by using the Vulnerability and patch management feature are automatically scanned for malware by Kaspersky technologies. These technologies are used for automatic file checks and include virus scanning, static analysis, dynamic analysis, behavior analysis in the sandbox environment, and machine learning.

Kaspersky experts do not perform manual analysis of third-party software updates that can be installed by using the Vulnerability and patch management feature. In addition, Kaspersky experts do not search for vulnerabilities (known or unknown) or undocumented features in such updates, nor do they perform other types of analysis of the updates other than those specified in the paragraph above.

The software update installation tasks have a number of limitations. These limitations depend on the license under which you are using Kaspersky Security Center Cloud Console and on the mode in which Kaspersky Security Center Cloud Console is working.

A user interaction may be required when you update a third-party application or fix a vulnerability in a third-party application on a managed device. For example, the user may be prompted to close the third-party application if it is currently open.

To fix some software vulnerabilities, you must accept the End User License Agreement (EULA) for installing the software if EULA acceptance is requested. If you decline EULA, the software vulnerability cannot be fixed.

The information about each fixed vulnerability is stored on the Administration Server for 90 days. After this time, it is automatically deleted.

See also:

Find vulnerabilities and required updates task settings

Creating the Find vulnerabilities and required updates task

Installing third-party software updates

Scenario: Finding and fixing software vulnerabilities

Page top

[Topic 182760]

Fixing software vulnerabilities

Expand all | Collapse all

After you obtain the software vulnerabilities list, you can fix software vulnerabilities on managed devices that are running Windows. You can fix software vulnerabilities in the operating system and in third-party software, including Microsoft software, by creating and running the Fix vulnerabilities task or the Install required updates and fix vulnerabilities task.

The software update installation tasks have a number of limitations. These limitations depend on the license under which you are using Kaspersky Security Center Cloud Console and on the mode in which Kaspersky Security Center Cloud Console is working.

A user interaction may be required when you update a third-party application or fix a vulnerability in a third-party application on a managed device. For example, the user may be prompted to close the third-party application if it is currently open.

As an option, you can create a task to fix software vulnerabilities in the following ways:

  • By opening the vulnerability list and specifying which vulnerabilities to fix.

    As a result, a new task to fix software vulnerabilities is created. As an option, you can add the selected vulnerabilities to an existing task.

  • By running the Vulnerability fix wizard.

    The availability of this feature depends on the Kaspersky Security Center Cloud Console mode and your current license.

    The wizard simplifies creation and configuration of a vulnerability fix task and enables you to eliminate the creation of redundant tasks that contain the same updates to install.

Fixing software vulnerabilities by using the vulnerability list

To fix software vulnerabilities:

  1. Open one of the lists of vulnerabilities:
    • To open the general vulnerability list, in the main menu, go to OperationsPatch managementSoftware vulnerabilities.
    • To open the vulnerability list for a managed device, in the main menu, go to Assets (Devices)Managed devices<device name>AdvancedSoftware vulnerabilities.
    • To open the vulnerability list for a specific application, in the main menu, go to OperationsThird-party applications → Applications registry<application name>Vulnerabilities.

    A page with a list of vulnerabilities in the third-party software is displayed.

  2. Select one or more vulnerabilities in the list, and then click the Fix vulnerability button.

    If a recommended software update to fix one of the selected vulnerabilities is absent, an informative message is displayed.

    To fix some software vulnerabilities, you must accept the End User License Agreement (EULA) for installing the software if EULA acceptance is requested. If you decline the EULA, the software vulnerability is not fixed.

  3. Select one of the following options:
    • New task

      The New task wizard starts. Depending on the Kaspersky Security Center Cloud Console mode and your current license, the Install required updates and fix vulnerabilities task or the Fix vulnerabilities task is preselected. Follow the steps of the wizard to complete the task creation.

    • Fix vulnerability (add rule to specified task)

      Select a task to which you want to add the selected vulnerabilities. Depending on the Kaspersky Security Center Cloud Console mode and your current license, select an Install required updates and fix vulnerabilities task or a Fix vulnerabilities task. If you select an Install required updates and fix vulnerabilities task, a new rule to fix the selected vulnerabilities will be automatically added to the selected task. If you select a Fix vulnerabilities task, the selected vulnerabilities will be added to the task properties.

      The task properties window opens. Click the Save button to save the changes.

If you have chosen to create a task, the task is created and displayed in the task list at Assets (Devices)Tasks. If you have chosen to add the vulnerabilities to an existing task, the vulnerabilities are saved in the task properties.

To fix the third-party software vulnerabilities, start the Install required updates and fix vulnerabilities task or the Fix vulnerabilities task. If you have created the Fix vulnerabilities task, you must manually specify the software updates to fix the software vulnerabilities listed in the task settings.

Fixing software vulnerabilities by using the Vulnerability fix wizard

The availability of the Vulnerability fix wizard depends on the license that you use and the mode in which Kaspersky Security Center Cloud Console is working.

To fix software vulnerabilities by using the Vulnerability fix wizard:

  1. In the main menu, go to OperationsPatch managementSoftware vulnerabilities.

    A page with a list of vulnerabilities in the third-party software installed on managed devices is displayed.

  2. Select the check box next to the vulnerability that you want to fix.
  3. Click the Run Vulnerability fix wizard button.

    The Vulnerability fix wizard starts. The Select the vulnerability fix task page displays the list of all existing tasks of the following types:

    • Install required updates and fix vulnerabilities
    • Install Windows Update updates
    • Fix vulnerabilities

    You cannot modify the last two types of tasks to install new updates. To install new updates, you can only use the Install required updates and fix vulnerabilities task.

  4. If you want the wizard to display only those tasks that fix the vulnerability that you selected, then enable the Show only tasks that fix this vulnerability option.
  5. Choose what you want to do:
    • To start a task, select the check box next to the task name, and then click the Start button.
    • To add a new rule to an existing task:
      1. Select the check box next to the task name, and then click the Add rule button.
      2. On the page that opens, configure the new rule:
        • Rule for fixing vulnerabilities of this severity level

          Sometimes software updates may impair the user experience with the software. In such cases, you may decide to install only those updates that are critical for the software operation and to skip other updates.

          If this option is enabled, the updates fix only those vulnerabilities for which the severity level set by Kaspersky is equal to or higher than the severity of the selected update (Medium, High, or Critical). Vulnerabilities with a severity level lower than the selected value are not fixed.

          If this option is disabled, the updates fix all vulnerabilities regardless of their severity level.

          By default, this option is disabled.

        • Rule for fixing vulnerabilities by means of updates of the same type as the update defined as recommended for the selected vulnerability (available only for Microsoft software vulnerabilities)
        • Rule for fixing vulnerabilities in applications from the selected vendor (available only for third-party software vulnerabilities)
        • Rule for fixing a vulnerability in all versions of the selected application (available only for third-party software vulnerabilities)
        • Rule for fixing the selected vulnerability
        • Approve updates that fix this vulnerability

          The selected update will be approved for installation. Enable this option if some applied rules of update installation allow installation of approved updates only.

          By default, this option is disabled.

      3. Click the Add button.
    • To create a task:
      1. Click the New task button.
      2. On the page that opens, configure the new rule:
        • Rule for fixing vulnerabilities of this severity level

          Sometimes software updates may impair the user experience with the software. In such cases, you may decide to install only those updates that are critical for the software operation and to skip other updates.

          If this option is enabled, the updates fix only those vulnerabilities for which the severity level set by Kaspersky is equal to or higher than the severity of the selected update (Medium, High, or Critical). Vulnerabilities with a severity level lower than the selected value are not fixed.

          If this option is disabled, the updates fix all vulnerabilities regardless of their severity level.

          By default, this option is disabled.

        • Rule for fixing vulnerabilities by using updates of the type (available only for Microsoft software vulnerabilities)
        • Rule for fixing vulnerabilities in applications from the selected vendor (available only for third-party software vulnerabilities)
        • Rule for fixing a vulnerability in all versions of the selected application (available only for third-party software vulnerabilities)
        • Rule for fixing the selected vulnerability
        • Approve updates that fix this vulnerability

          The selected update will be approved for installation. Enable this option if some applied rules of update installation allow installation of approved updates only.

          By default, this option is disabled.

      3. Click the Add button.

If you have chosen to start a task, you can close the wizard. The task will complete in background mode. No further actions are required.

If you have chosen to add a rule to an existing task, the task properties window opens. The new rule is already added to the task properties. You can view or modify the rule or other task settings. Click the Save button to save the changes.

If you have chosen to create a task, you continue to create the task in the New task wizard. The new rule that you added in the Vulnerability fix wizard is displayed in the New task wizard. When you complete the New task wizard, the Install required updates and fix vulnerabilities task is added to the task list.

See also:

Scenario: Finding and fixing software vulnerabilities

Page top

[Topic 201980]

Creating the Fix vulnerabilities task

Expand all | Collapse all

The Fix vulnerabilities task enables you fix vulnerabilities in Microsoft software on managed devices that are running Windows.

The availability of this feature depends on the Kaspersky Security Center Cloud Console mode and your current license. We recommend that you use the Install required updates and fix vulnerabilities task instead of the Fix vulnerabilities task. The Install required updates and fix vulnerabilities task enables you to install multiple updates and fix multiple vulnerabilities automatically, according to the rules that you define.

The software update installation tasks have a number of limitations. These limitations depend on the license under which you are using Kaspersky Security Center Cloud Console and on the mode in which Kaspersky Security Center Cloud Console is working.

A user interaction may be required when you update a third-party application or fix a vulnerability in a third-party application on a managed device. For example, the user may be prompted to close the third-party application if it is currently open.

To create the Fix vulnerabilities task:

  1. In the main menu, go to Assets (Devices)Tasks.
  2. Click Add.

    The New task wizard starts. Proceed through the wizard by using the Next button.

  3. For the Kaspersky Security Center Cloud Console application, select the Fix vulnerabilities task type.
  4. Specify the name for the task that you are creating.

    A task name cannot be more than 100 characters long and cannot include any special characters ("*<>?\:|).

  5. Select devices to which the task will be assigned.
  6. Click the Add button.

    The list of vulnerabilities opens.

  7. Select the vulnerabilities that you want to fix, and then click OK.
  8. Specify the operating system restart settings:
    • Do not restart the device

      Client devices are not restarted automatically after the operation. To complete the operation, you must restart a device (for example, manually or through a device management task). Information about the required restart is saved in the task results and in the device status. This option is suitable for tasks on servers and other devices where continuous operation is critical.

    • Restart the device

      Client devices are always restarted automatically if a restart is required for completion of the operation. This option is useful for tasks on devices that provide for regular pauses in their operation (shutdown or restart).

    • Prompt user for action

      The restart reminder is displayed on the screen of the client device, prompting the user to restart it manually. Some advanced settings can be defined for this option: text of the message for the user, the message display frequency, and the time interval after which a restart will be forced (without the user's confirmation). This option is most suitable for workstations where users must be able to select the most convenient time for a restart.

      By default, this option is selected.

    • Repeat prompt every (min)

      If this option is enabled, the application prompts the user to restart the operating system with the specified frequency.

      By default, this option is enabled. The default interval is 5 minutes. Available values are between 1 and 1440 minutes.

      If this option is disabled, the prompt is displayed only once.

    • Restart after (min)

      After prompting the user, the application forces restart of the operating system upon expiration of the specified time interval.

      By default, this option is enabled. The default delay is 30 minutes. Available values are between 1 and 1440 minutes.

    • Force closure of applications in blocked sessions

      Running applications may prevent a restart of the client device. For example, if a document is being edited in a word processing application and is not saved, the application does not allow the device to restart.

      If this option is enabled, such applications on a locked device are forced to close before the device restart. As a result, users may lose their unsaved changes.

      If this option is disabled, a locked device is not restarted. The task status on this device states that a device restart is required. Users have to manually close all applications running on locked devices and restart these devices.

      By default, this option is disabled.

  9. Specify the account settings:
    • Default account

      The task will be run under the same account as the application that performs this task.

      By default, this option is selected.

    • Specify account

      Fill in the Account and Password fields to specify the details of an account under which the task is run. The account must have sufficient rights for this task.

    • Account

      Account under which the task is run.

    • Password

      Password of the account under which the task will be run.

  10. If on the Finish task creation page you enable the Open task details when creation is complete option, you can modify the default task settings. If you do not enable this option, the task is created with the default settings. You can modify the default settings later, at any time.
  11. Click the Finish button.

    The task is created and displayed in the list of tasks.

  12. Click the name of the created task to open the task properties window.
  13. In the task properties window, specify the general task settings according to your needs.
  14. Click the Save button.

The task is created and configured.

See also:

Creating the Install required updates and fix vulnerabilities task

Fixing software vulnerabilities

Scenario: Finding and fixing software vulnerabilities

Page top

[Topic 182671_1]

Creating the Install required updates and fix vulnerabilities task

Expand all | Collapse all

The availability of the Install required updates and fix vulnerabilities task depends on the Kaspersky Security Center Cloud Console mode and your current license.

The Install required updates and fix vulnerabilities task is used to update and fix vulnerabilities in third-party software, including Microsoft software, installed on the managed devices. This task enables you to install multiple updates and fix multiple vulnerabilities according to certain rules.

To install updates or fix vulnerabilities by using the Install required updates and fix vulnerabilities task, you can do one of the following:

The software update installation tasks have a number of limitations. These limitations depend on the license under which you are using Kaspersky Security Center Cloud Console and on the mode in which Kaspersky Security Center Cloud Console is working.

To create the Install required updates and fix vulnerabilities task:

  1. In the main menu, go to Assets (Devices)Tasks.
  2. Click Add.

    The New task wizard starts. Follow the steps of the wizard.

  3. For the Kaspersky Security Center Cloud Console application, select the Install required updates and fix vulnerabilities task type.
  4. Specify the name for the task that you are creating. A task name cannot be more than 100 characters long and cannot include any special characters ("*<>?\:|).
  5. Select devices to which the task will be assigned.
  6. Specify the rules for update installation, and then specify the following settings:
    • Start installation at device restart or shutdown

      If this option is enabled, updates are installed when the device is restarted or shut down. Otherwise, updates are installed according to a schedule.

      Use this option if installing the updates might affect the device performance.

      By default, this option is disabled.

    • Install the required general system components

      If this option is enabled, before installing an update the application automatically installs all general system components (prerequisites) that are required to install the update. For example, these prerequisites can be operating system updates.

      If this option is disabled, you may have to install the prerequisites manually.

      By default, this option is disabled.

    • Allow installation of new application versions during updates

      If this option is enabled, updates are allowed when they result in installation of a new version of a software application.

      If this option is disabled, the software is not upgraded. You can then install new versions of the software manually or through another task. For example, you may use this option if your company infrastructure is not supported by a new software version or if you want to check an upgrade in a test infrastructure.

      By default, this option is enabled.

      Upgrading an application may cause malfunction of dependent applications installed on client devices.

    • Download updates to the device without installing them

      If this option is enabled, the application downloads updates to the device but does not install them automatically. You can then Install downloaded updates manually.

      Microsoft updates are downloaded to the system Windows storage. Updates of third-party applications (applications made by software vendors other than Kaspersky and Microsoft) are downloaded to the folder specified in the Download updates to field.

      If this option is disabled, the updates are installed to the device automatically.

      By default, this option is disabled.

    • Download updates to

      This folder is used to download updates of third-party applications (applications made by software vendors other than Kaspersky and Microsoft).

    • Enable advanced diagnostics

      If this feature is enabled, Network Agent writes traces even if tracing is disabled for Network Agent in Kaspersky Security Center Cloud Console Remote Diagnostics Utility. Traces are written to two files in turn; the total size of both files is determined by the Maximum size, in MB, of advanced diagnostics files value. When both files are full, Network Agent starts writing to them again. The files with traces are stored in the %WINDIR%\Temp folder. These files are accessible in the remote diagnostics utility, you can download or delete them there.

      If this feature is disabled, Network Agent writes traces according to the settings in Kaspersky Security Center Cloud Console Remote Diagnostics Utility. No additional traces are written.

      When creating a task, you do not have to enable advanced diagnostics. You may want to use this feature later if, for example, a task run fails on some of the devices and you want to get additional information during another task run.

      By default, this option is disabled.

    • Maximum size, in MB, of advanced diagnostics files

      The default value is 100 MB, and available values are between 1 MB and 2048 MB. You may be asked to change the default value by Kaspersky Technical Support specialists when information in the advanced diagnostics files sent by you is not enough to troubleshoot the problem.

  7. Specify operating system restart settings:
    • Do not restart the device

      Client devices are not restarted automatically after the operation. To complete the operation, you must restart a device (for example, manually or through a device management task). Information about the required restart is saved in the task results and in the device status. This option is suitable for tasks on servers and other devices where continuous operation is critical.

    • Restart the device

      Client devices are always restarted automatically if a restart is required for completion of the operation. This option is useful for tasks on devices that provide for regular pauses in their operation (shutdown or restart).

    • Prompt user for action

      The restart reminder is displayed on the screen of the client device, prompting the user to restart it manually. Some advanced settings can be defined for this option: text of the message for the user, the message display frequency, and the time interval after which a restart will be forced (without the user's confirmation). This option is most suitable for workstations where users must be able to select the most convenient time for a restart.

      By default, this option is selected.

    • Repeat prompt every (min)

      If this option is enabled, the application prompts the user to restart the operating system with the specified frequency.

      By default, this option is enabled. The default interval is 5 minutes. Available values are between 1 and 1440 minutes.

      If this option is disabled, the prompt is displayed only once.

    • Restart after (min)

      After prompting the user, the application forces restart of the operating system upon expiration of the specified time interval.

      By default, this option is enabled. The default delay is 30 minutes. Available values are between 1 and 1440 minutes.

    • Wait time before forced closure of applications in blocked sessions (min)

      Applications are forced to close when the user's device goes locked (automatically after a specified interval of inactivity, or manually).

      If this option is enabled, applications are forced to close on the locked device upon expiration of the time interval specified in the entry field.

      If this option is disabled, applications do not close on the locked device.

      By default, this option is disabled.

  8. If on the Finish task creation page you enable the Open task details when creation is complete option, you can modify the default task settings. If you do not enable this option, the task is created with the default settings. You can modify the default settings later, at any time.
  9. Click the Finish button.

    The task is created and displayed in the list of tasks.

  10. Click the name of the created task to open the task properties window.
  11. In the task properties window, specify the general task settings according to your needs.
  12. Click the Save button.

    The task is created and configured.

If the task results contain a warning of the 0x80240033 "Windows Update Agent error 80240033 ("License terms could not be downloaded.")" error, you can resolve this issue through the Windows Registry.

See also:

Scenario: Updating third-party software

Page top

[Topic 182798_1]

Adding rules for update installation

Expand all | Collapse all

The availability of this feature depends on the Kaspersky Security Center Cloud Console mode and your current license.

When installing software updates or fixing software vulnerabilities by using the Install required updates and fix vulnerabilities task, you must specify rules for the update installation. These rules determine the updates to install and the vulnerabilities to fix.

The exact settings depend on whether you add a rule for all updates, for Windows Update updates, or for updates of third-party applications (applications made by software vendors other than Kaspersky and Microsoft). When adding a rule for Windows Update updates or updates of third-party applications, you can select specific applications and application versions for which you want to install updates. When adding a rule for all updates, you can select specific updates that you want to install and vulnerabilities that you want to fix by means of installing updates.

You can add a rule for update installation in the following ways:

To add a new rule for all updates:

  1. Click the Add button.

    The Rule creation wizard starts. Proceed through the wizard by using the Next button.

  2. On the Rule type page, select Rule for all updates.
  3. On the General criteria page, use the drop-down lists to specify the following settings:
    • Set of updates to install

      Select the updates that must be installed on client devices:

      • Install approved updates only. This installs only approved updates.
      • Install all updates (except declined). This installs updates with the Approved or Undefined approval status.
      • Install all updates (including declined). This installs all updates, regardless of their approval status. Select this option with caution. For example, use this option if you want to check installation of some declined updates in a test infrastructure.
    • Fix vulnerabilities with a severity level equal to or higher than

      Sometimes software updates may impair the user experience with the software. In such cases, you may decide to install only those updates that are critical for the software operation and to skip other updates.

      If this option is enabled, the updates fix only those vulnerabilities for which the severity level set by Kaspersky is equal to or higher than the value selected in the list (Medium, High, or Critical). Vulnerabilities with a severity level lower than the selected value are not fixed.

      If this option is disabled, the updates fix all vulnerabilities regardless of their severity level.

      By default, this option is disabled.

  4. On the Updates page, select the updates to be installed:
    • Install all suitable updates

      Install all software updates that meet the criteria specified on the General criteria page of the wizard. Selected by default.

    • Install only updates from the list

      Install only software updates that you select manually from the list. This list contains all available software updates.

      For example, you may want to select specific updates in the following cases: to check their installation in a test environment, to update only critical applications, or to update only specific applications.

    • Automatically install all previous application updates that are required to install the selected updates

      Keep this option enabled if you agree with the installation of interim application versions when this is required for installing the selected updates.

      If this option is disabled, only the selected versions of applications are installed. Disable this option if you want to update applications in a straightforward manner, without attempting to install successive versions incrementally. If installing the selected updates is not possible without installing previous versions of applications, the updating of the application fails.

      For example, you have version 3 of an application installed on a device and you want to update it to version 5, but version 5 of this application can be installed only over version 4. If this option is enabled, the software first installs version 4, and then installs version 5. If this option is disabled, the software fails to update the application.

      By default, this option is enabled.

  5. On the Vulnerabilities page, select vulnerabilities that will be fixed by installing the selected updates:
    • Fix all vulnerabilities that match other criteria

      Fix all vulnerabilities that meet the criteria specified on the General criteria page of the wizard. Selected by default.

    • Fix only vulnerabilities from the list

      Fix only vulnerabilities that you select manually from the list. This list contains all detected vulnerabilities.

      For example, you may want to select specific vulnerabilities in the following cases: to check their fix in a test environment, to fix vulnerabilities only in critical applications, or to fix vulnerabilities only in specific applications.

  6. On the Name page, specify the name for the rule that you are adding. You can later change this name in the Settings section of the properties window of the created task.

After the Rule creation wizard completes its operation, the new rule is added and displayed in the rule list in the New task wizard or in the task properties.

To add a new rule for Windows Update updates:

  1. Click the Add button.

    The Rule creation wizard starts. Proceed through the wizard by using the Next button.

  2. On the Rule type page, select Rule for Windows Update.
  3. On the General criteria page, specify the following settings:
    • Set of updates to install

      Select the updates that must be installed on client devices:

      • Install approved updates only. This installs only approved updates.
      • Install all updates (except declined). This installs updates with the Approved or Undefined approval status.
      • Install all updates (including declined). This installs all updates, regardless of their approval status. Select this option with caution. For example, use this option if you want to check installation of some declined updates in a test infrastructure.
    • Fix vulnerabilities with a severity level equal to or higher than

      Sometimes software updates may impair the user experience with the software. In such cases, you may decide to install only those updates that are critical for the software operation and to skip other updates.

      If this option is enabled, the updates fix only those vulnerabilities for which the severity level set by Kaspersky is equal to or higher than the value selected in the list (Medium, High, or Critical). Vulnerabilities with a severity level lower than the selected value are not fixed.

      If this option is disabled, the updates fix all vulnerabilities regardless of their severity level.

      By default, this option is disabled.

    • Fix vulnerabilities with an MSRC severity level equal to or higher than

      Sometimes software updates may impair the user experience with the software. In such cases, you may decide to install only those updates that are critical for the software operation and to skip other updates.

      If this option is enabled, the updates fix only those vulnerabilities for which the severity level set by Microsoft Security Response Center (MSRC) is equal to or higher than the value selected in the list (Low, Medium, High, or Critical). Vulnerabilities with a severity level lower than the selected value are not fixed.

      If this option is disabled, the updates fix all vulnerabilities regardless of their severity level.

      By default, this option is disabled.

  4. On the Applications page, select the applications and application versions for which you want to install updates. By default, all applications are selected.
  5. On the Categories of updates page, select the categories of updates to be installed. These categories are the same as in Microsoft Update Catalog. By default, all categories are selected.
  6. On the Name page, specify the name for the rule that you are adding. You can later change this name in the Settings section of the properties window of the created task.

After the Rule creation wizard completes its operation, the new rule is added and displayed in the rule list in the New task wizard or in the task properties.

To add a new rule for updates of third-party applications:

  1. Click the Add button.

    The Rule creation wizard starts. Proceed through the wizard by using the Next button.

  2. On the Rule type page, select Rule for third-party updates.
  3. On the General criteria page, specify the following settings:
    • Set of updates to install

      Select the updates that must be installed on client devices:

      • Install approved updates only. This installs only approved updates.
      • Install all updates (except declined). This installs updates with the Approved or Undefined approval status.
      • Install all updates (including declined). This installs all updates, regardless of their approval status. Select this option with caution. For example, use this option if you want to check installation of some declined updates in a test infrastructure.
    • Fix vulnerabilities with a severity level equal to or higher than

      Sometimes software updates may impair the user experience with the software. In such cases, you may decide to install only those updates that are critical for the software operation and to skip other updates.

      If this option is enabled, the updates fix only those vulnerabilities for which the severity level set by Kaspersky is equal to or higher than the value selected in the list (Medium, High, or Critical). Vulnerabilities with a severity level lower than the selected value are not fixed.

      If this option is disabled, the updates fix all vulnerabilities regardless of their severity level.

      By default, this option is disabled.

  4. On the Applications page, select the applications and application versions for which you want to install updates. By default, all applications are selected.
  5. On the Name page, specify the name for the rule that you are adding. You can later change this name in the Settings section of the properties window of the created task.

After the Rule creation wizard completes its operation, the new rule is added and displayed in the rule list in the New task wizard or in the task properties.

See also:

Scenario: Finding and fixing software vulnerabilities

Page top

[Topic 183094]

Viewing information about software vulnerabilities detected on all managed devices

After you have scanned software on managed devices for vulnerabilities, you can view the list of software vulnerabilities detected on all managed devices. If you run the task for the hierarchy of Administration Servers, you can view the list of managed devices with detected vulnerabilities only for the selected Administration Server.

To view the list of software vulnerabilities detected on all managed devices,

In the main menu, go to Operations → Patch management → Software vulnerabilities.

The page displays the list of software vulnerabilities detected on client devices.

You can also generate and view a Report on vulnerabilities.

You can specify a filter to view the list of software vulnerabilities. Click the Filter icon () in the upper right corner of the software vulnerabilities list to manage the filter. You can also select one of preset filters from the Preset filters drop-down list above the software vulnerabilities list.

You can obtain detailed information about any vulnerability from the list.

To obtain information about a software vulnerability:

In the list of software vulnerabilities, click the link with the name of the vulnerability.

The properties window of the software vulnerability opens.

See also:

Scenario: Finding and fixing software vulnerabilities

Page top

[Topic 184794]

Viewing information about software vulnerabilities detected on the selected managed device

You can view information about software vulnerabilities detected on the selected managed device running Windows.

To view the list of software vulnerabilities detected on the selected managed device:

  1. In the main menu, go to Assets (Devices)Managed devices.

    The list of managed devices is displayed.

  2. In the list of managed devices, click the link with the name of the device for which you want to view detected software vulnerabilities.

    The properties window of the selected device is displayed.

  3. In the properties window of the selected device, select the Advanced tab.
  4. In the left pane, select the Software vulnerabilities section.

The list of software vulnerabilities detected on the selected managed device is displayed.

To view the properties of the selected software vulnerability,

Click the link with the name of the software vulnerability in the list of software vulnerabilities.

The properties window of the selected software vulnerability is displayed.

See also:

Scenario: Finding and fixing software vulnerabilities

Page top

[Topic 183984]

Viewing statistics of vulnerabilities on managed devices

You can view statistics for each software vulnerability on managed devices. Statistics are represented as a diagram. The diagram displays the number of devices with the following statuses:

  • Ignored on: <number of devices>. This status is assigned if, in the vulnerability properties, you have manually set the option to ignore the vulnerability.
  • Fixed on: <number of devices>. This status is assigned if the task to fix the vulnerability has successfully completed.
  • Fix scheduled on: <number of devices>. This status is assigned if you have created the task to fix the vulnerability, but the task is not performed yet.
  • Patch applied on: <number of devices>. This status is assigned if you have manually selected a software update to fix the vulnerability, but this software update has not fixed the vulnerability.
  • Fix required on: <number of devices>. This status is assigned if the vulnerability was fixed only on some managed devices, and the vulnerability is required to be fixed on more managed devices.

To view the statistics of a vulnerability on managed devices:

  1. In the main menu, go to Operations → Patch management → Software vulnerabilities.

    The page displays a list of vulnerabilities in applications detected on managed devices.

  2. Select the check box next to the required vulnerability.
  3. Click the Statistics of vulnerability on devices button.

A diagram of the vulnerability statuses is displayed. Clicking a status opens a list of devices on which the vulnerability has the selected status.

See also:

Scenario: Finding and fixing software vulnerabilities

Page top

[Topic 183983]

Exporting the list of software vulnerabilities to a file

You can export the displayed list of vulnerabilities to the CSV or TXT files. You can use these files, for example, to send them to your information security manager or to store them for purposes of statistics.

To export the list of software vulnerabilities detected on all managed devices to a text file:

  1. In the main menu, go to Operations → Patch management → Software vulnerabilities.

    The page displays a list of vulnerabilities in applications detected on managed devices.

  2. Click the Export to TXT or Export to CSV button, depending on the format you prefer for export.

The file containing the list of software vulnerabilities is downloaded to the device that you use at the moment.

To export the list of software vulnerabilities detected on selected managed device to a text file:

  1. Open the list of software vulnerabilities detected on selected managed device.
  2. Select the software vulnerabilities you want to export.

    Skip this step if you want to export a complete list of software vulnerabilities detected on the managed device.

    If you want to export complete list of software vulnerabilities detected on the managed device, only vulnerabilities displaying on the current page will be exported.

  3. Click the Export to TXT or Export to CSV button, depending on the format you prefer for export.

The file containing the list of software vulnerabilities detected on the selected managed device is downloaded to the device you are using at the moment.

See also:

Scenario: Finding and fixing software vulnerabilities

Page top

[Topic 184132]

Ignoring software vulnerabilities

You can ignore software vulnerabilities to be fixed. The reasons to ignore software vulnerabilities might be, for example, the following:

  • You do not consider the software vulnerability to be critical to your organization.
  • You understand that the software vulnerability fix can damage data related to the software that required the vulnerability fix.
  • You are sure that the software vulnerability is not dangerous for your organization's network because you use other measures to protect your managed devices.

You can ignore a software vulnerability on all managed devices or only on selected managed devices.

To ignore a software vulnerability on all managed devices:

  1. In the main menu, go to Operations → Patch management → Software vulnerabilities.

    The page displays the list of software vulnerabilities detected on managed devices.

  2. In the list of software vulnerabilities, click the link with the name of the software vulnerability you want to ignore.

    The software vulnerability properties window opens.

  3. On the General tab, enable the Ignore vulnerability option.
  4. Click the Save button.

    The software vulnerability properties window closes.

The software vulnerability is ignored on all managed devices.

To ignore a software vulnerability on the selected managed device:

  1. In the main menu, go to Assets (Devices) → Managed devices.

    The list of managed devices is displayed.

  2. In the list of managed devices, click the link with the name of the device on which you want to ignore a software vulnerability.

    The device properties window is opened.

  3. In the device properties window, select the Advanced tab.
  4. In the left pane, select the Software vulnerabilities section.

    The list of software vulnerabilities detected on the device is displayed.

  5. In the list of software vulnerabilities, select the vulnerability you want to ignore on the selected device.

    The software vulnerability properties window opens.

  6. In the software vulnerability properties window, on the General tab, enable the Ignore vulnerability option.
  7. Click the Save button.

    The software vulnerability properties window closes.

  8. Close the device properties window.

The software vulnerability is ignored on the selected device.

The ignored software vulnerability will not be fixed after the completion of the Fix vulnerabilities task or Install required updates and fix vulnerabilities task. You can exclude ignored software vulnerabilities from the list of vulnerabilities by using a filter.

See also:

Scenario: Finding and fixing software vulnerabilities

Page top

[Topic 184124_1]

Scenario: Finding and fixing software vulnerabilities

This section provides a scenario for finding and fixing vulnerabilities on the managed devices running Windows. You can find and fix software vulnerabilities in the operating system and in third-party software, including Microsoft software.

Prerequisites

  • Kaspersky Security Center Cloud Console is deployed in your organization.
  • There are managed devices running Windows in your organization.

Stages

Finding and fixing software vulnerabilities proceeds in stages:

  1. Scanning for vulnerabilities in the software installed on the client devices

    To find vulnerabilities in the software installed on the managed devices, run the Find vulnerabilities and required updates task. When this task is complete, Kaspersky Security Center Cloud Console receives the lists of detected vulnerabilities and required updates for the third-party software installed on the devices that you specified in the task properties.

    The Find vulnerabilities and required updates task is created automatically by Kaspersky Security Center Cloud Console quick start wizard. If you did not run the wizard, start it now or create the task manually.

    How-to instructions: Creating the Find vulnerabilities and required updates task

  2. Analyzing the list of detected software vulnerabilities

    View the Software vulnerabilities list and decide which vulnerabilities are to be fixed. To view detailed information about each vulnerability, click the vulnerability name in the list. For each vulnerability in the list, you can also view the statistics on the vulnerability on managed devices.

    How-to instructions:

  3. Configuring vulnerabilities fix

    When the software vulnerabilities are detected, you can fix the software vulnerabilities on the managed devices by using the Install required updates and fix vulnerabilities task or the Fix vulnerabilities task.

    The Install required updates and fix vulnerabilities task is used to update and fix vulnerabilities in third-party software, including Microsoft software, installed on the managed devices. This task enables you to install multiple updates and fix multiple vulnerabilities according to certain rules. Availability of this task depends on the Kaspersky Security Center Cloud Console mode and your current license. To fix software vulnerabilities, the Install required updates and fix vulnerabilities task uses recommended software updates.

    The Fix vulnerabilities task uses recommended fixes for Microsoft software.

    You can start Vulnerability fix wizard that creates one of these tasks automatically, or you can create one of these tasks manually.

    How-to instructions: Fixing vulnerabilities in third-party software, Creating the Install required updates and fix vulnerabilities

  4. Scheduling the tasks

    To be sure that the vulnerabilities list is always up-to-date, schedule the Find vulnerabilities and required updates task to run it automatically from time to time. The recommended average frequency is once a week.

    If you have created the Install required updates and fix vulnerabilities task, you can schedule it to run with the same frequency as the Find vulnerabilities and required updates task or less often. When scheduling the Fix vulnerabilities task, note that you have to select fixes for Microsoft software every time before starting the task.

    When scheduling the tasks, make sure that a task to fix vulnerability starts after the Find vulnerabilities and required updates task is complete.

  5. Ignoring software vulnerabilities (optional)

    If you want, you can ignore software vulnerabilities to be fixed on all managed devices or only on the selected managed devices.

    How-to instructions: Ignoring software vulnerabilities

  6. Running a vulnerability fix task

    Start the Install required updates and fix vulnerabilities task or the Fix vulnerabilities task. After the task is complete, make sure that it has the Completed successfully status in the task list.

  7. Create the report on results of fixing software vulnerabilities (optional)

    To view detailed statistics on the vulnerabilities fix, generate the Report on vulnerabilities. The report displays information about software vulnerabilities that are not fixed. Thus you can have an idea about finding and fixing vulnerabilities in third-party software, including Microsoft software, in your organization.

    How-to instructions: Generating and viewing a report

  8. Checking configuration of finding and fixing vulnerabilities in third-party software

    Make sure of the following:

Results

If you have created and configured the Install required updates and fix vulnerabilities task, the vulnerabilities are fixed on the managed devices automatically. When the task is run, it correlates the list of available software updates to the rules specified in the task settings. All software updates that meet the criteria in the rules will be downloaded to the repositories of distribution points and will be installed to fix software vulnerabilities.

If you have created the Fix vulnerabilities task, only software vulnerabilities in Microsoft software are fixed.

Page top

[Topic 222383]

Setting the maximum storage period for the information about fixed vulnerabilities

To set the maximum storage period in the database for the information about the vulnerabilities that have already been fixed on managed devices:

  1. In the main menu, click the settings icon () next to the name of the required Administration Server.

    The Administration Server properties window opens.

  2. On the page that opens, proceed to the Events repository tab.
  3. Specify the maximum storage period for the information about the fixed vulnerabilities in the database.

    By default, the storage period is 7 days in the trial mode and 60 days in the commercial mode. The maximum limit is 14 days in the trial mode and 365 days in the commercial mode.

  4. Click Save.

The maximum storage period for the information about the fixed vulnerabilities is limited to the specified number of days.

Page top

[Topic 183681]

Using Application Control to manage executable files

You can use the Application Control component to allow or block startup of executable files on user devices. The Application Control component supports Windows-based and Linux-based operating systems.

For Linux-based operating systems, Application Control component is available starting from Kaspersky Endpoint Security 11.2 for Linux.

Prerequisites

  • Kaspersky Security Center Cloud Console is deployed in your organization.
  • The policy of Kaspersky Endpoint Security for Windows or Kaspersky Endpoint Security for Linux is created and is active.

Stages

Application Control usage scenario proceeds in stages:

  1. Forming and viewing the list of executable files on client devices

    This stage helps you find out what executable files are found on managed devices. View the list of executable files and compare it with the lists of allowed and prohibited executable files. The restrictions on executable files usage can be related to the information security polices in your organization.

    How-to instructions: Obtaining and viewing a list of executable files installed on client devices

  2. Creating categories for the executable files used in your organization

    Analyze the lists of executable files stored on managed devices. Based on the analysis, create categories for executable files. It is recommended to create a "Work applications" category that covers the standard set of executable files that are used at your organization. If different security groups use their own sets of executable files in their work, a separate category can be created for each security group.

    How-to instructions: Creating application category with content added manually, Creating application category that includes executable files from selected devices

  3. Configuring Application Control in the Kaspersky Endpoint Security for Windows policy

    Configure the Application Control component in Kaspersky Endpoint Security for Windows policy using the categories you have created on the previous stage.

    How-to instructions: Configuring Application Control in the Kaspersky Endpoint Security for Windows policy

  4. Turning on Application Control component in test mode

    To ensure that Application Control rules do not block executable files required for user's work, it is recommended to enable testing of Application Control rules and analyze their operation after creating new rules. When testing is enabled, Kaspersky Endpoint Security for Windows will not block executable files whose startup is forbidden by Application Control rules, but will instead send notifications about their startup to the Administration Server.

    When testing Application Control rules, it is recommended to perform the following actions:

    • Determine the testing period. Testing period can vary from several days to two months.
    • Examine the events resulting from testing the operation of Application Control.

    How-to instructions: Configuring Application Control component in the Kaspersky Endpoint Security for Windows policy. Follow this instruction and enable the test mode in configuration process.

  5. Changing the categories settings of Application Control component

    If necessary, make changes to the Application Control settings. Based on the test results, you can add executable files related to events of the Application Control component to an application category with content added manually.

    How-to instructions: Adding event-related executable files to the application category

  6. Applying the rules of Application Control in operation mode

    After Application Control rules are tested and configuration of categories is complete, you can apply the rules of Application Control in operation mode.

    How-to instructions: Configuring Application Control component in the Kaspersky Endpoint Security for Windows policy. Follow this instruction and disable the test mode in configuration process.

  7. Verifying Application Control configuration

    Make sure of the following:

    • The list of categories for executable files is not empty. View the list of categories and make sure it contains the categories you have configured.
    • Application Control is configured using created categories for executable files. View the settings of the Kaspersky Endpoint Security for Windows policy and make sure you have configured Application Control in the Application settings → Security Controls → Application Control.
    • The rules of Application Control are applied in operation mode. Check the mode in the Kaspersky Endpoint Security for Windows policy and make sure you have disabled the Test mode in the Application settings → Security Controls Application Control.

Results

When the scenario is complete, startup of executable files on managed devices is controlled. The users can run only those executable files that are allowed in your organization and cannot run executable files that are prohibited in your organization.

For detailed information about Application Control, refer to the following Help topics:

Page top

[Topic 184061]

Application Control modes and categories

The Application Control component monitors users' attempts to start executable files. You can use Application Control rules to control the startup of executable files.

Application Control component is available for Kaspersky Endpoint Security for Windows and for Kaspersky Endpoint Security for Linux (version 11.2 and later). All the instructions in this section describe configuration of Application Control for Kaspersky Endpoint Security.

Startup of executable files whose settings do not match any of the Application Control rules is regulated by the selected operating mode of the component:

  • Denylist. The mode is used if you want to allow the startup of all executable files except those specified in block rules. Denylist mode is selected by default.
  • Allowlist. The mode is used if you want to block the startup of all executable files except those specified in allow rules.

The Application Control rules are implemented through categories for executable files. In Kaspersky Security Center Cloud Console there are two types of categories:

For detailed information about Application Control, refer to the following Help topics:

See also:

Using Application Control to manage executable files

Page top

[Topic 184063]

Obtaining and viewing a list of applications installed on client devices

Kaspersky Security Center Cloud Console inventories all software installed on managed client devices running Linux and Windows.

Network Agent compiles a list of applications installed on a device, and then transmits this list to Administration Server. It takes about 10-15 minutes for the Network Agent to update the application list.

For Windows-based client devices, Network Agent receives most of the information about installed applications from the Windows registry. For Linux-based client devices, package managers provide information about installed applications to Network Agent.

To view the list of applications installed on managed devices:

  1. In the main menu, go to Operations Third-party applications → Applications registry.

    The page displays a table with the applications that are installed on managed devices. Select the application to view its properties, for example, vendor name, version number, list of executable files, list of devices on which the application is installed, list of available software updates, and list of detected software vulnerabilities.

  2. You can group and filter the data of the table with installed applications as follows:
    • Click the settings icon (The Setting icon.) in the upper-right corner of the table.

      In the invoked Columns settings menu, select the columns to be displayed in the table. To view the operating system type of the client devices on which the application is installed, select the Operating system type column.

    • Click the filter icon (The Filter icon.) in the upper-right corner of the table, and then specify and apply the filter criterion in the invoked menu.

      The filtered table of installed applications is displayed.

To view the list of applications installed on a specific managed device,

In the main menu, go to DevicesManaged devices<device name>AdvancedApplications registry. In this menu, you can export the list of applications to a CSV file or TXT file.

For detailed information about Application Control, refer to the following Help topics:

See also:

Using Application Control to manage executable files

Page top

[Topic 184064]

Obtaining and viewing a list of executable files installed on client devices

You can obtain the list of executable files stored on client devices in one of the following ways:

  • Enabling notifications about applications startup in Kaspersky Endpoint Security policy.
  • Creating an inventory task.

Enabling notifications about applications startup in Kaspersky Endpoint Security policy

To enable notifications about applications startup:

  1. Open the Kaspersky Endpoint Security policy settings, and then go to General settingsReports and Storage.
  2. In the Data transfer to Administration Server settings group, select the About started applications check box, and save the changes.

When a user attempts to start executable files, information about these files is added to the list of executable files on a client device. Kaspersky Endpoint Security sends this information to Network Agent, and then Network Agent sends it to Administration Server.

Creating an inventory task

The feature of inventorying executable files is available for the following applications:

  • Kaspersky Endpoint Security for Windows
  • Kaspersky Endpoint Security for Linux (version 11.2 and later)

You can reduce load on the database while obtaining information about the installed applications. To do this, we recommend that you run an inventory task on reference devices on which a standard set of software is installed. The preferable number of devices is 1-3.

We strongly do not recommend running the inventory task when using the following databases: MySQL, PostgreSQL, SQL Server Express Edition, MariaDB (all editions).

To create an inventory task for executable files on client devices:

  1. In the main menu, go to Assets (Devices) → Tasks.

    The list of tasks is displayed.

  2. Click the Add button.

    The New task wizard starts. Follow the steps of the wizard.

  3. On the New task settings page, in the Application drop-down list, select Kaspersky Endpoint Security for Windows or Kaspersky Endpoint Security for Linux, depending on the operating system type of the client devices.
  4. In the Task type drop-down list, select Inventory.
  5. On the Finish task creation page, click the Finish button.

After the New task wizard is complete, the Inventory task is created and configured. If you want, you can change the settings for the created task. The newly created task is displayed in the list of tasks.

For a detailed description of the inventory task, refer to the following Helps:

After the Inventory task is performed, the list of executable files installed on managed devices is formed and you can view the list.

During inventory, the following formats of executable files can be detected (depending on the option that you select in the inventory task properties): MZ, COM, PE, NE, SYS, CMD, BAT, PS1, JS, VBS, REG, MSI, CPL, DLL, JAR, and HTML.

Viewing the list of executable files stored on managed devices

To view the list of executable files stored on client devices,

In the main menu, go to Operations → Third-party applications → Executable files.

The page displays the list of executable files installed on client devices.

If necessary, you can send the executable file of the managed device to the device where your Kaspersky Security Center Cloud Console is open.

To send an executable file:

  1. In the main menu, go to Operations → Third-party applications → Executable files.
  2. Click the link of the executable file that you want to send.
  3. In the window that opens, go to the Devices section, and then select the check box of the managed device from which you want to send the executable file.

    Before you send the executable file, make sure that the managed device has a direct connection to the Administration Server, by selecting the Do not disconnect from the Administration Server check box. The maximum total number of devices with the Do not disconnect from the Administration Server option selected is 300.

  4. Click the Send button.

The selected executable file is downloaded for further sending to the device where your Kaspersky Security Center Cloud Console is open.

See also:

Using Application Control to manage executable files

Page top

[Topic 184075]

Creating application category with content added manually

Expand all | Collapse all

You can specify a set of criteria as a template of executable files for which you want to allow or block a start in your organization. On the basis of executable files corresponding to the criteria, you can create an application category and use it in the Application Control component configuration.

To create an application category with content added manually:

  1. In the main menu, go to Operations Third-party applications → Application categories.

    The page with a list of application categories is displayed.

  2. Click the Add button.

    The New category wizard starts. Proceed through the wizard by using the Next button.

  3. On the Select category creation method step, select the Category with content added manually. Data of executable files is manually added to the category option.
  4. On the Conditions step, click the Add button to add a condition criterion to include files in the creating category.
  5. On the Condition criteria step, select a rule type for the creation of category from the list:
    • From KL category

      If this option is selected, you can specify a Kaspersky application category as the condition of adding applications to the user category. The applications from the specified Kaspersky category will be added to the user application category.

    • Select certificate from repository

      If this option is selected, you can specify certificates from the storage. Executable files that have been signed in accordance with the specified certificates will be added to the user category.

    • Specify path to application (masks supported)

      If this option is selected, you can specify the path to the file or folder on the client device containing the executable files that are to be added to the user application category. You can use regular expressions such as C:\path_to_exe\*, for example: C:\Program Files\Internet Explorer\*.

    • Removable drive

      If this option is selected, you can specify the type of the medium (any drive or removable drive) on which the application is run. Applications that have been run on the selected drive type are added to the user application category.

    • Hash, metadata, or certificate:
      • Select from list of executable files

        If this option is selected, you can use the list of executable files on the client device to select and add applications to the category.

      • Select from applications registry

        If this option is selected, application registry is displayed. You can select an application from the registry and specify the following file metadata:

        • File name.
        • File version. You can specify precise value of the version or describe a condition, for example "greater than 5.0".
        • Application name.
        • Application version. You can specify precise value of the version or describe a condition, for example "greater than 5.0".
        • Vendor.
      • Specify manually

        If this option is selected, you must specify file hash, or metadata, or certificate as the condition of adding applications to the user category.

        File Hash

        Depending on the version of the security application installed on devices on your network, you must select an algorithm for hash value computing by Kaspersky Security Center Cloud Console for files in this category. Information about computed hash values is stored in the Administration Server database. Storage of hash values does not increase the database size significantly.

        SHA256 is a cryptographic hash function: no vulnerabilities have been found in its algorithm, and so it is considered the most reliable cryptographic function nowadays. Kaspersky Endpoint Security 10 Service Pack 2 for Windows and later versions support SHA256 computing. Computing of the MD5 hash function is supported by all versions earlier than Kaspersky Endpoint Security 10 Service Pack 2 for Windows.

        Select either of the options of hash value computing by Kaspersky Security Center Cloud Console for files in the category:

        • If all instances of security applications installed on your network are Kaspersky Endpoint Security 10 Service Pack 2 for Windows or later versions, select the SHA256 check box. We do not recommend that you add any categories created according to the criterion of the SHA256 hash of an executable file for versions earlier than Kaspersky Endpoint Security 10 Service Pack 2 for Windows. This may result in failures in the security application operation. In this case, you can use the MD5 cryptographic hash function for files of the category.
        • If any versions earlier than Kaspersky Endpoint Security 10 Service Pack 2 for Windows are installed on your network, select the MD5 hash. You cannot add a category that was created based on the criterion of the MD5 checksum of an executable file for Kaspersky Endpoint Security 10 Service Pack 2 for Windows or later versions. In this case, you can use the SHA256 cryptographic hash function for files of the category.
        • If different devices on your network use both earlier and later versions of Kaspersky Endpoint Security 10, select both the SHA256 check box and the MD5 hash check box.

        Metadata

        If this option is selected, you can specify file metadata as file name, file version, vendor. The metadata will be sent to Administration Server. Executable files that contain the same metadata will be added to the application category.

        Certificate

        If this option is selected, you can specify certificates from the storage. Executable files that have been signed in accordance with the specified certificates will be added to the user category.

      • From file or from MSI package/archived folder

        If this option is selected, you can specify an MSI installer file as the condition of adding applications to the user category. The application installer metadata will be sent to Administration Server. The applications for which the installer metadata is the same as for the specified MSI installer are added to the user application category.

    The selected criterion is added to the list of conditions.

    You can add as many criteria for the creating application category as you need.

  6. On the Exclusions step, click the Add button to add an exclusive condition criterion to exclude files from the category that is being created.
  7. On the Condition criteria step, select a rule type from the list, in the same way that you selected a rule type for category creation.

When the wizard finishes, the application category is created. It is displayed in the list of application categories. You can use the created application category when you configure Application Control.

For detailed information about Application Control, refer to the following Help topics:

See also:

Using Application Control to manage executable files

Page top

[Topic 184076]

Creating application category that includes executable files from selected devices

Expand all | Collapse all

You can use executable files from selected devices as a template of executable files that you want to allow or block. Based on executable files from selected devices, you can create a category and use it in the Application Control component configuration.

To create a category that includes executable files from selected devices:

  1. In the main menu, go to Operations → Third-party applications → Application categories.

    The page with a list of categories for executable files is displayed.

  2. Click the Add button.

    The New category wizard starts. Proceed through the wizard by using the Next button.

  3. On the Select category creation method step, specify the category name and select the Category that includes executable files from selected devices. These executable files are processed automatically and their metrics are added to the category option.
  4. Click Add.
  5. In the window that opens, select a device or devices whose executable files will be used to create the category.
  6. Specify the following settings:
    • Hash value computing algorithm

      Depending on the version of the security application installed on devices on your network, you must select an algorithm for hash value computing by Kaspersky Security Center Cloud Console for files in this category. Information about computed hash values is stored in the Administration Server database. Storage of hash values does not increase the database size significantly.

      SHA256 is a cryptographic hash function: no vulnerabilities have been found in its algorithm, and so it is considered the most reliable cryptographic function nowadays. Kaspersky Endpoint Security 10 Service Pack 2 for Windows and later versions support SHA256 computing. Computing of the MD5 hash function is supported by all versions earlier than Kaspersky Endpoint Security 10 Service Pack 2 for Windows.

      Select either of the options of hash value computing by Kaspersky Security Center Cloud Console for files in the category:

      • If all instances of security applications installed on your network are Kaspersky Endpoint Security 10 Service Pack 2 for Windows or later versions, select the SHA256 check box. We do not recommend that you add any categories created according to the criterion of the SHA256 hash of an executable file for versions earlier than Kaspersky Endpoint Security 10 Service Pack 2 for Windows. This may result in failures in the security application operation. In this case, you can use the MD5 cryptographic hash function for files of the category.
      • If any versions earlier than Kaspersky Endpoint Security 10 Service Pack 2 for Windows are installed on your network, select the MD5 hash. You cannot add a category that was created based on the criterion of the MD5 checksum of an executable file for Kaspersky Endpoint Security 10 Service Pack 2 for Windows or later versions. In this case, you can use the SHA256 cryptographic hash function for files of the category.

      If different devices on your network use both earlier and later versions of Kaspersky Endpoint Security 10, select both the SHA256 check box and the MD5 hash check box.

      The Calculate SHA256 for files in this category (supported by Kaspersky Endpoint Security 10 Service Pack 2 for Windows and any later versions) check box is selected by default.

      The Calculate MD5 for files in this category (supported by versions earlier than Kaspersky Endpoint Security 10 Service Pack 2 for Windows) is cleared by default.

    • Synchronize data with Administration Server repository

      Select this option if you want that Administration Server periodically to check changes in the specified folder (or folders).

      By default, this option is disabled.

      If you enable this option, specify the period (in hours) to check changes in the specified folder (folders). By default, scan interval is 24 hours.

    • File type

      In this section, you can specify file type that is used to create the application category.

      All files. All files are taken into consideration when creating the category. By default, this option is selected.

      Only files outside the application categories. Only files outside the application categories are taken into consideration when creating the category.

    • Folders

      In this section you can specify which folders from the selected device (devices) contain files that are used to create the application category.

      All folders. All folders are taken into consideration for the creating category. By default, this option is selected.

      Specified folder. Only specified folder is taken into consideration for the creating category. If you select this option you must specify path to the folder.

When the wizard finishes, the category for executable files is created. It is displayed in the list of categories. You can use the created category when you configure Application Control.

See also:

Using Application Control to manage executable files

Page top

[Topic 191028]

Viewing the list of application categories

You can view the list of configured application categories and the settings of each application category.

To view the list of application categories,

In the main menu, go to Operations → Third-party applications → Application categories.

The page with a list of application categories is displayed.

To view properties of an application category,

Click the name of the application category.

The properties window of the application category is displayed. The properties are grouped on several tabs.

See also:

Using Application Control to manage executable files

Page top

[Topic 184079]

Configuring Application Control in the Kaspersky Endpoint Security for Windows policy

After you create Application Control categories, you can use them for configuring Application Control in Kaspersky Endpoint Security for Windows policies.

To configure Application Control in the Kaspersky Endpoint Security for Windows policy:

  1. In the main menu, go to Assets (Devices) → Policies & profiles.

    A page with a list of policies is displayed.

  2. Click Kaspersky Endpoint Security for Windows policy.

    The policy settings window opens.

  3. Go to Application settings → Security Controls → Application Control.

    The Application Control window with Application Control settings is displayed.

  4. The Application Control option is enabled by default. Switch the toggle button Application Control DISABLED to disable the option.
  5. In the Application Control Settings block settings, enable the operation mode to apply the Application Control rules and allow Kaspersky Endpoint Security for Windows to block startup of applications.

    If you want to test the Application Control rules, in the Application Control Settings section, enable test mode. In test mode, Kaspersky Endpoint Security for Windows does not block startup of applications, but logs information about triggered rules in the report. Click the View report link to view this information.

  6. Enable the Control DLL modules load option if you want Kaspersky Endpoint Security for Windows to monitor the loading of DLL modules when applications are started by users.

    Information about the module and the application that loaded the module will be saved to a report.

    Kaspersky Endpoint Security for Windows monitors only the DLL modules and drivers loaded after the Control DLL modules load option is selected. Restart the computer after selecting the Control DLL modules load option if you want Kaspersky Endpoint Security for Windows to monitor all DLL modules and drivers, including those loaded before Kaspersky Endpoint Security for Windows is started.

  7. (Optional) In the Message templates block, change the template of the message that is displayed when an application is blocked from starting and the template of the email message that is sent to you.
  8. In the Application Control Mode block settings, select the Denylist or Allowlist mode.

    By default, the Denylist mode is selected.

  9. Click the Rules Lists Settings link.

    The Denylists and allowlists window opens to let you add an application category. By default, the Denylist tab is selected if the Denylist mode is selected, and the Allowlist tab is selected if the Allowlist mode is selected.

  10. In the Denylists and allowlists window, click the Add button.

    The Application Control rule window opens.

  11. Click the Please choose a category link.

    The Application Category window opens.

  12. Add the application category (or categories) that you created earlier.

    You can edit the settings of a created category by clicking the Edit button.

    You can create a new category by clicking the Add button.

    You can delete a category from the list by clicking the Delete button.

  13. After the list of application categories is complete, click the OK button.

    The Application Category window closes.

  14. In the Application Control rule window, in the Subjects and their rights section, create a list of users and groups of users to apply the Application Control rule.
  15. Click the OK button to save the settings and to close the Application Control rule window.
  16. Click the OK button to save the settings and to close the Denylists and allowlists window.
  17. Click the OK button to save the settings and to close the Application Control window.
  18. Close the window with the Kaspersky Endpoint Security for Windows policy settings.

Application Control is configured. After the policy is propagated to the client devices, the startup of executable files is managed.

For detailed information about Application Control, refer to the following Help topics:

See also:

Using Application Control to manage executable files

Page top

[Topic 186329]

Adding event-related executable files to the application category

Expand all | Collapse all

After you configure Application Control in the Kaspersky Endpoint Security for Windows policies, the following events will be displayed in the list of events:

  • Application startup prohibited (Critical event). This event is displayed if you have configured Application Control to apply rules.
  • Application startup prohibited in test mode (Info event). This event is displayed if you have configured Application Control to test rules.
  • Message to administrator about application startup prohibition (Warning event). This event is displayed if you have configured Application Control to apply rules and a user has requested access to the application that is blocked at startup.

It is recommended to create event selections to view events related to Application Control operation.

You can add executable files related to Application Control events to an existing application category or to a new application category. You can add executable files only to an application category with content added manually.

To add executable files related to Application Control events to an application category:

  1. In the main menu, go to Monitoring & reporting → Event selections.

    The list of event selections is displayed.

  2. Select the event selection to view events related to Application Control and start this event selection.

    If you have not created event selection related to Application Control, you can select and start a predefined selection, for example, Recent events.

    The list of events is displayed.

  3. Select the events whose associated executable files you want to add to the application category, and then click the Assign to category button.

    The New category wizard starts. Proceed through the wizard by using the Next button.

  4. On the wizard page, specify the relevant settings:
    • In the Action on executable file related to the event section, select one of the following options:
      • Add to a new application category

        Select this option if you want to create a new application category based on event-related executable files.

        By default, this option is selected.

        If you have selected this option, specify a new category name.

      • Add to an existing application category

        Select this option if you want to add event-related executable files to an existing application category.

        By default, this option is not selected.

        If you have selected this option, select the application category with content added manually to which you want to add executable files.

    • In the Rule type section, select one of the following options:
      • Rules for adding to inclusions
      • Rules for adding to exclusions
    • In the Parameter used as a condition section, select one of the following options:
      • Certificate details (or SHA256 hashes for files without a certificate)

        Files may be signed with a certificate. Multiple files may be signed with the same certificate. For example, different versions of the same application may be signed with the same certificate, or several different applications from the same vendor may be signed with the same certificate. When you select a certificate, several versions of an application or several applications from the same vendor may end up in the category.

        Each file has its own unique SHA256 hash function. When you select an SHA256 hash function, only one corresponding file, for example, the defined application version, ends up in the category.

        Select this option if you want to add to the category rules the certificate details of an executable file (or the SHA256 hash function for files without a certificate).

        By default, this option is selected.

      • Certificate details (files without a certificate will be skipped)

        Files may be signed with a certificate. Multiple files may be signed with the same certificate. For example, different versions of the same application may be signed with the same certificate, or several different applications from the same vendor may be signed with the same certificate. When you select a certificate, several versions of an application or several applications from the same vendor may end up in the category.

        Select this option if you want to add the certificate details of an executable file to the category rules. If the executable file has no certificate, this file will be skipped. No information about this file will be added to the category.

      • Only SHA256 (files without a hash will be skipped)

        Each file has its own unique SHA256 hash function. When you select an SHA256 hash function, only one corresponding file, for example, the defined application version, ends up in the category.

        Select this option if you want to add only the details of the SHA256 hash function of the executable file.

      • Only MD5 (discontinued mode, only for Kaspersky Endpoint Security 10 Service Pack 1 version)

        Each file has its own unique MD5 hash function. When you select an MD5 hash function, only one corresponding file, for example, the defined application version, ends up in the category.

        Select this option if you want to add only the details of the MD5 hash function of the executable file. Computing of the MD5 hash function is supported by Kaspersky Endpoint Security 10 Service Pack 1 for Windows and all earlier versions.

  5. Click OK.

When the wizard finishes, executable files related to the Application Control events are added to the existing application category or to a new application category. You can view settings of the application category that you have modified or created.

For detailed information about Application Control, refer to the following Help topics:

See also:

Using Application Control to manage executable files

Page top

[Topic 201899]

Creating an installation package of a third-party application from the Kaspersky database

Kaspersky Security Center Web Console allows you to perform remote installation of third-party applications by using installation packages. Such third-party applications are included in a dedicated Kaspersky database.

Creating installation packages of third-party applications from the Kaspersky database is only available under the Vulnerability and patch management license.

To create an installation package of a third-party application from the Kaspersky database:

  1. In the main menu, go to Discovery & deploymentDeployment & assignmentInstallation packages.
  2. Click the Add button.
  3. On the New package wizard page that opens, select the Select an application from the Kaspersky database to create an installation package option, and then click Next.
  4. In the list of applications that opens, select the relevant application, and then click Next.
  5. Select the relevant localization language in the drop-down list, and then click Next.

    This step is only displayed if the application offers multiple language options.

  6. If you are prompted to accept a License Agreement for the installation, on the End User License Agreement page that opens, click the link to read the License Agreement on the vendor's website, and then select the I confirm that I have fully read, understand, and accept the terms and conditions of this End User License Agreement check box.
  7. On the Name of the new installation package page that opens, in the Package name field, enter the name for the installation package, and then click Next.

Wait until the newly created installation package is uploaded to Administration Server. When the New package wizard displays the message informing you the package creation process was successful, click Finish.

The newly created installation package appears on the list of installation packages. You can select this package when creating or reconfiguring the Install application remotely task.

See also:

Scenario: Configuring network protection

Page top

[Topic 201981]

Viewing and modifying the settings of an installation package of a third-party application from the Kaspersky database

If you have previously created any installation packages of third-party applications listed in the Kaspersky database, you can subsequently view and modify the settings of these packages.

Modifying the settings of an installation package of a third-party application from the Kaspersky database is only available under the Vulnerability and patch management license.

To view and modify the settings of an installation package of a third-party application from the Kaspersky database:

  1. In the main menu, go to Discovery & deploymentDeployment & assignmentInstallation packages.
  2. In the list of installation packages that opens, click the name of the relevant package.
  3. On the properties page that opens, modify the settings, if necessary.
  4. Click the Save button.

The settings that you modified are saved.

See also:

Scenario: Configuring network protection

Page top

[Topic 202244]

Settings of an installation package of a third-party application from the Kaspersky database

Expand all | Collapse all

The settings of an installation package of a third-party application are grouped on the following tabs:

Only a part of the settings listed below are displayed by default so you can add the corresponding columns by clicking the Filter button and selecting relevant column names from the list.

  • General tab:
    • Entry field that contains the name of the installation package that can be edited manually
    • Application

      The name of the third-party application for which the installation package is created.

    • Version

      The version number of the third-party application for which the installation package is created.

    • Size

      The size of the third-party installation package (in kilobytes).

    • Created

      The date and time the third-party installation package was created.

    • Path

      The path to the network folder where the third-party installation package is stored.

  • Installation procedure tab:
    • Install the required general system components

      If this option is enabled, before installing an update the application automatically installs all general system components (prerequisites) that are required to install the update. For example, these prerequisites can be operating system updates.

      If this option is disabled, you may have to install the prerequisites manually.

      By default, this option is disabled.

    • Table that displays the update properties and containing the following columns:
      • Name

        The name of the update.

      • Description

        The description of the update.

      • Source

        The source of the update, that is, whether it was released by Microsoft or by a different third-party developer.

      • Type

        The type of the update, that is, whether it is intended for a driver or an application.

      • Category

        The Windows Server Update Services (WSUS) category displayed for Microsoft updates (Critical Updates, Definition Updates, Drivers, Feature Packs, Security Updates, Service Packs, Tools, Update Rollups, Updates, or Upgrade).

      • Importance level according to MSRC

        The importance level of the update defined by Microsoft Security Response Center (MSRC).

      • Importance level

        The importance level of the update defined by Kaspersky.

      • Patch importance level

        The importance level of the patch if it is intended for a Kaspersky application.

      • Article

        The identifier (ID) of the article in the Knowledge Base describing the update.

      • Bulletin

        The ID of the security bulletin describing the update.

      • Not assigned for installation (new version)

        Displays whether the update has the Not assigned for installation status.

      • To be installed

        Displays whether the update has the To be installed status.

      • Installing

        Displays whether the update has the Installing status.

      • Installed

        Displays whether the update has the Installed status.

      • Failed

        Displays whether the update has the Failed status.

      • Restart is required

        Displays whether the update has the Restart is required status.

      • Registered

        Displays the date and time when the update was registered.

      • Installed in interactive mode

        Displays whether the update requires interaction with the user during installation.

      • Revoked

        Displays the date and time when the update was revoked.

      • Update approval status

        Displays whether the update is approved for installation.

      • Revision

        Displays the current revision number of the update.

      • Update ID

        Displays the ID of the update.

      • Application version

        Displays the version number to which the application is to be updated.

      • Superseded

        Displays other update(s) that can supersede the update.

      • Superseding

        Displays other update(s) that can be superseded by the update.

      • You must accept the terms of the License Agreement

        Displays whether the update requires acceptance of the terms of an End User License Agreement (EULA).

      • Description URL

        Displays the name of the update vendor.

      • Application family

        Displays the name of the family of applications to which the update belongs.

      • Application

        Displays the name of the application to which the update belongs.

      • Localization language

        Displays the language of the update localization.

      • Not assigned for installation (new version)

        Displays whether the update has the Not assigned for installation (new version) status.

      • Requires prerequisites installation

        Displays whether the update has the Requires prerequisites installation status.

      • Download mode

        Displays the mode of the update download.

      • Is a patch

        Displays whether the update is a patch.

      • Not installed

        Displays whether the update has the Not installed status.

  • Settings tab that displays the installation package settings—with their names, descriptions, and values—used as command-line parameters during installation. If the package provides no such settings, the corresponding message is displayed. You can modify the values of these settings.
  • Revision history tab that displays the installation package revisions and containing the following columns:
    • Revision—The revision number of the installation packages.
    • Time—Date and time the installation package settings were modified.
    • User—Name of the user who modified the installation package settings.
    • Action—Action performed on the installation package within the revision.
    • Description—Description of the revision related to the change made to the installation package settings.

      By default, the revision description is blank. To add a description to a revision, select the relevant revision, and then click the Edit description button. In the opened window, enter some text for the revision description.

See also:

Scenario: Configuring network protection

Page top

[Topic 147214]

Application tags

Kaspersky Security Center Cloud Console enables you to tag the applications from applications registry. A tag is the label of an application that can be used for grouping or finding applications. A tag assigned to applications can serve as a condition in device selections.

For example, you can create the [Browsers] tag and assign it to all browsers such as Microsoft Internet Explorer, Google Chrome, Mozilla Firefox.

See also:

Using Application Control to manage executable files

Page top

[Topic 160698]

Creating an application tag

To create an application tag:

  1. In the main menu, go to Operations Third-party applications → Application tags.
  2. Click Add.

    A new tag window opens.

  3. Enter the tag name.
  4. Click OK to save the changes.

The new tag appears in the list of application tags.

See also:

Using Application Control to manage executable files

Page top

[Topic 177853]

Renaming an application tag

To rename an application tag:

  1. In the main menu, go to Operations → Third-party applications → Application tags.
  2. Select the check box next to the tag that you want to rename, and then click Edit.

    A tag properties window opens.

  3. Change the tag name.
  4. Click OK to save the changes.

The updated tag appears in the list of application tags.

See also:

Using Application Control to manage executable files

Page top

[Topic 177855]

Assigning tags to an application

To assign one or several tags to an application:

  1. In the main menu, go to Operations → Third-party applications → Applications registry.
  2. Click the name of the application to which you want to assign tags.
  3. Select the Tags tab.

    The tab displays all application tags that exist on the Administration Server. For tags assigned to the selected application, the check box in the Tag assigned column is selected.

  4. For tags that you want to assign, select check boxes in the Tag assigned column.
  5. Click Save to save the changes.

The tags are assigned to the application.

See also:

Using Application Control to manage executable files

Page top

[Topic 177857]

Removing assigned tags from an application

To remove one or several tags from an application:

  1. In the main menu, go to Operations → Third-party applications → Applications registry.
  2. Click the name of the application from which you want to remove tags.
  3. Select the Tags tab.

    The tab displays all application tags that exist on the Administration Server. For tags assigned to the selected application, the check box in the Tag assigned column is selected.

  4. For tags that you want to remove, clear check boxes in the Tag assigned column.
  5. Click Save to save the changes.

The tags are removed from the application.

The removed application tags are not deleted. If you want, you can delete them manually.

See also:

Using Application Control to manage executable files

Page top

[Topic 177856]

Deleting an application tag

To delete an application tag:

  1. In the main menu, go to Operations → Third-party applications → Application tags.
  2. In the list, select the application tag that you want to delete.
  3. Click the Delete button.
  4. In the window that opens, click OK.

The application tag is deleted. The deleted tag is automatically removed from all of the applications to which it was assigned.

See also:

Using Application Control to manage executable files

Page top

[Topic 178059]

Creating a hierarchy of Administration Servers: adding a secondary Administration Server

Expand all | Collapse all

You can make an Administration Server running on-premises function as a secondary Administration Server, thus establishing a "primary/secondary" hierarchy on your network. For the Administration Server that is in the Kaspersky infrastructure, both primary and secondary Administration Servers on your network are secondary Servers. You can add a Windows-based Administration Server as well as a Linux-based Administration Server.

To add a secondary Administration Server that is available for connection:

  1. Make sure that the future secondary Administration Server has Kaspersky Security Center Web Console installed.
  2. On the future secondary Administration Server, download the Administration Server certificate and save it so you can add it to the primary Administration Server during one of the steps of the Add secondary Administration Server wizard.
  3. Perform the following actions via the Kaspersky Security Center Web Console on the future Secondary Administration Server (alternatively, you can prompt the administrator of the future Secondary Administration Server to perform these actions):
    1. In the main menu, click the settings icon () next to the name of the future secondary Administration Server.
    2. On the properties page that opens, proceed to the Hierarchy of Administration Servers section of the General tab.
    3. Select the This Administration Server is secondary in the hierarchy option.
    4. Select Cloud Console as the type of the primary Administration Server.

      The fields for settings to establish connection between secondary and primary Administration Servers become available.

    5. In the HDS server address (from primary Administration Server on Cloud Console) and HDS server ports fields, enter the address and port of the Kaspersky Security Center Cloud Console primary Administration Server.

      You can find HDS Server address and HDS Server port in the Kaspersky Security Center Cloud Console Administration Server, in the Hierarchy of Administration Servers section of the General tab of the properties window. You can copy and paste this data into the fields in the window of the secondary Administration Server.

    6. Click the Specify primary Administration Server certificate button, and then select the certificate.

      You can download this certificate from Kaspersky Security Center Cloud Console Administration Server, in the Hierarchy of Administration Servers section of the General tab of the properties window, by clicking the View Administration Server certificate button.

    7. Click the Specify Hosted Discovery Service certificates button, and then select the certificate.

      You can download this certificate from Kaspersky Security Center Cloud Console Administration Server, in Hierarchy of Administration Servers section of the General tab of the properties window, by clicking the HDS root CA certificate button.

    8. If you use a proxy server to connect to the Kaspersky Security Center Cloud Console Administration Server (that is, the primary Server in the hierarchy that you have built), specify this and enter the proxy server credentials.
    9. Select the Connect primary Administration Server to secondary Administration Server in DMZ option if the secondary Administration Server is in a demilitarized zone.
    10. Click Save to save the changes and exit the window.
  4. In the main menu, click the settings icon () next to the name of the future primary Administration Server.
  5. On the properties page that opens, click the Administration Servers tab.
  6. Select the check box next to the name of the administration group to which you want to add the secondary Administration Server.
  7. On the menu line, click Connect secondary Administration Server.

    The Add secondary Administration Server wizard starts. Proceed through the wizard by using the Next button.

  8. Fill in the following fields:
    • Secondary Administration Server display name

      A name by which the secondary Administration Server will be displayed in the hierarchy. If you want, you can enter the IP address as a name, or you can use a name like, for example, "Secondary Server for group 1".

    • Secondary Administration Server address (optional)

      Specify the IP address or the domain name of the secondary Administration Server.

      This parameter is required if the Connect primary Administration Server to secondary Administration Server in DMZ option is enabled.

  9. If you use a proxy server to connect to the Kaspersky Security Center Cloud Console Administration Server (that is, the future primary Server), specify this and enter the proxy server credentials.
  10. Follow the further instructions of the wizard.

After the wizard finishes, the "primary/secondary" hierarchy is built. The primary Administration Server starts receiving connection from the secondary Administration Server through port 13000. The tasks and policies from the primary Administration Server are received and applied. The secondary Administration Server is displayed on the primary Administration Server, in the administration group to which it was added.

See also:

Ports used by Kaspersky Security Center Cloud Console

Page top

[Topic 176098]

Configuring storage term of events concerning to the deleted devices

In Kaspersky Security Center Cloud Console, events are stored in an event repository. You cannot configure how many events to store in the event repository.

In the Events repository section of the Administration Server properties window, you can configure the maximum storage term of events concerning to the deleted devices. The maximum storage term is 1000 days.

To configure the number of days to store events relating to the deleted devices:

  1. In the main menu, click the settings icon () next to the Kaspersky Security Center Cloud Console Administration Server.

    The Administration Server properties window opens.

  2. On the General tab, select the Events repository section.
  3. Enable Store events after devices are deleted option.
  4. In the Maximum storage period (days) edit box specify the number of days to store events relating to the deleted devices.

The number of days to store events concerning to the deleted devices is limited by the specified value.

Additionally, you can change the settings of any task to save events related to the task progress, or save only task execution results. In doing so, you will reduce the number of events in the database, increase the speed of execution of scenarios associated with analysis of the event table in the database, and lower the risk that critical events will be overwritten by a large number of events.

See also:

Events of Kaspersky Security Center Cloud Console components

Page top

[Topic 189656]

Aggregate emails about events

During the operation, Kaspersky Security Center Cloud Console and managed Kaspersky applications generate events. Each event is attributed to a certain type and level of severity (Critical, Functional failure, Warning, or Info). Depending on the conditions under which an event occurred, Kaspersky Security Center Cloud Console can assign different levels of severity to events of the same type.

Kaspersky Security Center Cloud Console automatically sends, by email, notifications about events. Kaspersky Security Center Cloud Console sends notifications about events listed in the Administration Server properties window, on the Event configuration tab. Common notification settings are used for all event types.

To limit the number of emails that have to be sent, Kaspersky Security Center Cloud Console, during specific periods, aggregates events with the same severity level. Values of the periods are managed by Kaspersky specialists. As a result, recipients get aggregated email messages according to the following template: "<Number> <Severity_level> (and lower-level) events have occurred".

See also:

Configuring notification delivery

Monitoring and reporting

Page top

[Topic 191452]

Limitations on management of secondary Administration Servers running on-premises through Kaspersky Security Center Cloud Console

After you switch to a secondary Administration Server running on-premises by using the corresponding option in Kaspersky Security Center Cloud Console, the application imposes specific limitations on management of this secondary Administration Server. The following settings related to the Kaspersky Security Center Cloud Console operation become unavailable for the user:

  • In the settings of Network Agent policies and Administration Server policies, the Event configuration and Application settings tabs are unavailable; no new policies can be created.
  • In the settings of Network Agent tasks and Administration Server tasks, the Event configuration and Application settings tabs are unavailable; no new tasks can be created.
  • Management of Network Agent and Administration Server is unavailable, as well as the properties window of the secondary Administration Server.
  • The quick start wizard is unavailable.
  • The storage and notification settings for Network Agent and Administration Server events cannot be modified.
  • The Current application versions section is unavailable.
  • The Installation packages section is unavailable.
Page top

[Topic 178565]

Viewing the list of secondary Administration Servers

To view the list of the secondary (including virtual) Administration Servers:

In the main menu, click the name of the Administration Server, which is next to the settings icon ().

The drop-down list of the secondary (including virtual) Administration Servers is displayed.

You can proceed to any of these Administration Servers by clicking its name.

See also:

Creating a hierarchy of Administration Servers: adding a secondary Administration Server

Page top

[Topic 180308]

Deleting a hierarchy of Administration Servers

If you no longer want to have a hierarchy of Administration Servers, you can disconnect them from this hierarchy.

To delete a hierarchy of Administration Servers:

  1. In the main menu, click the settings icon () next to the name of the primary Administration Server.
  2. On the page that opens, proceed to the Administration Servers tab.
  3. In the administration group from which you want to delete the secondary Administration Server, select the secondary Administration Server.
  4. On the menu line, click Delete.
  5. In the window that opens, click OK to confirm that you want to delete the secondary Administration Server.

The former primary Administration Server and the former secondary Administration Server are now independent of each other. The hierarchy no longer exists.

See also:

Creating a hierarchy of Administration Servers: adding a secondary Administration Server

Page top

[Topic 195133]

Configuring the interface

Expand all | Collapse all

You can configure the Kaspersky Security Center Cloud Console interface to display and hide sections and interface elements, depending on the features that you use.

To configure the Kaspersky Security Center Cloud Console interface in accordance with the currently used set of features:

  1. In the main menu, go to your account settings, and then select Interface options.
  2. In the Interface options window that opens, enable or disable the options:
    • Show data encryption and protection

      You can use this option to hide or show the Operations → Data encryption and protection section in the interface. Kaspersky Security Center Cloud Console saves the value of this option only for your own user account while the other user can set a different value.

    • Show MDR features

      You can use this option to hide or show the Monitoring & reporting Incidents section in the interface. Kaspersky Security Center Cloud Console saves the value of this option only for your own user account while the other user can set a different value.

  3. Set the number of devices that Kaspersky Security Center Cloud Console displays in policy distribution results.
  4. Click Save.

The console interface settings are configured according to your preferences.

Page top

[Topic 177870]

Creating a virtual Administration Server

You can create virtual Administration Servers and add them to administration groups.

To create and add a virtual Administration Server:

  1. In the main menu, click the settings icon () next to the name of the required Administration Server.
  2. On the page that opens, proceed to the Administration Servers tab.
  3. Select the administration group to which you want to add a virtual Administration Server.
  4. On the menu line, click New virtual Administration Server.
  5. On the page that opens, define the Name of virtual Administration Server.
  6. Click Save.

The new virtual Administration Server is created, added to the administration group and displayed on the Administration Servers tab.

Page top

[Topic 218343]

Enabling and disabling a virtual Administration Server

When you create a new virtual Administration Server, it is enabled by default. You can disable or enable it again at any time. Disabling or enabling a virtual Administration Server is equal to switching off or on a physical Administration Server.

To enable or disable a virtual Administration Server:

  1. In the main menu, click the settings icon () next to the name of the required Administration Server.
  2. On the page that opens, proceed to the Administration Servers tab.
  3. Select the virtual Administration Server that you want to enable or disable.
  4. On the menu line, click the Enable / disable virtual Administration Server button.

The virtual Administration Server state is changed to enabled or disabled, depending on its previous state. The updated state is displayed next to the Administration Server name.

See also:

Virtual Administration Server

Deleting a virtual Administration Server

Page top

[Topic 237346]

Assigning an administrator for a virtual Administration Server

When you use virtual Administration Servers in your organization, you might want to assign a dedicated administrator for each virtual Administration Server. For example, this might be useful when you create virtual Administration Servers to manage separate offices or departments of your organization, or if you are an MSP provider and you manage your tenants through virtual Administration Servers.

When you create a virtual Administration Server, it inherits the user list and all of the user rights of the primary Administration Server. If a user has access rights to the primary Server, this user has access rights to the virtual Server as well. After creation, you configure the access rights to the Servers independently. If you want to assign an administrator for a virtual Administration Server only, make sure that the administrator is not included in the Access rights list in the properties of the primary Administration Server.

You assign an administrator for a virtual Administration Server by granting the administrator access rights to the virtual Administration Server. You can grant the required access rights in one of the following ways:

  • Configure access rights for the administrator manually
  • Assign one or more user roles for the administrator

When you assign an administrator, make sure that you grant access to a single virtual Administration Server. An administrator with access to multiple virtual Administration Servers cannot sign in to Kaspersky Security Center Cloud Console.

An administrator of a virtual Administration Server signs in to Kaspersky Security Center Cloud Console the same way as signing in to the primary Administration Server. Kaspersky Security Center Cloud Console authenticates the administrator and opens the virtual Administration Server to which the administrator has access rights. The administrator cannot switch between Administration Servers.

Prerequisites

Before you start, ensure that the following conditions are met:

  • The virtual Administration Server is created.
  • On the primary Administration Server, you have created an account for the administrator that you want to assign for the virtual Administration Server.
  • The created account of the virtual Server administrator is not included in the Access rights lists in the properties of any Servers—primary or secondary.
  • You have the Modify object ACLs right in the General featuresUser permissions functional area.

Configuring access rights manually

To assign an administrator for a virtual Administration Server:

  1. In the main menu, switch to the required virtual Administration Server:
    1. Click the chevron icon (The chevron icon.) to the right of the current Administration Server name.
    2. Select the required Administration Server.
  2. In the main menu, click the settings icon () next to the name of the Administration Server.

    The Administration Server properties window opens.

  3. On the Access rights tab, click the Add button.

    A unified list of users of the primary Administration Server and the current virtual Administration Server opens.

  4. From the list of users, select the account of the administrator that you want to assign for the virtual Administration Server, and then click the OK button.

    The application adds the selected user to the user list on the Access rights tab.

  5. Select the check box next to the added account, and then click the Access rights button.
  6. Configure the rights that the administrator will have on the virtual Administration Server.

    For successful authentication, at minimum, the administrator must have the following rights:

    • Read right in the General featuresBasic functionality functional area
    • Read right in the General featuresVirtual Administration Servers functional area

The application saves the modified user rights to the administrator account.

Configuring access rights by assigning user roles

Alternatively, you can grant the access rights to a virtual Administration Server administrator through user roles. For example, this might be useful if you want to assign several administrators on the same virtual Administration Server. If this is the case, you can assign the administrators' accounts the same one or more user roles instead of configuring the same user rights for several administrators.

To assign an administrator for a virtual Administration Server by assigning user roles:

  1. On the primary Administration Server, create a new user role, and then specify all of the required access rights that an administrator must have on the virtual Administration Server. You can create several roles, for example, if you want to separate access to different functional areas.
  2. In the main menu, switch to the required virtual Administration Server:
    1. Click the chevron icon (The chevron icon.) to the right of the current Administration Server name.
    2. Select the required Administration Server.
  3. Assign the new role or several roles to the administrator account.

    When assigning roles to a user, in the main menu, go to Users & rolesUsers & groups, and then select the Users tab. If you select the Groups tab, and then assign roles to the group where the user is a member, the user will not be able to log in to Kaspersky Security Center Cloud Console.

The application assigns the new role to the administrator account.

Configuring access rights at the object level

In addition to assigning access rights at the functional area level, you can configure access to specific objects on the virtual Administration Server, for example, to a specific administration group or a task. To do this, switch to the virtual Administration Server, and then configure the access rights in the object's properties.

See also:

Virtual Administration Server

Deleting a virtual Administration Server

Page top

[Topic 218393]

Deleting a virtual Administration Server

When you delete a virtual Administration Server, all of the objects created on the Administration Server, including policies and tasks, will be deleted as well. The managed devices from the administration groups that were managed by the virtual Administration Server will be removed from the administration groups. To return the devices under management of Kaspersky Security Center Cloud Console, run the network polling, and then move the found devices from the Unassigned devices group to the administration groups.

To delete a virtual Administration Server:

  1. In the main menu, click the settings icon () next to the name of the Administration Server.
  2. On the page that opens, proceed to the Administration Servers tab.
  3. Select the virtual Administration Server that you want to delete.
  4. On the menu line, click the Delete button.

The virtual Administration Server is deleted.

See also:

Virtual Administration Server

Enabling and disabling a virtual Administration Server

Page top

[Topic 165803]

Monitoring and reporting

This section describes the monitoring and reporting capabilities of Kaspersky Security Center Cloud Console. These capabilities give you an overview of your infrastructure, protection statuses, and statistics.

After Kaspersky Security Center Cloud Console deployment or during the operation, you can configure the monitoring and reporting features to best suit your needs.

In this section

Scenario: Monitoring and reporting

About types of monitoring and reporting

Dashboard and widgets

Reports

Events and event selections

Notifications and device statuses

Kaspersky announcements

Receiving license expiration warning

Cloud Discovery

Page top

[Topic 180118]

Scenario: Monitoring and reporting

This section provides a scenario for configuring the monitoring and reporting feature in Kaspersky Security Center Cloud Console.

Prerequisites

After you deploy Kaspersky Security Center Cloud Console on an organization's network you can start to monitor it and generate reports on its functioning.

Stages

Configuring monitoring and reporting on an organization's network proceeds in stages:

  1. Configuring the switching of device statuses

    Get acquainted with the settings for device statuses depending on specific conditions. By changing these settings, you can change the number of events with Critical or Warning importance levels. When configuring the switching of device statuses, be sure of the following:

    • New settings do not conflict with the information security policies of your organization.
    • You are able react to important security events on your organization's network in a timely manner.
  2. Configuring notifications about events on client devices

    How-to instructions: Configure notification (by email) of events on client devices

  3. Changing the response of your security network to the Virus outbreak event

    You can change the specific thresholds in the Administration Server properties. You can also create a stricter policy that will be activated or create a task that will be run at the occurrence of this event.

  4. Reviewing the security status of your organization's network

    How-to instructions:

  5. Locating client devices that are not protected

    How-to instructions:

  6. Checking protection of client devices

    How-to instructions:

  7. Reviewing license information

    How-to instructions:

Results

Upon completion of the scenario, you are informed about protection of your organization's network and, thus, can plan actions for further protection.

See also:

About types of monitoring and reporting

Dashboard and widgets

Reports

Events and event selections

Notifications and device statuses

Kaspersky announcements

Receiving license expiration warning

Cloud Discovery

Page top

[Topic 180005]

About types of monitoring and reporting

Information on security events on an organization's network is stored in the Administration Server database. Based on the events, Kaspersky Security Center Cloud Console provides the following types of monitoring and reporting on your organization's network:

  • Dashboard
  • Reports
  • Event selections

Dashboard

The dashboard allows you to monitor security trends on your organization's network by providing you with a graphical display of information.

Reports

The Reports feature allows you to get detailed numerical information about the security of your organization's network, save this information to a file, send it by email, and print it.

Event selections

Event selections provide an onscreen view of named sets of events that are selected from the Administration Server database. These sets of events are grouped according to the following categories:

  • By importance level—Critical events, Functional failures, Warnings, and Info events
  • By time—Recent events
  • By type—User requests and Audit events

You can create and view user-defined event selections based on the settings available, in the Kaspersky Security Center Cloud Console interface, for configuration.

See also:

Scenario: Monitoring and reporting

Page top

[Topic 233381]

Dashboard and widgets

This section contains information about the dashboard and the widgets that the dashboard provides. The section includes instructions on how to manage widgets and configure widget settings.

In this section

Using the dashboard

Adding widgets to the dashboard

Hiding a widget from the dashboard

Moving a widget on the dashboard

Changing the widget size or appearance

Changing widget settings

About the Dashboard-only mode

Configuring the Dashboard-only mode

Page top

[Topic 166064]

Using the dashboard

The dashboard allows you to monitor security trends on your organization's network by providing you with a graphical display of information.

The dashboard is available in the Kaspersky Security Center Cloud Console, in the Monitoring & reporting section, by clicking Dashboard.

The dashboard provides widgets that can be customized. You can choose a large number of different widgets, presented as pie charts or donut charts, tables, graphs, bar charts, and lists. The information displayed in widgets is automatically updated, the update period is one to two minutes. The interval between updates varies for different widgets. You can refresh data on a widget manually at any time by means of the settings menu.

By default, widgets include information about all events stored in the database of Administration Server.

Kaspersky Security Center Cloud Console has a default set of widgets for the following categories:

  • Protection status
  • Deployment
  • Updating
  • Threat statistics
  • Other

Some widgets have text information with links. You can view detailed information by clicking a link.

When configuring the dashboard, you can add widgets that you need, hide widgets that you do not need, change the size or appearance of widgets, move widgets, and change their settings.

See also:

Scenario: Monitoring and reporting

Page top

[Topic 176350]

Adding widgets to the dashboard

To add widgets to the dashboard:

  1. In the main menu, go to Monitoring & reporting Dashboard.
  2. Click the Add or restore web widget button.
  3. In the list of available widgets, select the widgets that you want to add to the dashboard.

    Widgets are grouped by category. To view the list of widgets included in a category, click the chevron icon () next to the category name.

  4. Click the Add button.

The selected widgets are added at the end of the dashboard.

You can now edit the representation and parameters of the added widgets.

See also:

Scenario: Monitoring and reporting

Page top

[Topic 176354]

Hiding a widget from the dashboard

To hide a displayed widget from the dashboard:

  1. In the main menu, go to Monitoring & reporting → Dashboard.
  2. Click the settings icon () next to the widget that you want to hide.
  3. Select Hide web widget.
  4. In the Warning window that opens, click OK.

The selected widget is hidden. Later, you can add this widget to the dashboard again.

See also:

Scenario: Monitoring and reporting

Page top

[Topic 176362]

Moving a widget on the dashboard

To move a widget on the dashboard:

  1. In the main menu, go to Monitoring & reporting → Dashboard.
  2. Click the settings icon () next to the widget that you want to move.
  3. Select Move.
  4. Click the place to which you want to move the widget. You can select only another widget.

The places of the selected widgets are swapped.

See also:

Scenario: Monitoring and reporting

Page top

[Topic 176369]

Changing the widget size or appearance

For widgets that display a graph, you can change its representation—a bar chart or a line chart. For some widgets, you can change their size: compact, medium, or maximum.

To change the widget representation:

  1. In the main menu, go to Monitoring & reporting → Dashboard.
  2. Click the settings icon () next to the widget that you want to edit.
  3. Do one of the following:
    • To display the widget as a bar chart, select Chart type: Bars.
    • To display the widget as a line chart, select Chart type: Lines.
    • To change the area occupied by the widget, select one of the values:
      • Compact
      • Compact (bar only)
      • Medium (donut chart)
      • Medium (bar chart)
      • Maximum

The representation of the selected widget is changed.

See also:

Scenario: Monitoring and reporting

Page top

[Topic 176370]

Changing widget settings

To change settings of a widget:

  1. In the main menu, go to Monitoring & reporting Dashboard.
  2. Click the settings icon () next to the widget that you want to change.
  3. Select Show settings.
  4. In the widget settings window that opens, change the widget settings as required.
  5. Click Save to save the changes.

The settings of the selected widget are changed.

The set of settings depends on the specific widget. Below are some of the common settings:

  • Web widget scope (the set of objects for which the widget displays information)—for example, an administration group or device selection.
  • Select task (the task for which the widget displays information).
  • Time interval (the time interval during which the information is displayed in the widget)—between the two specified dates; from the specified date to the current day; or from the current day minus the specified number of days to the current day.
  • Set to Critical if these are specified and Set to Warning if these are specified (the rules that determine the color of a traffic light).

After you change the widget settings, you can refresh data on the widget manually.

To refresh data on a widget:

  1. In the main menu, go to Monitoring & reporting → Dashboard.
  2. Click the settings icon () next to the widget that you want to move.
  3. Select Refresh.

The data on the widget is refreshed.

See also:

Scenario: Monitoring and reporting

Page top

[Topic 229787]

About the Dashboard-only mode

You can configure the Dashboard-only mode for employees who do not manage the network but who want to view the network protection statistics in Kaspersky Security Center Cloud Console (for example, a top manager). When a user has this mode enabled, only a dashboard with a predefined set of widgets is displayed to the user. Thus, he or she can monitor the statistics specified in the widgets, for example, the protection status of all managed devices, the number of recently detected threats, or the list of the most frequent threats in the network.

When a user works in the Dashboard-only mode, the following restrictions are applied:

  • The main menu is not displayed to the user, so he or she cannot change the network protection settings.
  • The user cannot perform any actions with widgets, for example, add or hide them. Therefore, you need to put all widgets required for the user on the dashboard and configure them, for instance, set the rule of counting objects or specify the time interval.

You cannot assign the Dashboard-only mode to yourself. If you want to work in this mode, contact a system administrator, Managed Service Provider (MSP), or a user with the Modify object ACLs right in the General features: User permissions functional area.

See also:

Configuring the Dashboard-only mode

Page top

[Topic 229700]

Configuring the Dashboard-only mode

Before you begin to configure the Dashboard-only mode, make sure that the following prerequisites are met:

  • You have the Modify object ACLs right in the General features: User permissions functional area. If you do not have this right, the tab for configuring the mode will be missing.
  • The user has the Read right in the General features: Basic functionality functional area.

If a hierarchy of Administration Servers is arranged in your network, for configuring the Dashboard-only mode go to the Server where the user account is available on the Users tab of the Users & rolesUsers & groups section. It can be a primary server or physical secondary server. It is not possible to adjust the mode on a virtual server.

To configure the Dashboard-only mode:

  1. In the main menu, go to Users & rolesUsers & groups, and then select the Users tab.
  2. Click the user account name for which you want to adjust the dashboard with widgets.
  3. In the account settings window that opens, select the Dashboard tab.

    On the tab that opens, the same dashboard is displayed for you as for the user.

  4. If the Display the console in Dashboard-only mode option is enabled, switch the toggle button to disable it.

    When this option is enabled, you are also unable to change the dashboard. After you disable the option, you can manage widgets.

  5. Configure the dashboard appearance. The set of widgets prepared on the Dashboard tab is available for the user with the customizable account. He or she cannot change any settings or size of the widgets, add, or remove any widgets from the dashboard. Therefore, adjust them for the user, so he or she can view the network protection statistics. For this purpose, on the Dashboard tab you can perform the same actions with widgets as in the Monitoring & reporting → Dashboard section:
  6. Switch the toggle button to enable the Display the console in Dashboard-only mode option.

    After that, only the dashboard is available for the user. He or she can monitor statistics but cannot change the network protection settings and dashboard appearance. As the same dashboard is displayed for you as for the user, you are also unable to change the dashboard.

    If you keep the option disabled, the main menu is displayed for the user, so he or she can perform various actions in Kaspersky Security Center Cloud Console, including changing security settings and widgets.

  7. Click the Save button when you finish configuring the Dashboard-only mode. Only after that will the prepared dashboard be displayed to the user.
  8. If the user wants to view statistics of supported Kaspersky applications and needs access rights to do so, configure the rights for the user. After that, Kaspersky applications data is displayed for the user in the widgets of these applications.

Now the user can log in to Kaspersky Security Center Cloud Console under the customized account and monitor the network protection statistics in the Dashboard-only mode.

Page top

[Topic 233382]

Reports

This section describes how to use reports, manage custom report templates, use report templates to generate new reports, and create report delivery tasks.

In this section

Using reports

Creating a report template

Viewing and editing report template properties

Exporting a report to a file

Generating and viewing a report

Creating a report delivery task

Deleting report templates

Page top

[Topic 166065]

Using reports

The Reports feature allows you to get detailed numerical information about the security of your organization's network, save this information to a file, send it by email, and print it.

Reports are available in the Kaspersky Security Center Cloud Console, in the Monitoring & reporting section, by clicking Reports.

By default, reports include information for the last 30 days.

Kaspersky Security Center Cloud Console has a default set of reports for the following categories:

  • Protection status
  • Deployment
  • Updating
  • Threat statistics
  • Other

You can create custom report templates, edit report templates, and delete them.

You can create reports that are based on existing templates, export reports to files, and create tasks for report delivery.

See also:

Scenario: Migration without a hierarchy of Administration Servers

Scenario: Monitoring and reporting

Page top

[Topic 176425]

Creating a report template

To create a report template:

  1. In the main menu, go to Monitoring & reporting Reports.
  2. Click Add.

    The New report template wizard starts. Proceed through the wizard by using the Next button.

  3. Enter the report name and select the report type.
  4. On the Scope step of the wizard, select the set of client devices (administration group, device selection, selected devices, or all networked devices) whose data will be displayed in reports that are based on this report template.
  5. On the Reporting period step of the wizard, specify the report period. Available values are as follows:
    • Between the two specified dates
    • From the specified date to the report creation date
    • From the report creation date, minus the specified number of days, to the report creation date

    This page may not appear for some reports.

  6. Click OK to close the wizard.
  7. Do one of the following:
    • Click the Save and run button to save the new report template and to run a report based on it.

      The report template is saved. The report is generated.

    • Click the Save button to save the new report template.

      The report template is saved.

You can use the new template for generating and viewing reports.

See also:

Scenario: Monitoring and reporting

Page top

[Topic 176428]

Viewing and editing report template properties

Expand all | Collapse all

You can view and edit basic properties of a report template, for example, the report template name or the fields displayed in the report.

To view and edit properties of a report template:

  1. In the main menu, go to Monitoring & reporting → Reports.
  2. Select the check box next to the report template whose properties you want to view and edit.

    As an alternative, you can first generate the report, and then click the Edit button.

  3. Click the Open report template properties button.

    The Editing report <Report name> window opens with the General tab selected.

  4. Edit the report template properties:
    • General tab:
      • Report template name
      • Maximum number of entries to display

        If this option is enabled, the number of entries displayed in the table with detailed report data does not exceed the specified value. Note that this option does not affect the maximum number of events that you can include in the report when you export the report to a file.

        Report entries are first sorted according to the rules specified in the FieldsDetails fields section of the report template properties, and then only the first of the resulting entries are kept. The heading of the table with detailed report data shows the displayed number of entries and the total available number of entries that match other report template settings.

        If this option is disabled, the table with detailed report data displays all available entries. We do not recommend that you disable this option. Limiting the number of displayed report entries reduces the load on the database management system (DBMS) and reduces the time required for generating and exporting the report. Some of the reports contain too many entries. If this is the case, you may find it difficult to read and analyze them all. Also, your device may run out of memory while generating such a report and, consequently, you will not be able to view the report.

        By default, this option is enabled. The default value is 1000.

        Note that the Kaspersky Security Center Cloud Console interface can display a maximum of 2500 entries. If you need to view a greater number of events, use the report export feature.

      • Group

        Click the Settings button to change the set of client devices for which the report is created. For some types of the reports, the button may be unavailable. The actual settings depend on the settings specified during creation of the report template.

      • Time interval

        Click the Settings button to modify the report period. For some types of the reports, the button may be unavailable. Available values are as follows:

        • Between the two specified dates
        • From the specified date to the report creation date
        • From the report creation date, minus the specified number of days, to the report creation date
      • Include data from secondary and virtual Administration Servers

        If this option is enabled, the report includes the information from the secondary and virtual Administration Servers that are subordinate to the Administration Server for which the report template is created.

        Disable this option if you want to view data only from the current Administration Server.

        By default, this option is enabled.

      • Up to nesting level

        The report includes data from secondary and virtual Administration Servers that are located under the current Administration Server on a nesting level that is less than or equal to the specified value.

        The default value is 1. You may want to change this value if you have to retrieve information from secondary Administration Servers located at lower levels in the tree.

      • Data wait interval (min)

        Before generating the report, the Administration Server for which the report template is created waits for data from secondary Administration Servers during the specified number of minutes. If no data is received from a secondary Administration Server at the end of this period, the report runs anyway. Instead of the actual data, the report shows data taken from the cache (if the Cache data from secondary Administration Servers option is enabled), or N/A (not available) otherwise.

        The default value is 5 (minutes).

      • Cache data from secondary Administration Servers

        Secondary Administration Servers regularly transfer data to the Administration Server for which the report template is created. There, the transferred data is stored in the cache.

        If the current Administration Server cannot receive data from a secondary Administration Server while generating the report, the report shows data taken from the cache. The date when the data was transferred to the cache is also displayed.

        Enabling this option allows you to view the information from secondary Administration Servers even if the up-to-date data cannot be retrieved. However, the displayed data can be obsolete.

        By default, this option is disabled.

      • Cache update frequency (h)

        Secondary Administration Servers at regular intervals transfer data to the Administration Server for which the report template is created. You can specify this period in hours. If you specify 0 hours, data is transferred only when the report is generated.

        The default value is 0.

      • Transfer detailed information from secondary Administration Servers

        In the generated report, the table with detailed report data includes data from secondary Administration Servers of the Administration Server for which the report template is created.

        Enabling this option slows the report generation and increases traffic between Administration Servers. However, you can view all data in one report.

        Instead of enabling this option, you may want to analyze detailed report data to detect a faulty secondary Administration Server, and then generate the same report only for that faulty Administration Server.

        By default, this option is disabled.

    • Fields tab

      Select the fields that will be displayed in the report, and use the Move up button and Move down button to change the order of these fields. Use the Add button or Edit button to specify whether the information in the report must be sorted and filtered by each of the fields.

      In the Filters of Details fields section, you can also click the Convert filters button to start using the extended filtering format. This format enables you to combine filtering conditions specified in various fields by using the logical OR operation. After you click the button, the Convert filters panel opens on the right. Click the Convert filters button to confirm conversion. You can now define a converted filter with conditions from the Details fields section that are applied by using the logical OR operation.

      Conversion of a report to the format supporting complex filtering conditions will make the report incompatible with the previous versions of Kaspersky Security Center (11 and earlier). Also, the converted report will not contain any data from secondary Administration Servers running such incompatible versions.

  5. Click Save to save the changes.
  6. Close the Editing report <Report name> window.

The updated report template appears in the list of report templates.

See also:

Scenario: Monitoring and reporting

Page top

[Topic 176429]

Exporting a report to a file

You can save one or multiple reports as XML, HTML, or as a PDF. Kaspersky Security Center Cloud Console allows you to export up to 10 reports to files of the specified format at the same time.

To export a report to a file:

  1. In the main menu, go to Monitoring & reporting → Reports.
  2. Choose the reports that you want to export.

    If you choose more than 10 reports, the Export report button will be disabled.

  3. Click the Export report button.
  4. In the opened window, specify the following export parameters:
    • File name.

      If you select one report to export, specify the report file name.

      If you select more than one report, the report file names will coincide with the name of the selected report templates.

    • Maximum number of entries.

      Specify the maximum number of entries included in the report file. The default value is 10,000.

    • File format.

      Select the report file format: XML, HTML, or PDF. If you export multiple reports, all selected reports are saved in the specified format as separate files.

  5. Click the Export report button.

The report is saved to a file in the specified format.

See also:

Scenario: Monitoring and reporting

Page top

[Topic 176423]

Generating and viewing a report

To create and view a report:

  1. In the main menu, go to Monitoring & reporting → Reports.
  2. Click the name of the report template that you want to use to create a report.

A report using the selected template is generated and displayed.

Report data is displayed only in English, other localizations are not available.

The report displays the following data:

  • On the Summary tab:
    • The name and type of report, a brief description and the reporting period, as well as information about the group of devices for which the report is generated.
    • Graph chart showing the most representative report data.
    • Consolidated table with calculated report indicators.
  • On the Details tab, a table with detailed report data is displayed.

See also:

Scenario: Updating third-party software

Scenario: Monitoring and reporting

Page top

[Topic 176430]

Creating a report delivery task

Expand all | Collapse all

You can create a task that will deliver selected reports.

To create a report delivery task:

  1. In the main menu, go to Monitoring & reporting → Reports.
  2. Select the check boxes next to the report templates for which you want to create a report delivery task.
  3. Click the Create delivery task button.

    The New task wizard starts. Proceed through the wizard by using the Next button.

  4. At the New task settings step of the wizard, enter the task name.

    The default name is Deliver reports. If a task with this name already exists, a sequence number (<N>) is added to the task name.

  5. At the Report configuration step of the wizard, specify the following settings:
    1. Report templates to be delivered by the task.
    2. The report format: HTML, XLS, or PDF.

      The wkhtmltopdf tool is required to convert a report to PDF. When you select the PDF option, Administration Server checks whether the wkhtmltopdf tool is installed on the device. If the tool is not installed, the application displays a message about the necessity to install the tool on the Administration Server device. Install the tool manually, and then proceed to the next step.

    3. Whether the reports are to be sent by email, together with email notification settings.

      You can specify up to 20 email addresses. To separate email addresses, press Enter. You can also paste a comma-separated list of email addresses, and then press Enter.

  6. At the Configure task schedule step of the wizard, select the task start schedule.

    The following task schedule options are available:

    • Manually

      The task does not run automatically. You can only start it manually.

      By default, this option is selected.

    • Every N minutes

      The task runs regularly, with the specified interval in minutes, starting from the specified time on the day that the task is created.

      By default, the task runs every 30 minutes, starting from the current system time.

    • Every N hours

      The task runs regularly, with the specified interval in hours, starting from the specified date and time.

      By default, the task runs every 6 hours, starting from the current system date and time.

    • Every N days

      The task runs regularly, with the specified interval in days. Additionally, you can specify a date and time of the first task run. These additional options become available, if they are supported by the application for which you create the task.

      By default, the task runs every day, starting from the current system date and time.

    • Every N weeks

      The task runs regularly, with the specified interval in weeks, on the specified day of week and at the specified time.

      By default, the task runs every Monday at the current system time.

    • Monthly

      The task runs regularly, on the specified day of the month, at the specified time.

      In months that lack the specified day, the task runs on the last day.

      By default, the task runs on the first day of each month, at the current system time.

    • On specified days

      The task runs regularly, on the specified days of each month, at the specified time.

      By default, no days of month are selected. The default start time is 18:00.

    • On virus outbreak

      The task runs after a Virus outbreak event occurs. Select application types that will monitor virus outbreaks. The following application types are available:

      • Anti-virus for workstations and file servers
      • Anti-virus for perimeter defense
      • Anti-virus for mail systems

      By default, all application types are selected.

      You may want to run different tasks depending on the security application type that reports a virus outbreak. In this case, remove the selection of the application types that you do not need.

    • On completing another task

      The current task starts after another task completes. This parameter only works if both tasks are assigned to the same devices. For example, you may want to run the Manage devices task with the Turn on the device option and, after it completes, run the Virus scan task as a triggering task.

      You have to select the triggering task from the table and the status with which this task must complete (Completed successfully or Failed).

      If necessary, you can search, sort, and filter the tasks in the table as follows:

      • Enter the task name in the search field, to search the task by its name.
      • Click the sort icon to sort the tasks by name.

        By default, the tasks are sorted in alphabetical ascending order.

      • Click the filter icon, and in the window that opens, filter the tasks by group, and then click the Apply button.
  7. At this step of the wizard, configure other task schedule settings:
    • In the Task schedule section, check or reconfigure the previously selected schedule and set the time interval, days of the month or week, set the virus outbreak condition or completing another task as a trigger to start the task. A start time can also be specified in this section if an applicable schedule is selected.
    • In the Additional settings section, specify the following settings:
      • Run missed tasks

        This option determines the behavior of a task if a client device is not visible on the network when the task is about to start.

        If this option is enabled, the system attempts to start the task the next time the Kaspersky application is run on the client device. If the task schedule is Manually, Once or Immediately, the task is started immediately after the device becomes visible on the network or immediately after the device is included in the task scope.

        If this option is disabled, only scheduled tasks run on client devices. For Manually, Once and Immediately schedule, tasks run only on those client devices that are visible on the network. For example, you may want to disable this option for a resource-consuming task that you want to run only outside of business hours.

        By default, this option is disabled.

      • Use automatically randomized delay for task starts

        If this option is enabled, the task is started on client devices randomly within a specified time interval, that is, distributed task start. A distributed task start helps to avoid a large number of simultaneous requests by client devices to the Administration Server when a scheduled task is running.

        The distributed start time is calculated automatically when a task is created, depending on the number of client devices to which the task is assigned. Later, the task is always started on the calculated start time. However, when task settings are edited or the task is started manually, the calculated value of the task start time changes.

        If this option is disabled, the task starts on client devices according to the schedule.

      • Use automatically randomized delay for task starts within an interval of

        If this option is enabled, the task is started on client devices randomly within the specified time interval. A distributed task start helps to avoid a large number of simultaneous requests by client devices to the Administration Server when a scheduled task is running.

        If this option is disabled, the task starts on client devices according to the schedule.

        By default, this option is disabled. The default time interval is one minute.

      • Stop the task if it runs longer than

        After the specified time period expires, the task is stopped automatically, whether it is completed or not.

        Enable this option if you want to interrupt (or stop) tasks that take too long to execute.

        By default, this option is disabled. The default task execution time is 120 minutes.

  8. At the Selecting an account to run the task step of the wizard, specify the credentials of the user account that is used to run the task.
  9. If you want to modify other task settings after the task is created, at the Finish task creation step of the wizard, enable the Open task details when creation is complete option (by default, this option is enabled).
  10. Click the Finish button to create the task and close the wizard.

    The report delivery task is created. If the Open task details when creation is complete option is enabled, the task settings window opens.

See also:

Scenario: Monitoring and reporting

Page top

[Topic 176417]

Deleting report templates

To delete one or several report templates:

  1. In the main menu, go to Monitoring & reporting → Reports.
  2. Select check boxes next to the report templates that you want to delete.
  3. Click the Delete button.
  4. In the window that opens, click OK to confirm your selection.

The selected report templates are deleted. If these report templates were included in the report delivery tasks, they are also removed from the tasks.

See also:

Scenario: Monitoring and reporting

Page top

[Topic 151331]

About events in Kaspersky Security Center Cloud Console

Kaspersky Security Center Cloud Console allows you to receive information about events that occur during the operation of Administration Server and Kaspersky applications installed on managed devices. Information about events is saved in the Administration Server database. You can export this information to external SIEM systems. Exporting event information to external SIEM systems enables administrators of SIEM systems to promptly respond to security system events that occur on managed devices or groups of devices.

Events by type

In Kaspersky Security Center Cloud Console, there are the following types of events:

  • General events. These events occur in all managed Kaspersky applications. An example of a general event is Virus outbreak. General events have strictly defined syntax and semantics. General events are used, for instance, in reports and dashboards.
  • Managed Kaspersky applications-specific events. Each managed Kaspersky application has its own set of events.

Events by source

You can view the full list of the events that can be generated by an application on the Event configuration tab in the application policy. For Administration Server, you can additionally view the event list in the Administration Server properties.

Events can be generated by the following applications:

  • Kaspersky Security Center Cloud Console components:
  • Managed Kaspersky applications

    For details about the events generated by Kaspersky managed applications, please refer to the documentation of the corresponding application.

Events by importance level

Each event has its own importance level. Depending on the conditions of its occurrence, an event can be assigned various importance levels. There are four importance levels of events:

  • A critical event is an event that indicates the occurrence of a critical problem that may lead to data loss, an operational malfunction, or a critical error.
  • A functional failure is an event that indicates the occurrence of a serious problem, error or malfunction that occurred during operation of the application or while performing a procedure.
  • A warning is an event that is not necessarily serious, but nevertheless indicates a potential problem in the future. Most events are designated as warnings if the application can be restored without loss of data or functional capabilities after such events occur.
  • An info event is an event that occurs for the purpose of informing about successful completion of an operation, proper functioning of the application, or completion of a procedure.

Each event has a defined storage term, during which you can view or modify it in Kaspersky Security Center Cloud Console. Some events are not saved in the Administration Server database by default because their defined storage term is zero. Only events that will be stored in the Administration Server database for at least one day can be exported to external systems.

See also:

Events of Kaspersky Security Center Cloud Console components

Configuring event export to SIEM systems

Page top

[Topic 151336]

Events of Kaspersky Security Center Cloud Console components

Each Kaspersky Security Center Cloud Console component has its own set of event types. This section lists types of events that occur in Kaspersky Security Center Cloud Console Administration Server and Network Agent. Types of events that occur in Kaspersky applications are not listed in this section.

For each event that can be generated by an application, you can specify notification settings and storage settings on the Event configuration tab in the application policy. For Administration Server, you can additionally view and configure the event list in the Administration Server properties. If you want to configure notification settings for all the events at once, configure general notification settings in the Administration Server properties.

In this section

Data structure of event type description

Administration Server events

Network Agent events

See also:

Scenario: Monitoring and reporting

Page top

[Topic 181756]

Data structure of event type description

For each event type, its display name, identifier (ID), alphabetic code, description, and the default storage term are provided.

  • Event type display name. This text is displayed in Kaspersky Security Center Cloud Console when you configure events and when they occur.
  • Event type ID. This numerical code is used when you process events by using third-party tools for event analysis.
  • Event type (alphabetic code). This code is used when you browse and process events by using public views that are provided in the Kaspersky Security Center Cloud Console database.
  • Description. This text contains the situations when an event occurs and what you can do in such a case.
  • Default storage term. This is the number of days during which the event is stored in the Administration Server database and is displayed in the list of events on Administration Server. After this period elapses, the event is deleted. If the event storage term value is 0, such events are detected but are not displayed in the list of events on Administration Server.

See also:

Events of Kaspersky Security Center Cloud Console components

Page top

[Topic 177080]

Administration Server critical events

The table below shows the events of Kaspersky Security Center Cloud Console Administration Server that have the Critical importance level.

For each event that can be generated by an application, you can specify notification settings and storage settings on the Event configuration tab in the application policy. For Administration Server, you can additionally view and configure the event list in the Administration Server properties. If you want to configure notification settings for all the events at once, configure general notification settings in the Administration Server properties.

Administration Server critical events

Event type display name

Event type ID

Event type

Description

Default storage term

License limit has been exceeded

4099

KLSRV_EV_LICENSE_CHECK_MORE_110

Once a day Kaspersky Security Center Cloud Console checks whether a license limit is exceeded.

Events of this type occur when Administration Server detects that some licensing limits are exceeded by Kaspersky applications installed on client devices and if the number of currently used licensing units covered by a single license exceeds 110% of the total number of units covered by the license.

Even when this event occurs, client devices are protected.

You can respond to the event in the following ways:

  • Look through the managed devices list. Delete devices that are not in use.
  • Provide a license for more devices (add a valid activation code or a key file to Administration Server).

Kaspersky Security Center Cloud Console determines the rules to generate events when a license limit is exceeded.

180 days

Virus outbreak

26 (for File Threat Protection)

GNRL_EV_VIRUS_OUTBREAK

Events of this type occur when the number of malicious objects detected on several managed devices exceeds the threshold within a short period.

You can respond to the event in the following ways:

  • Configure the threshold in the Administration Server properties.
  • Create a stricter policy that will be activated, or create a task that will be run, at the occurrence of this event.

180 days

Virus outbreak

27 (for Mail Threat Protection)

GNRL_EV_VIRUS_OUTBREAK

Events of this type occur when the number of malicious objects detected on several managed devices exceeds the threshold within a short period.

You can respond to the event in the following ways:

  • Configure the threshold in the Administration Server properties.
  • Create a stricter policy that will be activated, or create a task that will be run, at the occurrence of this event.

180 days

Virus outbreak

28 (for firewall)

GNRL_EV_VIRUS_OUTBREAK

Events of this type occur when the number of malicious objects detected on several managed devices exceeds the threshold within a short period.

You can respond to the event in the following ways:

  • Configure the threshold in the Administration Server properties.
  • Create a stricter policy that will be activated, or create a task that will be run, at the occurrence of this event.

180 days

Device has become unmanaged

4111

KLSRV_HOST_OUT_CONTROL

Events of this type occur if a managed device is visible on the network but has not connected to Administration Server for a specific period.

Find out what prevents the proper functioning of Network Agent on the device. Possible causes include network issues and removal of Network Agent from the device.

180 days

Device status is Critical

4113

KLSRV_HOST_STATUS_CRITICAL

Events of this type occur when a managed device is assigned the Critical status. You can configure the conditions under which the device status is changed to Critical.

180 days

Limited functionality mode

4130

KLSRV_EV_LICENSE_SRV_LIMITED_MODE

Events of this type occur when Kaspersky Security Center Cloud Console starts to operate with basic functionality, without Vulnerability and patch management and without Mobile Device Management features.

Following are causes of, and appropriate responses to, the event:

  • License term has expired. Provide a license to use the full functionality mode of Kaspersky Security Center Cloud Console (add a valid activation code or a key file to Administration Server).
  • Administration Server manages more devices than specified by the license limit. Move devices from the administration groups of an Administration Server to those of another Administration Server (if the license limit of the other Administration Server allows).

180 days

License expires soon

4129

KLSRV_EV_LICENSE_SRV_EXPIRE_SOON

Events of this type occur when the commercial license expiration date is approaching.

Once a day Kaspersky Security Center checks whether a license expiration date is approaching. Events of this type are published 30 days, 15 days, 5 days and 1 day before the license expiration date. This number of days cannot be changed. If the Administration Server is turned off on the specified day before the license expiration date, the event will not be published until the next day.

When the commercial license expires, Kaspersky Security Center Cloud Console provides only basic functionality.

You can respond to the event in the following ways:

  • Make sure that a reserve license key is added to Administration Server.
  • If you use a subscription, make sure to renew it. An unlimited subscription is renewed automatically if it has been prepaid to the service provider by the due date.

180 days

MDM certificate has expired

4132

KLSRV_CERTIFICATE_EXPIRED

Events of this type occur when the Administration Server certificate for Mobile Device Management expires.

You need to update the expired certificate.

180 days

Updates for Kaspersky application modules have been revoked

4142

KLSRV_SEAMLESS_UPDATE_REVOKED

Events of this type occur if seamless updates have been revoked (Revoked status is displayed for these updates) by Kaspersky technical specialists; for example, they must be updated to a newer version. The event concerns Kaspersky Security Center Cloud Console patches and does not concern modules of Kaspersky managed applications. The event provides the reason that the seamless updates are not installed.

180 days

Audit: Export to SIEM failed

5130

KLAUD_EV_SIEM_EXPORT_ERROR

Events of this type occur when exporting events to the SIEM system failed due to a connection error with the SIEM system.

180 days

See also:

Administration Server events

About events in Kaspersky Security Center Cloud Console

Administration Server functional failure events

Administration Server informational events

Administration Server warning events

Page top

[Topic 177081]

Administration Server functional failure events

The table below shows the events of Kaspersky Security Center Cloud Console Administration Server that have the Functional failure importance level.

For each event that can be generated by an application, you can specify notification settings and storage settings on the Event configuration tab in the application policy. For Administration Server, you can additionally view and configure the event list in the Administration Server properties. If you want to configure notification settings for all the events at once, configure general notification settings in the Administration Server properties.

Administration Server functional failure events

Event type display name

Event type ID

Event type

Description

Default storage term

Limit of installations has been exceeded for one of the licensed applications groups

4126

KLSRV_INVLICPROD_EXCEDED

Administration Server generates events of this type periodically (every hour). Events of this type occur if in Kaspersky Security Center Cloud Console you manage license keys of third-party applications and if the number of installations has exceeded the limit set by the license key of the third-party application.

You can respond to the event in the following ways:

  • Look through the managed devices list. Delete the third-party application from devices on which the application is not in use.
  • Use a third-party license for more devices.

You can manage license keys of third-party applications using the functionality of licensed applications groups. A licensed applications group includes third-party applications that meet criteria set by you.

180 days

Failed to poll the cloud segment

4143

KLSRV_KLCLOUD_SCAN_ERROR

Events of this type occur when Administration Server fails to poll a network segment in a cloud environment. Read the details in the event description and respond accordingly.

Not stored

See also:

Administration Server events

Administration Server critical events

Administration Server informational events

Administration Server warning events

About events in Kaspersky Security Center Cloud Console

Page top

[Topic 177082]

Administration Server warning events

The table below shows the events of Kaspersky Security Center Cloud Console Administration Server that have the Warning importance level.

For each event that can be generated by an application, you can specify notification settings and storage settings on the Event configuration tab in the application policy. For Administration Server, you can additionally view and configure the event list in the Administration Server properties. If you want to configure notification settings for all the events at once, configure general notification settings in the Administration Server properties.

Administration Server warning events

Event type display name

Event type ID

Event type

Description

Default storage term

License limit has been exceeded

4098

KLSRV_EV_LICENSE_CHECK_100_110

Once a day Kaspersky Security Center Cloud Console checks whether a license limit is exceeded.

Events of this type occur when Administration Server detects that some licensing limits are exceeded by Kaspersky applications installed on client devices and if the number of currently used licensing units covered by a single license constitute 100% to 110% of the total number of units covered by the license.

Even when this event occurs, client devices are protected.

You can respond to the event in the following ways:

  • Look through the managed devices list. Delete devices that are not in use.
  • Provide a license for more devices (add a valid activation code or a key file to Administration Server).

Kaspersky Security Center Cloud Console determines the rules to generate events when a license limit is exceeded.

90 days

Device has remained inactive on the network for a long time

4103

KLSRV_EVENT_HOSTS_NOT_VISIBLE

Events of this type occur when a managed device shows inactivity for some time.

Most often, this happens when a managed device is decommissioned.

You can respond to the event in the following ways:

90 days

Conflict of device names

4102

KLSRV_EVENT_HOSTS_CONFLICT

Events of this type occur when Administration Server considers two or more managed devices as a single device.

Although cloning is not supported in Kaspersky Security Center Cloud Console, this event may occur if you perform cloning using a third-party tool. To avoid the event, when copying the image of a device with Network Agent installed, you have to meet the following recommendations:

  • On the reference device, stop the Network Agent service and run the klmover utility with the -dupfix key. Avoid any subsequent runs of Network Agent service until the image capturing operation completes.
  • Make sure that the klmover utility will be run with the -dupfix key before (mandatory requirement) the first run of the Network Agent service on target devices, at the first launch of the operating system after the image deployment.

The klmover utility is included in the installation package of Network Agent.

If you capture the image of a device without Network Agent installed, perform image deployment on target devices and then deploy Network Agent. You have to provide access to the network folder with stand-alone installation packages from a device.

90 days

Device status is Warning

4114

KLSRV_HOST_STATUS_WARNING

Events of this type occur when a managed device is assigned the Warning status. You can configure the conditions under which the device status is changed to Warning.

90 days

Limit of installations will soon be reached for one of the licensed applications groups

4127

KLSRV_INVLICPROD_FILLED

Events of this type occur when the number of installations for third-party applications included in a licensed applications group reaches 90% of the maximum allowed value specified in the license key properties.

You can respond to the event in the following ways:

  • If the third-party application is not in use on some of the managed devices, delete the application from these devices.
  • If you expect that the number of installations for the third-party application will exceed the allowed maximum in the near future, consider obtaining a third-party license for a greater number of devices in advance.

You can manage license keys of third-party applications using the functionality of licensed applications groups.

90 days

Certificate has been requested

4133

KLSRV_CERTIFICATE_REQUESTED

Events of this type occur when a certificate for Mobile Device Management fails to be automatically reissued.

Following might be the causes and appropriate responses to the event:

  • Automatic reissue was initiated for a certificate for which the Certificate has been requested option is disabled. This might be due to an error that occurred during creation of the certificate. Manual reissue of the certificate might be required.
  • If you use an integration with a public key infrastructure, the cause might be a missing SAM-Account-Name attribute of the account used for integration with PKI and for issuance of the certificate. Review the account properties.

90 days

Certificate has been removed

4134

KLSRV_CERTIFICATE_REMOVED

Events of this type occur when an administrator removes any type of certificate (General, Mail, VPN) for Mobile Device Management.

After removing a certificate, mobile devices connected via this certificate will fail to connect to Administration Server.

This event might be helpful when investigating malfunctions associated with the management of mobile devices.

90 days

APNs certificate has expired

4135

KLSRV_APN_CERTIFICATE_EXPIRED

Events of this type occur when an APNs certificate expires.

You need to manually renew the APNs certificate and install it on an iOS MDM Server.

90 days

APNs certificate expires soon

4136

KLSRV_APN_CERTIFICATE_EXPIRES_SOON

Events of this type occur when there are fewer than 14 days left before the APNs certificate expires.

When the APNs certificate expires, you need to manually renew the APNs certificate and install it on an iOS MDM Server.

We recommend that you schedule the APNs certificate renewal in advance of the expiration date.

90 days

Failed to send the FCM message to the mobile device

4138

KLSRV_GCM_DEVICE_ERROR

Events of this type occur when Mobile Device Management is configured to use Google Firebase Cloud Messaging (FCM) for connecting to managed mobile devices with an Android operating system and FCM Server fails to handle some of the requests received from Administration Server. It means that some of the managed mobile devices will not receive a push notification.

Read the HTTP code in the details of the event description and respond accordingly. For more information on the HTTP codes received from FCM Server and related errors, please refer to the Google Firebase service documentation (see chapter "Downstream message error response codes").

90 days

HTTP error sending the FCM message to the FCM server

4139

KLSRV_GCM_HTTP_ERROR

Events of this type occur when Mobile Device Management is configured to use Google Firebase Cloud Messaging (FCM) for connecting managed mobile devices with the Android operating system and FCM Server reverts to the Administration Server a request with a HTTP code other than 200 (OK).

Following might be the causes and appropriate responses to the event:

  • Problems on the FCM server side. Read the HTTP code in the details of the event description and respond accordingly. For more information on the HTTP codes received from FCM Server and related errors, please refer to the Google Firebase service documentation (see chapter "Downstream message error response codes").
  • Problems on the proxy server side (if you use proxy server). Read the HTTP code in the details of the event and respond accordingly.

90 days

Failed to send the FCM message to the FCM server

4140

KLSRV_GCM_GENERAL_ERROR

Events of this type occur due to unexpected errors on the Administration Server side when working with the Google Firebase Cloud Messaging HTTP protocol.

Read the details in the event description and respond accordingly.

If you cannot find the solution to an issue on your own, we recommend that you contact Kaspersky Technical Support.

90 days

Connection to the secondary Administration Server has been interrupted

4116

KLSRV_EV_SLAVE_SRV_DISCONNECTED

Events of this type occur when a connection to the secondary Administration Server is interrupted.

Read the operating system log on the device where the secondary Administration Server is installed and respond accordingly.

90 days

Connection to the primary Administration Server has been interrupted

4118

KLSRV_EV_MASTER_SRV_DISCONNECTED

Events of this type occur when a connection to the primary Administration Server is interrupted.

Read the operating system log on the device where the primary Administration Server is installed and respond accordingly.

90 days

Audit: Test connection to SIEM server failed

5120

KLAUD_EV_SIEM_TEST_FAILED

Events of this type occur when an automatic connection test to the SIEM server failed.

90 days

See also:

Administration Server events

About events in Kaspersky Security Center Cloud Console

Administration Server critical events

Administration Server functional failure events

Administration Server informational events

Page top

[Topic 177083]

Administration Server informational events

The table below shows the events of Kaspersky Security Center Cloud Console Administration Server that have the Info importance level.

For each event that can be generated by an application, you can specify notification settings and storage settings on the Event configuration tab in the application policy. For Administration Server, you can additionally view and configure the event list in the Administration Server properties. If you want to configure notification settings for all the events at once, configure general notification settings in the Administration Server properties.

Administration Server informational events

Event type display name

Event type ID

Event type

Description

Default storage term

Over 90% of the license key is used up

4097

KLSRV_EV_LICENSE_CHECK_90

Events of this type occur when Administration Server detects that some licensing limits are close to being exceeded by Kaspersky applications installed on client devices and if the number of currently used licensing units covered by a single license constitute over 90% of the total number of units covered by the license.

Even when a licensing limit is exceeded, client devices are protected.

You can respond to the event in the following ways:

  • Look through the managed devices list. Delete devices that are not in use.
  • Provide a license for more devices (add a valid activation code or a key file to Administration Server).

Kaspersky Security Center Cloud Console determines the rules to generate events when a licensing limit is exceeded.

30 days

New device has been detected

4100

KLSRV_EVENT_HOSTS_NEW_DETECTED

Events of this type occur when new networked devices have been discovered.

30 days

Device has been automatically moved according to a rule

4101

KLSRV_EVENT_HOSTS_NEW_REDIRECTED

Events of this type occur when devices have been assigned to a group according to device moving rules.

30 days

Device has been removed from the group: inactive on the network for a long time

4104

KLSRV_INVISIBLE_HOSTS_REMOVED

Events of this type occur when devices have been automatically removed from a group for inactivity.

30 days

Limit of installations will soon be exceeded (more than 95% is used up) for one of the licensed applications groups

4128

KLSRV_INVLICPROD_EXPIRED_SOON

Events of this type occur when the number of installations for third-party applications included in a licensed applications group reaches 90% of the maximum allowed value specified in the license key properties.

You can respond to the event in the following ways:

  • If the third-party application is not in use on some of the managed devices, delete the application from these devices.
  • If you expect that the number of installations for the third-party application will exceed the allowed maximum in the near future, consider obtaining a third-party license for a greater number of devices in advance.

You can manage license keys of third-party applications using the functionality of licensed applications groups.

30 days

Files have been found to send to Kaspersky for analysis

4131

KLSRV_APS_FILE_APPEARED

 

30 days

FCM Instance ID has changed on this mobile device

4137

KLSRV_GCM_DEVICE_REGID_CHANGED

Events of this type occur when the Firebase Cloud Messaging token has changed on the device.

For information on the FCM token rotation, please refer to the Firebase service documentation.

30 days

Updates have been successfully copied to the specified folder

4122

KLSRV_UPD_REPL_OK

Events of this type occur when the Download updates to the Administration Server repository task finishes copying files to a specified folder.

30 days

Connection to the secondary Administration Server has been established

4115

KLSRV_EV_SLAVE_SRV_CONNECTED

Refer to the following topic for details: Creating a hierarchy of Administration Servers: adding a secondary Administration Server.

30 days

Connection to the primary Administration Server has been established

4117

KLSRV_EV_MASTER_SRV_CONNECTED

 

30 days

Databases have been updated

(In Kaspersky Security Center Cloud Console, this event type is available only for a secondary Administration Server.)

4144

KLSRV_UPD_BASES_UPDATED

Events of this type occur when the Download updates to the Administration Server repository task finishes updating databases.

30 days

KSN Proxy has started. KSN availability check has completed successfully

7718

KSNPROXY_STARTED_CON_CHK_OK

 

30 days

KSN Proxy has stopped

7720

KSNPROXY_STOPPED

 

30 days

Audit: Connection to the Administration Server has been established

4147

KLAUD_EV_SERVERCONNECT

 

30 days

Audit: Object has been modified

4148

KLAUD_EV_OBJECTMODIFY

This event tracks changes in the following objects:

  • Administration group
  • Security group
  • User
  • Package
  • Task
  • Policy
  • Server
  • Virtual Server

30 days

Audit: Object status has changed

4150

KLAUD_EV_TASK_STATE_CHANGED

For example, this event occurs when a task has failed with an error.

30 days

Audit: Group settings have been modified

4149

KLAUD_EV_ADMGROUP_CHANGED

Events of this type occur when a security group has been edited.

30 days

Audit: Encryption keys have been imported or exported from Administration Server

5100

KLAUD_EV_DPEKEYSEXPORT

 

30 days

Audit: Test connection to SIEM server succeeded

5110

KLAUD_EV_SIEM_TEST_SUCCESS

 

30 days

See also:

Administration Server events

Page top

[Topic 184667]

Network Agent events

This section contains information about the events related to Network Agent.

In this section

Network Agent functional failure events

Network Agent warning events

Network Agent informational events

See also:

Events of Kaspersky Security Center Cloud Console components

Page top

[Topic 165484]

Network Agent functional failure events

The table below shows the events of Kaspersky Security Center Network Agent that have the Functional failure severity level.

For each event that can be generated by an application, you can specify notification settings and storage settings on the Event configuration tab in the application policy. If you want to configure notification settings for all the events at once, configure general notification settings in the Administration Server properties.

Network Agent functional failure events

Event type display name

Event type ID

Event type

Description

Default storage term

Update installation error

7702

KLNAG_EV_PATCH_INSTALL_ERROR

Events of this type occur if automatic updating and patching for Kaspersky Security Center Cloud Console components was not successful. The event does not concern updates of the managed Kaspersky applications.

Read the event description. A Windows issue on the Administration Server might be a reason for this event. If the description mentions any issue of Windows configuration, resolve this issue.

30 days

Failed to install the third-party software update

7697

KLNAG_EV_3P_PATCH_INSTALL_ERROR

Events of this type occur if Vulnerability and patch management and Mobile Device Management features are in use, and if update of third-party software was not successful.

Check whether the link to the third-party software is valid. Read the event description.

30 days

Failed to install the Windows Update updates

7717

KLNAG_EV_WUA_INSTALL_ERROR

Events of this type occur if Windows Updates were not successful. Configure Windows Updates in a Network Agent policy.

Read the event description. Look for the error in the Microsoft Knowledge Base. Contact Microsoft Technical Support if you cannot resolve the issue yourself.

30 days

See also:

Network Agent warning events

Network Agent informational events

Page top

[Topic 173538]

Network Agent warning events

The table below shows the events of Kaspersky Security Center Network Agent that have the Warning severity level.

For each event that can be generated by an application, you can specify notification settings and storage settings on the Event configuration tab in the application policy. If you want to configure notification settings for all the events at once, configure general notification settings in the Administration Server properties.

Network Agent warning events

Event type display name

Event type ID

Event type

Default storage term

Warning has been returned during installation of the software module update

7701

KLNAG_EV_PATCH_INSTALL_WARNING

30 days

Third-party software update installation has completed with a warning

7696

KLNAG_EV_3P_PATCH_INSTALL_WARNING

30 days

Third-party software update installation has been postponed

7698

KLNAG_EV_3P_PATCH_INSTALL_SLIPPED

30 days

Security issue has occurred

549

GNRL_EV_APP_INCIDENT_OCCURED

30 days

KSN Proxy has started. Failed to check KSN for availability

7718

KSNPROXY_STARTED_CON_CHK_FAILED

30 days

See also:

Network Agent functional failure events

Network Agent informational events

Page top

[Topic 173727]

Network Agent informational events

The table below shows the events of Kaspersky Security Center Network Agent that have the Info severity level.

For each event that can be generated by an application, you can specify notification settings and storage settings on the Event configuration tab in the application policy. If you want to configure notification settings for all the events at once, configure general notification settings in the Administration Server properties.

Network Agent informational events

Event type display name

Event type ID

Event type

Default storage term

Update for software modules has been installed successfully

7699

KLNAG_EV_PATCH_INSTALLED_SUCCESSFULLY

30 days

Installation of update for software modules has started

7700

KLNAG_EV_PATCH_INSTALL_STARTING

30 days

Application has been installed

7703

KLNAG_EV_INV_APP_INSTALLED

30 days

Application has been uninstalled

7704

KLNAG_EV_INV_APP_UNINSTALLED

30 days

Monitored application has been installed

7705

KLNAG_EV_INV_OBS_APP_INSTALLED

30 days

Monitored application has been uninstalled

7706

KLNAG_EV_INV_OBS_APP_UNINSTALLED

30 days

Third-party application has been installed

7707

KLNAG_EV_INV_CMPTR_APP_INSTALLED

30 days

New device has been added

7708

KLNAG_EV_DEVICE_ARRIVAL

30 days

Device has been removed

7709

KLNAG_EV_DEVICE_REMOVE

30 days

Device has been detected

7710

KLNAG_EV_NAC_DEVICE_DISCOVERED

30 days

Device has been authorized

7711

KLNAG_EV_NAC_HOST_AUTHORIZED

30 days

Windows Desktop Sharing: File has been read

7712

KLUSRLOG_EV_FILE_READ

30 days

Windows Desktop Sharing: File has been modified

7713

KLUSRLOG_EV_FILE_MODIFIED

30 days

Windows Desktop Sharing: Application has been started

7714

KLUSRLOG_EV_PROCESS_LAUNCHED

30 days

Windows Desktop Sharing: Started

7715

KLUSRLOG_EV_WDS_BEGIN

30 days

Windows Desktop Sharing: Stopped

7716

KLUSRLOG_EV_WDS_END

30 days

Third-party software update has been installed successfully

7694

KLNAG_EV_3P_PATCH_INSTALLED_SUCCESSFULLY

30 days

Third-party software update installation has started

7695

KLNAG_EV_3P_PATCH_INSTALL_STARTING

30 days

KSN Proxy has started. KSN availability check has completed successfully

7719

KSNPROXY_STARTED_CON_CHK_OK

30 days

KSN Proxy has stopped

7720

KSNPROXY_STOPPED

30 days

See also:

Network Agent functional failure events

Network Agent warning events

Page top

[Topic 166234]

Using event selections

Event selections provide an onscreen view of named sets of events that are selected from the Administration Server database. These sets of events are grouped according to the following categories:

  • By importance level—Critical events, Functional failures, Warnings, and Info events
  • By time—Recent events
  • By type—User requests and Audit events

You can create and view user-defined event selections based on the settings available, in the Kaspersky Security Center Cloud Console interface, for configuration.

Event selections are available in the Kaspersky Security Center Cloud Console, in the Monitoring & reporting section, by clicking Event selections.

By default, event selections include information for the last seven days.

Kaspersky Security Center Cloud Console has a default set of event (predefined) selections:

  • Events with different importance levels:
    • Critical events
    • Functional failures
    • Warnings
    • Informational messages
  • User requests (events of managed applications)
  • Recent events (over the last week)
  • Audit events

    In Kaspersky Security Center Cloud Console, audit events related to service operations in your workspace are displayed. These events are conditioned by actions of Kaspersky specialists. These events, for example include the following: Administration Server ports changing; Administration Server database backup; creation, modification, and deletion of user accounts.

You can also create and configure additional user-defined selections. In user-defined selections, you can filter events by the properties of the devices they originated from (device names, IP ranges, and administration groups), by event types and severity levels, by application and component name, and by time interval. It is also possible to include task results in the search scope. You can also use a simple search field where a word or several words can be typed. All events that contain any of the typed words anywhere in their attributes (such as event name, description, component name) are displayed.

Both for predefined and user-defined selections, you can limit the number of displayed events or the number of records to search. Both options affect the time it takes Kaspersky Security Center Cloud Console to display the events. The larger the database is, the more time-consuming the process can be.

You can do the following:

See also:

Device selections

Scenario: Monitoring and reporting

Page top

[Topic 176385]

Creating an event selection

To create an event selection:

  1. In the main menu, go to Monitoring & reporting Event selections.
  2. Click Add.
  3. In the New event selection window that opens, specify the settings of the new event selection. Do this in one or more of the sections in the window.
  4. Click Save to save the changes.

    The confirmation window opens.

  5. To view the event selection result, keep the Go to selection result check box selected.
  6. Click Save to confirm the event selection creation.

If you kept the Go to selection result check box selected, the event selection result is displayed. Otherwise, the new event selection appears in the list of event selections.

See also:

Scenario: Monitoring and reporting

Page top

[Topic 177708]

Editing an event selection

To edit an event selection:

  1. In the main menu, go to Monitoring & reporting → Event selections.
  2. Select the check box next to the event selection that you want to edit.
  3. Click the Properties button.

    An event selection settings window opens.

  4. Edit the properties of the event selection.

    For predefined event selections, you can edit only the properties on the following tabs: General (except for the selection name), Time, and Access rights.

    For user-defined selections, you can edit all properties.

  5. Click Save to save the changes.

The edited event selection is shown in the list.

See also:

Scenario: Monitoring and reporting

Page top

[Topic 176415]

Viewing a list of an event selection

To view an event selection:

  1. In the main menu, go to Monitoring & reporting → Event selections.
  2. Select the check box next to the event selection that you want to start.
  3. Do one of the following:
    • If you want to configure sorting in the event selection result, do the following:
      1. Click the Reconfigure sorting and start button.
      2. In the displayed Reconfigure sorting for event selection window, specify the sorting settings.
      3. Click the name of the selection.
    • Otherwise, if you want to view the list of events as they are sorted on the Administration Server, click the name of the selection.

The event selection result is displayed.

See also:

Scenario: Monitoring and reporting

Page top

[Topic 236067]

Exporting an event selection

Kaspersky Security Center Cloud Console allows you to save an event selection and its settings to a KLO file. You can use this KLO file to import the saved event selection both to Kaspersky Security Center Windows and Kaspersky Security Center Linux.

Note that you can export only user-defined event selections. Event selections from the default set of Kaspersky Security Center Cloud Console (predefined selections) cannot be saved to a file.

To export an event selection:

  1. In the main menu, go to Monitoring & reporting → Event selections.
  2. Select the check box next to the event selection that you want to export.

    You cannot export multiple event selections at the same time. If you select more than one selection, the Export button will be disabled.

  3. Click the Export button.
  4. In the opened Save as window, specify the event selection file name and path, and then click the Save button.

    The Save as window is displayed only if you use Google Chrome, Microsoft Edge, or Opera. If you use another browser, the event selection file is automatically saved in the Downloads folder.

Page top

[Topic 236654]

Importing an event selection

Kaspersky Security Center Cloud Console allows you to import an event selection from a KLO file. The KLO file contains the exported event selection and its settings.

To import an event selection:

  1. In the main menu, go to Monitoring & reporting → Event selections.
  2. Click the Import button, and then choose an event selection file that you want to import.
  3. In the opened window, specify the path to the KLO file, and then click the Open button. Note that you can select only one event selection file.

    The event selection processing starts.

The notification with the import results appears. If the event selection is imported successfully, you can click the View import details link to view the event selection properties.

After a successful import, the event selection is displayed in the selection list. The settings of the event selection are also imported.

If the newly imported event selection has a name identical to that of an existing event selection, the name of the imported selection is expanded with the (<next sequence number>) index, for example: (1), (2).

Page top

[Topic 171287]

Viewing details of an event


To view details of an event:

  1. Start an event selection.
  2. Click the time of the required event.

    The Event properties window opens.

  3. In the displayed window, you can do the following:
    • View the information about the selected event
    • Go to the next event and the previous event in the event selection result
    • Go to the device on which the event occurred
    • Go to the administration group that includes the device on which the event occurred
    • For an event related to a task, go to the task properties

See also:

Scenario: Monitoring and reporting

Page top

[Topic 178646]

Exporting events to a file

To export events to a file:

  1. Start an event selection.
  2. Select the check box next to the required event.
  3. Click the Export to file button.

The selected event is exported to a file.

See also:

Scenario: Monitoring and reporting

Page top

[Topic 177727]

Viewing an object history from an event

From an event of creation or modification of an object that supports revision management, you can switch to the revision history of the object.

To view an object history from an event:

  1. Start an event selection.
  2. Select the check box next to the required event.
  3. Click the Revision history button.

The revision history of the object is opened.

See also:

Scenario: Monitoring and reporting

Page top

[Topic 159815]

Logging information about events for tasks and policies

This section offers recommendations on how to minimize the number of events for tasks and policies stored in the database of Kaspersky Security Center Cloud Console. By default, every 1000 devices have 100,000 events. If this limit is exceeded, new events overwrite old ones. As a result, critical events may disappear. Also, the Administration Server warning event named The limit on the number of events in the database is exceeded, the events have been deleted may occur. In these cases, we recommend that you follow the instructions in this section.

As a result, you will increase the speed of executing scenarios associated with the analysis of the events. Also, these recommendations help you lower the risk that critical events will be overwritten by a large number of events.

By default, the properties of each task and policy provide for storing all events related to task execution and policy enforcement. However, if a task is run frequently (for example, more than once per week), the number of events may turn out to be too large and the events may flood the database. In this case, we recommend selecting one of two options in the task settings:

  • Save events related to task progress. In this case, Kaspersky Security Center Cloud Console stores only information about task launch, progress, and completion (successful, with a warning, or with an error) from each device on which the task is run.
  • Save only task execution results. In this case, Kaspersky Security Center Cloud Console stores only information about task completion (successful, with a warning, or with an error) from each device on which the task is run.

If a policy has been defined for a fairly large number of devices (for example, more than 10,000), the number of events may also turn out to be large, and the events may flood the database. In this case, we recommend selecting only the most critical events in the policy settings and enabling their logging. You are advised to disable the logging of all other events.

You can also reduce the storage term for events associated with a task or a policy. The default period is 7 days for task-related events and 30 days for policy-related events. When changing the event storage term, consider the work procedures in place at your organization and the amount of time that the system administrator can devote to analyzing each event.

It is advisable to modify the event storage settings if events about changes in the intermediate statuses of group tasks and events about applying policies occupy a large share of all events in the Kaspersky Security Center Cloud Console database.

Page top

[Topic 178626]

Deleting events

To delete one or several events:

  1. Start an event selection.
  2. Select the check boxes next to the required events.
  3. Click the Delete button.

The selected events are deleted and cannot be restored.

See also:

Scenario: Monitoring and reporting

Page top

[Topic 176418]

Deleting event selections

You can delete only user-defined event selections. Predefined event selections cannot be deleted.

To delete one or several event selections:

  1. In the main menu, go to Monitoring & reporting → Event selections.
  2. Select the check boxes next to the event selections that you want to delete.
  3. Click Delete.
  4. In the window that opens, click OK.

The event selection is deleted.

See also:

Scenario: Monitoring and reporting

Page top

[Topic 233384]

Notifications and device statuses

This section contains information on how to view notifications, configure notification delivery, use device statuses, and enable changing device statuses.

In this section

About notifications

Configuring the switching of device statuses

Configuring notification delivery

Page top

[Topic 179103]

About notifications

Kaspersky Security Center Cloud Console provides the capability to monitor your organization's network by sending notifications about any event that you consider important. For any event you can configure notifications by email.

Upon receiving notifications by email, you can decide on your response to an event. This response has to be one that is the most appropriate for your organization's network.

See also:

Scenario: Monitoring and reporting

Page top

[Topic 181770_1]

Configuring the switching of device statuses

You can change conditions to assign the Critical or Warning status to a device.

To enable changing the device status to Critical:

  1. In the main menu, go to Assets (Devices)Hierarchy of groups.
  2. In the list of groups that opens, click the link with the name of a group for which you want to change switching the device statuses.
  3. In the properties window that opens, select the Device status tab.
  4. In the left pane, select Critical.
  5. In the right pane, in the Set to Critical if these are specified section, enable the condition to switch a device to the Critical status.

    You can change only settings that are not locked in the parent policy.

  6. Select the radio button next to the condition in the list.
  7. In the upper-left corner of the list, click the Edit button.
  8. Set the required value for the selected condition.

    Values cannot be set for every condition.

  9. Click OK.

When specified conditions are met, the managed device is assigned the Critical status.

To enable changing the device status to Warning:

  1. In the main menu, go to Assets (Devices)Hierarchy of groups.
  2. In the list of groups that opens, click the link with the name of a group for which you want to change switching the device statuses.
  3. In the properties window that opens, select the Device status tab.
  4. In the left pane, select Warning.
  5. In the right pane, in the Set to Warning if these are specified section, enable the condition to switch a device to the Warning status.

    You can change only settings that are not locked in the parent policy.

  6. Select the radio button next to the condition in the list.
  7. In the upper-left corner of the list, click the Edit button.
  8. Set the required value for the selected condition.

    Values cannot be set for every condition.

  9. Click OK.

When specified conditions are met, the managed device is assigned the Warning status.

See also:

Notifications and device statuses

About device statuses

Scenario: Monitoring and reporting

Scenario: Configuring network protection

Page top

[Topic 180968]

Configuring notification delivery

You can configure email notification about events occurring in Kaspersky Security Center Cloud Console.

To configure notification delivery of events occurring in Kaspersky Security Center Cloud Console:

  1. In the main menu, click the settings icon () next to the name of the required Administration Server.

    The Administration Server properties window opens with the General tab selected.

  2. Click the Notification section, and in the right pane define the email notification settings:

    Recipients (email addresses)

    The email addresses to which the Kaspersky Security Center Cloud Console will send notifications. You can specify multiple addresses in this field, by separating them with semicolons.

    You can specify no more than 24 email addresses.

  3. Click the Send test message button to check whether you configured notifications properly: the application sends a test notification to the email addresses that you specified.
  4. Click the OK button to close Administration Server properties window.

The saved notification delivery settings are applied to all events that occur in Kaspersky Security Center Cloud Console.

You can override notification delivery settings for certain events in the Event configuration section of the Administration Server settings, of a policy's settings, or of an application's settings.

See also:

Scenario: Monitoring and reporting

Page top

[Topic 233385]

Kaspersky announcements

This section describes how to use, configure, and disable Kaspersky announcements.

In this section

About Kaspersky announcements

Disabling Kaspersky announcements

Page top

[Topic 210552]

About Kaspersky announcements

The Kaspersky announcements section (Monitoring & reporting → Kaspersky announcements) keeps you informed by providing information related to Kaspersky Security Center Cloud Console and the managed applications installed on the managed devices. Kaspersky Security Center Cloud Console periodically updates the information in the section by removing outdated announcements and adding new information.

Kaspersky Security Center Cloud Console shows only those Kaspersky announcements that are related to the currently connected Administration Server and the Kaspersky applications installed on the managed devices of this Administration Server. The announcements are shown individually for any type of Administration Server—primary, secondary, or virtual.

If several administrators use Kaspersky Security Center Cloud Console and they set different interface languages, Kaspersky Security Center Cloud Console displays Kaspersky announcements in every language used by the administrators. When you change the interface language, Kaspersky announcements in the selected language are added to the section automatically after you sign out of the console and then sign in again.

The announcements include information of the following types:

  • Security-related announcements

    Security-related announcements are intended to keep the Kaspersky applications installed in your network up-to-date and fully functional. The announcements may include information about critical updates for Kaspersky applications, fixes for found vulnerabilities, and ways to fix other issues in Kaspersky applications. Security-related announcements are enabled by default. If you do not want to receive the announcements, you can disable this feature.

    You cannot disable the security-related announcements in the trial mode of Kaspersky Security Center Cloud Console.

    To show you the information that corresponds to your network protection configuration, Kaspersky Security Center Cloud Console sends data to Kaspersky cloud servers and receives only those announcements that relate to the Kaspersky applications installed in your network. The data set that can be sent to the servers is described in the Kaspersky Security Center Cloud Console Agreement that you accept when you create a company workspace.

  • Marketing announcements

    Marketing announcements include information about special offers for your Kaspersky applications, advertisements, and news from Kaspersky. Marketing announcements are disabled by default. You receive this type of announcements only if you enabled Kaspersky Security Network (KSN). You can disable marketing announcements by disabling KSN.

    To show you only relevant information that might be helpful in protecting your network devices and in your everyday tasks, Kaspersky Security Center Cloud Console sends data to Kaspersky cloud servers and receives the appropriate announcements. The data set that can be sent to the servers is described in the Processed Data section of the KSN Statement.

New information is divided into the following categories, according to importance:

  1. Critical info
  2. Important news
  3. Warning
  4. Info

When new information appears in the Kaspersky announcements section, Kaspersky Security Center Cloud Console displays a notification label that corresponds to the importance level of the announcements. You can click the label to view this announcement in the Kaspersky announcements section.

See also:

Disabling Kaspersky announcements

About KSN

Page top

[Topic 210639]

Disabling Kaspersky announcements

The Kaspersky announcements section (Monitoring & reporting → Kaspersky announcements) keeps you informed by providing information related to your version of Kaspersky Security Center Cloud Console and managed applications installed on the managed devices. If you do not want to receive Kaspersky announcements, you can disable this feature.

The Kaspersky announcements include two types of information: security-related announcements and marketing announcements. You can disable the announcements of each type separately.

You cannot disable the security-related announcements in the trial mode of Kaspersky Security Center Cloud Console.

To disable security-related announcements:

  1. In the main menu, click the settings icon () next to the name of the Administration Server.

    The Administration Server properties window opens.

  2. On the General tab, select the Kaspersky announcements section.
  3. Switch the toggle button to the Security-related announcements Disabled position.
  4. Click the Save button.

    Kaspersky announcements are disabled.

Marketing announcements are disabled by default. You receive marketing announcements only if you enabled Kaspersky Security Network (KSN). You can disable this type of announcement by disabling KSN.

To disable marketing announcements:

  1. In the main menu, click the settings icon () next to the name of the Administration Server.

    The Administration Server properties window opens.

  2. On the General tab, select the KSN settings section.
  3. Disable the I agree to use Kaspersky Security Network option.
  4. Click the Save button.

    Marketing announcements are disabled.

See also:

About Kaspersky announcements

Page top

[Topic 195503]

Receiving license expiration warning

To add a Kaspersky Endpoint Security for Business Select license key to the Administration Server:

  1. In the main menu, click the settings icon () next to the name of the Administration Server.

    The Administration Server properties window opens.

  2. On the General tab, select the License keys section.
  3. Click Select.
  4. In the window that opens, select your license and click OK.

    Alternatively, if no license is displayed, you can click Add new license key and use your activation code.

The license is added to the Administration Server repository. This makes the Administration Server generate a critical event License expires soon one day before the license term expires and a critical event Limited functionality mode after the license term expires. If you want, you can configure notification delivery.

If you add a Kaspersky Endpoint Security for Business Select license key to the Administration Server repository, then the license is considered used on one device.

See also:

Application licensing

Scenario: Monitoring and reporting

Page top

[Topic 126963]

Cloud Discovery

Kaspersky Security Center Cloud Console allows you to monitor the use of cloud services on managed devices running Windows and to block access to cloud services that you consider unwanted. Cloud Discovery tracks user attempts to gain access to these services through both browsers and desktop applications. It also tracks user attempts to gain access to cloud services over unencrypted connections (for example, using the HTTP protocol). This feature helps you to detect and halt the use of cloud services by shadow IT.

The Cloud Discovery feature is only available if you have purchased a Kaspersky Next license. For details, refer to Licenses and the minimum number of devices for each license.

You can enable the Cloud Discovery feature and select the security policies or profiles for which you want to enable the feature. You can also enable or disable the feature separately in each security policy or profile. You can block access to cloud services that you do not want users to access.

To be able to block access to unwanted cloud services, make sure that the following prerequisites are met:

  • You use Kaspersky Endpoint Security 11.2 for Windows or later. Earlier versions of the security application only allow you to monitor the use of cloud services.
  • You have purchased a Kaspersky Next license, which provides the ability to block access to unwanted cloud services. For details, refer to Kaspersky Next Help.

The Cloud Discovery widget and the Cloud Discovery reports display information about successful and blocked attempts to gain access to cloud services. The widget also displays the risk level of each cloud service. Kaspersky Security Center Cloud Console gets information about the use of cloud services from all of the managed devices that are protected only by the security policies or profiles that have the feature enabled.

In this section

Enabling Cloud Discovery by using the widget

Adding the Cloud Discovery widget to the dashboard

Viewing information about the use of cloud services

Risk level of a cloud service

Blocking access to unwanted cloud services

Page top

[Topic 138009]

Enabling Cloud Discovery by using the widget

The Cloud Discovery feature allows you to get information about the use of cloud services from all of the managed devices that are protected only by the security policies that have the feature enabled. You can enable or disable Cloud Discovery for the Kaspersky Endpoint Security for Windows policy only.

There are two ways to enable the Cloud Discovery feature:

  • By using the Cloud Discovery widget.
  • In the properties of the Kaspersky Endpoint Security for Windows policy.

    For details on how to enable the Cloud Discovery feature in the Kaspersky Endpoint Security for Windows policy properties, refer to the Cloud Discovery section of Kaspersky Endpoint Security for Windows Help.

Note that you can disable the Cloud Discovery feature in the Kaspersky Endpoint Security for Windows policy parameters only.

To enable Cloud Discovery, you must have the Write right in the General features: Basic functionality functional area.

To enable the Cloud Discovery feature by using the Cloud Discovery widget:

  1. Go to Kaspersky Security Center Cloud Console.
  2. In the main menu, go to Monitoring & reporting Dashboard.
  3. On the Cloud Discovery widget, click the Enable button.
  4. In the Enable Cloud Discovery window that opens, select the security policies for which you want to enable the feature, and then click the Enable button.

    The following policy settings will be enabled automatically: Inject script into web traffic to interact with web pages, Web Session monitor, and Encrypted connections scan.

The Cloud Discovery feature is enabled and the widget is added to the dashboard.

Page top

[Topic 274418]

Adding the Cloud Discovery widget to the dashboard

You can add the Cloud Discovery widget to the dashboard to monitor the use of cloud services on managed devices.

To add the Cloud Discovery widget to the dashboard, you must have the Write right in the General features: Basic functionality functional area.

To add the Cloud Discovery widget to the dashboard:

  1. Go to Kaspersky Security Center Cloud Console.
  2. In the main menu, go to Monitoring & reporting Dashboard.
  3. Click the Add or restore web widget button.
  4. In the list of available widgets, click the chevron icon () next to the Other category.
  5. Select the Cloud Discovery widget, and then click the Add button.

    If the Cloud Discovery feature is disabled, follow the instructions in the Enabling Cloud Discovery by using the widget section.

The selected widget is added at the end of the dashboard.

Page top

[Topic 123382]

Viewing information about the use of cloud services

You can view the Cloud Discovery widget that shows information about attempts to gain access to cloud services. The widget also displays the risk level of each cloud service. Kaspersky Security Center Cloud Console gets information about the use of cloud services from all of the managed devices that are protected only by the security policies that have the feature enabled.

Before viewing, make sure that:

To view the Cloud Discovery widget:

  1. Go to Kaspersky Security Center Cloud Console.
  2. In the main menu, go to Monitoring & reporting Dashboard.

    The Cloud Discovery widget is displayed on the dashboard.

  3. On the left side of the Cloud Discovery widget, select a category of cloud services.

    The table on the right side of the widget displays up to five services from the selected category, to which users most often try to gain access. Both successful and blocked attempts are counted.

  4. On the right side of the widget, select a specific service.

    The table below displays up to ten devices that most often attempt to gain access to the service. In this table, you can generate two types of reports: report on successful access attempts and report on blocked access attempts.

    In addition, in this table you can block access to the cloud service for a specific device.

The widget displays the requested information.

From the displayed widget, you can do the following:

  • Proceed to the Monitoring & reporting Reports section, to view the Cloud Discovery reports.
  • Block or allow access to the selected cloud service.

The Cloud Discovery feature is only available if you have purchased a Kaspersky Next license. For details, refer to Licenses and the minimum number of devices for each license.

Page top

[Topic 222985]

Risk level of a cloud service

For each cloud service, Cloud Discovery provides you with a risk level. The risk level helps you determine which services do not fit the security requirements of your organization. For example, you may want to take the risk level into account when deciding whether to block access to a certain service.

The risk level is an estimated index and does not say anything about the quality of a cloud service or about the service manufacturer. The risk level is simply a recommendation from Kaspersky experts.

Risk levels of cloud services are displayed in the Cloud Discovery widget and in the list of all monitored cloud services.

Page top

[Topic 139384]

Blocking access to unwanted cloud services

You can block access to cloud services that you do not want users to access. You can also allow access to cloud services that were previously blocked.

Among other considerations, you may want to take the risk level into account when deciding whether to block access to a certain service.

You can block or allow access to cloud services for a security policy or profile.

There are two ways to block access to unwanted cloud services:

  • By using the Cloud Discovery widget.

    In this case, you can block access to the services one by one.

  • In the properties of the Kaspersky Endpoint Security for Windows policy.

    In this case, you can block access to the services one by one or block an entire category at once.

    For details on how to enable the Cloud Discovery feature in the Kaspersky Endpoint Security for Windows policy properties, refer to the Cloud Discovery section of Kaspersky Endpoint Security for Windows Help.

To block or allow access to a cloud service by using the widget:

  1. Open the Cloud Discovery widget, and then select the required cloud service.
  2. In the Top 10 devices that use the service pane, find the security policy or profile for which you want to block or allow the service.
  3. On the required line, in the Access status in policy or profile column, do any of the following:
    • To block the service, select Blocked in the drop-down list.
    • To allow the service, select Allowed in the drop-down list.
  4. Click the Save button.

Access to the selected service is blocked or allowed for the security policy or profile.

Page top

[Topic 197041_1]

Remote diagnostics of client devices

You can use remote diagnostics for remote execution of the following operations on Windows-based and Linux-based client devices:

  • Enabling and disabling tracing, changing the tracing level, and downloading the trace file
  • Downloading system information and application settings
  • Downloading event logs
  • Generating a dump file for an application
  • Starting diagnostics and downloading diagnostics reports
  • Starting, stopping, and restarting applications

You can use event logs and diagnostics reports downloaded from a client device to troubleshoot problems on your own. Also, if you contact Kaspersky Technical Support, a Technical Support specialist might ask you to download trace files, dump files, event logs, and diagnostics reports from a client device for further analysis at Kaspersky.

In this section

Opening the remote diagnostics window

Enabling and disabling tracing for applications

Downloading trace files of an application

Deleting trace files

Downloading application settings

Downloading system information from a client device

Downloading event logs

Starting, stopping, restarting the application

Running the remote diagnostics of an application and downloading the results

Running an application on a client device

Generating a dump file for an application

Running remote diagnostics on a Linux-based client device

Page top

[Topic 197042_1]

Opening the remote diagnostics window

To perform remote diagnostics on Windows-based and Linux-based client devices, you first have to open the remote diagnostics window.

To open the remote diagnostics window:

  1. To select the device for which you want to open the remote diagnostics window, perform one of the following:
    • If the device belongs to an administration group, in the main menu, go to Assets (Devices) → Groups → <group name> → Managed devices.
    • If the device belongs to the Unassigned devices group, in the main menu, go to Discovery & deploymentUnassigned devices.
  2. Click the name of the required device.
  3. In the device properties window that opens, select the Advanced tab.
  4. On the Advanced tab, click Remote diagnostics.

    This opens the Remote diagnostics window of a client device. If connection between Administration Server and the client device is not established, the error message is displayed.

Alternatively, if you need to obtain all diagnostic information about a Linux-based client device at once, you can run the collect.sh script on this device.

Page top

[Topic 197056_1]

Enabling and disabling tracing for applications

Expand all | Collapse all

You can enable and disable tracing for applications, including Xperf tracing.

Enabling and disabling tracing

To enable or disable tracing on a remote device:

  1. Open the remote diagnostics window of a client device.
  2. In the remote diagnostics window, select the Kaspersky applications tab.

    In the Application management section, the list of Kaspersky applications installed on the device displays.

  3. In the application list, select the application for which you want to enable or disable tracing.

    The list of remote diagnostics options opens.

  4. If you want to enable tracing:
    1. In the Tracing section, click Enable tracing.
    2. In the Modify tracing level window that opens, we recommend that you keep the default values of the settings. When required, a Technical Support specialist will guide you through the configuration process. The following settings are available:
      • Tracing level

        The tracing level defines the amount of detail that the trace file contains.

      • Rotation-based tracing

        The application overwrites the tracing information to prevent excessive increase in the size of the trace file. Specify the maximum number of files to be used to store the tracing information, and the maximum size of each file. If the maximum number of trace files of the maximum size are written, the oldest trace file is deleted so that a new trace file can be written.

        This setting is available for Kaspersky Endpoint Security only.

    3. Click Save.

    The tracing is enabled for the selected application. In some cases, the security application and its task must be restarted in order to enable tracing.

    On Linux-based client devices, tracing for the Updater of Kaspersky Security Agent component is regulated by the Network Agent settings. Therefore, the Enable tracing and Modify tracing level options are disabled for this component on client devices running Linux.

  5. If you want to disable tracing for the selected application, click Disable tracing.

    The tracing is disabled for the selected application.

Enabling Xperf tracing

For Kaspersky Endpoint Security, a Technical Support specialist may ask you to enable Xperf tracing for information about the system performance.

To enable and configure Xperf tracing or disable it:

  1. Open the remote diagnostics window of a client device.
  2. In the remote diagnostics window, select the Kaspersky applications tab.

    In the Application management section, the list of Kaspersky applications installed on the device displays.

  3. In the list of applications, select Kaspersky Endpoint Security for Windows.

    The list of remote diagnostics options for Kaspersky Endpoint Security for Windows displays.

  4. In the Xperf tracing section, click Enable Xperf tracing.

    If Xperf tracing is already enabled, the Disable Xperf tracing button is displayed instead. Click this button if you want to disable Xperf tracing for Kaspersky Endpoint Security for Windows.

  5. In the Change Xperf tracing level window that opens, depending on the request from the Technical Support specialist, do the following:
    1. Select one of the following tracing levels:
      • Light level

        A trace file of this type contains the minimum amount of information about the system.

        By default, this option is selected.

      • Deep level

        A trace file of this type contains more detailed information than trace files of the Light type and may be requested by Technical Support specialists when a trace file of the Light type is not enough for the performance evaluation. A Deep trace file contains technical information about the system including information about hardware, operating system, list of started and finished processes and applications, events used for performance evaluation, and events from Windows System Assessment Tool.

    2. Select one of the following Xperf tracing types:
      • Basic type

        The tracing information is received during operation of the Kaspersky Endpoint Security application.

        By default, this option is selected.

      • On-restart type

        The tracing information is received when the operating system starts on the managed device. This tracing type is effective when the issue that affects the system performance occurs after the device is turned on and before Kaspersky Endpoint Security starts.

      You may also be asked to enable the Rotation file size, in MB option to prevent excessive increase in the size of the trace file. Then specify the maximum size of the trace file. When the file reaches the maximum size, the oldest tracing information is overwritten with new information.

    3. Define the rotation file size.
    4. Click Save.

    Xperf tracing is enabled and configured.

  6. If you want to disable Xperf tracing for Kaspersky Endpoint Security for Windows, click Disable Xperf tracing in the Xperf tracing section.

    Xperf tracing is disabled.

Page top

[Topic 197112_1]

Downloading trace files of an application

You can download trace files from a client device only if one of the following conditions is met: the Do not disconnect from the Administration Server option is enabled in the settings of the device, a push server is in use, or a connection gateway is in use. Otherwise, downloading is not possible.

The maximum total number of devices with the Do not disconnect from the Administration Server option selected is 300.

To download a trace file of an application:

  1. Open the remote diagnostics window of a client device.
  2. In the remote diagnostics window, select the Kaspersky applications tab.

    In the Application management section, the list of Kaspersky applications installed on the device displays.

  3. In the list of applications, select the application for which you want to download a trace file.
  4. In the Tracing section, click the Trace files button.

    This opens the Device tracing logs window, where a list of trace files is displayed.

  5. In the list of trace files, select the file that you want to download.
  6. Do one of the following:
    • Download the selected file by clicking the Download. You can select one or several files for downloading.
    • Download a portion of the selected file:
      1. Click Download a portion.

        You cannot download portions of several files at the same time. If you select more than one trace file, the Download a portion button will be disabled.

      2. In the window that opens, specify the name and the file portion to download, according to your needs.

        For Linux-based devices, editing the file portion name is not available.

      3. Click Download.

The selected file, or its portion, is downloaded to the location that you specify.

Page top

[Topic 198282_1]

Deleting trace files

You can delete trace files that are no longer needed.

To delete a trace file:

  1. Open the remote diagnostics window of a client device.
  2. In the remote diagnostics window that opens, select the Event logs tab.
  3. In the Trace files section, click Windows Update logs or Remote installation logs, depending on which trace files you want to delete.

    This opens the Device tracing logs window, where a list of trace files is displayed.

  4. In the list of trace files, select one or several files that you want to delete.
  5. Click the Remove button.

The selected trace files are deleted.

Page top

[Topic 197067_1]

Downloading application settings

You can download application settings from a client device only if one of the following conditions is met: the Do not disconnect from the Administration Server option is enabled in the settings of the device, a push server is in use, or a connection gateway is in use. Otherwise, downloading is not possible.

The maximum total number of devices with the Do not disconnect from the Administration Server option selected is 300.

To download application settings from a client device:

  1. Open the remote diagnostics window of a client device.
  2. In the remote diagnostics window, select the Kaspersky applications tab.
  3. In the Application settings section, click the Download button to download information about the settings of the applications installed on the client device.

The ZIP archive with information is downloaded to the specified location.

Page top

[Topic 249394_1]

Downloading system information from a client device

You can download system information to your device from a client device only if one of the following conditions is met: the Do not disconnect from the Administration Server option is enabled in the settings of the device, a push server is in use, or a connection gateway is in use. Otherwise, downloading is not possible.

The maximum total number of devices with the Do not disconnect from the Administration Server option selected is 300.

To download system information from a client device:

  1. Open the remote diagnostics window of a client device.
  2. In the remote diagnostics window, select the System information tab.
  3. Click the Download button to download the system information about the client device.

The file with information is downloaded to the specified location.

Page top

[Topic 197068_1]

Downloading event logs

You can download event logs to your device from a client device only if one of the following conditions is met: the Do not disconnect from the Administration Server option is enabled in the settings of the device, a push server is in use, or a connection gateway is in use. Otherwise, downloading is not possible.

The maximum total number of devices with the Do not disconnect from the Administration Server option selected is 300.

To download an event log from a remote device:

  1. Open the remote diagnostics window of a client device.
  2. In the remote diagnostics window, on the Event logs tab, click All device logs.
  3. In the All device logs window, select one or several relevant logs.
  4. Do one of the following:
    • Download the selected log by clicking Download entire file.
    • Download a portion of the selected log:
      1. Click Download a portion.

        You cannot download portions of several logs at the same time. If you select more than one event log, the Download a portion button will be disabled.

      2. In the window that opens, specify the name and the log portion to download, according to your needs.
      3. Click Download.

The selected event log, or a portion of it, is downloaded to the specified location.

Page top

[Topic 197117_1]

Starting, stopping, restarting the application

You can start, stop, and restart applications on a client device.

To start, stop, or restart an application:

  1. Open the remote diagnostics window of a client device.
  2. In the remote diagnostics window, select the Kaspersky applications tab.

    In the Application management section, the list of Kaspersky applications installed on the device displays.

  3. In the list of applications, select the application that you want to start, stop, or restart.
  4. Select an action by clicking one of the following buttons:
    • Stop application

      This button is available only if the application is currently running.

    • Restart application

      This button is available only if the application is currently running.

    • Start application

      This button is available only if the application is not currently running.

Depending on the action that you have selected, the required application is started, stopped, or restarted on the client device.

If you restart the Network Agent, a message is displayed stating that the current connection of the device to the Administration Server will be lost.

Page top

[Topic 197886_1]

Running the remote diagnostics of an application and downloading the results

To start diagnostics for an application on a remote device and download the results:

  1. Open the remote diagnostics window of a client device.
  2. In the remote diagnostics window, select the Kaspersky applications tab.

    In the Application management section, the list of Kaspersky applications installed on the device displays.

  3. In the list of applications, select the application for which you want to run remote diagnostics.

    The list of remote diagnostics options opens.

  4. In the Diagnostics report section, click the Run diagnostics button.

    This starts the remote diagnostics process and generates a diagnostics report. When the diagnostics process is complete, the Download diagnostics report button becomes available.

  5. Click the Download diagnostics report button to download the report.

The report is downloaded to the specified location.

Page top

[Topic 198283_1]

Running an application on a client device

You may have to run an application on the client device, if a Kaspersky support specialist requests it. You do not have to install the application on that device.

To run an application on the client device:

  1. Open the remote diagnostics window of a client device.
  2. In the remote diagnostics window, select the Running a remote application tab.
  3. In the Object type field, select the type of object that you want to upload:
    • Select File to upload the executable file.
    • Select Folder to upload the folder containing the application that you want to run on the client device.

      If you select this object type, the Name of the executable file to be run field appears. In this field, specify the name of the executable file in the folder. You can also specify the relative path to the file.

    • Select Archive to upload the ZIP archive containing the application that you want to run on the client device.

      If you select this object type, the Name of the executable file to be run field appears. In this field, specify the name of the file in the folder that you want to run on the client device. You can also specify the relative path to the file.

      The ZIP archive must include the utility folder. This folder contains the executable file to be run on a remote device.

  4. Upload the object by selecting it in the system window, or dragging it to the upload field.
  5. If necessary, in the Command line arguments field, specify the command line arguments to be passed when running the executable file.
  6. In the Running a remote application section, click the Upload button to select a ZIP archive containing the application that you want to run on the client device.
  7. Click the Upload and run button to run the selected application on a client device.
  8. After the application execution is completed successfully, download the execution results by clicking the Download application execution results button.

    The application execution results are stored until you run a new diagnostic or close the window.

Remote diagnostics of the client device by using the application is completed.

Page top

[Topic 249403_1]

Generating a dump file for an application

An application dump file allows you to view parameters of the application running on a client device at a point in time. This file also contains information about modules that were loaded for an application.

Generating dump files is available only for 32-bit processes running on Windows-based client devices. For client devices running Linux and for 64-bit processes this feature is not supported.

To create a dump file for an application:

  1. Open the remote diagnostics window of a client device.
  2. In the remote diagnostics window, select click the Running a remote application tab.
  3. In the Generating the process dump file section, specify the executable file of the application for which you want to generate a dump file.
  4. Click the Download button to save the dump file for the specified application.

    If the specified application is not running on the client device, the error message will be displayed.

Page top

[Topic 257310]

Running remote diagnostics on a Linux-based client device

Kaspersky Security Center Cloud Console allows you to download the basic diagnostic information from a client device. Alternatively, you can obtain the diagnostic information about a Linux-based device by using the collect.sh script by Kaspersky. This script is run on the Linux-based client device that needs to be diagnosed, and then it generates a file with the diagnostic information, the system information about this device, trace files of applications, device logs, and a dump file for emergency-terminated applications.

We recommend that you use the collect.sh script to obtain all diagnostic information about the Linux-based client device at once. If you download the diagnostic information remotely through Kaspersky Security Center Cloud Console, you will need to go through all sections of the remote diagnostics interface. Also the diagnostic information for a Linux-based device will probably not be obtained completely.

If you need to send the generated file with the diagnostic information to the Kaspersky Technical Support, delete all confidential information before sending the file.

To download the diagnostic information from a Linux-based client device by using the collect.sh script:

  1. Download the collect.sh script packed in the collect.tar.gz archive.
  2. Copy the downloaded archive to the Linux-based client device that needs to be diagnosed.
  3. Run the following command to unpack the collect.tar.gz archive:

    # tar -xzf collect.tar.gz

  4. Run the following command to specify the script execution rights:

    # chmod +x collect.sh

  5. Run the collect.sh script by using an account with administrator rights:

    # ./collect.sh

A file with the diagnostic information is generated and saved to the /tmp/$HOST_NAME-collect.tar.gz folder.

Page top

[Topic 151328]

Configuring event export to SIEM systems

This section provides a scenario for configuring the export of events from Administration Server to external SIEM systems. Exporting information about events to external SIEM systems enables administrators of SIEM systems to respond promptly to security system events that occur on a managed device or groups of devices.

Prerequisites

Before you start configuring the export of events in the Kaspersky Security Center Cloud Console:

You can perform the steps of this scenario in any order.

Stages

The process of the export of events to a SIEM system consists of the following stages:

Results

After configuring the export of events to a SIEM system, you can view the export results if you selected events that you want to export.

See also:

Before you begin

About events in Kaspersky Security Center Cloud Console

About event export

Configuring an event export in a SIEM system

Marking of events for export to SIEM systems in Syslog format

About exporting events using Syslog format

Configuring Kaspersky Security Center Cloud Console for export of events to a SIEM system

Viewing export results

Page top

[Topic 151329]

Before you begin

Expand all | Collapse all

When setting up the automatic export of events in the Kaspersky Security Center Cloud Console, you must specify some of the SIEM system settings. It is recommended that you check these settings in advance in order to prepare for setting up Kaspersky Security Center Cloud Console.

To successfully configure automatic sending of events to a SIEM system, you must know the following settings:

  • SIEM system server address

    The IP address of the server on which the currently used SIEM system is installed. Check this value in your SIEM system settings.

  • SIEM system server port

    Port number used to establish a connection between Kaspersky Security Center Cloud Console and your SIEM system server. You specify this value in the Kaspersky Security Center Cloud Console settings and in the receiver settings of your SIEM system.

  • Protocol

    Protocol used for transferring messages from Kaspersky Security Center Cloud Console to your SIEM system. You specify this value in the Kaspersky Security Center Cloud Console settings and in the receiver settings of your SIEM system.

See also:

Configuring event export to SIEM systems

Page top

[Topic 151330]

About event export

Kaspersky Security Center Cloud Console allows you to receive information about events that occur during the operation of Administration Server and Kaspersky applications installed on managed devices. Information about events is saved in the Administration Server database.

You can use event export within centralized systems that deal with security issues on an organizational and technical level, provide security monitoring services, and consolidate information from different solutions. These are SIEM systems, which provide real-time analysis of security alerts and events generated by network hardware and applications, or Security Operation Centers (SOCs).

These systems receive data from many sources, including networks, security, servers, databases, and applications. SIEM systems also provide functionality to consolidate monitored data in order to help you avoid missing critical events. In addition, the systems perform automated analysis of correlated events and alerts in order to notify the administrators of immediate security issues. Alerting can be implemented through a dashboard or can be sent through third-party channels such as email.

The process of exporting events from Kaspersky Security Center Cloud Console to external SIEM systems involves two parties: an event sender, Kaspersky Security Center Cloud Console, and an event receiver, a SIEM system. To successfully export events, you must configure this in your SIEM system and in the Kaspersky Security Center Cloud Console. It does not matter which side you configure first. You can either configure the transmission of events in the Kaspersky Security Center Cloud Console, and then configure the receipt of events by the SIEM system, or vice versa.

Syslog format of event export

You can send events in the Syslog format to any SIEM system. Using the Syslog format, you can relay any events that occur on the Administration Server and in Kaspersky applications that are installed on managed devices. When exporting events in the Syslog format, you can select exactly which types of events will be relayed to the SIEM system.

Receipt of events by the SIEM system

The SIEM system must receive and correctly parse the events received from Kaspersky Security Center Cloud Console. For these purposes, you must properly configure the SIEM system. The configuration depends on the specific SIEM system utilized. However, there are a number of general steps in the configuration of all SIEM systems, such as configuring the receiver and the parser.

Page top

[Topic 151335]

Configuring an event export in a SIEM system

The process of exporting events from Kaspersky Security Center Cloud Console to external SIEM systems involves two parties: an event sender, Kaspersky Security Center Cloud Console, and an event receiver, a SIEM system. You must configure the export of events in your SIEM system and in the Kaspersky Security Center Cloud Console.

The settings that you specify in the SIEM system depend on the particular system that you are using. Generally, for all SIEM systems you must set up a receiver and, optionally, a message parser to parse received events.

Setting up the receiver

To receive events sent by Kaspersky Security Center Cloud Console, you must set up the receiver in your SIEM system. In general, the following settings must be specified in the SIEM system:

Depending on the SIEM system used, you may have to specify some additional receiver settings.

Message parsers

Exported events are passed to SIEM systems as messages. These messages must be properly parsed so that information on the events can be used by the SIEM system. Message parsers are a part of the SIEM system—they are used to split the contents of the message into the relevant fields, such as event ID, severity, description, parameters, and so on. This enables the SIEM system to process events received from Kaspersky Security Center Cloud Console so that they can be stored in the SIEM system database.

See also:

Configuring event export to SIEM systems

Page top

[Topic 218223]

Marking of events for export to SIEM systems in Syslog format

After enabling automatic export of events, you must select which events will be exported to the external SIEM system.

You can configure export of events in the Syslog format to an external system based on one of the following conditions:

  • Marking general events. If you mark events to export in a policy, in the settings of an event, or in the Administration Server settings, the SIEM system will receive the marked events that occurred in all applications managed by the specific policy. If exported events were selected in the policy, you will not be able to redefine them for an individual application managed by this policy.
  • Marking events for a managed application. If you mark events to export for a managed application installed on a managed device, the SIEM system will receive only the events that occurred in this application.

In this section

Marking events of a Kaspersky application for export in the Syslog format

Marking general events for export in Syslog format

See also:

Configuring event export to SIEM systems

Page top

[Topic 218295]

Marking events of a Kaspersky application for export in the Syslog format

If you want to export events that occurred in a specific managed application installed on the managed devices, mark the events for export in the application policy. In this case, the marked events are exported from all of the devices included in the policy scope.

To mark events for export for a specific managed application:

  1. In the main menu, go to Assets (Devices)Policies & profiles.
  2. Click the policy of the application for which you want to mark events.

    The policy settings window opens.

  3. Go to the Event configuration section.
  4. Select the check boxes next to the events that you want to export to a SIEM system.
  5. Click the Mark for export to SIEM system by using Syslog button.

    You can also mark an event for export to a SIEM system in the Event registration section, which opens by clicking the link of the event.

  6. A check mark (The check mark icon.) appears in the Syslog column of the event or events that you marked for export to the SIEM system.
  7. Click the Save button.

The marked events from the managed application are ready to be exported to a SIEM system.

You can mark which events to export to a SIEM system for a specific managed device. If previously exported events were marked in an application policy, you will not be able to redefine the marked events for a managed device.

To mark events for export for a managed device:

  1. In the main menu, go to Assets (Devices)Managed devices.

    The list of managed devices is displayed.

  2. Click the link with the name of the required device in the list of managed devices.

    The properties window of the selected device is displayed.

  3. Go to the Applications section.
  4. Click the link with the name of the required application in the list of applications.
  5. Go to the Event configuration section.
  6. Select the check boxes next to the events that you want to export to SIEM.
  7. Click the Mark for export to SIEM system by using Syslog button.

    Also, you can mark an event for export to a SIEM system in the Event registration section, that opens by clicking the link of the event.

  8. A check mark (The check mark icon.) appears in the Syslog column of the event or events that you marked for export to the SIEM system.

From now on, Administration Server sends the marked events to the SIEM system if export to the SIEM system is configured.

See also:

Configuring event export to SIEM systems

About events in Kaspersky Security Center Cloud Console

Page top

[Topic 215566]

Marking general events for export in Syslog format

You can mark general events that Administration Server will export to SIEM systems by using the Syslog format.

To mark general events for export to a SIEM system:

  1. Do one of the following:
    • In the main menu, click the settings icon () next to the name of the required Administration Server.
    • In the main menu, go to Assets (Devices) → Policies & profiles, and then click a link of a policy.
  2. In the window that opens, go to the Event configuration tab.
  3. Click Mark for export to SIEM system by using Syslog.

    Also, you can mark an event for export to SIEM system in the Event registration section, that opens by clicking the link of the event.

  4. A check mark (The check mark icon.) appears in the Syslog column of the event or events that you marked for export to the SIEM system.

From now on, Administration Server sends the marked events to the SIEM system if export to the SIEM system is configured.

See also:

Configuring event export to SIEM systems

About events in Kaspersky Security Center Cloud Console

Page top

[Topic 151333]

About exporting events using Syslog format

You can use the Syslog format to export to SIEM systems the events that occur in Administration Server and other Kaspersky applications installed on managed devices.

Syslog is a standard for message logging protocol. It permits separation of the software that generates messages, the system that stores them, and the software that reports and analyzes them. Each message is labeled with a facility code, indicating the software type that generates the message, and is assigned a severity level.

The Syslog format is defined by Request for Comments (RFC) documents published by the Internet Engineering Task Force (internet standards). The RFC 5424 standard is used to export the events from Kaspersky Security Center Cloud Console to external systems.

In Kaspersky Security Center Cloud Console, you can configure export of the events to the external systems using the Syslog format.

The export process consists of two steps:

  1. Enabling automatic event export. At this step, Kaspersky Security Center Cloud Console is configured so that it sends events to the SIEM system. Kaspersky Security Center Cloud Console starts sending events immediately after you enable automatic export.
  2. Selecting the events to be exported to the external system. At this step, you select which event to export to the SIEM system.

See also:

Configuring event export to SIEM systems

Page top

[Topic 216090]

Configuring Kaspersky Security Center Cloud Console for export of events to a SIEM system

Expand all | Collapse all

To export events to a SIEM system, you have to configure the process of export in Kaspersky Security Center Cloud Console.

To configure export to SIEM systems in the Kaspersky Security Center Cloud Console:

  1. In the main menu, click the settings icon () next to the name of the required Administration Server.

    The Administration Server properties window opens.

  2. On the General tab, select the SIEM section.
  3. Click the Settings link.

    The Export settings section opens.

  4. Specify the settings in the Export settings section:
    • SIEM system server address

      The IP address of the server on which the currently used SIEM system is installed. Check this value in your SIEM system settings.

    • SIEM system port

      Port number used to establish a connection between Kaspersky Security Center Cloud Console and your SIEM system server. You specify this value in the Kaspersky Security Center Cloud Console settings and in the receiver settings of your SIEM system.

    • Protocol

      You can use only TLS over TCP protocol for transferring messages to the SIEM system. To do this, specify the TLS settings:

      • Server authentication

        In the Server authentication field, you can select the Trusted certificates or SHA fingerprints values:

        • Trusted certificates. You can receive a complete certificate chain (including the root certificate) from a trusted certification authority (CA) and upload the file to Kaspersky Security Center Cloud Console. Kaspersky Security Center Cloud Console checks whether the certificate chain of the SIEM system server is also signed by a trusted CA or not.

          To add a trusted certificate, click the Browse for CA certificates file button, and then upload the certificate.

        • SHA fingerprints. You can specify SHA1 thumbprints of the complete certificate chain of the SIEM system (including the root certificate) in Kaspersky Security Center Cloud Console. To add a SHA1 thumbprint, enter it in the Thumbprints field, and then click the Add button.

        By using the Add client authentication setting, you can generate a certificate to authenticate Kaspersky Security Center Cloud Console. Thus, you will use a self-signed certificate issued by Kaspersky Security Center Cloud Console. In this case, you can use both a trusted certificate and a SHA fingerprint to authenticate the SIEM system server.

      • Add Subject name/Subject alternative name

        Subject name is a domain name for which the certificate is received. Kaspersky Security Center Cloud Console cannot connect to the SIEM system server if the domain name of the SIEM system server does not match the subject name of the SIEM system server certificate. However, the SIEM system server can change its domain name if the name has changed in the certificate. In this case, you can specify subject names in the Add Subject name/Subject alternative name field. If any of the specified subject names matches the subject name of the SIEM system certificate, Kaspersky Security Center Cloud Console validates the SIEM system server certificate.

      • Add client authentication

        For client authentication, you can insert your certificate or generate it in Kaspersky Security Center Cloud Console.

        • Insert certificate. You can use a certificate that you received from any source, for example, from any trusted CA. You must specify the certificate and its private key by using one of the following certificate types:
          • X.509 certificate PEM. Upload a file with a certificate in the File with certificate field, and a file with a private key in the File with key field. Both files do not depend on each other and the order of loading the files is not significant. When both files are uploaded, specify the password for decoding the private key in the Password or certificate verification field. The password can have an empty value if the private key is not encoded.
          • X.509 certificate PKCS12. Upload a single file that contains a certificate and its private key in the File with certificate field. When the file is uploaded, specify the password for decoding the private key in the Password or certificate verification field. The password can have an empty value if the private key is not encoded.
        • Generate key. You can generate a self-signed certificate in Kaspersky Security Center Cloud Console. As a result, Kaspersky Security Center Cloud Console stores the generated self-signed certificate, and you can pass the public part of the certificate or SHA1-fingerprint to the SIEM system.
  5. If you want, you can export archived events from the Administration Server database and set the start date from which you want to start the export of archived events:
    1. Click the Set the export start date link.
    2. In the section that opens, specify the start date in the Date to start export from field.
    3. Click the OK button.
  6. Switch the option to the Automatically export events to SIEM system database Enabled position.
  7. To check that the SIEM system connection is successfully configured, click the Check connection button.

    The connection status will be displayed.

  8. Click the Save button.

Export to a SIEM system is configured. From now on, if you configured the receiving of events in a SIEM system, Administration Server exports the marked events to a SIEM system. If you set the start date of export, Administration Server also exports the marked events stored in the Administration Server database from the specified date.

See also:

Configuring event export to SIEM systems

Configuring an event export in a SIEM system

Page top

[Topic 151340]

Viewing export results

You can control for successful completion of the event export procedure. To do this, check whether messages with export events are received by your SIEM system.

If the events sent from Kaspersky Security Center Cloud Console are received and properly parsed by your SIEM system, configuration on both sides is done properly. Otherwise, check the settings you specified in Kaspersky Security Center Cloud Console against the configuration in your SIEM system.

The figure below shows the events exported to ArcSight. For example, the first event is a critical Administration Server event: "Device status is Critical".

The representation of export events in the SIEM system varies according to the SIEM system you use.

The events exported to ArcSight.

Example of events

See also:

Configuring event export to SIEM systems

Page top

[Topic 152833]

About Kaspersky Security Center Cloud Console

Kaspersky Security Center Cloud Console is an application hosted and maintained by Kaspersky. You do not have to install Kaspersky Security Center Cloud Console on your computer or server. Kaspersky Security Center Cloud Console enables the administrator to install Kaspersky security applications on devices on a corporate network, remotely run scan and update tasks, and manage the security policies of managed applications. The administrator can use a detailed dashboard that provides a snapshot of corporate device statuses, detailed reports, and granular settings in protection policies.

In this section

Key features of Kaspersky Security Center Cloud Console

About licensing of Kaspersky Security Center Cloud Console for MSPs

About detection and response capabilities for MSPs

Page top

[Topic 152882]

Key features of Kaspersky Security Center Cloud Console

Kaspersky Security Center Cloud Console enables you to do the following:

  • Install Kaspersky applications on devices on your network and manage the installed applications.
  • Create a hierarchy of administration groups to manage a selection of client devices as a whole.
  • Create virtual Administration Servers and arrange them in a hierarchy.
  • Protect your network devices, including workstations and servers:
    • Manage an antimalware protection system built on Kaspersky applications.
    • Use the detection and response (EDR and MDR) capabilities (a license for Kaspersky Endpoint Detection and Response and/or for Kaspersky Managed Detection and Response is required), including:
      • Analyzing and investigating incidents
      • Incident visualization through creating a threat development chain graph
      • Accepting or rejecting responses manually or setting up the auto-accept of all responses
  • Use Kaspersky Security Center Cloud Console as a multi-tenant application.
  • Remotely manage Kaspersky applications installed on client devices.
  • Perform centralized deployment of license keys for Kaspersky applications to client devices.
  • Create and manage security policies for devices on your network.
  • Create and manage user accounts.
  • Create and manage user roles (RBAC).
  • Create and manage tasks for applications installed on your network devices.
  • View reports on the security system status for every client organization individually.

Page top

[Topic 152974]

About licensing of Kaspersky Security Center Cloud Console for MSPs

When you start using Kaspersky Security Center Cloud Console, you can either request a trial workspace (in this case, you are granted a 30-day trial license that is embedded in your workspace) or enter an activation code for a commercial license.

You cannot convert a trial workspace into a commercial one. To continue using Kaspersky Security Center Cloud Console after the trial license expires, you must delete the trial workspace and create another one with a commercial license.

Later, you can add one or several commercial license keys to the Administrator Server repository.

Page top

[Topic 220113]

About detection and response capabilities for MSPs

Kaspersky Security Center Cloud Console can integrate features of other Kaspersky applications into the console interface. For example, you can add the detection and response features to the functionality of Kaspersky Security Center Cloud Console by integrating the following applications:

  • Kaspersky Endpoint Detection and Response Optimum

    Kaspersky Endpoint Detection and Response Optimum is a solution designed to protect an organization's IT infrastructure from complex cyberthreats. The solution's functionality combines automatic threat detection with the ability to respond to these threats to resist complex attacks, including new exploits, ransomware, fileless attacks, and methods that use legitimate system tools.

    After a Kaspersky Endpoint Protection Platform (EPP) application detects a security incident, a detailed card with important data about the security incident is generated in Kaspersky Security Center Cloud Console. The incident card is generated by one of the following applications:

    • Kaspersky Endpoint Agent which is installed together with a Kaspersky EPP application
    • Kaspersky Endpoint Security 11.7.0 for Windows or later which has built-in EDR Optimum functionality and does not require additional installation of Kaspersky Endpoint Agent

    An incident card enables you to analyze and investigate the incident. Also, you can visualize the incident by creating a threat development chain graph. The graph describes the deployment stages of the detected attack in time. The created graph includes information about the modules involved in the attack and the actions performed by these modules.

    You can also initiate a chain of response actions: create an execution prevention rule for an untrusted object; search for similar incidents in the device group, based on the selected indicators of compromise (IOC); isolate an untrusted object; isolate a compromised device from the network.

    For information about the application activation, see the Kaspersky Endpoint Detection and Response Optimum documentation.

    If integrated, this application adds the Alerts section to the interface of Kaspersky Security Center Cloud Console (Monitoring & reporting Alerts).

  • Kaspersky Managed Detection and Response

    Kaspersky Managed Detection and Response delivers round-the-clock protection from the growing volume of threats that circumvent automated security barriers to organizations who struggle to find the expertise and staff, or for those with limited in-house resources. The MDR SOC analysts of Kaspersky or a third-party company investigate the incidents and offer responses to solve the incidents. You can accept or reject the offered measures manually, or enable the option to auto-accept all of the responses.

    For information about the application activation, see the Kaspersky Managed Detection and Response documentation.

    If integrated, this application adds the Incidents section to the interface of Kaspersky Security Center Cloud Console (Monitoring & reporting Incidents).

You can show or hide the interface elements that refer to the Kaspersky Endpoint Detection and Response or Kaspersky Managed Detection and Response features at any time in the Interface options section of Kaspersky Security Center Cloud Console.

Page top

[Topic 153079]

Getting started with Kaspersky Security Center Cloud Console

After you complete the scenario in this section, Kaspersky Security Center Cloud Console is ready to use.

Getting started scenario

The scenario proceeds in stages:

  1. Create an account

    To start using Kaspersky Security Center Cloud Console, you need an account.

    To create an account:

    1. Open your browser and enter the following address: https://ksc.kaspersky.com.
    2. Click the Create an account button.
    3. Follow the onscreen instructions.
  2. Create a workspace

    After you create the account, you can register your company and create your workspace.

    When you start using Kaspersky Security Center Cloud Console, you can either request a trial workspace (in this case, you are granted a 30-day trial license that is embedded in your workspace) or enter an activation code for a commercial license.

    You cannot convert a trial workspace into a commercial one. To continue using Kaspersky Security Center Cloud Console after the trial license expires, you must delete the trial workspace and create another one with a commercial license.

    To register a company and create a workspace:

    1. Open your browser and enter the following address: https://ksc.kaspersky.com.
    2. Click the Sign in button.
    3. Follow the onscreen instructions.
  3. Perform initial setup of Kaspersky Security Center Cloud Console

    When you enter the created workspace for the first time, you are automatically prompted to run the quick start wizard. The quick start wizard guides you to create a minimum of necessary tasks and policies, adjust a minimum of settings, and start creating installation packages of Kaspersky applications. Follow the onscreen instructions.

When initial setup is complete, Kaspersky Security Center Cloud Console is ready to use.

Page top

[Topic 153086]

Recommendations on managing your customers' devices

This section contains recommendations for organizing the customer devices that you want to protect.

Recommendations depend on whether you are using Kaspersky Security Center for the first time or have already used the on-premises version:

  • If you have never used Kaspersky Security Center before, you have two options:
    • Create a virtual Administration Server for the devices of each customer (recommended option). In this case, the devices of each customer can be managed through a dedicated virtual Administration Server independently from other customers. At the same time, you can use the primary Administration Server to create common policies and tasks for all of the customers. The reports generated on the primary Administration Server can include data from all of the virtual Administration Servers.
    • Create an administration group for the devices of each customer. If you want to divide customer devices further, you can create a hierarchy of subordinate administration groups under each parent group. For example, you may need subordinate groups if you want to use different protection settings for devices of employees who work in different departments.
  • If you have already used Kaspersky Security Center running on-premises, you can migrate your existing administration groups and related objects from Kaspersky Security Center on-premises to Kaspersky Security Center Cloud Console.

    You cannot migrate virtual Administration Servers. After migrating the administration groups and other objects, you can create virtual Administration Servers in Kaspersky Security Center Cloud Console.

    Proceed to configuring migration.

The administrator of a virtual Administration Server can only proceed to this virtual Server from the primary Administration Server. All the objects created on the primary Administration Server are available for reading to the administrator of a virtual Administration Server (for example, widgets, reports, or the user roles).

Page top

[Topic 220042]

Typical deployment scheme for MSPs

This section provides a description of the deployment scheme typically used by MSPs to manage multiple tenants. The scheme is based on management through virtual Administration Servers individually created for each tenant.

Virtual Server is created for each tenant. A managed device acts as a distribution point receiving and distributing updates.

Typical deployment scheme for MSPs

The scheme comprises the following main components:

  • Kaspersky Security Center Cloud Console. Provides a user interface to the administration services of your workspace. You use Kaspersky Security Center Cloud Console to deploy, manage, and maintain the protection system of a client organization's network.
  • Kaspersky update servers. HTTP(S) servers at Kaspersky from which Kaspersky applications download database and application module updates.
  • Virtual Administration Servers. An MSP administrator typically creates a virtual Administration Server for each tenant to deploy, manage, and maintain the protection system of the corresponding client organization's network.
  • Tenants. Client organizations whose devices are to be protected.
  • Managed devices. Client company's devices protected by Kaspersky Security Center Cloud Console. Each device that has to be protected must have Network Agent and one of the Kaspersky security applications installed.
  • Managed device working as a distribution point. Computer that has Network Agent installed and is used for update distribution, network polling, remote installation of applications, getting information about computers in an administration group, and / or broadcasting domain. The administrator selects the appropriate devices and assigns them distribution points manually.

See also:

Scenario: Protection deployment (tenant management through virtual Administration Servers)

Page top

[Topic 219967]

Scenario: Protection deployment (tenant management through virtual Administration Servers)

If you have never used Kaspersky Security Center and you want to manage your tenants through virtual Administration Servers, proceed as described in this section. After you complete this scenario, your customers' devices will be protected.

If you manage several tenants, then perform the scenario for each of the tenants separately.

The scenario proceeds in stages:

  1. Creating a virtual Administration Server

    Create a virtual Administration Server for your customer. The new virtual Administration Server appears in the hierarchy of Administration Servers:

    The created virtual Administration Servers are nested in the Managed devices node.

    Virtual Administration Servers in the hierarchy of Administration Servers

  2. Selecting a device to act as a distribution point

    Among the devices of the customer, decide which device will act as a

    .

    You cannot have more than 100 distribution points within one workspace.

  3. Creating a stand-alone installation package for Network Agent

    Switch to the created virtual Administration Server, and then create a stand-alone installation package for Network Agent. You can switch Administration Servers in the main menu by clicking the chevron icon (The chevron icon.) to the right of the current Administration Server name, and then selecting the required Administration Server. During creation of the stand-alone installation package, specify the Managed devices administration group to move the device to.

  4. Installing Network Agent on the selected device to act as a distribution point

    You can use any method that is suitable for you:

    • Manual installation

      To deliver the stand-alone installation package to the device, you can, for example, copy it to a removable drive (such as a flash drive) or place it in a shared folder.

    • Deployment by using Active Directory
    • Deployment by using your remote monitoring and management (RMM) software solution
  5. Assigning a distribution point

    Assign the device with Network Agent installed to act as a distribution point.

  6. Network polling

    Configure and perform network polling through the distribution point.

    Kaspersky Security Center Cloud Console provides the following methods of network polling:

    • IP range polling
    • Windows network polling
    • Active Directory polling

    After network polling according to schedule is complete, your customers' devices are discovered and placed in the Unassigned devices group.

  7. Moving the discovered devices to the administration groups

    Set up the rules for automatically moving the discovered devices to the required administration groups; or move these devices to the required administration groups manually. If you plan to manage the customer's devices in a single administration group, you can move the devices to the Managed devices group.

  8. Creating installation packages for Network Agent and managed Kaspersky applications

    Create installation packages for Kaspersky applications.

  9. Removing third-party security applications

    If third-party security applications are installed on your customers' devices, remove them before installing Kaspersky applications.

  10. Installing Kaspersky applications on client devices

    Create remote installation tasks to install Network Agent and managed Kaspersky applications on your customers' devices.

    If necessary, you can create several remote installation tasks to install managed Kaspersky applications for different administration groups or different device selections.

    After the tasks are created, you can configure their settings. Make sure that the schedule for each task meets your requirements. First, the task to install Network Agent must be run. After Network Agent is installed on your customers' devices, the task to install managed Kaspersky applications must be run.

  11. Verifying initial deployment of Kaspersky applications

    Generate and view the Report on Kaspersky application versions. Make sure that the managed Kaspersky applications are installed on all of the devices of your customer.

  12. Creating policies for Kaspersky applications

    Create a policy for the required Kaspersky application. If you want to create a universal policy for all your customers, switch the current virtual Administration Server to the primary Administration Server, and then create a policy for the required Kaspersky application.

Page top

[Topic 153487]

Scenario: Protection deployment (tenant management through administration groups)

If you have never used Kaspersky Security Center and you want to manage your tenants through administration groups, proceed as described in this section. After you complete this scenario, your customers' devices will be protected.

The scenario proceeds in stages:

  1. Creating administration groups

    Create an administration group for each of your customers.

  2. Planning the distribution points structure

    Among the devices of each customer, decide which device will act as a distribution point.

    You cannot have more than 100 distribution points within one workspace.

  3. Creating a stand-alone installation package for Network Agent

    Create a stand-alone installation package for Network Agent.

  4. Installation of Network Agent on the selected devices to act as distribution points

    Install Network Agent on the selected devices that will act as distribution points.

    You can use any method that is suitable for you:

    • Manual installation

      To deliver the stand-alone installation package to the devices, you can, for example, copy it to a removable drive (such as a flash drive) or place it in a shared folder.

    • Deployment by using Active Directory
    • Deployment by using your remote monitoring and management (RMM) software solution
  5. Assigning distribution points

    Assign the devices with Network Agent installed to act as distribution points.

  6. Network polling

    Configure and perform network polling through the distribution point.

    Kaspersky Security Center Cloud Console provides the following methods of network polling:

    • IP range polling
    • Windows network polling
    • Active Directory polling

    After network polling according to schedule is complete, your customers' devices are discovered and placed in the Unassigned devices group.

  7. Moving the discovered devices to the administration groups

    Set up the rules for automatically moving the discovered devices to the required administration groups; or move these devices to the required administration groups manually.

  8. Creating installation packages for Network Agent and managed Kaspersky applications

    If you did not start the quick start wizard, or skipped the step of creating installation packages, create installation packages for Kaspersky applications.

  9. Removing third-party security applications

    If third-party security applications are installed on your customers' devices, remove them before installing Kaspersky applications.

  10. Installing Kaspersky applications on your customers' devices

    Create remote installation tasks to install Network Agent and managed Kaspersky applications on your customers' devices.

    If necessary, you can create several remote installation tasks to install managed Kaspersky applications for different administration groups or different device selections.

    After the tasks are created, you can configure their settings. Make sure that the schedule for each task meets your requirements. First, the task to install Network Agent must be run. After Network Agent is installed on your customers' devices, the task to install managed Kaspersky applications must be run.

  11. Verifying initial deployment of Kaspersky applications

    Generate and view the Report on Kaspersky application versions. Make sure that the managed Kaspersky applications are installed on all of the devices of your customers.

  12. Creating policies for Kaspersky applications

    Go to the Assets (Devices) → Groups menu; if you want to create a universal policy for all your customers, select Administration Server. If you want to create a specific policy for an individual customer, select the administration group corresponding to that customer. Create a policy for the required Kaspersky application.

Page top

[Topic 153348]

Joint usage of Kaspersky Security Center on-premises and Kaspersky Security Center Cloud Console

If you have already used Kaspersky Security Center running on-premises, you can convert your existing Administration Servers running on-premises into secondary Administration Servers of your new Kaspersky Security Center Cloud Console Administration Server, as described in this section.

If you configure joint usage of Kaspersky Security Center on-premises and Kaspersky Security Center Cloud Console, you will not be able to migrate from Kaspersky Security Center on-premises to Kaspersky Security Center Cloud Console unless you remove the hierarchy of Administration Servers.

To create a hierarchy of Administration Servers,

Add your existing Administration Servers running on-premises as secondary Administration Servers.

Page top

[Topic 153950]

Licensing of Kaspersky applications for MSPs

Kaspersky Security Center Cloud Console enables you to perform centralized distribution of license keys for Kaspersky applications on your customers' devices, monitor their use, and renew licenses.

If you manage several tenants, you can distribute license keys in the following ways:

  • One license key for all of the tenants.
  • An individual license key for each tenant.

To distribute license keys to your customers' devices:

  1. Add the required license keys to the Administration Server repository.
  2. Do one of the following:
    • Configure automatic distribution of a license key.

      In this case, Kaspersky Security Center Cloud Console selects one of the applicable license keys and automatically deploys it every time a new device is discovered.

    • Configure the Add a key task to distribute a license key to devices.

      When configuring the task, you select the license key that must be deployed to devices and select the administration group that contains the required devices.

      One task can distribute only one license key. This means that if you want to distribute several license keys, you must create a task for each of them.

The Kaspersky applications installed on your customers' devices are activated.

Adding an active license key to the primary Administration Server is mandatory. Otherwise, the associated workspace will be deleted in 90 days, regardless of the status of license keys on other Administration Servers within that workspace.

Page top

[Topic 153088]

Monitoring and reporting capabilities for MSPs

Kaspersky Security Center Cloud Console provides you with monitoring and reporting capabilities. These capabilities give you an overview of your organization infrastructure, protection statuses, and statistics.

When you have deployed Kaspersky Security Center Cloud Console, you can configure the monitoring and reporting features to best suit your needs.

Kaspersky Security Center Cloud Console provides the following types features of monitoring and reporting:

  • Dashboard
  • Reports
  • Event selections
  • Email notifications

Dashboard

The dashboard allows you to monitor security trends on your organization's network by providing you with a graphical display of information. (See the figure below.)

Widgets: Protection status, Incidents by status, priority, requiring actions and the button to add and restore widgets.

The Dashboard section

Reports

The Reports feature allows you to get detailed numerical information about the security of your organization's network, save this information to a file, send it by email, and print it. You can also schedule report delivery by email (see the figure below).

The Reports section contains a list of reports. You can manage the report list and configure each report.

The Reports section

Event selections

Event selections provide an onscreen view of named sets of events that are selected from the Administration Server database. Kaspersky Security Center Cloud Console contains a number of predefined event selections (for example, Recent events and Critical events). Also, you can create custom event selections.

Email notifications

You can configure email notification about events occurring in Kaspersky Security Center Cloud Console and on your customers' devices.

Page top

[Topic 198790]

Working with Kaspersky Security Center Cloud Console in a cloud environment

This section provides information about Kaspersky Security Center Cloud Console features related to the operation and maintenance of Kaspersky Security Center Cloud Console in cloud environments, such as Amazon Web Services, Microsoft Azure, or Google Cloud.

To work within a cloud environment, you need a special license. If you do not have such a license, the interface elements related to cloud devices are not operable.

Updates functionality (including providing anti-virus signature updates and codebase updates), as well as KSN functionality may not be available in the software in the U.S.

In this section

Licensing options in a cloud environment

Preparing for work in a cloud environment through Kaspersky Security Center Cloud Console

Cloud environment configuration wizard in Kaspersky Security Center Cloud Console

Network segment polling via Kaspersky Security Center Cloud Console

Synchronization with Cloud: Configuring the moving rule

Remote installation of applications to the Azure virtual machines

Page top

[Topic 176966]

Licensing options in a cloud environment

Work in a cloud environment is possible both in trial mode and in commercial mode of Kaspersky Security Center Cloud Console:

  • In trial mode, all cloud environment features are available within the entire validity period of your workspace. No license is required.
  • In commercial mode, the cloud environment features are available only if a Kaspersky Hybrid Cloud Security license key has been added as active in the Administration Server properties.

In both cases, Vulnerability and patch management is automatically activated.

You may encounter an error when trying to activate the feature Support of the cloud environment using the license for Kaspersky Hybrid Cloud Security.

Page top

[Topic 215255]

Preparing for work in a cloud environment through Kaspersky Security Center Cloud Console

This section tells you how to prepare for working with Kaspersky Security Center Cloud Console in the following cloud environments:

  • Amazon Web Services
  • Microsoft Azure
  • Google Cloud

In this section

Working in Amazon Web Services cloud environment

Working in Microsoft Azure cloud environment

Working in Google Cloud

Page top

[Topic 148750]

Working in Amazon Web Services cloud environment

This section tells you how to prepare for working with Kaspersky Security Center Cloud Console in Amazon Web Services.

The addresses of web pages cited in this document are correct as of the Kaspersky Security Center Cloud Console release date.

In this section

About work in Amazon Web Services cloud environment

Creating IAM user accounts for Amazon EC2 instances

Page top

[Topic 150767]

About work in Amazon Web Services cloud environment

To work with the AWS platform and, in particular, to create instances, you need an Amazon Web Services account. You can create a free account at https://aws.amazon.com. You can also use an existing Amazon account.

To learn more about an AMI and how AWS Marketplace works, please visit the AWS Marketplace Help page. For more information about working with the AWS platform, using instances, and related concepts, please refer to the Amazon Web Services documentation.

The addresses of web pages cited in this document are correct as of the Kaspersky Security Center Cloud Console release date.

Page top

[Topic 149566]

Creating IAM user accounts for Amazon EC2 instances

This section describes the actions that must be performed to ensure correct operation of Kaspersky Security Center Cloud Console. These actions include work with the AWS Identity and Access Management (IAM) user accounts. Also described are the actions that must be taken on client devices to install Network Agent on them and then install Kaspersky Security for Windows Server and Kaspersky Endpoint Security for Linux.

In this section

Ensuring that Kaspersky Security Center Cloud Console has the permissions to work with AWS

Creating an IAM user account for work with Kaspersky Security Center Cloud Console

Page top

[Topic 160141]

Ensuring that Kaspersky Security Center Cloud Console has the permissions to work with AWS

To operate in the Amazon Web Services cloud environment using Kaspersky Security Center Cloud Console, you must create an IAM user account, that will be used by Kaspersky Security Center Cloud Console to work with AWS services. Before starting to work with the Administration Server, create an IAM user account with an AWS IAM access key (hereinafter also referred to as IAM access key).

Creation of an IAM user account requires the AWS Management Console. To work with the AWS Management Console, you will need a user name and password from an account in AWS.

Page top

[Topic 149021]

Creating an IAM user account for work with Kaspersky Security Center Cloud Console

An IAM user account is required for working with Kaspersky Security Center Cloud Console. You can create one IAM user account with all the necessary permissions, or you can create two separate user accounts.

An IAM access key that you will need to provide to Kaspersky Security Center Cloud Console during initial configuration is automatically created for the IAM user. An IAM access key consists of an access key ID and a secret key. For more details about the IAM service, please refer to the following AWS reference pages:

To create an IAM user account with the necessary permissions:

  1. Open the AWS Management Console and sign in under your account.
  2. In the list of AWS services, select IAM.

    A window opens containing a list of user names and a menu that lets you work with the tool.

  3. Navigate through the areas of the console dealing with user accounts, and add a new user name or names.
  4. For the user(s) you add, specify the following AWS properties:
    • Access type: Programmatic Access.
    • Permissions boundary not set.
    • Permission: ReadOnlyAccess.

      After you add the permission, view it for accuracy. In case of a mistaken selection, go back to the previous screen and make the selection again.

  5. After you create the user account, a table appears containing the IAM access key of the new IAM user. The access key ID is displayed in the Access key ID column. The secret key is displayed as asterisks in the Secret access key column. To view the secret key, click Show.

The newly created account is displayed in the list of IAM user accounts that corresponds to your account in AWS.

The addresses of web pages cited in this document are correct as of the Kaspersky Security Center Cloud Console release date.

Page top

[Topic 173508]

Working in Microsoft Azure cloud environment

This section provides information about Kaspersky Security Center Cloud Console operation and maintenance in a cloud environment provided by Microsoft Azure, as well as details of protection deployment on virtual machines in this cloud environment.

In this section

About work in Microsoft Azure

Creating a subscription, Application ID, and password

Assigning a role to the Azure Application ID

Page top

[Topic 173515]

About work in Microsoft Azure

To work with the Microsoft Azure platform and, in particular, to purchase apps at the Azure Marketplace and create virtual machines, you will need an Azure subscription. Before starting to work with Microsoft Azure in Kaspersky Security Center Cloud Console, create an Azure Application ID with permissions required for installation of applications on virtual machines.

Page top

[Topic 173604]

Creating a subscription, Application ID, and password

To work with Kaspersky Security Center Cloud Console in the Microsoft Azure environment, you need an Azure subscription, Azure Application ID, and Azure Application password. You can use an existing subscription, if you already have one.

An Azure subscription grants its owner access to the Microsoft Azure Platform Management Portal and to Microsoft Azure services. The owner can use the Microsoft Azure Platform to manage services such as Azure SQL and Azure Storage.

To create a Microsoft Azure subscription,

Go to https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/create-subscription and follow the instructions there.

More information about creating a subscription is available on the Microsoft website. You will get a subscription ID, which you will later provide to Kaspersky Security Center Cloud Console together with Application ID and password.

To create and save Azure Application ID and password:

  1. Go to https://portal.azure.com and make sure that you are logged in.
  2. Following the instructions on the reference page, create your Application ID.
  3. Go to the Keys section of the application settings.
  4. In the Keys section, fill in the Description and Expires fields and leave the Value field empty.
  5. Click Save.

    When you click Save, the system automatically fills the Value field with a long sequence of characters. This sequence is your Azure Application password (for example, yXyPOy6Tre9PYgP/j4XVyJCvepPHk2M/UYJ+QlfFvdU=). The description is displayed as you entered it.

  6. Copy the password and save it, so that you can later provide the Application ID and password to Kaspersky Security Center Cloud Console.

    You can copy the password only when it has been created. Later, the password will no longer be displayed and you cannot restore it.

The addresses of web pages cited in this document are correct as of the Kaspersky Security Center Cloud Console release date.

Page top

[Topic 176476]

Assigning a role to the Azure Application ID

If you only want to detect virtual machines using device discovery, your Azure Application ID must have the Reader role. If you want not only to detect virtual machines, but also to deploy protection by means of the Azure API, your Azure Application ID must have the Virtual Machine Contributor role.

Follow the instructions on the Microsoft website to assign a role to your Azure Application ID.

Page top

[Topic 193319]

Working in Google Cloud

Expand all | Collapse all

This section provides information about work with Kaspersky Security Center Cloud Console in a cloud environment provided by Google.

You can use the Google API to work with Kaspersky Security Center Cloud Console in Google Cloud Platform. A Google account is required. Please refer to the Google documentation at https://cloud.google.com for more information.

You will need to create and provide Kaspersky Security Center Cloud Console with the following credentials:

  • Client email

    Client email is the email address that you used for registering your project at Google Cloud.

  • Project ID

    Project ID is the ID that you received when you registered your project at Google Cloud.

  • Private key

    Private key is the sequence of characters that you received as your private key when you registered your project at Google Cloud. You might want to copy and paste this sequence to avoid mistakes.

Page top

[Topic 198709]

Cloud environment configuration wizard in Kaspersky Security Center Cloud Console

To configure Kaspersky Security Center Cloud Console using this wizard, you must have the following:

The Cloud environment configuration wizard starts automatically at the first connection to Kaspersky Security Center Cloud Console if your workspace was created by using the Kaspersky Hybrid Cloud Security license. You can also start the Cloud environment configuration wizard manually at any time.

To start the Cloud environment configuration wizard manually,

In the main menu, go to Discovery & deployment → Deployment & assignmentConfigure cloud environment.

The wizard starts.

An average work session with this wizard lasts about 15 minutes.

In this section

Step 1. Checking the required plug-ins and installation packages

Step 2. Selecting the application activation method

Step 3. Selecting the cloud environment and authorization

Step 4. Segment polling and configuring synchronization with Cloud

Step 5. Selecting an application to create a policy and tasks for

Step 6. Configuring Kaspersky Security Network for Kaspersky Security Center Cloud Console

Step 7. Creating an initial configuration of protection

Page top

[Topic 241277]

Step 1. Checking the required plug-ins and installation packages

This step is not displayed if you have all of the required web plug-ins and installation packages listed below.

To configure a cloud environment, you must have the following components:

  • Installation packages:
    • Network Agent for Windows
    • Network Agent for Linux
    • Kaspersky Endpoint Security for Linux
  • Web plug-in for Kaspersky Endpoint Security for Linux
  • At least one of the following:
    • Installation package and web plug-in for Kaspersky Endpoint Security for Windows (recommended)
    • Installation package and web plug-in for Kaspersky Security for Windows Server

      We recommend that you use Kaspersky Endpoint Security for Windows instead of Kaspersky Security for Windows Server.

Kaspersky Security Center Cloud Console automatically detects the components that you already have and lists only ones that are missing. Download the listed components by clicking the Select applications to download button, and then selecting the required plug-ins and installation packages. After you download a component, you can use the Refresh button to update the list of missing components.

See also:

Creating installation packages for Kaspersky applications

Page top

[Topic 148963]

Step 2. Selecting the application activation method

This step is displayed only if you used a license other than Kaspersky Hybrid Cloud Security during the workspace creation and never added a Kaspersky Hybrid Cloud Security license key to the activation field of Administration Server. In this case, you must activate Administration Server by using a Kaspersky Hybrid Cloud Security license.

See also:

Licensing options in a cloud environment

Page top

[Topic 198733]

Step 3. Selecting the cloud environment and authorization

Expand all | Collapse all

Specify the following settings:

  • Cloud environment

    Select the cloud environment in which you are deploying Kaspersky Security Center Cloud Console: AWS, Azure, or Google Cloud.

    If you plan to work with more than one cloud environment, select one environment and then run the wizard again.

  • Connection name

    Enter a name for the connection. The name cannot contain more than 256 characters. Only Unicode characters are permitted.

    This name will also be used as the name for the administration group for the cloud devices.

    If you plan to work with more than one cloud environment, you might want to include the name of the environment in the connection name, for example, "Azure Segment", "AWS Segment", or "Google Segment".

Enter your credentials to receive authorization in the cloud environment that you specified.

AWS

If you selected AWS as the cloud segment type, use an AWS IAM access key for further polling of the cloud segment. Enter the following key data:

  • Access key ID

    The IAM access key ID is a sequence of alphanumeric characters. You received the key ID when you created the IAM user account.

    The field is available after you selected an AWS IAM access key for authorization.

  • Secret key

    The secret key that you received with the access key ID when you created the IAM user account.

    The characters of the secret key are displayed as asterisks. After you begin entering the secret key, the Show button is displayed. Click and hold this button for the necessary amount of time to view the characters you entered.

    The field is available after you selected an AWS IAM access key for authorization.

    To see the characters that you entered, click and hold the Show button.

Azure

If you selected Azure as the cloud segment type, specify the following settings for the connection that will be used for further polling of the cloud segment:

  • Azure Application ID

    You created this application ID on the Azure portal.

    You can provide only one Azure Application ID for polling and other purposes. If you want to poll another Azure segment, you must first delete the existing Azure connection.

  • Azure Subscription ID

    You created the subscription on the Azure portal.

  • Azure Application password

    You received the password of the Application ID when you created the Application ID.

    The characters of the password are displayed as asterisks. After you begin entering the password, the Show button becomes available. Click and hold this button to view the characters you entered.

    To see the characters that you entered, click and hold the Show button.

  • Azure storage account name

    You created the name of the Azure storage account for working with Kaspersky Security Center Cloud Console.

  • Azure storage access key

    You received a password (key) when you created Azure storage account for working with Kaspersky Security Center Cloud Console.

    The key is available in section "Overview of the Azure storage account", in subsection "Keys".

    To see the characters that you entered, click and hold the Show button.

Google Cloud

If you selected Google Cloud as the cloud segment type, specify the following settings for the connection that will be used for further polling the cloud segment:

  • Client email address

    Client email is the email address that you used for registering your project at Google Cloud.

  • Project ID

    Project ID is the ID that you received when you registered your project at Google Cloud.

  • Private key

    Private key is the sequence of characters that you received as your private key when you registered your project at Google Cloud. You might want to copy and paste this sequence to avoid mistakes.

    To see the characters that you entered, click and hold the Show button.

The connection that you specified is saved in the application settings.

The Cloud environment configuration wizard enables you to specify only one segment. Later, you can specify more connections to manage other cloud segments.

Click Next to proceed.

See also:

Adding connections for cloud segment polling via Kaspersky Security Center Cloud Console

Page top

[Topic 198743]

Step 4. Segment polling and configuring synchronization with Cloud

At this step, cloud segment polling starts and a special administration group for cloud devices is automatically created. The devices found during polling are placed into this group. The cloud segment polling schedule is configured every five minutes by default (you can change this setting later).

A Synchronize with Cloud automatic moving rule is also created. For each subsequent scan of the cloud network, virtual devices that are detected will be moved to the corresponding subgroup within the Managed devices\Cloud group.

Define the Synchronize administration groups with cloud structure setting.

If this option is enabled, the Cloud group is automatically created within the Managed devices group and a cloud device discovery is started. The instances and virtual machines detected during each cloud network scan are placed into the Cloud group. The structure of the administration subgroups within this group matches the structure of your cloud segment (in AWS, availability zones and placement groups are not represented in the structure; in Azure, subnets are not represented in the structure). Devices that have not been identified as instances in the cloud environment are in the Unassigned devices group. This group structure enables you to use group installation tasks to install anti-virus applications on instances, as well as set up different policies for different groups.

If this option is disabled, the Cloud group is also created and the cloud device discovery is also started; however, subgroups matching the cloud segment structure are not created within the group. All detected instances are in the Cloud administration group so they are displayed in a single list. If your work with Kaspersky Security Center Cloud Console requires synchronization, you can modify the properties of the Synchronize with Cloud rule and enforce it. Enforcing this rule alters the structure of subgroups in the Cloud group so that it matches the structure of your cloud segment.

By default, this option is disabled.

Click Next to proceed.

See also:

Synchronization with Cloud: Configuring the moving rule

Page top

[Topic 241303]

Step 5. Selecting an application to create a policy and tasks for

This step is only displayed if you have installation packages and plug-ins for both Kaspersky Endpoint Security for Windows and Kaspersky Security for Windows Server. If you have a plug-in and an installation package for only one of those applications, this step is skipped and Kaspersky Security Center Cloud Console creates a policy and tasks for the existing application.

Select an application for which you want to create a policy and tasks:

  • Kaspersky Endpoint Security for Windows
  • Kaspersky Security for Windows Server
Page top

[Topic 198783]

Step 6. Configuring Kaspersky Security Network for Kaspersky Security Center Cloud Console

Expand all | Collapse all

This step is skipped when running Kaspersky Security Center Cloud Console in trial mode or on a virtual Administration Server.

Specify the settings for relaying information about Kaspersky Security Center Cloud Console operations to the Kaspersky Security Network (KSN) knowledge base. Select one of the following options:

  • I agree to use Kaspersky Security Network

    Kaspersky Security Center Cloud Console and managed applications installed on client devices will automatically transfer their operation details to Kaspersky Security Network. Participation in Kaspersky Security Network ensures faster updates of databases containing information about viruses and other threats, which ensures a faster response to emergent security threats.

  • I do not agree to use Kaspersky Security Network

    Kaspersky Security Center Cloud Console and managed applications will provide no information to Kaspersky Security Network.

    If you select this option, the use of Kaspersky Security Network will be disabled.

Kaspersky recommends participation in Kaspersky Security Network.

KSN agreements for managed applications may also be displayed. If you agree to use Kaspersky Security Network, the managed application will send data to Kaspersky. If you do not agree to participate in Kaspersky Security Network, the managed application will not send data to Kaspersky. You can change this setting later in the application policy.

Click Next to proceed.

Page top

[Topic 198789]

Step 7. Creating an initial configuration of protection

You can check a list of policies and tasks that are created.

Wait for the creation of policies and tasks to complete, and then click Next to proceed. On the last page of the wizard, click the Finish button to exit.

Page top

[Topic 198852]

Network segment polling via Kaspersky Security Center Cloud Console

Information about the structure of the network (and devices in it) is received through regular polling of cloud segments by using the AWS API, Azure API, or Google API tools. Kaspersky Security Center Cloud Console uses this information to update the contents of the Unassigned devices and Managed devices folders. If you have configured devices to be moved to administration groups automatically, detected devices are included in administration groups.

To allow the polling of cloud segments, you must have the corresponding rights that are provided with an IAM user account (in AWS); with an Application ID and password (in Azure); or with a Google client email, Google project ID, and private key (in Google Cloud).

You can add and delete connections, as well as set the polling schedule, for each cloud segment.

In this section

Adding connections for cloud segment polling via Kaspersky Security Center Cloud Console

Deleting a connection for cloud segment polling

Configuring the polling schedule via Kaspersky Security Center Cloud Console

Viewing the results of cloud segment polling via Kaspersky Security Center Cloud Console

Viewing the properties of cloud devices via Kaspersky Security Center Cloud Console

Page top

[Topic 198846]

Adding connections for cloud segment polling via Kaspersky Security Center Cloud Console

Expand all | Collapse all

To add a connection for cloud segment polling to the list of available connections:

  1. In the main menu, go to Discovery & deployment → DiscoveryCloud.
  2. In the window that opens, click Properties.
  3. In the Settings window that opens, click Add.

    The Cloud segment settings window opens.

  4. Specify the name of the cloud environment for the connection that will be used for further polling of the cloud segment:
    • Cloud environment

      Select the cloud environment in which you are deploying Kaspersky Security Center Cloud Console: AWS, Azure, or Google Cloud.

      If you plan to work with more than one cloud environment, select one environment and then run the wizard again.

    • Connection name

      Enter a name for the connection. The name cannot contain more than 256 characters. Only Unicode characters are permitted.

      This name will also be used as the name for the administration group for the cloud devices.

      If you plan to work with more than one cloud environment, you might want to include the name of the environment in the connection name, for example, "Azure Segment", "AWS Segment", or "Google Segment".

  5. Enter your credentials to receive authorization in the cloud environment that you specified.
    • If you selected AWS, specify the following:
      • Access key ID

        The IAM access key ID is a sequence of alphanumeric characters. You received the key ID when you created the IAM user account.

        The field is available after you selected an AWS IAM access key for authorization.

      • Secret key

        The secret key that you received with the access key ID when you created the IAM user account.

        The characters of the secret key are displayed as asterisks. After you begin entering the secret key, the Show button is displayed. Click and hold this button for the necessary amount of time to view the characters you entered.

        The field is available after you selected an AWS IAM access key for authorization.

        To see the characters that you entered, click and hold the Show button.

    • If you selected Azure, specify the following settings:
      • Azure Application ID

        You created this application ID on the Azure portal.

        You can provide only one Azure Application ID for polling and other purposes. If you want to poll another Azure segment, you must first delete the existing Azure connection.

      • Azure Subscription ID

        You created the subscription on the Azure portal.

      • Azure Application password

        You received the password of the Application ID when you created the Application ID.

        The characters of the password are displayed as asterisks. After you begin entering the password, the Show button becomes available. Click and hold this button to view the characters you entered.

        To see the characters that you entered, click and hold the Show button.

      • Azure storage account name

        You created the name of the Azure storage account for working with Kaspersky Security Center Cloud Console.

      • Azure storage access key

        You received a password (key) when you created Azure storage account for working with Kaspersky Security Center Cloud Console.

        The key is available in section "Overview of the Azure storage account", in subsection "Keys".

        To see the characters that you entered, click and hold the Show button.

    If you selected Google Cloud, specify the following settings:

    • Client email address

      Client email is the email address that you used for registering your project at Google Cloud.

    • Project ID

      Project ID is the ID that you received when you registered your project at Google Cloud.

    • Private key

      Private key is the sequence of characters that you received as your private key when you registered your project at Google Cloud. You might want to copy and paste this sequence to avoid mistakes.

      To see the characters that you entered, click and hold the Show button.

  6. If you want, click Set polling schedule and change the default settings.

The connection is saved in the application settings.

After the new cloud segment is polled for the first time, the subgroup corresponding to that segment appears in the Managed devices\Cloud administration group.

If you specify incorrect credentials, no instances will be found during cloud segment polling and a new subgroup will not appear in the Managed devices\Cloud administration group.

Page top

[Topic 198901]

Deleting a connection for cloud segment polling

If you no longer have to poll a specific cloud segment, you can delete the connection corresponding to it from the list of available connections. You can also delete a connection if, for example, permissions to poll a cloud segment have been transferred to another user who has different credentials.

To delete a connection:

  1. In the main menu, go to Discovery & deployment → DiscoveryCloud.
  2. In the window that opens, click Properties.
  3. In the Settings window that opens, click the name of the segment that you want to delete.
  4. Click Delete.
  5. In the window that opens, click the OK button to confirm your selection.

The connection is deleted. The devices in the cloud segment corresponding to this connection are automatically deleted from the administration groups.

Page top

[Topic 198848]

Configuring the polling schedule via Kaspersky Security Center Cloud Console

Expand all | Collapse all

Cloud segment polling is performed according to schedule. You can set the polling frequency.

The polling frequency is automatically set at five minutes by the Cloud environment configuration wizard. You can change this value at any time and set a different schedule. However, it is not recommended to configure polling to run more frequently than every five minutes, because this could lead to errors in the API operation.

To configure a cloud segment polling schedule:

  1. In the main menu, go to Discovery & deployment → DiscoveryCloud.
  2. In the window that opens, click Properties.
  3. In the Settings window that opens, click the name of the segment for which you want to configure a polling schedule.

    The Cloud segment settings window opens.

  4. In the Cloud segment settings window, click the Set polling schedule button.

    The Schedule window opens.

  5. In the Schedule window, define the following settings:
    • Scheduled start

      Polling schedule options:

      • Every N days

        The polling runs regularly, with the specified interval in days, starting from the specified date and time.

        By default, the polling runs every day, starting from the current system date and time.

      • Every N minutes

        The polling runs regularly, with the specified interval in minutes, starting from the specified time.

        By default, the polling runs every five minutes, starting from the current system time.

      • By days of week

        The polling runs regularly, on the specified days of week, and at the specified time.

        By default, the polling runs every Friday at 6:00:00 PM.

      • Every month on specified days of selected weeks

        The polling runs regularly, on the specified days of each month, and at the specified time.

        By default, no days of month are selected; the default start time is 6:00:00 PM.

    • Start interval (days)

      Specify what N is equal to (for minutes or days).

    • Starting from

      Specify when to start the first poll.

    • Run missed tasks

      If your workspace is unavailable during the time for which the poll is scheduled, Kaspersky Security Center Cloud Console can either start the poll immediately after the workspace is available again, or wait for the next time for which the poll is scheduled.

      If this option is enabled, Kaspersky Security Center Cloud Console starts polling immediately after the workspace is available again.

      If this option is disabled, Kaspersky Security Center Cloud Console waits for the next time for which the polling is scheduled.

      By default, this option is enabled.

  6. Click Save to save the changes.

The polling schedule for the segment is configured and saved.

Page top

[Topic 199091]

Viewing the results of cloud segment polling via Kaspersky Security Center Cloud Console

You can view the results of cloud segment polling, that is, view the list of cloud devices managed by the Administration Server.

To view the results of cloud segment polling,

In the main menu, go to Discovery & deployment → DiscoveryCloud.

The cloud segments available for polling are displayed.

Page top

[Topic 200119]

Viewing the properties of cloud devices via Kaspersky Security Center Cloud Console

You can view the properties of each cloud device.

To view the properties of a cloud device:

  1. In the main menu, go to Assets (Devices) → Managed devices.
  2. Click the name of the device whose properties you want to view.

    A properties window opens with the General section selected.

  3. If you want to view the properties specific for cloud devices, select the System section in the properties window.

    The properties are displayed depending on the cloud platform of the device.

    For devices in AWS, the following properties are displayed:

    • Device discovered using API (value: AWS)
    • Cloud region
    • Cloud VPC
    • Cloud availability zone
    • Cloud subnet
    • Cloud placement group (this unit is only displayed if the instance belongs to a placement group; otherwise, it is not displayed)

    For devices in Azure, the following properties are displayed:

    • Device discovered using API (value: Microsoft Azure)
    • Cloud region
    • Cloud subnet

    For devices in Google Cloud, the following properties are displayed:

    • Device discovered using API (value: Google Cloud)
    • Cloud region
    • Cloud VPC
    • Cloud availability zone
    • Cloud subnet

Page top

[Topic 199139]

Synchronization with Cloud: Configuring the moving rule

Expand all | Collapse all

During the Cloud environment configuration wizard operation, the Synchronize with Cloud rule is created automatically. This rule enables you to automatically move devices detected in each poll from the Unassigned devices group to the Managed devices\Cloud group, to make these devices available for centralized management. By default, the rule is active after it is created. You can disable, modify, or enforce the rule at any time.

To edit the properties of the Synchronize with Cloud rule and/or enforce the rule:

  1. In the main menu, go to Discovery & deployment → Deployment & assignmentMoving rules.

    A list of moving rules opens.

  2. In the list of moving rules, select Synchronize with cloud.

    The rule properties window opens.

  3. If necessary, specify the following settings in the Rule conditions tab, in the Cloud segments tab:
    • Device is in a cloud segment

      The rule only applies to devices that are in the selected cloud segment. Otherwise, the rule applies to all devices that have been discovered.

      By default, this option is selected.

    • Include child objects

      The rule applies to all devices in the selected segment and in all nested cloud subsections. Otherwise, the rule only applies to devices that are in the root segment.

      By default, this option is selected.

    • Move devices from nested objects to corresponding subgroups

      If this option is enabled, devices from nested objects are automatically moved to the subgroups that correspond to their structure.

      If this option is disabled, devices from nested objects are automatically moved to the root of the Cloud subgroup without any further branching.

      By default, this option is enabled.

    • Create subgroups corresponding to containers of newly detected devices

      If this option is enabled, when the structure of the Managed devices\Cloud group has no subgroups that will match the section containing the device, Kaspersky Security Center Cloud Console creates such subgroups. For example, if a new subnet is discovered during device discovery, a new group with the same name will be created under the Managed devices\Cloud group.

      If this option is disabled, Kaspersky Security Center Cloud Console does not create any new subgroups. For example, if a new subnet is discovered during network poll, a new group with the same name will not be created under the Managed devices\Cloud group, and the devices that are in that subnet will be moved into the Managed devices\Cloud group.

      By default, this option is enabled.

    • Delete subgroups for which no match is found in the cloud segments

      If this option is enabled, the application deletes from the Cloud group all the subgroups that do not match any existing cloud objects.

      If this option is disabled, subgroups that do not match any of the existing cloud objects are retained.

      By default, this option is enabled.

    If you enabled the Synchronize administration groups with cloud structure option when using the Cloud environment configuration wizard, the Synchronize with cloud rule is created with the Create subgroups corresponding to containers of newly detected devices and Delete subgroups for which no match is found in the cloud segments options enabled.

    If you did not enable the Synchronize administration groups with cloud structure option, the Synchronize with cloud rule is created with these options disabled (cleared). If your work with Kaspersky Security Center Cloud Console requires that the structure of subgroups in the Managed devices\Cloud subgroup matches the structure of cloud segments, enable the Create subgroups corresponding to containers of newly detected devices and Delete subgroups for which no match is found in the cloud segments options in the rule properties, and then enforce the rule.

  4. In the Device discovered by using the API drop-down list, select one of the following values:
    • No. The device cannot be detected by using the AWS, Azure, or Google API, that is, it is either outside the cloud environment, or it is in the cloud environment but for some reason it cannot be detected by using an API.
    • AWS. The device is discovered by using the AWS API, that is, the device is definitely in the AWS cloud environment.
    • Azure. The device is discovered by using the Azure API, that is, the device is definitely in the Azure cloud environment.
    • Google Cloud. The device is discovered by using the Google API, that is, the device is definitely in the Google cloud environment.
    • No value. This criterion cannot be applied.
  5. If necessary, set up other rule properties in the other sections.

The moving rule is configured.

See also:

Step 4. Segment polling and configuring synchronization with Cloud

Page top

[Topic 218327]

Remote installation of applications to the Azure virtual machines

Expand all | Collapse all

You must have a valid license to install applications on Microsoft Azure virtual machines.

Kaspersky Security Center Cloud Console supports the following scenarios:

  • A client device is discovered by means of Azure API; the installation is also performed by means of an API. Using the Azure API means that you can only install the following applications:
    • Kaspersky Endpoint Security for Linux
    • Kaspersky Endpoint Security for Windows
    • Kaspersky Security for Windows Server
  • A client device is discovered by means of Azure API; the installation is performed by means of a distribution point or, if there are no distribution points, manually by using standalone installation packages. You can install any application supported by Kaspersky Security Center Cloud Console in this way.

To create a task for remote installation of an application on Azure virtual machines:

  1. In the main menu, go to Assets (Devices) → Tasks.
  2. Click Add.

    The New task wizard starts.

  3. Follow the instructions of the wizard:
    1. Select Install application remotely as the task type.
    2. On the Installation packages page, select Remote installation by Microsoft Azure API.
    3. When selecting the account to access devices, use an existing Azure account, or click Add and enter the credentials of your Azure account:
      • Azure Account Name

        Enter any name for the credentials you are specifying. This name will be displayed in the list of the accounts to run the task.

      • Azure Application ID

        You created this application ID on the Azure portal.

        You can provide only one Azure Application ID for polling and other purposes. If you want to poll another Azure segment, you must first delete the existing Azure connection.

      • Azure Application password

        You received the password of the Application ID when you created the Application ID.

        The characters of the password are displayed as asterisks. After you begin entering the password, the Show button becomes available. Click and hold this button to view the characters you entered.

    4. Select the relevant devices from the Managed devices\Cloud group.

After the wizard finishes, the task for remote installation of the application appears in the list of tasks.

See also:

Scenario: Kaspersky applications initial deployment

Page top

[Topic 241127]

Contact Technical Support

This section describes how to get technical support and the terms on which it is available.

In this section

How to get technical support

Technical support via Kaspersky CompanyAccount

Information required for Kaspersky Technical Support specialists

Page top

[Topic 68247]

How to get technical support

If you can't find a solution to your issue in the Kaspersky Security Center Cloud Console documentation or in any of the sources of information about Kaspersky Security Center Cloud Console, contact Kaspersky Technical Support. Technical Support specialists will answer all your questions about installing and using Kaspersky Security Center Cloud Console.

Kaspersky provides support of Kaspersky Security Center Cloud Console during its lifecycle (see the application support lifecycle page). Before contacting Technical Support, please read the support rules.

You can contact Technical Support in one of the following ways:

Page top

[Topic 68417]

Technical support via Kaspersky CompanyAccount

Kaspersky CompanyAccount is a portal for companies that use Kaspersky applications. The Kaspersky CompanyAccount portal is designed to facilitate interaction between users and Kaspersky specialists through online requests. You can use Kaspersky CompanyAccount to track the status of your online requests and store a history of them as well.

You can register all of your organization's employees under a single account on Kaspersky CompanyAccount. A single account lets you centrally manage electronic requests from registered employees to Kaspersky and also manage the privileges of these employees via Kaspersky CompanyAccount.

The Kaspersky CompanyAccount portal is available in the following languages:

  • English
  • Spanish
  • Italian
  • German
  • Polish
  • Portuguese
  • Russian
  • French
  • Japanese

To learn more about Kaspersky CompanyAccount, visit the Technical Support website.

Page top

[Topic 227940]

Information required for Kaspersky Technical Support specialists

When you contact Kaspersky Technical Support specialists, they may ask you to provide the following information:

  • General information about Kaspersky Security Center Cloud Console
  • Workspace ID
  • License information
  • Number of installed applications
  • Tenant ID and status

You can find this information in the Your account menuTechnical Support section. Copy and share this information to get help on your issue.

See also:

How to get technical support

Technical support via Kaspersky CompanyAccount

Page top

[Topic 166360]

Sources of information about the application

Kaspersky Security Center Cloud Console page on the Kaspersky website

On the Kaspersky Security Center Cloud Console page on the Kaspersky website, you can view general information about the application, its functions, and features.

Kaspersky Security Center Cloud Console page in the Knowledge Base

The Knowledge Base is a section on the Kaspersky Technical Support website.

On the Kaspersky Security Center Cloud Console page in the Knowledge Base, you can read articles that provide useful information, recommendations, and answers to frequently asked questions on how to buy, install, and use the application.

Articles in the Knowledge Base may provide answers to questions that relate both to Kaspersky Security Center Cloud Console as well as to other Kaspersky applications. Articles in the Knowledge Base may also contain Technical Support news.

Discuss Kaspersky applications with the community

If your question does not require an immediate answer, you can discuss it with Kaspersky experts and other users on our Forum.

On the Forum, you can view discussion topics, post your comments, and create new discussion topics.

An internet connection is required to access website resources.

If you cannot find a solution to your problem, contact Technical Support.

Page top

[Topic 218755]

Known issues

Kaspersky Security Center Cloud Console has a number of limitations that are not critical to operation of the application:

  • You cannot add an installation package with the same localization language several times. For example, if you already added the Kaspersky Endpoint Security for Windows (English) installation package, you can add Kaspersky Endpoint Security for Windows installation packages localized in other languages, except English.
  • When you try to activate the Kaspersky MDR solution, an error occurs if the MDR services are unavailable.
  • In the Kaspersky Endpoint Security for Mac policy, in the Advanced Threat Protection section, if you click the KSN Statement button several times, the window containing KSN Statement opens as many times as you have clicked the button.
  • In the Alert details window, if you click any link that opens another section, and then try to return and click the Back button of your browser (or press Alt+Left), the Alert details window loads indefinitely.
  • When you try to remove the last license key in the Kaspersky licenses section, the Remove button in the confirmation window is not visible if the dark interface theme of Web Console is enabled.
  • In the Kaspersky Endpoint Security for Mac policy, if you enable the integration with KATA and you do not specify the server address and certificate, an attempt to enable the Web Control feature returns an error.
  • When you import the Download updates to the repositories of distribution points or Update verification task the Select devices to which the task will be assigned option is enabled. These tasks cannot be assigned to a device selection or specific devices. If you assign the Download updates to the repositories of distribution points or Update verification task to specific devices, the task will be imported incorrectly.
  • After the Inventory scan task is complete for a Linux device, an attempt to send the received files to Kaspersky for analysis returns an error.
  • If you make an attempt to log in to Kaspersky Security Center Cloud Console by using Active Directory Federation Services (ADFS), but the required permissions are missing, Kaspersky Security Center Cloud Console still returns the "Invalid credentials" error instead of warning the user of missing permissions.
  • The Manage devices task does not work correctly for devices running macOS.
  • In the Remote diagnostics window, clicking the Download entire file button might not result in correct downloading.
  • An ignored third-party vulnerability (not including Microsoft software) is not shown on the Statistics of vulnerability on devices diagram.

Page top

[Topic 95897]

Glossary

Account on Kaspersky Security Center Cloud Console

An account that you must have to configure Kaspersky Security Center Cloud Console by, for example, adding and removing user accounts, and configuring security profiles (security policies). This account lets you use the My Kaspersky service. You create this account when you start using Kaspersky Security Center Cloud Console.

Active key

A key that is currently used by the application.

Additional (or reserve) license key

A key that certifies the right to use the application but is not currently being used.

Administration group

A set of devices grouped by function and by installed Kaspersky applications. Devices are grouped as a single entity for the convenience of management. A group can include other groups. Group policies and group tasks can be created for each installed application in the group.

Administration Server

A component of Kaspersky Security Center Cloud Console that centrally stores information about all Kaspersky applications that are installed on the corporate network. It can also be used to manage these applications.

Amazon EC2 instance

A virtual machine created based on an AMI image using Amazon Web Services.

Amazon Machine Image (AMI)

The template containing the software configuration necessary for running the virtual machine. Multiple instances can be created based on a single AMI.

Anti-virus databases

Databases that contain information about computer security threats known to Kaspersky as of when the anti-virus databases are released. Entries in anti-virus databases allow malicious code to be detected in scanned objects. Anti-virus databases are created by Kaspersky specialists and updated hourly.

Application tag

A label for third-party applications that can be used for grouping or finding applications. A tag assigned to applications can serve as a condition in device selections.

Authentication Agent

Interface that lets you complete authentication to access encrypted hard drives and load the operating system after the bootable hard drive has been encrypted.

Available update

A set of updates for Kaspersky application modules, including critical updates accumulated over a certain period of time.

AWS Application Program Interface (AWS API)

The application programming interface of the AWS platform that is used by Kaspersky Security Center Cloud Console. Specifically, AWS API tools are used for cloud segment polling.

AWS IAM access key

A combination consisting of the key ID (which looks like "AKIAIOSFODNN7EXAMPLE") and secret key (which looks like "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"). This pair belongs to the IAM user and is used to obtain access to AWS services.

AWS Management Console

The web interface for viewing and managing AWS resources. AWS Management Console is available on the web at https://aws.amazon.com/console/.

Broadcast domain

A logical area of a network in which all nodes can exchange data using a broadcasting channel at the level of OSI (Open Systems Interconnection Basic Reference Model).

Centralized application management

Remote application management using the administration services provided in Kaspersky Security Center Cloud Console.

Cloud Discovery

Cloud Discovery is a component of the Cloud Access Security Broker (CASB) solution that protects the cloud infrastructure of an organization. Cloud Discovery manages user access to cloud services. Cloud services include, for example, Microsoft Teams, Salesforce, Microsoft Office 365. Cloud services are grouped in categories, for example, Data exchange, Messengers, Email.

Connection gateway

A connection gateway is a Network Agent acting in a special mode. A connection gateway accepts connections from other Network Agents and tunnels them to the Administration Server through its own connection with the Server. Unlike an ordinary Network Agent, a connection gateway waits for connections from the Administration Server rather than establishes connections to the Administration Server.

Demilitarized zone (DMZ)

Demilitarized zone is a segment of a local network that contains servers, which respond to requests from the global Web. In order to ensure the security of an organization's local network, access to the LAN from the demilitarized zone is protected with a firewall.

Device owner

Device owner is a user whom the administrator can contact when the need arises to perform certain operations on a device.

Device tag

A label of a device that can be used for grouping, describing, or finding devices.

Direct application management

Application management through a local interface.

Distribution point

Computer that has Network Agent installed and is used for update distribution, network polling, remote installation of applications, getting information about computers in an administration group, and / or broadcasting domain. The administrator selects the appropriate devices and assigns them distribution points manually.

Event repository

A part of the Administration Server database dedicated to storage of information about events that occur in Kaspersky Security Center Cloud Console.

Event severity

Property of an event encountered during the operation of a Kaspersky application. There are the following severity levels:

  • Critical event
  • Functional failure
  • Warning
  • Info

Events of the same type can have different severity levels depending on the situation in which the event occurred.

Forced installation

Method for remote installation of Kaspersky applications that allows you to install software on specific client devices. For successful forced installation, the account used for the task must have sufficient rights to start applications remotely on client devices. This method is recommended for installing applications on devices that are running Microsoft Windows operating systems and that support this functionality.

Group task

A task defined for an administration group and performed on all client devices included in that administration group.

Home Administration Server

Home Administration Server is the Administration Server that was specified during Network Agent installation. The home Administration Server can be used in settings of Network Agent connection profiles.

HTTPS

Secure protocol for data transfer, using encryption, between a browser and a web server. HTTPS is used to gain access to restricted information, such as corporate or financial data.

IAM role

Set of rights for making requests to AWS-based services. IAM roles are not linked to a specific user or group; they provide access rights without AWS IAM access keys. You can assign an IAM role to IAM users, EC2 instances, and AWS-based applications or services.

IAM user

The user of AWS services. An IAM user may have the rights to perform cloud segment polling.

Identity and Access Management (IAM)

The AWS service that enables management of user access to other AWS services and resources.

Incompatible application

An anti-virus application from a third-party developer or a Kaspersky application that does not support management through Kaspersky Security Center Cloud Console.

Installation package

A set of files created for remote installation of a Kaspersky application by using the Kaspersky Security Center Cloud Console remote administration system. The installation package contains a range of settings needed to install the application and get it running immediately after installation. Settings correspond to application defaults. The installation package is created using files with the .kpd and .kud extensions included in the application distribution kit.

JavaScript

A programming language that expands the performance of web pages. Web pages created using JavaScript can perform functions (for example, change the view of interface elements or open additional windows) without refreshing the web page with new data from a web server. To view pages created by using JavaScript, enable JavaScript support in the configuration of your browser.

Kaspersky Next Expert View

An application designed for the centralized execution of basic administration and maintenance tasks on an organization's network. Kaspersky Next Expert View is hosted and maintained by Kaspersky. The application is a part of the Kaspersky Next cloud solution. Within this solution, you can also use Kaspersky Next Pro View.

Kaspersky Private Security Network (KPSN)

Kaspersky Private Security Network is a solution that gives users of devices with Kaspersky applications installed access to reputation databases of Kaspersky Security Network and other statistical data—without sending data from their devices to Kaspersky Security Network. Kaspersky Private Security Network is designed for corporate customers who are unable to participate in Kaspersky Security Network for any of the following reasons:

  • Devices are not connected to the internet.
  • Transmission of any data outside the country or the corporate LAN is prohibited by law or corporate security policies.

Kaspersky Security Center Cloud Console Administrator

The person managing application operations through the Kaspersky Security Center Cloud Console remote centralized administration system.

Kaspersky Security Center Cloud Console Operator

A user who monitors the status and operation of a protection system managed with Kaspersky Security Center Cloud Console.

Kaspersky Security Network (KSN)

An infrastructure of cloud services that provides access to the Kaspersky database with constantly updated information about the reputation of files, web resources, and software. Kaspersky Security Network ensures faster responses by Kaspersky applications to threats, improves the performance of some protection components, and reduces the likelihood of false positives.

Kaspersky update servers

HTTP(S) servers at Kaspersky from which Kaspersky applications download database and application module updates.

Key file

A file in xxxxxxxx.key format that makes it possible to use a Kaspersky application under a trial or commercial license.

License term

A time period during which you have access to the application features and rights to use additional services. The services you can use depend on the type of the license.

Local installation

Installation of a security application on a device on a corporate network that presumes manual installation startup from the distribution package of the security application or manual startup of a published installation package that was pre-downloaded to the device.

Local task

A task defined and running on a single client computer.

Managed device

A computer with Network Agent installed or a mobile device with a Kaspersky security application installed.

Management web plug-in

A special component that is used for remote administration of Kaspersky software by means of Kaspersky Security Center Cloud Console. A management plug-in is an interface between Kaspersky Security Center Cloud Console and a specific Kaspersky application. With a management plug-in, you can configure tasks and policies for the application.

Network Agent

A Kaspersky Security Center Cloud Console component that enables interaction between the Administration Server and Kaspersky applications that are installed on a specific network node (workstation or server). This component is common to all of the company's applications for Microsoft Windows. Separate versions of Network Agent exist for Kaspersky applications developed for Unix-like OS and macOS.

Network anti-virus protection

A set of technical and organizational measures that lower the risk of allowing viruses and spam to penetrate the network of an organization, and that prevent network attacks, phishing, and other threats. Network security increases when you use security applications and services and when you apply and adhere to the corporate data security policy.

Network protection status

Current protection status, which defines the safety of corporate networked devices. The network protection status includes such factors as installed security applications, usage of license keys, and number and types of threats detected.

Patch importance level

Attribute of the patch. There are five importance levels for Microsoft patches and third-party patches:

  • Critical
  • High
  • Medium
  • Low
  • Unknown

The importance level of a third-party patch or Microsoft patch is determined by the least favorable severity level among the vulnerabilities that the patches should fix.

Policy

A policy determines an application's settings and manages the ability to configure that application on computers within an administration group. An individual policy must be created for each application. You can create multiple policies for applications installed on computers in each administration group, but only one policy can be applied at a time to each application within an administration group.

Policy profile

A named subset of policy settings. This subset is distributed on target devices together with the policy, supplementing it under a specific condition called the profile activation condition.

Program settings

Application settings that are common to all types of tasks and govern the overall operation of the application, such as application performance settings, report settings, and backup settings.

Protection status

Current protection status, which reflects the level of computer security.

Quarantine

A special repository for storing files that are probably infected with viruses and files that cannot be disinfected at the time when they are detected.

Remote installation

Installation of Kaspersky applications by using the services provided by Kaspersky Security Center Cloud Console.

Restoration

Relocation of the original object from Quarantine or Backup to its original folder where the object had been stored before it was quarantined, disinfected or deleted, or to a user-defined folder.

SSL

A data encryption protocol used on the internet and local networks. The Secure Sockets Layer (SSL) protocol is used in web applications to create a secure connection between a client and server.

Task

Functions performed by the Kaspersky application are implemented as tasks, such as: Real-time file protection, Full computer scan, and Database update.

Task for specific devices

A task assigned to a set of client devices from arbitrary administration groups and performed on those devices.

Task settings

Application settings that are specific for each task type.

UEFI protection device

Device with a Kaspersky solution or application for UEFI integrated at the BIOS level. Integrated protection ensures device security from the moment the system starts, while protection on devices without integrated software begins functioning only after the security application starts.

Update

The procedure of replacing or adding new files (databases or application modules) retrieved from the Kaspersky update servers.

Virtual Administration Server

A component of Kaspersky Security Center Cloud Console, designed for management of the protection system of a client organization's network.

Virtual Administration Server is a particular case of a secondary Administration Server and has the following restrictions as compared with a physical Administration Server:

  • Virtual Administration Servers can work only as secondary Administration Servers.
  • Virtual Administration Server does not support creation of secondary Administration Servers (including virtual Servers).
Virus activity threshold

Maximum allowed number of events of the specified type within a limited time; when this number is exceeded, it is interpreted as increased virus activity and as a threat of a virus outbreak. This feature is important during periods of virus outbreaks because it enables administrators to respond in a timely manner to virus attack threats.

Virus outbreak

A series of deliberate attempts to infect a device with a virus.

Vulnerability

A flaw in an operating system or an application that may be exploited by malware makers to penetrate the operating system or application, and corrupt its integrity. The presence of a large number of vulnerabilities in an operating system makes it unreliable, because viruses that penetrate the operating system may cause disruptions in the operating system itself and in installed applications.

Workspace

An instance of Kaspersky Security Center Cloud Console created for a specific company. When a customer creates a workspace, Kaspersky creates and configures the infrastructure and cloud-based Administration Console that are required to manage security applications installed on the devices of the company.

Page top

[Topic 189965]

Information about third-party code

Information about third-party code is contained in the file legal_notices.txt.

The file legal_notices.txt is also located in the installation folder of Network Agent for Windows and Network Agent for Linux.

For additional information about third-party code used for the workspaces, refer to the Kaspersky Endpoint Security Cloud documentation.

Page top

[Topic 49304]

Trademark notices

Registered trademarks and service marks are the property of their respective owners.

Adobe, Acrobat, Flash, PostScript, Reader, Shockwave are either registered trademarks or trademarks of Adobe in the United States and/or other countries.

AMD64 is a trademark or registered trademark of Advanced Micro Devices, Inc.

Amazon, Amazon EC2, Amazon Web Services, AWS and AWS Marketplace are trademarks of Amazon.com, Inc. or its affiliates.

Apache is either a registered trademark or a trademark of the Apache Software Foundation.

Apple, App Store, AppleScript, FileVault, iPhone, iTunes, Mac, Mac OS, macOS, OS X, Safari, and QuickTime are trademarks of Apple Inc.

Arm is a registered trademark of Arm Limited (or its subsidiaries) in the US and/or elsewhere.

The Bluetooth word, mark and logos are owned by Bluetooth SIG, Inc.

Ubuntu, LTS are registered trademarks of Canonical Ltd.

Cisco, IOS, Cisco Jabber are registered trademarks or trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

Citrix, XenServer are either registered trademarks or trademarks of Cloud Software Group, Inc., and/or its subsidiaries in the United States and/or other countries.

Cloudflare, the Cloudflare logo, and Cloudflare Workers are trademarks and/or registered trademarks of Cloudflare, Inc. in the United States and other jurisdictions.

Corel, and CorelDRAW are trademarks or registered trademarks of Corel Corporation and/or its subsidiaries in Canada, the United States and/or other countries.

Dropbox is a trademark of Dropbox, Inc.

Radmin is a registered trademark of Famatech.

Firebird is a registered trademark of the Firebird Foundation.

Foxit is a registered trademark of Foxit Corporation.

FreeBSD is a registered trademark of The FreeBSD Foundation.

Google, Android, Chrome, Dalvik, Firebase, Google Chrome, Google Earth, Google Maps, Google Play, Google Public DNS are trademarks of Google LLC.

HUAWEI, EulerOS, HUAWEI CLOUD are trademarks of Huawei Technologies Co., Ltd.

Intel and Core are trademarks of Intel Corporation or its subsidiaries.

IBM, QRadar are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide.

Node.js is a trademark of Joyent, Inc.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Logitech is either a registered trademark or trademark of Logitech in the United States and/or other countries.

Microsoft, Active Directory, ActiveSync, ActiveX, BitLocker, Excel, Hyper-V, InfoPath, Internet Explorer, Microsoft Edge, MS-DOS, MultiPoint, Office 365, OneNote, Outlook, PowerPoint, PowerShell, Segoe, Skype, SQL Server, Tahoma, Visio, Win32, Windows, Windows Azure, Windows Media, Windows Mobile, Windows Phone, Windows Server, and Windows Vista are trademarks of the Microsoft group of companies.

CVE is a registered trademark of The MITRE Corporation.

Mozilla, Firefox, Thunderbird are trademarks of the Mozilla Foundation in the U.S. and other countries.

Novell is a registered trademark of Novell Enterprises Inc. in the United States and other countries.

NetWare is a registered trademark of Novell Inc. in the United States and other countries.

OpenVPN is a registered trademark of OpenVPN, Inc.

Oracle, Java, JavaScript are registered trademarks of Oracle and/or its affiliates.

Parallels, the Parallels logo, and Coherence are trademarks or registered trademarks of Parallels International GmbH.

Python is a trademark or registered trademark of the Python Software Foundation.

Red Hat, Red Hat Enterprise Linux, CentOS, Fedora are trademarks or registered trademarks of Red Hat, Inc. or its subsidiaries in the United States and other countries.

BlackBerry is owned by Research In Motion Limited and is registered in the United States and may be pending or registered in other countries.

SAMSUNG is a trademark of SAMSUNG in the United States or other countries.

Debian is a registered trademark of Software in the Public Interest, Inc.

Splunk is a trademark and registered trademark of Splunk Inc. in the United States and other countries.

SUSE is a registered trademark of SUSE LLC in the United States and other countries.

Symbian trademark is owned by the Symbian Foundation Ltd.

OpenAPI is a trademark of The Linux Foundation.

Rocky Linux is a trademark of The Rocky Enterprise Software Foundation.

UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited.

Page top