Kaspersky Secure Mobility Management

Contents

[Topic 216446]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Kaspersky Security for Mobile Help

Kaspersky Security for Mobile is intended for protecting and managing corporate mobile devices, as well as personal mobile devices used by company employees for corporate purposes.

The components and features of Kaspersky Security for Mobile depend on the Kaspersky Security Center console that you use as an interface for protecting and managing mobile devices.

Select the necessary Help section, depending on your Kaspersky Security Center console:

Separate Help sections describe features and operations that are available to users of the Kaspersky Endpoint Security for Android app and the Kaspersky Security for iOS app.

Page top

[Topic 180199]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

What's new

Kaspersky Secure Mobility Management 1.0

In this release, we added a wide range of features to plug-ins for MMC-based Administration Console to set up control over corporate mobile devices.

The following features were added to the plug-in for managing Android devices:

  • The Kaspersky Endpoint Security for Android app now supports devices that operate in device owner mode. You can generate a QR code for app installation in device owner mode that allows you to configure different device settings.
  • Features for Android devices in device owner mode:
    • Restrictions of Android operating system features. These restrictions include:
      • Device features (reset to factory settings, screen capture, calls and SMS messages, and so on).
      • Apps (the use of different apps, app installation settings, and so on).
      • Storage (mounting external media, file transfer over USB, and so on).
      • Network (Wi-Fi and mobile networks, VPN settings, and so on).
      • Location Services (the use of location and changing location settings).
    • Management of Google Chrome settings.
    • Kiosk mode (with a single app or set of apps).
    • Management of Exchange ActiveSync settings for Gmail.
    • Connection to a NDES/SCEP server.
    • Installation of root certificates on devices.
    • Silent installation of required apps and uninstallation of blocked apps defined in App Control rules.
    • Option to delete apps blocked by App Control.
  • Features to configure screen unlock passwords for Android devices:
    • You can specify different password requirements.
    • You can manage the use of biometric unlock methods.
    • You can specify the password lifetime and history length.
    • You can specify the unlock password in the Administration Console and force the change on the device.
  • New options for Samsung KNOX devices:
    • Option to prohibit developer mode.
    • Option to prohibit sending crash reports to Google.
  • New features to configure Wi-Fi networks:
    • Support for the 802.1.x EAP security protocol and ability to configure its protection settings (such as the EAP method).
    • You can specify the list of allowed Wi-Fi networks to connect automatically and hide other networks from the user device.
  • New options to delete all data on a lost or stolen Android device after failed attempts to enter the unlock password.
  • Adding web clips to devices.

This release also includes the following new features in the plug-in for managing iOS MDM devices:

  • The new Compliance Control component that lets you monitor iOS MDM devices for compliance with corporate security requirements and take various actions.
  • You can manage apps on iOS MDM devices based on lists of allowed and prohibited apps.
  • New commands are added:
    • Reset password
    • Schedule operating system update
    • Set Bluetooth state
  • New features to configure VPN connections:
    • Support for the IKEv2 protocol.
    • You can set up activating the VPN connection for selected website domains in Safari.
  • New option to force the use of a password on a device.
  • New options to manage operating system features on supervised devices:
    • Delay software updates.
    • Manage access to USB devices.
    • Manage Wi-Fi, VPN, and Personal Hotspot settings.
    • Manage the use of NFC.

Starting from release 1.0, Kaspersky Security for Mobile no longer supports management of mobile devices by using the Exchange ActiveSync protocol (management of EAS devices). Instead, you can integrate with Exchange Server via policy settings for Android or iOS MDM devices. If you want to continue managing your devices via the Exchange ActiveSync protocol, please use earlier versions of the Kaspersky Security for Mobile solution.

Page top

[Topic 216976]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Comparison of application features depending on the management tools

You can manage mobile devices in Kaspersky Security Center by using the following management tools:

  • Microsoft Management Console-based (hereinafter referred to as "MMC-based") Administration Console of Kaspersky Security Center
  • Kaspersky Security Center Web Console
  • Kaspersky Security Center Cloud Console

The table below compares the features that are available in these tools.

Availability of features depending on the management tools

 

MMC-based Console

Web Console

Cloud Console

General

Android devices management

Available

Available

Available

iOS devices management

Available

(via an APNs certificate)

Available

(via the Kaspersky Security for iOS app)

Available

(via the Kaspersky Security for iOS app)

Mobile devices management

Adding devices by using a Google Play link

Available

Available

Available

Adding devices by using an App Store link

Not available

Available

Available

Adding iOS devices by using an iOS MDM profile

Available

Not available

Not available

Adding devices by creating an installation package

Available

Not available

Not available

Sending commands to mobile devices

Available

Available

(except the Mugshot command)

Available

(except the Mugshot command)

Removing mobile devices from Kaspersky Security Center

Available

Available

(Removing from the list of devices only. The app must be removed from the device manually.)

Available

(Removing from the list of devices only. The app must be removed from the device manually.)

Certificates management

Issuing mail certificates

Available

Not available

Not available

Issuing VPN certificates

Available

Not available

Not available

Issuing mobile certificates

Available

Available

Available

Issuing mobile certificates through Administration Server tools

Available

Available

Available

Specifying certificate files

Available

Not available

Not available

Integration with Public Key Infrastructure

Available

Not available

Not available

Policies management

Role-based access to configuring group policies

Available

Not available

Not available

Configuring mobile device synchronization with Kaspersky Security Center

Available

Available

Available

Configuring virus scans on mobile devices

Available

Available

Available

Configuring mobile device protection

Available

Available

Available

Configuring anti-virus database updates

Available

Available

Available

Configuring protection of stolen or lost device data

Available

Available

Available

Configuring user access to websites

Available

Available

Available

Configuring app control

Available

Available

Available

Configuring compliance control

Available

Available

Available

Configuring Android work profiles

Available

Not available

Not available

Configuring connection to a Wi-Fi network

Available

Not available

Not available

Samsung KNOX

Available

Not available

Not available

Other features

Global acceptance of EULA in Kaspersky Security Center

Available

Not available

Not available

Configuring Kaspersky Private Security Network

Available

Not available

Not available

Page top

[Topic 214493]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Distribution kit

The Kaspersky Security for Mobile distribution kit may include various components, depending on the chosen application version.

Mobile device management in Kaspersky Security Center Web Console

  • on_prem_ksm_devices_xx.x.x.x.zip

    Archive that contains the files required for the installation of the Kaspersky Security for Mobile (Devices) plug-in:

    • plugin.zip

      Archive that contains the Kaspersky Security for Mobile (Devices) plug-in.

    • signature.txt

      File that contains the signature for the Kaspersky Security for Mobile (Devices) plug-in.

  • on_prem_ksm_policies_xx.x.x.x.zip

    Archive that contains the files required for the installation of the Kaspersky Security for Mobile (Policies) plug-in:

    • plugin.zip

      Archive that contains the Kaspersky Security for Mobile (Policies) plug-in.

    • signature.txt

      File that contains the signature for the Kaspersky Security for Mobile (Policies) plug-in.

Mobile device management in Kaspersky Security Center Cloud Console

To manage mobile device in Kaspersky Security Center Cloud Console, you do not need to download a distribution package. You only need to create an account in Kaspersky Security Center Cloud Console. For more information about creating an account, please refer to Kaspersky Security Center Cloud Console Help.

Mobile device management in MMC-based Administration Console

  • Klcfginst_en.exe

    Installer of Kaspersky Endpoint Security for Android Administration Plug-in for administering the application by means of the Kaspersky Security Center remote administration system.

  • Klmdminst.exe

    Installer of Kaspersky Device Management for iOS Administration Plug-in for managing the application by means of the Kaspersky Security Center remote administration system.

File of the Kaspersky Endpoint Security for Android app

KES10_xx_xx_xxx.apk—Android package file of the Kaspersky Endpoint Security for Android app.

Auxiliary files

  • sc_package_xx.exe

    Self-extracting archive that contains the files required for installing the Kaspersky Endpoint Security for Android app by creating installation packages:

    • adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll

      Files required for creating installation packages.

    • installer.ini

      Configuration file that contains Administration Server connection settings.

    • KES10_xx_xx_xxx.apk

      Android package file of the Kaspersky Endpoint Security for Android app.

    • kmlisten.exe

      Utility for delivering installation packages through the administrator's computer.

    • kmlisten.ini

      Configuration file that contains the settings for the kmlisten.exe utility.

    • kmlisten.kpd

      Application description file.

  • SigningUtility.zip

    Archive that contains the utility for signing the distribution packages of the Kaspersky Endpoint Security for Android app and containers for iOS devices.

Documentation

  • Help for Kaspersky Security for Mobile.
Page top

[Topic 216448]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Working in Kaspersky Security Center Web Console and Kaspersky Security Center Cloud Console

This Help section describes protection and management of mobile devices by using Kaspersky Security Center Web Console (hereinafter also referred to as Web Console) or Kaspersky Security Center Cloud Console (hereinafter also referred to as Cloud Console).

In this section

About mobile device management in Kaspersky Security Center Web Console and Cloud Console

Deploying a mobile device management solution in Kaspersky Security Center Web Console or Cloud Console

Managing mobile devices in Kaspersky Security Center Web Console and Cloud Console

Managing group policies

Defining policy settings

Network load

Page top

[Topic 214475]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

About mobile device management in Kaspersky Security Center Web Console and Cloud Console

You can manage mobile devices in Kaspersky Security Center Web Console and Cloud Console by using the following components:

  • Kaspersky Endpoint Security for Android app

    The Kaspersky Endpoint Security for Android app ensures protection of mobile devices against web threats, viruses, and other programs that pose threats.

  • Kaspersky Security for iOS app

    The Kaspersky Security for iOS app ensures protection of mobile devices against phishing and web threats.

  • Kaspersky Security for Mobile (Devices) plug-in

    The Kaspersky Security for Mobile (Devices) plug-in provides the interface for managing mobile devices and the mobile apps installed on them through Kaspersky Security Center Web Console and Cloud Console.

  • Kaspersky Security for Mobile (Policies) plug-in

    The Kaspersky Security for Mobile (Policies) plug-in lets you define the configuration settings for devices connected to Kaspersky Security Center, by using group policies.

The plug-ins are integrated into the Kaspersky Security Center remote administration system. You can use Kaspersky Security Center Web Console or Cloud Console to manage mobile devices, as well as client computers and virtual systems. After you connect mobile devices to the Administration Server, they become managed. You can remotely monitor managed devices.

In this section

Key features of mobile device management in Kaspersky Security Center Web Console and Cloud Console

About the Kaspersky Endpoint Security for Android app

About the Kaspersky Security for iOS app

About the Kaspersky Security for Mobile (Devices) plug-in

About the Kaspersky Security for Mobile (Policies) plug-in

Hardware and software requirements

Known issues and considerations

Page top

[Topic 221102]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Key features of mobile device management in Kaspersky Security Center Web Console and Cloud Console

Kaspersky Security for Mobile provides the following features:

  • Distribution of email messages for connecting Android mobile devices to Kaspersky Security Center by using links to download the Kaspersky Endpoint Security for Android app from Google Play.
  • Distribution of email messages for connecting iOS mobile devices to Kaspersky Security Center by using links to download the Kaspersky Security for iOS app from App Store.
  • Remote connection of mobile devices to Kaspersky Security Center and other third-party EMM systems (for example, VMWare AirWatch, MobileIron, IBM Maas360, SOTI MobiControl).
  • Remote configuration of the mobile app, as well as remote configuration of services, apps, and functions of mobile devices.
  • Remote configuration of mobile devices in accordance with the corporate security requirements.
  • Prevention of leakage of corporate information stored on mobile devices, in case they are lost or stolen (Anti-Theft). Supported for Android devices only.
  • Control of compliance with corporate security requirements (Compliance Control). Supported for Android devices only.
  • Control of protection against online threats and control of internet use on mobile devices (Web Protection).
  • Setup of notifications shown to the user in the Kaspersky Endpoint Security for Android and Kaspersky Security for iOS apps.
  • Administrator notifications about the status and events of the Kaspersky Endpoint Security for Android and Kaspersky Security for iOS apps can be communicated in Kaspersky Security Center or by email.
  • Change Control for policy settings (revision history).

Kaspersky Security for Mobile includes the following protection and management components:

  • Anti-Virus (for Android devices)
  • Anti-Theft (for Android devices)
  • Web Protection (for Android and iOS devices)
  • App Control (for Android devices)
  • Compliance Control (for Android devices)
  • Detection of root privileges on Android devices and jailbreak detection on iOS devices

Page top

[Topic 214476]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

About the Kaspersky Endpoint Security for Android app

The Kaspersky Endpoint Security for Android app ensures protection of mobile devices against web threats, viruses, and other programs that pose threats.

The Kaspersky Endpoint Security for Android app includes the following components:

  • Anti-Virus. This component detects and neutralizes threats on your device by using the Anti-Virus databases and the Kaspersky Security Network cloud service. Anti-Virus includes the following components:
    • Protection. It detects threats in open files, scans new apps, and prevents device infection in real time.
    • Scan. It is started on demand for the entire file system, only for installed apps, or a selected file or folder.
    • Update. It allows you to download new Anti-Virus databases for the application.
  • Anti-Theft. This component protects information on the device against unauthorized access in case the device is lost or stolen. This component lets you send the following commands to the device:
    • Locate. Get the coordinates of the device's location.
    • Alarm. Make the device sound a loud alarm.
    • Wipe. Erase corporate data to protect sensitive company information.
  • 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. Web Protection scans websites before you open them, by using the Kaspersky Security Network cloud service. After scanning, Web Protection allows trustworthy websites to load and blocks malicious websites. Web Protection also supports website filtering by categories defined in the Kaspersky Security Network cloud service. This allows the administrator to restrict user access to certain categories of web pages (for example, web pages from the "Gambling, lotteries, sweepstakes" or "Internet communication" categories).
  • App Control. This component lets you install recommended and required apps to your device via a direct link to the distribution package or a link to Google Play. App Control lets you remove blocked apps that violate corporate security requirements.
  • Compliance control. This component allows you to check managed devices for compliance with the corporate security requirements and impose restrictions on certain functions of non-compliant devices.

You can configure the components of the Kaspersky Endpoint Security for Android app in Kaspersky Security Center Web Console and Cloud Console by defining the settings of group policies.

Page top

[Topic 234086]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

About the Kaspersky Security for iOS app

The Kaspersky Security for iOS app ensures protection of mobile devices against phishing and web threats.

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. Web Protection scans websites before you open them, by using the Kaspersky Security Network cloud service. After scanning, Web Protection allows trustworthy websites to load and blocks malicious websites. You can configure this component in Kaspersky Security Center Web Console and Cloud Console by defining the settings of group policies.
  • Jailbreak detection. When Kaspersky Security for iOS detects a jailbreak, it displays a critical message and informs you about the issue.
Page top

[Topic 216974]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

About the Kaspersky Security for Mobile (Devices) plug-in

The Kaspersky Security for Mobile (Devices) plug-in provides the interface for managing mobile devices and the mobile apps installed on them through Kaspersky Security Center Web Console and Cloud Console. The Kaspersky Security for Mobile (Devices) plug-in allows you to perform the following:

The Kaspersky Security for Mobile (Devices) plug-in can be installed when configuring Kaspersky Security Center Web Console. If you are using Kaspersky Security Center Cloud Console, you do not need to install this plug-in. For more information about deployment scenarios in different types of consoles, see section "Deployment scenarios".

Page top

[Topic 214478]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

About the Kaspersky Security for Mobile (Policies) plug-in

The Kaspersky Security for Mobile (Policies) plug-in lets you define the configuration settings for devices connected to Kaspersky Security Center, by using group policies. The Kaspersky Security for Mobile (Policies) plug-in can be used to perform the following:

The Kaspersky Security for Mobile (Policies) plug-in can be installed when configuring Kaspersky Security Center Web Console. If you are using Kaspersky Security Center Cloud Console, you do not need to install this plug-in. For more information about deployment scenarios in different types of consoles, see section "Deployment scenarios".

Page top

[Topic 214494]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Hardware and software requirements

This section lists the hardware and software requirements for the administrator's computer that is used to install the Kaspersky Security for Mobile (Devices) plug-in and the Kaspersky Security for Mobile (Policies) plug-in in Kaspersky Security Center Web Console and Cloud Console, as well as the hardware and software requirements of the mobile apps.

Hardware and software requirements for the administrator's computer

To install the Kaspersky Security for Mobile (Devices) plug-in and the Kaspersky Security for Mobile (Policies) plug-in, the administrator's computer must meet the hardware requirements of Kaspersky Security Center. For more information about the hardware and software requirements of Kaspersky Security Center:

To use the Kaspersky Security for Mobile (Devices) plug-in and the Kaspersky Security for Mobile (Policies) plug-in in Kaspersky Security Center Web Console, Kaspersky Security Center Web Console must be installed on the administrator's computer.

To use the Kaspersky Security for Mobile (Devices) plug-in and the Kaspersky Security for Mobile (Policies) plug-in in Kaspersky Security Center Cloud Console, you must create an account in Kaspersky Security Center Cloud Console. For more information about creating an account, please refer to Kaspersky Security Center Cloud Console Help.

The Kaspersky Endpoint Security for Android app can function within the following third-party EMM systems:

  • VMware AirWatch 9.3 or later
  • MobileIron 10.0 or later
  • IBM MaaS360 10.68 or later
  • Microsoft Intune 1908 or later
  • SOTI MobiControl 14.1.4 (1693) or later

Hardware and software requirements for the user's mobile device to support installation of the Kaspersky Endpoint Security for Android app

The Kaspersky Endpoint Security for Android app has the following hardware and software requirements:

  • Smartphone or tablet with a screen resolution of 320x480 pixels or higher
  • 65 MB of free disk space in the main memory of the device
  • Android 5.0–13 (including Android 12L, excluding Go Edition)
  • x86, x86-64, Arm5, Arm6, Arm7, or Arm8 processor architecture

The app can be installed only to the main memory of the device.

Hardware and software requirements for the user's mobile device to support installation of the Kaspersky Security for iOS app

The Kaspersky Security for iOS app has the following hardware requirements:

  • iPhone 6S or later
  • iPad Air 2 or later

The Kaspersky Security for iOS app has the following software requirements:

  • iOS 14.1 or later
  • iPadOS 14.1 or later

The Kaspersky Security for iOS app can't operate properly when a VPN client with an active VPN connection is running on the same mobile device.

Page top

[Topic 214562]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Known issues and considerations

Kaspersky Endpoint Security for Android and Kaspersky Security for iOS have several known issues that are non-critical for the operation of these apps.

Known issues of Kaspersky Security for iOS

  • The Kaspersky Security for iOS app can't operate properly when a VPN client with an active VPN connection is running on the same mobile device.

Known issues of Kaspersky Endpoint Security for Android

Known issues when installing apps

  • Kaspersky Endpoint Security for Android is installed only in the main memory of the device.
  • On devices running Android 7.0, an error may occur during attempts to disable administrator rights for Kaspersky Endpoint Security for Android in device settings if Kaspersky Endpoint Security for Android is prohibited from overlaying on other windows. This issue is caused by a well-known defect in Android 7.
  • Kaspersky Endpoint Security for Android on devices running Android 7.0 or later does not support multi-window mode.
  • Kaspersky Endpoint Security for Android does not work on Chromebook devices running the Chrome operating system.
  • Kaspersky Endpoint Security for Android does not work on devices running Android (Go edition) operating systems.
  • When using the Kaspersky Endpoint Security for Android app with third-party EMM systems (for example, VMWare AirWatch), only the Anti-Virus and Web Protection components are available. The administrator can configure the settings of Anti-Virus and Web Protection in the EMM system console. In this case, notifications about app operation are available only in the interface of the Kaspersky Endpoint Security for Android app (Reports).

Known issues when upgrading the app version

  • You can upgrade Kaspersky Endpoint Security for Android only to a more recent version of the app. Kaspersky Endpoint Security for Android cannot be downgraded to an older version.

Known issues in Anti-Virus operation

  • Due to technical limitations, Kaspersky Endpoint Security for Android cannot scan files with a size of 2 GB or more. During a scan, the app skips such files without notifying you that such files were skipped.
  • For additional analysis of a device for new threats whose information has not yet been added to anti-virus databases, you must enable the use of Kaspersky Security Network. Kaspersky Security Network (KSN) is an infrastructure of cloud services providing access to Kaspersky online knowledge base with information about the reputation of files, web resources, and software. To use KSN, the mobile device must be connected to the internet.
  • In some cases, updating anti-virus databases from the Administration Server on a mobile device may fail. In this case, run the anti-virus database update task on the Administration Server.
  • On some devices, Kaspersky Endpoint Security for Android does not detect devices connected over USB OTG. It is not possible to run a virus scan on such devices.
  • On devices running Android 11 or later, the Kaspersky Endpoint Security for Android app can't scan the "Android/data" and "Android/obb" folders and detect malware in them due to technical limitations.
  • On devices running Android 11 or later, the user must grant the "Allow access to manage all files" permission.
  • On devices running Android 7.0 or later, the configuration window for the virus scan run schedule might be incorrectly displayed (management elements are not shown). This issue is caused by a well-known defect in Android 7.
  • On devices running Android 7.0, real-time protection in the extended mode does not detect threats in files that are stored on an external SD card.
  • On devices running Android 6.0, Kaspersky Endpoint Security for Android does not detect the downloading of a malicious file to the device memory. A malicious file may be detected by Anti-Virus when the file is run, or during a virus scan of the device. This issue is caused by a well-known defect in Android 6.0. To ensure device security, it is recommended to configure scheduled virus scans.

Known issues in Web Protection operation

  • Web Protection on Android devices works only in the Google Chrome browser (including the Custom Tabs feature), Huawei Browser, and Samsung Internet Browser.

  • For Web Protection to work, you must enable the use of Kaspersky Security Network. Web Protection blocks websites based on the KSN data on the reputation and category of websites.
  • Forbidden websites may remain unblocked by Web Protection on devices running Android 6.0 with Google Chrome version 51 (or any earlier version) installed if the website is opened in the following ways (this issue is caused by a well-known defect in Google Chrome):
    • From search results.
    • From the bookmarks list.
    • From search history.
    • Using the web address autocomplete function.
    • Opening the website in a new tab in Google Chrome.
  • Forbidden websites may remain unblocked in Google Chrome version 50 (or any earlier version) if the website is opened from Google search results while the Merge Tabs and Apps feature is enabled in the browser settings. This issue is caused by a well-known defect in Google Chrome.
  • Websites from blocked categories may remain unblocked in Google Chrome if the user opens them from third-party apps, for example, from an IM client app. This issue is related to how the Accessibility service works with the Chrome Custom Tabs feature.
  • Forbidden websites may remain unblocked in Samsung Internet Browser if the user opens them in background mode from the context menu or from third-party apps, for example, from an IM client app.
  • Kaspersky Endpoint Security for Android must be set as an Accessibility feature to ensure proper functioning of Web Protection.
  • On some Xiaomi devices, the "Display pop-up window" and "Display pop-up windows while running in the background" permissions should be granted for Web Protection to work.
  • Allowed websites may be blocked in Samsung Internet Browser in the Only listed websites are allowed Web Protection mode when the page is refreshed. Websites are blocked if a regular expression contains advanced settings (for example, ^https?://example.com/pictures/). It is recommended to use regular expressions without additional settings (for example, ^https?://example.com).
  • If Web Protection is set to All websites are blocked, Kaspersky Endpoint Security for Android does not block search in the Google Search widget. Instead, it blocks user access to the search results.
  • In a work profile, if Web Protection is set to All websites are blocked, Kaspersky Endpoint Security for Android endlessly reloads the Google Chrome home page, blocks the browser, and interferes with the device.

Known issues in Anti-Theft operation

  • For timely delivery of commands to Android devices, the app uses the Firebase Cloud Messaging (FCM) service. If FCM is not configured, commands will be delivered to the device only during synchronization with Kaspersky Security Center according to the schedule defined in the policy, for example, every 24 hours.
  • To lock a device, Kaspersky Endpoint Security for Android must be set as the device administrator.
  • To lock devices running Android 7.0 or later, Kaspersky Endpoint Security for Android must be set as an Accessibility feature.
  • On some devices, Anti-Theft commands may fail to execute if Battery Saver mode is enabled on the device. This defect has been confirmed on Alcatel 5080X.
  • To locate devices running Android 10.0 or later, the user must grant the "All the time" permission to device location.

Known issues in App Control operation

  • Kaspersky Endpoint Security for Android must be set as an Accessibility feature to ensure proper functioning of App Control. This does not apply to device owner mode.
  • For App Control (app categories) to work, you must enable the use of Kaspersky Security Network. App Control determines the category of an app based on data that is available in KSN. To use KSN, the mobile device must be connected to the internet. For App Control, you can add individual apps to the lists of blocked and allowed apps. In this case, KSN is not required.
  • When configuring App Control, it is recommended to clear the Block system apps check box. Blocking system apps may lead to problems in device operation.

Known issues when configuring device unlock password strength

  • On devices running Android 10.0 or later, Kaspersky Endpoint Security resolves the password strength requirements into one of the system values: medium or high.

    If the password length required is 1 to 4 symbols, then the app prompts the user to set a medium-strength password. It must be either numeric (PIN), with no repeating or ordered (e.g. 1234) sequences; or alphanumeric. The PIN or password must be at least 4 characters long.

    If the password length required is 5 or more symbols, then the app prompts the user to set a high-strength password. It must be either numeric (PIN), with no repeating or ordered sequences; or alphanumeric (password). The PIN must be at least 8 digits long; the password must be at least 6 characters long.

  • On devices running Android 7.1.1, if the unlock password does not meet the corporate security requirements (Compliance Control), the Settings system app may function improperly when an attempt is made to change the unlock password through Kaspersky Endpoint Security for Android. The issue is caused by a well-known defect in Android 7.1.1. In this case, to change the unlock password, use the Settings system app only.
  • On some devices running Android 6.0 or later, an error may occur when screen unlock password is entered, if device data is encrypted. This issue is related to specific features of the Accessibility service with MIUI firmware.

Known issues with App removal protection

  • Kaspersky Endpoint Security for Android must be set as the device administrator.
  • To protect the app from removal on devices running Android 7.0 or later, Kaspersky Endpoint Security for Android must be set as an Accessibility feature.
  • On some Xiaomi and Huawei devices, Kaspersky Endpoint Security for Android removal protection does not work. This issue is caused by the specific features of MIUI 7 and 8 firmware on Xiaomi and EMUI firmware on Huawei.

Known issues when configuring device restrictions

  • On devices running Android 10.0 or later, prohibiting the use of Wi-Fi networks is not supported.
  • On devices running Android 10.0 or later, the use of the camera cannot be completely prohibited.
  • On devices running Android 11 or later, Kaspersky Endpoint Security for Android must be set as an Accessibility feature. Kaspersky Endpoint Security for Android prompts the user to set the app as an Accessibility feature through the Initial Configuration Wizard. The user can skip this step or disable this service in the device settings at a later time. If this is the case, you will not be able to restrict use of the camera.

Known issues when sending commands to mobile devices

  • On devices running Android 12 or later, if the user granted the "Use approximate location" permission, the Kaspersky Endpoint Security for Android app first tries to get the precise device location. If this is not successful, the approximate device location is returned only if it was received not more than 30 minutes earlier. Otherwise, the Locate device command fails.

Known issues with specific devices

  • On certain devices (for example, Huawei, Meizu, and Xiaomi), you must grant Kaspersky Endpoint Security for Android an autostart permission or manually add it to the list of apps that are started when the operating system starts. If the app is not added to the list, Kaspersky Endpoint Security for Android stops performing all of its functions after the mobile device is restarted. In addition, if the device has been locked, you cannot use a command to unlock the device. You can unlock the device only by using a one-time unlock code.
  • On certain devices (for example, Meizu and Asus) running Android 6.0 or later, after encrypting data and restarting the Android device, you must enter a numeric password to unlock the device. If the user uses a graphic password to unlock the device, you must convert the graphic password to a numeric password. For more details about converting a graphic password into a numeric password, please refer to the Technical Support website of the mobile device manufacturer. This issue is related to the operation of the Accessibility Features service.
  • On some Huawei devices running Android 5.Х, after Kaspersky Endpoint Security for Android is set as an Accessibility feature, an incorrect message about the lack of appropriate rights may be displayed. To hide this message, enable the app as a protected app in the device settings.
  • On some Huawei devices running Android 5.X or 6.X, when Battery Saver mode is enabled for Kaspersky Endpoint Security for Android, the user can manually terminate the app. The user device becomes unprotected after that. This issue is due to some features of Huawei software. To restore the device protection, run Kaspersky Endpoint Security for Android manually. It is recommended to disable Battery Saver mode for Kaspersky Endpoint Security for Android in the device settings.
  • On Huawei devices with EMUI firmware running Android 7.0, the user can hide the notification regarding the protection status of Kaspersky Endpoint Security for Android. This issue is due to some features of Huawei software.
  • On some Xiaomi devices, when setting the password length to more than 5 characters in a policy, the user will be prompted to change the screen unlock password instead of the PIN code. You cannot set a PIN code that has more than 5 characters. This issue is due to some features of Xiaomi software.
  • On Xiaomi devices with MIUI firmware running Android 6.0, the Kaspersky Endpoint Security for Android icon may be hidden in the status bar. This issue is due to some features of Xiaomi software. It is recommended to allow the display of notification icons in Notifications settings.
  • On some Nexus devices running Android 6.0.1, the privileges required for proper operation cannot be granted through the Quick Start Wizard of Kaspersky Endpoint Security for Android. This issue is caused by a well-known defect in Security Patch for Android by Google. To ensure proper operation, the required privileges must be manually granted in the device settings.
  • On certain Samsung devices running Android 7.0 or later, when the user attempts to configure unsupported methods for unlocking the device (for example, a graphical password), the device may be locked if the following conditions are met: Kaspersky Endpoint Security for Android removal protection is enabled and screen unlock password strength requirements are set. To unlock the device, you must send a special command to the device.
  • On certain Samsung devices, it is impossible to block the use of fingerprints for unlocking the screen.
  • Web Protection cannot be enabled on some Samsung devices, if the device is connected to a 3G/4G network, has Battery Saver mode enabled and restricts background data. It is recommended to disable the function that restricts background processes in Battery Saver settings.
  • On certain Samsung devices, if the unlock password does not comply with corporate security requirements, Kaspersky Endpoint Security for Android does not block the use of fingerprints for unlocking the screen.
  • On some Honor and Huawei devices, you cannot restrict the use of Bluetooth. When Kaspersky Endpoint Security for Android attempts to restrict the use of Bluetooth, the operating system shows a notification containing the options to reject or allow this restriction. The user can reject this restriction and continue to use Bluetooth.
  • On Blackview devices, the user can clear the memory for the Kaspersky Endpoint Security for Android app. As a result, the device protection and management are disabled, all defined settings become ineffective, and the Kaspersky Endpoint Security for Android app is removed from the Accessibility features. This is because this vendor's devices provide the customized Recent screens app with elevated privileges. This app can override Kaspersky Endpoint Security for Android settings and cannot be replaced because it is part of the Android operating system.
  • On some Google Pixel devices running Android 11 or earlier, the Kaspersky Endpoint Security for Android app crashes immediately after the start. This is caused by an issue in Android.
  • On Samsung Galaxy S23 and S24 series devices Real-Time Protection may not work.

Known issues in app operation on Android 13

  • On Android 13, the user can use the Foreground Services Task Manager to stop Kaspersky Endpoint Security from running in the background. This is caused by a well-known issue in Android 13.
  • On Android 13, the permission to send notifications is requested when the initial app configuration begins. This is due to specifics of the Android 13 operating system.

Page top

[Topic 214499]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Deploying a mobile device management solution in Kaspersky Security Center Web Console or Cloud Console

To manage mobile devices by using Kaspersky Security Center Web Console or Cloud Console, you must deploy a mobile device management solution.

In this section

Deployment scenarios

Preparing Kaspersky Security Center Web Console and Cloud Console for deployment

Deploying administration plug-ins

Deploying the mobile app

Managing certificates

Exchanging information with Firebase Cloud Messaging

Page top

[Topic 218256]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Deployment scenarios

Deployment in Kaspersky Security Center Web Console

Deployment of mobile device management solution in Kaspersky Security Center Web Console consists of the following steps:

  1. Preparing Kaspersky Security Center Web Console for deployment
  2. Deploying administration plug-ins
  3. Deploying the mobile app
  4. (Optional, for Android only) Configuring the information exchange with Firebase Cloud Messaging

    It is recommended to perform this step to ensure timely delivery of commands to mobile devices and forced synchronization when policy settings are changed.

Deployment in Kaspersky Security Center Cloud Console

Deployment of mobile device management solution in Kaspersky Security Center Cloud Console consists of the following steps:

  1. Preparing Kaspersky Security Center Cloud Console for deployment
  2. Deploying the mobile app
  3. (Optional, for Android only) Configuring the information exchange with Firebase Cloud Messaging

    It is recommended to perform this step to ensure timely delivery of commands to mobile devices and forced synchronization when policy settings are changed.

Page top

[Topic 214951]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Preparing Kaspersky Security Center Web Console and Cloud Console for deployment

This section provides instructions on preparing Kaspersky Security Center Web Console and Cloud Console for deployment.

In this section

Configuring Administration Server for connection of mobile devices

Configuring a connection gateway to connect mobile devices to Kaspersky Security Center Administration Server

Creating an administration group

Creating a rule for automatically allocating a device to administration groups

Page top

[Topic 218229]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring Administration Server for connection of mobile devices

To connect mobile devices to the Administration Server, you must define the connection settings before installing the app on devices.

  • If you are using Kaspersky Security Center Web Console, configure its properties as described below.
  • If you are using Kaspersky Security Center Cloud Console, the connection settings are defined during the initial configuration of Kaspersky Security Center Cloud Console. For more information, please refer to Kaspersky Security Center Cloud Console Help.

To define Kaspersky Security Center Web Console properties for a mobile device connection:

  1. In the main window of Kaspersky Security Center Web Console, click Settings (NWC_settings_icon).

    The Administration Server properties window opens.

  2. Configure the Administration Server ports that will be used by mobile devices:
    1. Select the Additional ports section.
    2. Enable the Open port for mobile devices toggle button.
    3. In the Port for mobile device synchronization field, specify the port through which mobile devices will connect to the Administration Server.

      Port 13292 is used by default.

      If the Open port for mobile devices toggle button is off or an incorrect connection port is specified, mobile devices will not be able to connect to the Administration Server.

    4. In the Port for mobile device activation field, specify the port to be used by mobile devices to connect to the Administration Server for activation of the mobile app.

      Port 17100 is used by default.

      If you specify an incorrect connection port, the users of mobile devices will not be able to activate the mobile app by using the Administration Server.

  3. If necessary, edit the certificate that will be used by mobile devices to connect to the Administration Server.

    By default, Administration Server uses the certificate that was created during Administration Server installation. If you want, replace the certificate issued through the Administration Server with another certificate or reissue the certificate issued through the Administration Server.

    To edit the certificate:

    1. Select the Certificates section.
    2. Define the required settings.

      For detailed information about the certificates, please refer to Kaspersky Security Center Help.

  4. Click the Save button to save the changes you have made to the settings and exit the Administration Server properties window.

After you configure the mobile device connection settings, you can install the Kaspersky Endpoint Security for Android app or the Kaspersky Security for iOS app on mobile devices and connect them to the Administration Server by using the specified settings.

Page top

[Topic 245223]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring a connection gateway to connect mobile devices to Kaspersky Security Center Administration Server

This topic describes how to configure a connection gateway to connect mobile devices to Kaspersky Security Center Administration Server. The configuration proceeds in the following steps:

  1. Install Network Agent in the connection gateway role on a host
  2. Configure the connection gateway on Kaspersky Security Center Administration Server

This article contains an overview of the scenario. For detailed instructions, please refer to the Kaspersky Security Center documentation.

Requirements

For a connection gateway to work correctly with mobile devices, the following requirements must be met:

  • Port 13292 must be open on the host with the connection gateway.
  • Port 13000 must be open between the connection gateway and Kaspersky Security Center. It does not need to be open outside the DMZ.
  • The host must have a static address accessible from the internet.

Install Network Agent in the connection gateway role on a host

First, you need to install Network Agent on the selected host device acting in the gateway connection role. You can download a full installation package of Kaspersky Security Center or use a local installation of Kaspersky Security Center.

By default, the installation file is located at: \\<server name>\KLSHARE\PkgInst\NetAgent_<version number>

To install Network Agent in the connection gateway role:

  1. Start the Network Agent Setup Wizard and follow its instructions leaving default values for all of the options until the Select Administration Server window opens.
  2. In the Select Administration Server window, configure the following settings:
    • Enter the address of the device with Administration Server installed.
    • In the Port, SSL port, and UDP port fields, leave the default values.
    • Select the Use SSL to connect to Administration Server check box to establish a connection to the Administration Server through a secure port via SSL.

      We recommend that you do not clear this check box so your connection remains secured.

    • Select the Allow Network Agent to open UDP port check box to manage client devices and receive information about them.
  3. Click Next and proceed through the Wizard with default settings up to the Connection gateway window.
  4. In the Connection gateway window, select Use Network Agent as a connection gateway in DMZ.

    This mode simultaneously activates the connection gateway role and tells Network Agent to wait for connections from Administration Server, rather than establish connections to Administration Server.

  5. Click Next and start the installation.

Network Agent is now installed and configured in the connection gateway role.

Configure the connection gateway on Kaspersky Security Center Administration Server

Once you have installed Network Agent in the connection gateway role, you need to connect it to Administration Server. Administration Server does not yet list the device with the connection gateway among the managed devices because the connection gateway has not tried to connect to Administration Server. Therefore, you need to add the connection gateway as a distribution point to ensure that Administration Server initiates a connection to the connection gateway.

To configure the connection gateway on Administration Server:

  1. Add the connection gateway as a distribution point in Kaspersky Security Center.
    1. In the console tree, select the Administration Server node.
    2. In the context menu of Administration Server, select Properties.
    3. In the Administration Server properties window, select the Distribution points section.
    4. Click the Add button.

      The Add distribution point window opens.

    5. In the Add distribution point window, perform the following actions:
      • Specify the IP address of the device with Network Agent installed in the Device to act as distribution point field. To do this, select Add connection gateway in DMZ by address in the drop-down list.

        Enter the IP address of the connection gateway or enter the name if the connection gateway is accessible by name.

      • In the Distribution point scope field, select the group to which the connection gateway will be distributed from the drop-down list, and then click OK.
    6. In the Distribution points section, click OK to save the changes you have made.

    The connection gateway will be saved as a new entry named Temporary entry for connection gateway.

    Administration Server almost immediately attempts to connect to the connection gateway at the address that you specified. If it succeeds, the entry name changes to the name of the connection gateway device. This process takes up to five minutes.

    While the temporary entry for the connection gateway is being converted to a named entry, the connection gateway also appears in the Unassigned devices group.

  2. Create a new group under the Managed devices group. This new group will contain external managed devices.
  3. Move the connection gateway from the Unassigned devices group to the group that you have created for external devices.
  4. Configure properties of the connection gateway that you have deployed:
    1. In the Distribution points section of the Administration Server properties, select the connection gateway and click Properties.
    2. In the General section, under DNS domain names of the distribution point for access by mobile devices (included in the certificate), specify your connection gateway DNS name that will be used to connect to the mobile device.
    3. In the Connection Gateway section, select the following check boxes and leave the default port numbers:
      • Open port for mobile devices (SSL authentication of the Administration Server only)
      • Open port for mobile devices (two-way SSL authentication)
    4. Click OK to save the changes you have made.

The connection gateway is now configured. You can now add new mobile devices by specifying the connection gateway address. New devices will appear on Administration Server.

Page top

[Topic 218231]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Creating an administration group

Group policies are used to perform centralized configuration of the Kaspersky Endpoint Security for Android and Kaspersky Security for iOS apps installed on the users' mobile devices.

To apply a policy to a group of devices, you are advised to create a separate group for these devices in Managed devices prior to installing mobile apps on user devices.

After creating an administration group, it is recommended to configure the option to automatically allocate devices on which you want to install the apps to this group. Then configure settings that are common to all devices by using a group policy.

To create an administration group:

  1. In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Hierarchy of groups.
  2. In the administration group structure, select the administration group that is to include the new administration group.
  3. Click the Add button.
  4. In the Name of the new administration group window that opens, enter a name for the group, and then click the Add button.

A new administration group with the specified name appears in the hierarchy of administration groups.

Page top

[Topic 214519]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Creating a rule for automatically allocating a device to administration groups

When the Kaspersky Endpoint Security for Android app or the Kaspersky Security for iOS app is installed on mobile devices, they are displayed on the Discovery & deployment > Unassigned devices page of Kaspersky Security Center Web Console or Cloud Console. In order to manage newly connected devices, you can move them to an administration group manually or create a rule for allocating them automatically to administration groups.

To create a rule for automatic allocation of mobile devices to administration groups:

  1. In the main window of Kaspersky Security Center Web Console or Cloud Console, select Discovery & deployment > Deployment & assignment > Moving rules.
  2. In the New rule window that opens, click the Add button.
  3. In the Rule name field, specify the rule name.
  4. In the Administration group field, select the administration group to which mobile devices will be allocated after the app has been installed on them.
  5. In the Apply rule section, select Run once for each device.
  6. Select the Move only devices not added to an administration group check box to prevent the moving of the mobile devices that are allocated to other administration groups when applying the rule.
  7. Select the Enable rule check box, to apply the rule immediately after creating it.

    You can enable the rule at any time later by using the toggle button on the Moving rules page.

  8. Select Rule conditions > Applications and do the following:
    1. Enable the Operating system version toggle button.
    2. In the list of operating systems that opens, select Android or iOS.

    The rule will be applied to the corresponding devices. You must specify at least one condition to create a rule.

  9. Click Save to create the rule.

The newly created rule is displayed on the Moving rules page. According to the rule, Kaspersky Security Center will allocate all newly connected devices to the selected administration group.

For detailed information on administration groups management and actions with unassigned devices:

Page top

[Topic 218473]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Deploying administration plug-ins

To manage mobile devices in Kaspersky Security Center Web Console, the following administration plug-ins must be installed:

If you are using Kaspersky Security Center Cloud Console, you do not need to install the administration plug-ins. You only need to create an account in Kaspersky Security Center Cloud Console. For more information about creating an account, please refer to Kaspersky Security Center Cloud Console Help.

You can use the following methods to install administration plug-ins:

In this section

Installing administration plug-ins from the list of available distribution packages

Installing administration plug-ins from the distribution package

Page top

[Topic 218683]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Installing administration plug-ins from the list of available distribution packages

To install the administration plug-ins:

  1. In the main window of Kaspersky Security Center Web Console, select Console settings > Web plug-ins.
  2. Click the Add button.

    This opens the list of up-to-date versions of Kaspersky applications.

  3. Install the administration plug-ins:
    1. In the list of available applications, click the Mobile devices section to expand it.
    2. Select Kaspersky Security for Mobile (Devices), and then click Install plug-in.
    3. Select Kaspersky Security for Mobile (Policies), and then click Install plug-in.

The distribution packages are downloaded and the plug-ins are installed. When each plug-in is installed and added to Kaspersky Security Center Web Console, a confirmation window is displayed.

Page top

[Topic 218684]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Installing administration plug-ins from the distribution package

You can download the distribution package on the Kaspersky website.

To install the Kaspersky Security for Mobile (Devices) plug-in from the distribution package:

  1. Copy the plugin.zip and signature.txt files from the on_prem_ksm_devices_xx.x.x.x.zip archive of the distribution package to the administrator's workstation.
  2. In the main window of Kaspersky Security Center Web Console, select Console settings > Web plug-ins.
  3. Click Add from file.
  4. In the Add from file window that opens, click Upload ZIP file, and then browse for plugin.zip.
  5. Click Upload signature, and then browse for signature.txt.
  6. Click the Add button.

The Kaspersky Security for Mobile (Devices) plug-in is installed and added to Kaspersky Security Center Web Console.

To install the Kaspersky Security for Mobile (Policies) plug-in from the distribution package:

  1. Copy the plugin.zip and signature.txt files from the on_prem_ksm_policies_xx.x.x.x.zip archive of the distribution package to the administrator's workstation.
  2. In the main window of Kaspersky Security Center Web Console, select Console settings > Web plug-ins.
  3. Click Add from file.
  4. In the Add from file window that opens, click Upload ZIP file, and then browse for plugin.zip.
  5. Click Upload signature, and then browse for signature.txt.
  6. Click the Add button.

The Kaspersky Security for Mobile (Policies) plug-in is installed and added to Kaspersky Security Center Web Console.

You can make sure that the administration plug-ins have been installed by viewing the list of installed plug-ins on the Console settings > Web plug-ins page.

Page top

[Topic 214500]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Deploying the mobile app

To manage mobile devices in Kaspersky Security Center Web Console or Cloud Console, you must deploy the Kaspersky Endpoint Security for Android app or the Kaspersky Security for iOS app on mobile devices. You can deploy apps on mobile devices by using Kaspersky Security Center Web Console or Cloud Console.

In this section

Deploying the mobile app by using Kaspersky Security Center Web Console or Cloud Console

Activating the mobile app

Providing the required permissions for the Kaspersky Endpoint Security for Android app

Page top

[Topic 218255]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Deploying the mobile app by using Kaspersky Security Center Web Console or Cloud Console

The mobile app is deployed on the mobile devices of users whose user accounts have been added to Kaspersky Security Center. For more information about user accounts in Kaspersky Security Center:

You can use the Kaspersky Security for Mobile (Devices) plug-in to install the app from Kaspersky Security Center Web Console and Cloud Console by sending an installation link to a mobile device.

  • On an Android device, the user receives a Google Play link to download the Kaspersky Endpoint Security for Android app. The app can be installed by following the standard installation procedure on the Android platform. After the installation of the app, the user must provide the required permissions.

    Some Huawei and Honor devices do not have Google services and therefore no access to apps in Google Play. If some users of Huawei and Honor devices cannot install the app from Google Play, they should be instructed to install the app from Huawei App Gallery.

  • On an iOS device, the user receives an App Store link to download the Kaspersky Security for iOS app. The app can be installed by following the standard installation procedure on the iOS platform.

    Before connecting an iOS device, send the address of Kaspersky Security Center to the device user to improve connection security. The user will see this address during app installation and can cancel the connection if the displayed address doesn't match the address you sent.

The link contains the following data:

  • Kaspersky Security Center synchronization settings
  • Mobile certificate

To deploy the app on a mobile device:

  1. Start the Mobile Device Connection Wizard:
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices, and then click Add.
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Users & roles > Users. Click the name of the user or the user group to whom you want to send the link for connecting a mobile device, and then select Devices. Click Add mobile device. In this case, skip step 3.

    Proceed through the Wizard by using the Next button.

  2. Select the operating system of the devices that you want to add:
    • Android
    • iOS and iPadOS
  3. Select users and user groups to whom you want to send the link for connecting a mobile device.
  4. Select email addresses where to send the link:
    • All email addresses
    • Main email address
    • Alternative email address
    • Another email address

      If you select this option, specify the email address below.

  5. The link summary is displayed.

    Make sure that all parameters of the link are correct, and then click Send.

  6. A window opens with a confirmation that the link for adding a mobile device has been sent.

    Click OK to finish the Wizard.

When the user installs the Kaspersky Endpoint Security for Android app or the Kaspersky Security for iOS app, the user's device will be displayed on the Devices > Mobile > Devices tab of Web Console or Cloud Console.After installing the app on users' mobile devices, you will be able to configure the settings for devices and apps by using group policies. You will also be able to send commands to mobile devices (for Android only) for data protection in case devices are lost or stolen.

Page top

[Topic 214522]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Activating the mobile app

In Kaspersky Security Center, the license can cover various groups of features. To ensure that the Kaspersky Endpoint Security for Android app and the Kaspersky Security for iOS app are fully functional, the Kaspersky Security Center license purchased by the organization must provide for the Mobile Device Management functionality. The Mobile Device Management functionality is intended for connecting mobile devices to Kaspersky Security Center and managing them.

For detailed information about licensing Kaspersky Security Center and licensing options:

Activating the Kaspersky Endpoint Security for Android app or the Kaspersky Security for iOS app on a mobile device is done by providing valid license information to the app. License information is delivered to the mobile device, together with the policy, when the device is synchronized with Kaspersky Security Center.

If the activation of the mobile app is not completed within 30 days from the time of installation on the mobile device, the app is automatically switched to the limited functionality mode. In this mode, most of the app components are not operational. When switched to the limited functionality mode, the app stops performing automatic synchronization with Kaspersky Security Center. Therefore, if the activation of the app has not been completed within 30 days after the installation, the user must synchronize the device with Kaspersky Security Center manually.

If Kaspersky Security Center is not deployed in your organization or is not accessible to mobile devices, users can activate the mobile app on their devices manually.

To activate the mobile app:

  1. Open the policy properties window:
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Policies & profiles. In the list of group policies that opens, click the name of the policy that you want to configure.
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices. Click the mobile device that falls under the policy that you want to configure, and then select the policy on the Active policies and policy profiles tab.
  2. In the policy properties page, select Application settings > Licenses.
  3. Use the drop-down list to select the required license key from the key storage of the Administration Server.

    The details of the license key are displayed in the fields below.

    If a key file is selected from the Kaspersky Security Center key storage and sent to the device, Kaspersky Security for iOS will be not able to process it, because Kaspersky Security for iOS does not support this activation method. To activate Kaspersky Security for iOS, you must add the license to Kaspersky Security Center as an activation code.

    You can replace the existing activation key on the mobile device if it is different from the one selected in the drop-down list above. To do so, select the If the key on device is different, replace with this key check box.

  4. Click the Save button to save the changes you have made to the policy and exit the policy properties window.

Mobile device settings are configured after the next device synchronization with Kaspersky Security Center.

Page top

[Topic 214532]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Providing the required permissions for the Kaspersky Endpoint Security for Android app

Certain features of the Kaspersky Endpoint Security for Android app require permissions. Kaspersky Endpoint Security for Android asks for mandatory permissions during installation, as well as after installation and prior to using individual features of the app. It is impossible to install Kaspersky Endpoint Security for Android without providing the mandatory permissions.

On certain devices (for example, Huawei, Meizu, and Xiaomi), you must manually add Kaspersky Endpoint Security for Android to the list of apps that are started when the operating system starts, in the device settings. If the app is not added to the list, Kaspersky Endpoint Security for Android stops performing all of its functions after the mobile device is restarted.

On devices running Android 11 or later, you must disable the Remove permissions if app isn't used system setting. Otherwise, after the app is not used for a few months, the system automatically resets the permissions that the user granted to the app.

Permissions requested by the Kaspersky Endpoint Security for Android app

Permission

App function

Phone (for Android 5.0–9.X)

Connect to Kaspersky Security Center (device ID)

Storage (mandatory)

Anti-Virus

Access to manage all files (for Android 11 or later)

Anti-Virus

Nearby Bluetooth devices (for Android 12 or later)

Restrict use of Bluetooth

Notifications (for Android 13)

Notify the user about security issues and app events

Allow running in the background (for Android 12 or later)

Ensure continuous operation of the app. If permission is not granted, the app may be unloaded from memory and unable to restart.

Device administrator (mandatory)

Anti-Theft—lock the device (only for Android 5.0–6.X)

Anti-Theft—take a mugshot with frontal camera

Although taking mugshots is not supported in Kaspersky Security Center Web Console and Cloud Console, the Kaspersky Endpoint Security for Android app requires this permission so that it can be managed by all Kaspersky Security Center consoles.

Anti-Theft—sound an alarm

Anti-Theft—full reset

Password protection

App removal protection

Install security certificate

App Control

Restrict use of the camera, Bluetooth, and Wi-Fi

Camera

Anti-Theft—take a mugshot with frontal camera

Although taking mugshots is not supported in Kaspersky Security Center Web Console and Cloud Console, the Kaspersky Endpoint Security for Android app requires this permission so that it can be managed by all Kaspersky Security Center consoles.

On devices running Android 11.0 or later, the user must grant the "While using the app" permission when prompted.

Location

Anti-Theft—locate device

On devices running Android 10.0 or later, the user must grant the "All the time" permission when prompted.

Accessibility

 

Anti-Theft—lock the device (only for Android 7.0 or later)

Web Protection

App Control

App removal protection (only for Android 7.0 or later)

Display of warnings of Kaspersky Endpoint Security for Android (only for Android 10.0 or later)

Restrict use of the camera (only for Android 11 or later)

Display pop-up window (for some Xiaomi devices)

Web Protection

Display pop-up windows while running in the background (for some Xiaomi devices)

Web Protection

Page top

[Topic 214957]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Managing certificates

Mobile certificates are used for the purpose of identifying the users of mobile devices on the Administration Server.

Kaspersky Security Center Web Console and Cloud Console allow you to perform the following actions with user mobile certificates:

  • View the certificates and their statuses.
  • Create new certificates.
  • Renew the expiring certificates.
  • Delete certificates.

For more information on Kaspersky Security Center certificates:

Page top

[Topic 218601]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Viewing the list of certificates

Kaspersky Security Center Web Console and Cloud Console allow you to view the applied user mobile certificates, their statuses, and properties.

To view the list of applied user mobile certificates:

  1. In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices.
  2. Select Manage certificates.

The Mobile certificates page opens with information about the applied user mobile certificates. You can view details of a certificate by clicking it in the User name column.

Page top

[Topic 218624]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Defining certificate settings

You can use Kaspersky Security Center Web Console or Cloud Console to configure the lifetime, automatic updates, and password protection of mobile certificates.

To define mobile certificate settings:

  1. In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices.
  2. Select Manage certificates.
  3. Select Certificate settings.
  4. In the Generate mobile certificates window that opens, you can configure the following:
    • Certificate validity period (days)

      Certificate lifetime period in days. The default lifetime of a certificate is 365 days. When this period expires, the mobile device will not be able to connect to the Administration Server.

    • Reissue when certificate will expire in (days)

      The number of days remaining until the current certificate's expiration during which Administration Server should issue a new certificate. For example, if the value of the field is 4, Administration Server issues a new certificate four days before the current certificate expires. The default value is 1.

    • Reissue certificate automatically if possible

      If possible, certificates will be reissued automatically. If this option is disabled, certificates must be reissued manually as they expire. By default, this option is disabled.

    • Prompt for password during certificate installation

      The user will be prompted for a password when the certificate is installed on a mobile device. The password is used only once—during installation of the certificate on the mobile device. The password will be automatically generated by the Administration Server and sent to the user by email. You can specify the password length in the Password length field.

  5. Click Save to apply the changes and close the window.

The specified settings will be used by Kaspersky Security Center for creating, updating, and protecting mobile certificates.

Page top

[Topic 218257]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Creating a certificate

You can create mobile certificates in Kaspersky Security Center Web Console and Cloud Console for the purpose of identifying the users of mobile devices.

To create a mobile certificate:

  1. In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices.
  2. Select Manage certificates.
  3. In the Mobile certificates window that opens, click Add to start Mobile Certificate Creation Wizard. Proceed through the Wizard by using the Next button.
  4. Select users or user groups whose mobile devices you want to manage with a new certificate.
  5. Specify the Publication parameters:
    • If you want to notify the users about the new certificate, select the Notify user about the new certificate check box.
    • If you want to allow using one certificate multiple times on the same device, select the Allow using one certificate multiple times on the same device (only for devices with Kaspersky Endpoint Security for Android installed) check box.
  6. Select the Authentication type:
    • Select Credentials (domain login or user name) if you want users to access the certificate by using their credentials.
    • Select One-time password if you want users to access the certificate by using a one-time password.

      This option is available if you did not select the Allow using one certificate multiple times on the same device (only for devices with Kaspersky Endpoint Security for Android installed) check box in the previous step.

    • Select Password if you want users to access the certificate by using a password.

      This option is available if you selected the Allow using one certificate multiple times on the same device (only for devices with Kaspersky Endpoint Security for Android installed) check box in the previous step.

  7. Specify the method of certificate delivery in the Certificate delivery field:
    • If you have selected One-time password in the previous step, select one of the following options:
      • If you want to send the password by email, select Notify user by email.

        Then select which email address to use or select Another email address to specify another email address.

      • If you want to notify users about the password by other means, select Show the password after finishing the Wizard.
    • If you have selected Credentials (domain login or user name) in the previous step, select which email address to use or select Another email address to specify another email address.
  8. The certificate summary is displayed.

    Make sure that all parameters are correct, and then click Create.

As a result, Mobile Certificate Creation Wizard creates a certificate that users can install on their mobile devices. The certificate becomes available after the next synchronization of mobile devices with Kaspersky Security Center.

For more information about creating certificates and configuring rules for issuing them:

Page top

[Topic 218603]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Renewing a certificate

If any of the applied mobile certificates is about to expire, you can renew it by using Kaspersky Security Center Web Console or Cloud Console.

To renew a mobile certificate:

  1. In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices.
  2. Select Manage certificates.
  3. Select the certificate that you want to renew, and then click Reissue.

The status of the certificate changes to The certificate has been reissued.

Page top

[Topic 218604]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Deleting a certificate

You can delete mobile certificates by using Kaspersky Security Center Web Console or Cloud Console.

If you delete a mobile certificate, the device can no longer synchronize with the Administration Server and cannot be managed by means of Kaspersky Security Center. To start managing the mobile device again, you will need to reinstall the Kaspersky Endpoint Security for Android app on it.

To delete a mobile certificate:

  1. In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices.
  2. Select Manage certificates.
  3. Select the certificate that you want to delete, and then click Delete.

The certificate is deleted and removed from the list of certificates.

Page top

[Topic 216467]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Exchanging information with Firebase Cloud Messaging

Kaspersky Endpoint Security for Android uses the Firebase Cloud Messaging (FCM) service to ensure timely delivery of commands to mobile devices and forced synchronization when policy settings are changed.

To use the Firebase Cloud Messaging service, you must define the service settings in Kaspersky Security Center Web Console or Cloud Console.

To enable Firebase Cloud Messaging in Kaspersky Security Center Web Console or Cloud Console:

  1. In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Android devices synchronization.

    The Android devices synchronization window opens.

  2. In the Sender ID and Server key fields, specify the Firebase Cloud Messaging settings: SENDER_ID and API Key.

Firebase Cloud Messaging is enabled.

To obtain a Sender ID and the Server key:

  1. Register on Google portal.
  2. Go to Google Cloud Platform.
  3. Create a new project.

    Wait for the project to be created.

  4. Find the relevant SENDER_ID of the project.
  5. Enable Google Firebase Cloud Messaging for Android.
  6. Follow the onscreen instructions to create credentials.
  7. Retrieve the API Key from the properties of the newly created credentials.

For detailed information about operations in Google Cloud Platform, please refer to its documentation.

You now have a Sender ID and a Server key to configure the Firebase Cloud Messaging settings.

If the Firebase Cloud Messaging settings are not defined, commands on the mobile device and policy settings will be delivered when the device is synchronized with Kaspersky Security Center, according to the schedule set in the policy (for example, every 24 hours). In other words, commands and policy settings will be delivered with a delay.

For the purposes of supporting the main functionality of the product, you agree to automatically provide the Firebase Cloud Messaging service with the unique ID of the app installation (Instance ID), and the following data:

  • Information about the installed software: app version, app ID, app build version, app package name.
  • Information about the computer on which the software is installed: OS version, device ID, version of Google services.
  • Information about FCM: app ID in FCM, FCM user ID, protocol version.

Data is transmitted to Firebase services over a secure connection. Access to and protection of information is regulated by the relevant terms of use of the Firebase services: Firebase Data Processing and Security Terms, Privacy and Security in Firebase.

To prevent the exchange of information with the Firebase Cloud Messaging service:

  1. In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Android devices synchronization.

    The Android devices synchronization window opens.

  2. Click Reset.
  3. In the window that opens, click the OK button to confirm resetting.

The Firebase Cloud Messaging settings are cleared.

Page top

[Topic 214977]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Managing mobile devices in Kaspersky Security Center Web Console and Cloud Console

You can manage mobile devices in Kaspersky Security Center Web Console and Cloud Console by using group policies and by sending commands to mobile devices (for Android only).

To manage mobile devices in Kaspersky Security Center Web Console, you must install administration plug-ins.

In this section

Connecting mobile devices to Kaspersky Security Center

Moving unassigned mobile devices to administration groups

Sending commands to mobile devices

Removing mobile devices from Kaspersky Security Center

Page top

[Topic 214537]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Connecting mobile devices to Kaspersky Security Center

To manage a mobile device by using Kaspersky Security Center Web Console or Cloud Console, the device must be connected to Kaspersky Security Center. You can view the list of mobile devices connected to Kaspersky Security Center on the Devices > Mobile > Devices tab of Web Console or Cloud Console.

Before connecting an iOS device, send the address of Kaspersky Security Center to the device user to improve connection security. The user will see this address during app installation and can cancel the connection if the displayed address doesn't match the address you sent.

To connect a mobile device to Kaspersky Security Center:

  1. Start the Mobile Device Connection Wizard:
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices, and then click Add.
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Users & roles > Users. Click the name of the user or the user group to whom you want to send the link for connecting a mobile device, and then select Devices. Click Add mobile device. In this case, skip step 3.

    Proceed through the Wizard by using the Next button.

  2. Select the operating system of the devices that you want to add:
    • Android
    • iOS and iPadOS
  3. Select users and user groups to whom you want to send the link for connecting a mobile device.
  4. Select email addresses where to send the link:
    • All email addresses
    • Main email address
    • Alternative email address
    • Another email address

      If you select this option, specify the email address below.

  5. The link summary is displayed.

    Make sure that all parameters of the link are correct, and then click Send.

  6. A window opens with a confirmation that the link for adding a mobile device has been sent.

    Click OK to finish the Wizard.

When the user installs the Kaspersky Endpoint Security for Android app or the Kaspersky Security for iOS app, the user's device will be displayed on the Devices > Mobile > Devices tab of Web Console or Cloud Console.

Page top

[Topic 218459]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Moving unassigned mobile devices to administration groups

When the Kaspersky Endpoint Security for Android app or the Kaspersky Security for iOS app is installed on mobile devices, they are displayed on the Discovery & deployment > Unassigned devices page of Kaspersky Security Center Web Console or Cloud Console. In order to manage newly connected devices, you can create a rule for their automatic allocating to administration groups or move them to an administration group manually.

To move an unassigned mobile device to an administration group:

  1. In the main window of Kaspersky Security Center Web Console or Cloud Console, select Discovery & deployment > Unassigned devices.
  2. Select the device that you want to move to an administration group, and then click Move to group.
  3. In the tree of administration groups that opens, select the target group to which you want to move the device.

    You can create a new administration group by selecting an existing group, and then clicking Add child group.

  4. Click Move.

The device is moved to the specified administration group and the group policy is applied to it.

Page top

[Topic 214964]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Sending commands to mobile devices

You can send commands to Android mobile devices to protect data on a mobile device that is lost or stolen, or to perform forced synchronization of a mobile device with Kaspersky Security Center.

You can't send commands to iOS devices.

The following commands are supported:

  • Lock device

    The mobile device is locked.

  • Unlock device

    The mobile device is unlocked. After unlocking the mobile device running Android 5.0 – 6.Х, the screen unlock password is reset to "1234". After unlocking a device running Android 7.0 or later, the screen unlock password is not changed.

  • Reset to factory settings

    All data is deleted from the mobile device and the settings are rolled back to their default values.

  • Wipe corporate data

    Containerized data and the corporate email account are wiped from the mobile device.

  • Locate device

    Device is located and shown on Google Maps. The mobile service provider may charge a fee for internet access.

    On devices running Android 12 or later, if the user granted the "Use approximate location" permission, the Kaspersky Endpoint Security for Android app first tries to get the precise device location. If this is not successful, the approximate device location is returned only if it was received not more than 30 minutes earlier. Otherwise, the Locate device command fails.

  • Sound alarm

    The mobile device sounds an alarm. The alarm sounds for 5 minutes (or for 1 minute if the device battery is low).

  • Synchronize device

    The mobile device is synchronized with Kaspersky Security Center.

Kaspersky Endpoint Security for Android app requires specific permissions for the execution of commands. When the Initial Configuration Wizard is running, Kaspersky Endpoint Security for Android prompts the user to grant the application all required permissions. The user can skip these steps or disable these permissions in the device settings at a later time. If this is the case, it will be impossible to execute commands.

On devices running Android 10.0 or later, the user must grant the "All the time" permission to access the location. On devices running Android 11.0 or later, the user must also grant the "While using the app" permission to access the camera. Otherwise, anti-theft commands will not function. The user will be notified of this limitation and will again be prompted to grant the required level of permissions. If the user selects the "Only this time" option for the camera permission, access is considered granted by the app. It is recommended to contact the user directly if the camera permission is requested again.

To send a command to a mobile device:

  1. In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices.
  2. Select the device to which you want to send the command, and then click either Control or Manage.
  3. Select the required command in the Available commands list, and then click OK.
  4. Click OK if you are prompted to confirm the operation.

The specified command is sent to the mobile device and the confirmation window is displayed.

Page top

[Topic 219533]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Removing mobile devices from Kaspersky Security Center

If you do not need to manage a mobile device any longer, you can remove it from Kaspersky Security Center by using Web Console or Cloud Console.

To remove a mobile device from Kaspersky Security Center:

  1. Remove the mobile app from the device or make sure that the user has removed the app from the required device.
  2. In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices.
  3. Select the mobile device that you want to remove, and then click Delete.
  4. Click OK to confirm the operation.

The device is removed from Kaspersky Security Center.

Page top

[Topic 214501]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Managing group policies

This section describes how to manage group policies in Kaspersky Security Center Web Console and Cloud Console.

In this section

Group policies for managing mobile devices

Viewing the list of group policies

Viewing the policy distribution results

Creating a group policy

Modifying a group policy

Copying a group policy

Moving a policy to another administration group

Deleting a group policy

Page top

[Topic 214502]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Group policies for managing mobile devices

A group policy is a package of settings for managing mobile devices that belong to an administration group and for managing mobile apps installed on the devices.

You can use a policy to configure settings of both individual devices and a group of devices. For a group of devices, administration settings can be configured in the window of group policy properties.

Each parameter represented in a policy has a "lock" attribute, which shows whether the setting is allowed for modification in the policies of nested hierarchy levels (for nested groups and secondary Administration Servers), in local application settings.

The values of settings configured in the policy and in local application settings are saved on the Administration Server, distributed to mobile devices during synchronization, and saved to devices as current settings. If the user has specified other values of settings that have not been "locked", during the next synchronization of the device with the Administration Server the new values of settings are relayed to the Administration Server and saved in the local settings of the application instead of the values that had been previously specified by the administrator.

To keep corporate security of Android mobile devices up to date, you can monitor users' devices for compliance with corporate security requirements.

For more details on managing policies and administration groups in Kaspersky Security Center Web Console and Cloud Console:

Page top

[Topic 219575]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Viewing the list of group policies

Kaspersky Security Center Web Console and Cloud Console allow you to view the group policies, their statuses, and properties.

To view the list of group policies,

In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Policies & profiles.

The list of group policies opens with brief information about the group policies. On this page, you can create, modify, copy, move, and delete group policies.

Page top

[Topic 219617]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Viewing the policy distribution results

Kaspersky Security Center Web Console and Cloud Console allow you to view the distribution chart of a group policy and information about all devices that fall under that policy.

To view the distribution results of a group policy:

  1. In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Policies & profiles.
  2. In the list of group policies that opens, select the check box next to the name of the policy for which you want to view the distribution results, and then click Distribution.

The policy distribution results page opens. This page contains the policy summary, the policy distribution chart, and the table with information about all devices that fall under that policy. You can open the policy properties window by clicking the Configure policy button.

Page top

[Topic 216828]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Creating a group policy

Kaspersky Security Center Web Console and Cloud Console allow you to create group policies for the purpose of managing mobile devices.

To create a group policy:

  1. In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Policies & profiles.
  2. In the list of Kaspersky Security Center group policies that opens, click Current path to select the administration group for which you want to create a policy.

    By default, the new group policy is applied to the Managed devices group.

  3. Click Add to start the Policy Creation Wizard. Proceed through the Wizard by using the Next button.
  4. Select Kaspersky Security for Mobile (Policies).
  5. Type the name for the new policy in the Name field. If you specify the name of an existing policy, it will have (1) added at the end automatically.
  6. Select the policy status:
    • Active

      The Wizard saves the created policy on the Administration Server. At the next synchronization of the mobile device with the Administration Server, the policy will be used on the device as the active policy.

    • Inactive

      The Wizard saves the created policy on the Administration Server as a backup policy. This policy can be activated in the future after a specific event. If necessary, an inactive policy can be switched to active state.

      Several policies can be created for one application in the group, but only one of them can be active. When a new active policy is created, the previous active policy automatically becomes inactive.

  7. You can enable or disable two options of inheritance, Inherit settings from parent policy and Force inheritance of settings in child policies:
    • If you enable Inherit settings from parent policy for a child administration group and lock some settings in the parent policy, then you cannot change these settings in the policy for the child group. You can, however, change the settings that are not locked in the parent policy.
    • If you disable Inherit settings from parent policy for a child administration group, then you can change all the settings in the child group, even if some settings are locked in the parent policy.
    • If you enable Force inheritance of settings in child policies in the parent administration 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 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.
    • In the policies for the Managed devices group, the Inherit settings from parent policy option does not affect any settings, because the Managed devices group does not have any upstream groups and therefore does not inherit any policies.

    By default, the Inherit settings from parent policy option is enabled and the Force inheritance of settings in child policies option is disabled.

  8. If you want, you can define the settings of the newly created policy. To do so, select the Application settings tab, and then proceed as described in the "Defining policy settings" section.

    Alternatively, you can do that later.

  9. Click Save to create the policy.

A new group policy for managing mobile devices is created.

Page top

[Topic 216829]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Modifying a group policy

Kaspersky Security Center Web Console and Cloud Console allow you to modify the settings of group policies.

To modify a group policy:

  1. Open the policy properties window:
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Policies & profiles. In the list of group policies that opens, click the name of the policy that you want to configure.
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices. Click the mobile device that falls under the policy that you want to configure, and then select the policy on the Active policies and policy profiles tab.
  2. In the policy properties window, select Application settings, and then define the policy settings as described in the "Defining policy settings" section.

    You can also configure general settings, settings inheritance, events logging and notifications, policy profiles, and view revision history. For more information, please refer to Kaspersky Security Center Help.

  3. Click the Save button to save the changes you have made to the policy and exit the policy properties window.

Mobile device settings are configured after the next device synchronization with Kaspersky Security Center.

Page top

[Topic 219624]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Copying a group policy

Kaspersky Security Center Web Console and Cloud Console allow you to create a copy of a group policy.

To create a copy of a group policy:

  1. In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Policies & profiles.
  2. In the list of group policies that opens, select the check box next to the name of the policy for which you want to create a copy, and then click Copy.
  3. In the tree of administration groups that opens, select the target group in which you want to create a copy of the policy.

    You can create a new administration group by selecting an existing group, and then clicking Add child group.

  4. Click Copy.
  5. Click OK to confirm the operation.

A copy of the policy will be created in the target group under the same name. The status of each copied or moved policy in the target group will be Inactive. You can change the status to Active at any time.

If a policy with a name identical to that of the newly created or moved policy already exists in the target group, the (<next sequence number>) index is added to the name of the newly created or moved policy, for example: (1).

Page top

[Topic 219627]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Moving a policy to another administration group

Kaspersky Security Center Web Console and Cloud Console allow you to move a policy to another administration group.

To move a policy to another administration group:

  1. In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Policies & profiles.
  2. In the list of group policies that opens, select the check box next to the name of the policy that you want to move to another administration group, and then click Move.
  3. In the tree of administration groups that opens, select the target group to which you want to move the policy.

    You can create a new administration group by selecting an existing group, and then clicking Add child group.

  4. Click Move.
  5. Click OK to confirm the operation.

The result depends on the policy inheritance properties:

  • If the policy is not inherited in the source group, it will be moved to the target group.
  • If the policy is inherited in the source group, it will not be moved. Instead, a copy of this policy will be created in the target group.

The status of each copied or moved policy in the target group will be Inactive. You can change the status to Active at any time.

If a policy with a name identical to that of the newly created or moved policy already exists in the target group, the (<next sequence number>) index is added to the name of the newly created or moved policy, for example: (1).

Page top

[Topic 219613]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Deleting a group policy

Kaspersky Security Center Web Console and Cloud Console allow you to delete group policies.

You can delete only a policy that is not inherited in the current 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 group policy:

  1. In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Policies & profiles.
  2. In the list of group policies that opens, select the check box next to the name of the policy that you want to delete, and then click Delete.
  3. Click OK to confirm the operation.

The group policy will be deleted.

Page top

[Topic 214480]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring anti-virus protection

You can define these policy settings only for Android devices.

For the timely detection of threats, viruses, and other malicious applications, you should configure real-time protection and autorun of virus scans.

Kaspersky Endpoint Security for Android detects the following types of objects:

  • Viruses, worms, Trojans, and malicious tools
  • Adware
  • Apps that can be exploited by criminals to harm your device or personal data

Due to technical limitations, Kaspersky Endpoint Security for Android cannot scan files with a size of 2 GB or more. During a scan, the app skips large files and does not notify you that such files were skipped.

In this section

Configuring real-time protection

Configuring autorun of virus scans on a mobile device

Configuring anti-virus database updates

Page top

[Topic 216851]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring real-time protection

You can define these policy settings only for Android devices.

To configure real-time protection:

  1. Open the policy properties window:
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Policies & profiles. In the list of group policies that opens, click the name of the policy that you want to configure.
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices. Click the mobile device that falls under the policy that you want to configure, and then select the policy on the Active policies and policy profiles tab.
  2. In the policy properties window, select Application settings > Essential protection.
  3. In the Anti-Virus section, configure the mobile device file system protection:
    • To enable real-time protection of the mobile device against threats, select the Enable real-time anti-virus protection check box.
    • Specify the level of protection:
      • If you want Kaspersky Endpoint Security for Android to scan only new apps and files from the Downloads folder, select Scan only new apps.
      • To enable extended protection of the mobile device against threats, select Scan all apps and monitor actions with files.

        Kaspersky Endpoint Security for Android will scan all files that the user opens, modifies, moves, copies, installs, or saves on the device, as well as newly installed mobile apps.

        On devices running Android 8.0 or later, Kaspersky Endpoint Security for Android scans files that the user modifies, moves, installs, and saves, as well as copies of files. Kaspersky Endpoint Security for Android does not scan files when they are opened, or source files when they are copied.

    • To enable additional scanning of new apps before they are started for the first time on the user's device by using the Kaspersky Security Network cloud service, select the Additional protection by Kaspersky Security Network check box.
    • To block adware and apps that can be exploited by criminals to harm the device or user data, select the Detect adware, autodialers, and apps that may be used by cybercriminals to cause harm to the user's device and data check box.
  4. In the Anti-Virus settings section, select the action to be performed on threat detection:
    • Delete and save a backup copy of file in quarantine

      Detected objects will be automatically deleted. The user is not required to take any additional actions. Prior to deleting an object, Kaspersky Endpoint Security for Android will create a backup copy of file and save it in quarantine.

    • Delete

      Detected objects will be automatically deleted. The user is not required to take any additional actions. Prior to deleting an object, Kaspersky Endpoint Security for Android will display a temporary notification about the detection of the object.

    • Skip

      If the detected objects have been skipped, Kaspersky Endpoint Security for Android warns the user about problems in device protection. For each skipped threat, the app provides actions that the user can perform to eliminate the threat. The list of skipped objects may change, for example, if a malicious file was deleted or moved. To receive an up-to-date list of threats, run a full device scan. To ensure reliable protection of your data, eliminate all detected objects.

  5. Click the Save button to save the changes you have made to the policy and exit the policy properties window.

Mobile device settings are configured after the next device synchronization with Kaspersky Security Center.

Page top

[Topic 216852]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring autorun of virus scans on a mobile device

You can define these policy settings only for Android devices.

To configure autorun of virus scans on a mobile device:

  1. Open the policy properties window:
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Policies & profiles. In the list of group policies that opens, click the name of the policy that you want to configure.
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices. Click the mobile device that falls under the policy that you want to configure, and then select the policy on the Active policies and policy profiles tab.
  2. In the policy properties window, select Application settings > Essential protection.
  3. To block adware and apps that can be exploited by criminals to harm the device or user data, select the Detect adware, autodialers, and apps that may be used by cybercriminals to cause harm to the user's device and data checkbox in the Device scan section.
  4. In the Action on threat detection list, select one of the following options:
    • Delete and save a backup copy of file in quarantine

      Detected objects will be automatically deleted. The user is not required to take any additional actions. Prior to deleting an object, Kaspersky Endpoint Security for Android will create a backup copy of file and save it in quarantine.

    • Delete

      Detected objects will be automatically deleted. The user is not required to take any additional actions. Prior to deleting an object, Kaspersky Endpoint Security for Android will display a temporary notification about the detection of the object.

    • Skip

      If the detected objects have been skipped, Kaspersky Endpoint Security for Android warns the user about problems in device protection. For each skipped threat, the app provides actions that the user can perform to eliminate the threat. The list of skipped objects may change, for example, if a malicious file was deleted or moved. To receive an up-to-date list of threats, run a full device scan. To ensure reliable protection of your data, eliminate all detected objects.

    • Ask user

      The Kaspersky Endpoint Security for Android app displays a notification prompting the user to choose the action to take on the detected object: Skip or Delete.

      When the app detects several objects, the Ask user option allows the device user to apply a selected action to each file by using the Apply to all threats check box.

      Kaspersky Endpoint Security for Android must be set as an Accessibility feature to ensure the display of notifications on mobile devices running Android 10.0 or later. Kaspersky Endpoint Security for Android prompts the user to set the app as an Accessibility feature through the Initial Configuration Wizard. The user can skip this step or disable this service in the device settings at a later time. In this case, Kaspersky Endpoint Security for Android displays an Android system window prompting the user to choose the action to take on the detected object: Skip or Delete. To apply an action to multiple objects, you need to open Kaspersky Endpoint Security.

  5. In the Scheduled scan section, you can configure the automatic full scan of the device file system.

    Select one of the following options:

    • Disabled

      The scan of the device file system will not be launched automatically.

    • After database update

      The device file system will be scanned automatically on each anti-virus database update.

    • Daily

      The device file system will be scanned automatically every day.

      If you select this option, you can also specify the time of the scan in the Start time field.

    • Weekly on

      The device file system will be scanned automatically once a week.

      If you select this option, you can also select the day of the week when you want to run the scan, by using the drop-down list and specify the time of the scan in the Start time field.

    On Android 12 or later, the app may perform this task later than specified if the device is in battery saver mode.

  6. Click the Save button to save the changes you have made to the policy and exit the policy properties window.

Mobile device settings are configured after the next device synchronization with Kaspersky Security Center.

Page top

[Topic 216853]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring anti-virus database updates

You can define these policy settings only for Android devices.

To configure anti-virus database updates:

  1. Open the policy properties window:
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Policies & profiles. In the list of group policies that opens, click the name of the policy that you want to configure.
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices. Click the mobile device that falls under the policy that you want to configure, and then select the policy on the Active policies and policy profiles tab.
  2. In the policy properties window, select Application settings > Database update.
  3. In the Database update section, configure the schedule of automatic database updates on the user's device.

    Select one of the following options:

    • Disabled

      Automatic updates of anti-virus databases will be disabled.

    • Daily

      Anti-virus databases will be updated every day.

      If you select this option, you can also specify the time of update in the Update time field.

    • Weekly

      Anti-virus databases will be updated once a week.

      If you select this option, you can also specify the time of update in the Update time field and the day of the week when you want to run update in the Day of the week drop-down list.

    On Android 12 or later, the app may perform this task later than specified if the device is in battery saver mode.

  4. In the Database update source section, specify the update source from which Kaspersky Endpoint Security for Android receives and installs anti-virus database updates:
    • Kaspersky servers

      Kaspersky Endpoint Security for Android will use a Kaspersky update server as an update source for downloading anti-virus databases to the user's device.

    • Administration Server

      Available only if you use Kaspersky Security Center Web Console.

      Kaspersky Endpoint Security for Android will use the repository of Kaspersky Security Center Administration Server as an update source for downloading anti-virus databases to the user's device.

    • Other source

      Kaspersky Endpoint Security for Android will use a third-party server as an update source for downloading anti-virus databases to the user's device.

      If you select this option, you must specify the address of an HTTP server in the Use another server as an update source for anti-virus databases field.

  5. If you want Kaspersky Endpoint Security for Android to download anti-virus database updates according to the update schedule when the user's device is roaming, select the Allow database update while roaming check box in the Update anti-virus databases while roaming section.
  6. Click the Save button to save the changes you have made to the policy and exit the policy properties window.

Mobile device settings are configured after the next device synchronization with Kaspersky Security Center.

Updates functionality (including providing anti-virus signature updates and codebase updates), as well as KSN functionality will not be available in the software in the U.S. territory from 12:00 AM Eastern Daylight Time (EDT) on September 10, 2024 in accordance with the restrictive measures.

Page top

[Topic 215298]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Defining device unlock settings

You can define these policy settings only for Android devices.

To keep a mobile device secure, you need to configure the use of a password for which the user is prompted when the device comes out of sleep mode.

You can impose restrictions on the user's activity on the device if the unlock password is weak (for example, lock the device). You can impose restrictions by using the Compliance Control component.

On certain Samsung devices running Android 7.0 or later, when the user attempts to configure unsupported methods for unlocking the device (for example, a graphical password), the device may be locked if the following conditions are met: Kaspersky Endpoint Security for Android removal protection is enabled and screen unlock password strength requirements are set. To unlock the device, you must send a special command to the device.

To configure device unlock password strength:

  1. Open the policy properties window:
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Policies & profiles. In the list of group policies that opens, click the name of the policy that you want to configure.
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices. Click the mobile device that falls under the policy that you want to configure, and then select the policy on the Active policies and policy profiles tab.
  2. In the policy properties window, select Application settings > Essential protection.
  3. If you want the app to check whether an unlock password has been set, select the Require to set screen unlock password in the Password protection section.

    If the application detects that no system password has been set on the device, it prompts the user to set it. The password is set according to the parameters defined by the administrator.

  4. Specify the minimum number of characters in the user password.

    Possible values: 4 to 16 characters.

    The user's password is 4 characters long by default.

    On devices running Android 10.0 or later, Kaspersky Endpoint Security resolves the password strength requirements into one of the system values: medium or high.

    The values for devices running Android 10.0 or later are determined by the following rules:

    • If the password length required is 1 to 4 symbols, then the app prompts the user to set a medium-strength password. It must be either numeric (PIN) with no repeating or ordered (e.g. 1234) sequences, or alphanumeric. The PIN or password must be at least 4 characters long.
    • If the password length required is 5 or more symbols, then the app prompts the user to set a high-strength password. It must be either numeric (PIN) with no repeating or ordered sequences, or alphanumeric (password). The PIN must be at least 8 digits long; the password must be at least 6 characters long.
  5. If you want the user to have the capability to use fingerprints to unlock the screen, select the Allow use of fingerprints (for devices running Android 9 or earlier) check box. If the unlock password is not compliant with corporate security requirements, you cannot use a fingerprint scanner to unlock the screen.

    On devices running Android 10.0 or later, the use of a fingerprint to unlock the screen is not supported.

    Kaspersky Endpoint Security for Android does not restrict the use of a fingerprint scanner for signing in to apps or confirming purchases.

    On certain Samsung devices, it is impossible to block the use of fingerprints for unlocking the screen.

    On certain Samsung devices, if the unlock password does not comply with corporate security requirements, Kaspersky Endpoint Security for Android does not block the use of fingerprints for unlocking the screen.

    After adding a fingerprint in the device settings, the user can unlock the screen by using the following methods:

    • Press the finger to the fingerprint scanner (main method).
    • Enter the unlock password (backup method).
  6. Click the Save button to save the changes you have made to the policy and exit the policy properties window.

Mobile device settings are configured after the next device synchronization with Kaspersky Security Center.

Page top

[Topic 214549]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring protection of stolen or lost device data

You can define these policy settings only for Android devices.

To protect corporate data in case a mobile device is lost or stolen, you must configure the unauthorized access protection.

To ensure protection of stolen or lost device data, Kaspersky Endpoint Security for Android must be set as an Accessibility feature. Kaspersky Endpoint Security for Android prompts the user to set the app as an Accessibility feature through the Initial Configuration Wizard. The user can skip this step or disable this service in the device settings at a later time.

To configure protection of stolen or lost device data:

  1. Open the policy properties window:
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Policies & profiles. In the list of group policies that opens, click the name of the policy that you want to configure.
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices. Click the mobile device that falls under the policy that you want to configure, and then select the policy on the Active policies and policy profiles tab.
  2. In the policy properties window, select Application settings > Essential protection.
  3. In the Anti-Theft section, configure device locking:
    • Specify the number of characters in the unlock code.
    • Specify the text to be displayed when the device is locked.
  4. Click the Save button to save the changes you have made to the policy and exit the policy properties window.

Mobile device settings are configured after the next device synchronization with Kaspersky Security Center.

Page top

[Topic 214553]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring app control

You can define these policy settings only for Android devices.

App Control checks that the apps installed on a mobile device are compliant with corporate security requirements. In Kaspersky Security Center, the administrator creates lists of allowed, blocked, mandatory, and recommended apps according to the corporate security requirements. As a result of App Control, Kaspersky Endpoint Security prompts the user to install mandatory and recommended apps, and to remove blocked apps. It is impossible to start blocked apps on the user's mobile device.

In Kaspersky Security Center Web Console and Cloud Console, you can manage apps on users' devices by applying pre-defined rules. You can configure two types of App Control rules: application rules and category rules.

An App rule is applied to a specific app, while a Category rule is applied to any app that belongs to a pre-defined category. App categories are specified by Kaspersky experts.

To configure App Control:

  1. Open the policy properties window:
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Policies & profiles. In the list of group policies that opens, click the name of the policy that you want to configure.
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices. Click the mobile device that falls under the policy that you want to configure, and then select the policy on the Active policies and policy profiles tab.
  2. In the policy properties page, select Application settings > Security controls.
  3. In the table under the App Control section, add rules that will define what apps will be controlled.
    • To add a rule for a specific app:
      1. In the table, click App rule.
      2. In the App rule window that opens, choose the action that will be performed with the apps covered by the created rule.
      3. Specify the app that will be subject to the rule by filling in Link to installation package (for example, https://play.google.com/store/apps/details?id=com.kaspersky.kes), Package name (for example, katana.facebook.com), and App name.
      4. Click Save.

      The rule is added to the list of App Control rules.

    • To add a rule for a category of apps:
      1. In the table under the App Control section, click Category rule.
      2. In the Category rule window that opens, select the app category from the drop-down list.

        Apps within the selected category will be subject to the created rule.

      3. In the Operation mode section, select the action that will be performed when any apps within the selected category attempt to start up: Forbidden apps or Allowed apps.
      4. Fill in the Additional comment shown on the user's device when an app of a specified category is detected, if necessary.
      5. Click Save.

      The rule is added to the list of App Control rules.

  4. In the Actions with forbidden apps section, choose what action is performed for forbidden applications:
    • If you want Kaspersky Endpoint Security for Android to block the startup of forbidden applications on the user's mobile device, select Block apps from launching.
    • If you want Kaspersky Endpoint Security for Android to send data on forbidden apps to the event log without blocking them, select Do not block forbidden apps, report only.
  5. In the Operation mode section, choose whether the rules you add will define allowed apps or forbidden apps:
    • If you want the rules to define which apps are allowed, select Forbidden apps.

      If you want Kaspersky Endpoint Security for Android to block the startup of system apps on the user's mobile device (such as Calendar, Camera, and Settings) in the Forbidden apps mode, select the Block system apps check box.

      Kaspersky experts recommend against blocking system apps because this could lead to failures in device operation.

    • If you want the rules to define which apps are forbidden, select Allowed apps.
  6. To receive information about all apps installed on mobile devices, in the Application report section, select the Send a list of installed apps on all mobile devices check box.

    Kaspersky Endpoint Security for Android sends data to the event log each time an app is installed or removed from the device.

  7. Click the Save button to save the changes you have made to the policy and exit the policy properties window.

Mobile device settings are configured after the next device synchronization with Kaspersky Security Center.

Page top

[Topic 214554]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring compliance control of mobile devices with corporate security requirements

You can define these policy settings only for Android devices.

Compliance control allows you to monitor Android devices for compliance with corporate security requirements and take actions in case of non-compliance. Corporate security requirements regulate how the user can work with the device. For example, real-time protection must be enabled on the device, anti-virus databases must be up-to-date, and the device password must be sufficiently strong. Compliance control is based on a list of rules. A compliance rule includes the following components:

  • Device non-compliance criterion.
  • Action that will be taken on a device if the user does not fix the non-compliance within the set time period.
  • Time period allocated for the user to fix the non-compliance (for example, 24 hours).

    When the specified time period is over, the selected action will be taken on the user's device.

    On Android 12 or later, the app may perform this task later than specified if the device is in battery saver mode.

To configure compliance control, you can perform the following actions:

In this section

Enabling and disabling compliance rules

Editing compliance rules

Adding compliance rules

Deleting compliance rules

List of non-compliance criteria

List of actions in case of non-compliance

Page top

[Topic 216834]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Enabling and disabling compliance rules

You can define these policy settings only for Android devices.

To enable or disable existing rules of compliance control of mobile devices with corporate security requirements:

  1. Open the policy properties window:
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Policies & profiles. In the list of group policies that opens, click the name of the policy that you want to configure.
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices. Click the mobile device that falls under the policy that you want to configure, and then select the policy on the Active policies and policy profiles tab.
  2. In the policy properties page, select Application settings > Security controls.
  3. In the Compliance Control section, enable or disable the existing compliance rules by using the toggle buttons in the Status column.
  4. Click the Save button to save the changes you have made to the policy and exit the policy properties window.

Mobile device settings are configured after the next device synchronization with Kaspersky Security Center.

Page top

[Topic 216835]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Editing compliance rules

You can define these policy settings only for Android devices.

To edit a rule for controlling the compliance of mobile devices with corporate security requirements:

  1. Open the policy properties window:
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Policies & profiles. In the list of group policies that opens, click the name of the policy that you want to configure.
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices. Click the mobile device that falls under the policy that you want to configure, and then select the policy on the Active policies and policy profiles tab.
  2. In the policy properties page, select Application settings > Security controls.
  3. In the Compliance Control section, select the rule that you want to edit, and then click Edit.
  4. In the Rule window that opens, edit the rule as follows:
    1. In the Action column, configure the list of actions to be performed in case of non-compliance with the rule by adding new actions, editing the existing actions, or deleting them.
    2. Optionally, specify the time period in which a user can fix the non-compliance by using the Time to rectification column for each action.
    3. Click the Save button to save the rule.
  5. Click the Save button to save the changes you have made to the policy and exit the policy properties window.

Mobile device settings are configured after the next device synchronization with Kaspersky Security Center.

Page top

[Topic 216836]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Adding compliance rules

You can define these policy settings only for Android devices.

To add a rule for controlling the compliance of mobile devices with corporate security requirements:

  1. Open the policy properties window:
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Policies & profiles. In the list of group policies that opens, click the name of the policy that you want to configure.
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices. Click the mobile device that falls under the policy that you want to configure, and then select the policy on the Active policies and policy profiles tab.
  2. In the policy properties page, select Application settings > Security controls.
  3. In the Compliance Control section, click Rule.
  4. In the Rule window that opens, define the rule as follows:
    1. Select the non-compliance criterion for the rule.
    2. Click Add, and then select the action to be performed in case of non-compliance with the rule in the Action column.

      You can add several actions.

    3. Specify the time period in which a user can fix the non-compliance by using the Time to rectification column for each action.
    4. Click the Save button to save the rule.
  5. Click the Save button to save the changes you have made to the policy and exit the policy properties window.

Mobile device settings are configured after the next device synchronization with Kaspersky Security Center.

Page top

[Topic 216839]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Deleting compliance rules

You can define these policy settings only for Android devices.

To delete a rule for controlling the compliance of mobile devices with corporate security requirements:

  1. Open the policy properties window:
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Policies & profiles. In the list of group policies that opens, click the name of the policy that you want to configure.
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices. Click the mobile device that falls under the policy that you want to configure, and then select the policy on the Active policies and policy profiles tab.
  2. In the policy properties page, select Application settings > Security controls.
  3. In the Compliance Control section, select the rule that you want to delete, and then click Delete.
  4. Click the Save button to save the changes you have made to the policy and exit the policy properties window.

Mobile device settings are configured after the next device synchronization with Kaspersky Security Center.

Page top

[Topic 216911]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

List of non-compliance criteria

You can define these policy settings only for Android devices.

To ensure that an Android device complies with corporate security requirements, Kaspersky Endpoint Security for Android can check the device against the following criteria:

  • Real-time protection is disabled.

    Real-time protection must be enabled.

    For more information on configuring real-time protection, see the "Configuring real-time protection" section.

  • Anti-Virus databases are out of date.

    The anti-virus database of Kaspersky Endpoint Security for Android must be regularly updated.

    For more information on defining the settings of anti-virus database updates, see the "Configuring anti-virus protection" section.

  • Forbidden apps are installed.

    The device must not have applications installed that are classified as Block from launching, as specified in the App Control section.

    For more information on creating rules for applications, see the "Configuring App Control" section.

  • Apps from forbidden categories are installed.

    The device must not have applications installed that fall under a category that is classified as Block from launching, as specified in the App Control section.

    For more information on creating rules for application categories, see the "Configuring App Control" section.

  • Not all required apps are installed.

    The device must have specific applications installed that are classified as Force to install, as specified in the App Control section.

    For more information on creating rules for applications, see the "Configuring App Control" section.

  • Operating system version is out of date.

    The device must have an allowed version of the operating system.

    For using this non-compliance criterion, you must specify the range of allowed operating system versions in the Minimum operating system version and Maximum operating system version drop-down lists.

  • Device has not been synchronized for a long time.

    The device must be regularly synchronized with the Administration Server.

    For using this non-compliance criterion, you must specify the maximum time interval between device synchronizations in the Synchronization period drop-down list.

  • Device has been rooted.

    The device must not be rooted.

    For more information, see the "Detecting device hacks (root)" section.

  • Unlock password is not compliant with security requirements.

    The device must be protected with an unlock password that complies with the unlock password strength requirements.

Page top

[Topic 216913]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

List of actions in case of non-compliance

You can define these policy settings only for Android devices.

If the user does not fix a non-compliance issue within the specified time, the following actions are available:

  • Block all apps except system apps.

    All apps on the user's mobile device, except system apps, are blocked from starting.

  • Lock device.

    Mobile device is locked. To obtain access to data, you must unlock the device. If the reason for locking the device is not rectified after the device is unlocked, the device will be locked again after the specified time period.

  • Wipe corporate data.

    Wipe containerized data, corporate email account, settings for connecting to the corporate Wi-Fi network and VPN, and Access Point Name (APN).

  • Fully reset device to factory settings.

    All data is deleted from the mobile device and the settings are rolled back to their factory values.

Page top

[Topic 214543]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring user access to websites

You can define these policy settings for Android and iOS devices.

To protect personal and corporate data stored on mobile devices during internet browsing, you can configure user access to websites by using Web Protection. Web Protection scans websites before a user opens them, and then blocks websites that distribute malicious code and phishing websites designed to steal confidential data and gain access to financial accounts.

For Android devices, this feature also supports website filtering by categories defined in the Kaspersky Security Network cloud service. Filtering allows you to restrict access to certain websites or categories of websites (for example, those from the "Gambling, lotteries, sweepstakes" or "Internet communication" categories).

To enable Web Protection on iOS devices, the user must allow the Kaspersky Security for iOS app to add a VPN configuration.

To enable Web Protection on Android devices:

  • Kaspersky Endpoint Security must be enabled as an Accessibility Features service.
  • The Statement regarding data processing for the purpose of using Web Protection (Web Protection Statement) should be accepted. Kaspersky Endpoint Security uses Kaspersky Security Network (KSN) to scan websites. The Web Protection Statement contains the terms of data exchange with KSN.

    You can accept the Web Protection Statement for the user in Kaspersky Security Center. In this case, the user is not required to take any action.

    If you have not accepted the Web Protection Statement and prompt the user to do this, the user must read and accept the Web Protection Statement in the app settings.

    If you have not accepted the Web Protection Statement, Web Protection is not available.

Web Protection on Android devices works only in the Google Chrome browser (including the Custom Tabs feature), Huawei Browser, and Samsung Internet Browser. Web Protection for Samsung Internet Browser does not block sites on a mobile device if a work profile is used and Web Protection is enabled only for the work profile.

To configure user access to websites:

  1. Open the policy properties window:
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Policies & profiles. In the list of group policies that opens, click the name of the policy that you want to configure.
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices. Click the mobile device that falls under the policy that you want to configure, and then select the policy on the Active policies and policy profiles tab.
  2. In the policy properties page, select Application settings > Security controls.
  3. In the Web Protection section, select the Enable Web Protection check box to enable the feature.
  4. For Android devices, you can select one of the following options:
    • To restrict user access to websites based on their content:
      1. Select Block websites of specified categories.
      2. Select the check boxes next to the categories of websites to which Kaspersky Endpoint Security for Android will block access.

        If Web Protection is enabled, user access to websites in the Phishing and Malware sites categories is always blocked.

    • To specify the list of allowed websites:
      1. Select Allow only specified websites.
      2. Create a list of websites by adding website addresses to which the app will not block access. Kaspersky Endpoint Security for Android supports only regular expressions. When entering the address of an allowed website, use the following templates:
        • https://example.com.*—All child pages of the website are allowed (for example, https://example.com/about).
        • https://.*example.com—All subdomain pages of the website are allowed (for example, https://pictures.example.com).
      3. You can also use the expression https? to select HTTP and HTTPS. For more details on regular expressions, please refer to the Oracle Technical Support website.
    • To block user access to all websites, select Block all websites.
  5. Click the Save button to save the changes you have made to the policy and exit the policy properties window.

Mobile device settings are configured after the next device synchronization with Kaspersky Security Center.

Page top

[Topic 214515]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring feature restrictions

You can define these policy settings only for Android devices.

Kaspersky Security Center Web Console enables you to configure user access to the following features of mobile devices:

  • Wi-Fi
  • Camera
  • Bluetooth

By default, the user can use Wi-Fi, camera, and Bluetooth on the device without restrictions.

To configure the Wi-Fi, camera, and Bluetooth usage restrictions on the device:

  1. Open the policy properties window:
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Policies & profiles. In the list of group policies that opens, click the name of the policy that you want to configure.
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices. Click the mobile device that falls under the policy that you want to configure, and then select the policy on the Active policies and policy profiles tab.
  2. In the policy properties page, select Application settings > Security controls.
  3. In the Feature management section, configure the usage of Wi-Fi, camera, and Bluetooth:
    • To disable the Wi-Fi module on the user's mobile device, select the Prohibit use of Wi-Fi (only for devices running Android version 9 and earlier) check box.

      On devices running Android 10.0 or later, prohibiting the use of Wi-Fi networks is not supported.

    • To disable the camera on the user's mobile device, select the Prohibit use of camera check box.

      On devices running Android 10.0 or later, the use of the camera cannot be completely prohibited.

      On devices running Android 11 or later, Kaspersky Endpoint Security for Android must be set as an Accessibility feature. Kaspersky Endpoint Security for Android prompts the user to set the app as an Accessibility feature through the Initial Configuration Wizard. The user can skip this step or disable this service in the device settings at a later time. If this is the case, you will not be able to restrict use of the camera.

    • To disable Bluetooth on the user's mobile device, select the Prohibit use of Bluetooth check box.

      On Android 12 or later, the use of Bluetooth can be disabled only if the device user granted the Nearby Bluetooth devices permission. The user can grant this permission during the Initial Configuration Wizard or at a later time.

      On personal devices running Android 13 or later, the use of Bluetooth cannot be disabled.

  4. Click the Save button to save the changes you have made to the policy and exit the policy properties window.

Mobile device settings are configured after the next device synchronization with Kaspersky Security Center.

Page top

[Topic 214507]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Protecting Kaspersky Endpoint Security for Android against removal

For mobile device protection and compliance with corporate security requirements, you can enable protection against the removal of Kaspersky Endpoint Security for Android. In this case, the user cannot remove the app by using the Kaspersky Endpoint Security for Android interface. When removing the app by using the tools of the Android operating system, the user is prompted to disable administrator rights for Kaspersky Endpoint Security for Android. After disabling the rights, the mobile device will be locked.

To enable protection against the removal of Kaspersky Endpoint Security for Android:

  1. Open the policy properties window:
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Policies & profiles. In the list of group policies that opens, click the name of the policy that you want to configure.
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices. Click the mobile device that falls under the policy that you want to configure, and then select the policy on the Active policies and policy profiles tab.
  2. In the policy properties page, select Application settings > Security controls.
  3. In the Manage app on mobile device section, clear the Allow removal of Kaspersky Endpoint Security for Android from device check box.

    To protect the app from removal on devices running Android 7.0 or later, Kaspersky Endpoint Security for Android must be set as an Accessibility feature. When the Initial Configuration Wizard is running, Kaspersky Endpoint Security for Android prompts the user to grant the application all required permissions. The user can skip these steps or disable these permissions in the device settings at a later time. If this is the case, the app is not protected from removal.

  4. Click the Save button to save the changes you have made to the policy and exit the policy properties window.

Mobile device settings are configured after the next device synchronization with Kaspersky Security Center.

If an attempt is made to remove the app, the mobile device will be locked.

Page top

[Topic 214539]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring synchronization of mobile devices with Kaspersky Security Center

You can define these policy settings for Android and iOS devices.

To manage mobile devices and receive reports or statistics from mobile devices, you must define synchronization settings. Synchronization of mobile devices with Kaspersky Security Center can be performed in the following ways:

  • By schedule. Synchronization by schedule is performed by using HTTP. You can configure the synchronization schedule in the policy properties. Modifications to policy settings, commands, and tasks are performed when mobile devices are synchronized with Kaspersky Security Center according to the schedule—that is, with a delay. By default, mobile devices are synchronized with Kaspersky Security Center automatically every six hours.

    On Android 12 or later, the app may perform this task later than specified if the device is in battery saver mode.

  • Forced (for Android devices). Forced synchronization is performed by using push notifications of the FCM service (Firebase Cloud Messaging). Forced synchronization is primarily intended for timely delivery of commands to a mobile device. If you want to use forced synchronization, make sure that the FCM settings are configured in Kaspersky Security Center.

To configure mobile device synchronization with Kaspersky Security Center:

  1. Open the policy properties window:
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Policies & profiles. In the list of group policies that opens, click the name of the policy that you want to configure.
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices. Click the mobile device that falls under the policy that you want to configure, and then select the policy on the Active policies and policy profiles tab.
  2. In the policy properties page, select Application settings > Synchronization.
  3. In the Synchronization with the Administration Server section, use the Synchronization period drop-down list to select the synchronization period.

    By default, synchronization is performed every six hours.

  4. For Android devices, you can disable synchronization when the device is roaming. To do so, select the Do not synchronize while roaming check box.

    By default, synchronization while roaming is enabled.

  5. Click the Save button to save the changes you have made to the policy and exit the policy properties window.

Mobile device settings are configured after the next device synchronization with Kaspersky Security Center.

Page top

[Topic 214505]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Kaspersky Security Network

To protect mobile devices more effectively, Kaspersky Endpoint Security for Android and Kaspersky Security for iOS use data acquired from users around the globe. Kaspersky Security Network is designed to process such data.

Kaspersky Security Network (KSN) is an infrastructure of cloud services providing access to the Kaspersky online knowledge base with 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 performance of some protection components, and reduces the likelihood of false alarms.

Your participation in Kaspersky Security Network helps Kaspersky to acquire real-time information about the types and sources of new threats, develop methods of neutralizing them, and reduce the number of false alarms. Participation in Kaspersky Security Network also lets you access reputation statistics for applications and websites.

When you participate in Kaspersky Security Network, some statistics are acquired while the mobile app is running and they are automatically sent to Kaspersky. This information makes it possible to keep track of threats in real time. Files or their parts that may be exploited by intruders to harm the computer or user's content can be also sent to Kaspersky for additional examination.

The following app components use the Kaspersky Security Network cloud service:

  • The Anti-Virus, Web Protection, and App Control components in the Kaspersky Endpoint Security for Android app.
  • The Web Protection component in the Kaspersky Security for iOS app.

To start using KSN, you must accept the terms and conditions of the End User License Agreement. For more information about sending data to KSN, refer to Information exchange with Kaspersky Security Network.

Refusal to participate in KSN reduces the level of device protection, which may lead to infection of the device and loss of data.

To improve the performance of the mobile app, you can also provide statistical data to Kaspersky Security Network.

Providing the information to Kaspersky Security Network is voluntary.

Updates functionality (including providing anti-virus signature updates and codebase updates), as well as KSN functionality will not be available in the software in the U.S. territory from 12:00 AM Eastern Daylight Time (EDT) on September 10, 2024 in accordance with the restrictive measures.

In this section

Information exchange with Kaspersky Security Network

Enabling and disabling Kaspersky Security Network

Page top

[Topic 214534]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Information exchange with Kaspersky Security Network

Information exchange in Kaspersky Endpoint Security for Android

To improve real-time protection, Kaspersky Endpoint Security for Android uses the Kaspersky Security Network cloud service for operating the following components:

  • Anti-Virus. The app obtains access to the Kaspersky online knowledge base regarding the reputation of files and apps. The scan is performed for threats whose information has not yet been added to Anti-Virus databases but is already available in KSN. Kaspersky Security Network cloud service provides full operation of Anti-Virus and reduces the likelihood of false alarms.
  • Web Protection. The app uses data received from KSN to scan websites before they are opened. The app also determines the website category to control internet access to users, based on lists of allowed and blocked categories (for example, the "Internet communication" category).
  • App Control. The app determines the app category to restrict the startup of apps that do not meet corporate security requirements, based on lists of allowed and blocked categories (for example, the "Games" category).

Information on the type of data submitted to Kaspersky when using KSN during operation of Anti-Virus and App Control is available in the End User License Agreement. By accepting the terms and conditions of the License Agreement, you agree to transfer this information.

Information on the type of data submitted to Kaspersky when using KSN during operation of Web Protection is available in the Statement regarding data processing for Web Protection. By accepting the terms and conditions of the Statement, you agree to transfer this information.

For more information about data provision to KSN, refer to Data provision in Kaspersky Endpoint Security for Android.

Providing data to KSN is voluntary. If you want, you can disable data exchange with KSN.

Information exchange in Kaspersky Security for iOS

To improve real-time protection, Kaspersky Security for iOS uses the Kaspersky Security Network cloud service for operating the Web Protection component. The app uses data received from KSN to scan web resources before they are opened.

Information on the type of data submitted to Kaspersky when using KSN during operation of Web Protection is available in the End User License Agreement. By accepting the terms and conditions of the License Agreement, you agree to transfer this information.

For more information about data provision to KSN, refer to Data provision in Kaspersky Security for iOS.

Providing data to KSN is voluntary. If you want, you can disable data exchange with KSN.

Sending statistics to KSN from Android and iOS apps

To exchange data with KSN for the purposes of improving the performance of the app, the following conditions must be fulfilled:

  • The device user must read and accept the terms of the Kaspersky Security Network Statement.
  • You must configure the group policy settings to allow statistics to be sent to KSN.

You can opt out of sending statistic data to Kaspersky Security Network at any time. Information on the type of statistic data submitted to Kaspersky when using KSN during operation of the mobile app is available in the Kaspersky Security Network Statement.

Page top

[Topic 214533]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Enabling and disabling Kaspersky Security Network

By default, the use of Kaspersky Security Network is enabled.

If the use of Kaspersky Security Network is disabled, Web Protection, App Control, and additional protection in Kaspersky Security Network are disabled automatically and their settings become unavailable.

To enable or disable the use of Kaspersky Security Network:

  1. Open the policy properties window:
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Policies & profiles. In the list of group policies that opens, click the name of the policy that you want to configure.
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices. Click the mobile device that falls under the policy that you want to configure, and then select the policy on the Active policies and policy profiles tab.
  2. In the policy properties page, select Application settings > KSN and statistics.
  3. To enable or disable the use of Kaspersky Security Network, select or clear the Use Kaspersky Security Network check box.
  4. If the use of Kaspersky Security Network is enabled and if you agree to submit data to Kaspersky, select the Allow statistics to be sent to Kaspersky Security Network check box. This data will help the mobile app more quickly respond to threats, improve the performance of protection components, and decrease the likelihood of false alarms.
  5. Click the Save button to save the changes you have made to the policy and exit the policy properties window.

Mobile device settings are configured after the next device synchronization with Kaspersky Security Center.

Page top

[Topic 214544]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Exchanging information with Google Analytics for Firebase, SafetyNet Attestation, Firebase Performance Monitoring, and Crashlytics

You can define these policy settings only for Android devices.

Kaspersky Endpoint Security for Android exchanges data with the Google Analytics for Firebase, SafetyNet Attestation, Firebase Performance Monitoring, and Crashlytics services in order to improve the quality, appearance, and performance of Kaspersky software, products, services, and infrastructure by analyzing users' experience, features, status, and device settings used.

Exchanging information with the Google Analytics for Firebase, SafetyNet Attestation, Firebase Performance Monitoring, and Crashlytics services is disabled by default.

To enable data exchange:

  1. Open the policy properties window:
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Policies & profiles. In the list of group policies that opens, click the name of the policy that you want to configure.
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices. Click the mobile device that falls under the policy that you want to configure, and then select the policy on the Active policies and policy profiles tab.
  2. In the policy properties page, select Application settings > KSN and statistics.
  3. In the Sending statistics to third-party services section, select the Allow data transfer to help improve the quality, appearance, and performance of the app check box.
  4. Click the Save button to save the changes you have made to the policy and exit the policy properties window.

Mobile device settings are configured after the next device synchronization with Kaspersky Security Center.

Page top

[Topic 214558]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring notifications on mobile devices

You can define these policy settings only for Android devices.

If you do not want the mobile device user to be distracted by Kaspersky Endpoint Security for Android notifications, you can disable certain notifications.

Kaspersky Endpoint Security uses the following tools to display the device protection status:

  • Protection status notification. This notification is pinned to the notification bar. A protection status notification cannot be removed. The notification displays the device protection status (for example, ) and number of issues, if any. The device user can tap the device protection status and see the list of issues in the app.
  • App notifications. These notifications inform the device user about the application (for example, threat detection).
  • Pop-up messages. Pop-up messages require an action from the device user (for example, an action to take when a threat is detected).

All Kaspersky Endpoint Security for Android notifications are enabled by default.

On Android 13, the device user should grant permission to send notifications during the Initial Configuration Wizard or later.

An Android device user can disable all notifications from Kaspersky Endpoint Security for Android in the settings on the notification bar. If notifications are disabled, the user does not monitor the operation of the app and can ignore important information (for example, information about failures during device synchronization with Kaspersky Security Center). In this case, to find out the app operating status, the user must open Kaspersky Endpoint Security for Android.

To configure the display of notifications about the operation of Kaspersky Endpoint Security for Android on a mobile device:

  1. Open the policy properties window:
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Policies & profiles. In the list of group policies that opens, click the name of the policy that you want to configure.
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices. Click the mobile device that falls under the policy that you want to configure, and then select the policy on the Active policies and policy profiles tab.
  2. In the policy properties page, select Application settings > Notifications and reports.
  3. In the Notifications section, configure the display of notifications:
    • To hide all notifications and pop-up messages, disable the Display notifications when Kaspersky Endpoint Security is in the background toggle button.

      Kaspersky Endpoint Security for Android will display the protection status notification only. The notification displays the device protection status (for example, ) and number of issues. The app also displays notifications when the user is working with the app (for example, the user updates anti-virus databases manually).

      Kaspersky experts recommend that you enable notifications and pop-up messages. If you disable notifications and pop-up messages when the app is in background mode, the app will not warn users about threats in real time. Mobile device users can learn about the device protection status only when they open the app.

    • In List of security issues displayed on users' devices, select the Kaspersky Endpoint Security for Android issues that you want to be displayed on the user's mobile device.
  4. Click the Save button to save the changes you have made to the policy and exit the policy properties window.

Mobile device settings are configured after the next device synchronization with Kaspersky Security Center.

Page top

[Topic 214555]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Detecting device hacks

Kaspersky Security Center Web Console enables you to detect device hacks (root) on Android devices and jailbreaks on iOS devices. System files are unprotected on a hacked device and can therefore be modified. Moreover, third-party apps from unknown sources could be installed on hacked devices. Upon detection of a hack attempt, we recommend that you immediately restore normal operation of the device.

Kaspersky Endpoint Security for Android uses the following services to detect when a user obtains root privileges:

  • Embedded service of Kaspersky Endpoint Security for Android. A Kaspersky service that checks whether a mobile device user has obtained root privileges (Kaspersky Mobile Security SDK).
  • SafetyNet Attestation. A Google service that checks the integrity of the operating system, analyzes the device hardware and software, and identifies other security issues. For more details about SafetyNet Attestation, visit the Android Technical Support website.

Kaspersky Security for iOS uses the following service to detect a jailbreak:

  • Embedded service of Kaspersky Security for iOS. A Kaspersky service that checks whether a mobile device is jailbroken (Kaspersky Mobile Security SDK).

If the device is hacked, you receive a notification. You can view hacking notifications in Kaspersky Security Center Web Console on the Monitoring & reporting > Dashboard tab. You can also disable notifications about hacks in the event notification settings.

On Android devices, you can impose restrictions on the user's activity if the device is hacked (for example, lock the device). You can impose restrictions by using the Compliance Control component. To do this, create a compliance rule with the Device has been rooted criterion.

Page top

[Topic 218553]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Defining licensing settings

You can define these policy settings for Android and iOS devices.

To manage mobile devices in Kaspersky Security Center Web Console or Cloud Console, you must activate the mobile app on the mobile devices. Activating the Kaspersky Endpoint Security for Android app or the Kaspersky Security for iOS app on a mobile device is done by providing valid license information to the app. License information is delivered to the mobile device, together with the policy, when the device is synchronized with Kaspersky Security Center.

If the activation of the mobile app is not completed within 30 days from the time of installation on the mobile device, the app is automatically switched to the limited functionality mode. In this mode, most of the app components are not operational. When switched to the limited functionality mode, the app stops performing automatic synchronization with Kaspersky Security Center. Therefore, if the activation of the app has not been completed within 30 days after the installation, the user must synchronize the device with Kaspersky Security Center manually.

To define licensing settings of a group policy:

  1. Open the policy properties window:
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Policies & profiles. In the list of group policies that opens, click the name of the policy that you want to configure.
    • In the main window of Kaspersky Security Center Web Console or Cloud Console, select Devices > Mobile > Devices. Click the mobile device that falls under the policy that you want to configure, and then select the policy on the Active policies and policy profiles tab.
  2. In the policy properties page, select Application settings > Licenses.
  3. Use the drop-down list to select the required license key from the key storage of the Administration Server.

    The details of the license key are displayed in the fields below.

    You can replace the existing activation key on the mobile device if it is different from the one selected in the drop-down list above. To do so, select the If the key on device is different, replace with this key check box.

  4. Click the Save button to save the changes you have made to the policy and exit the policy properties window.

Mobile device settings are configured after the next device synchronization with Kaspersky Security Center.

Page top

[Topic 214517]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring events

You can define these policy settings for Android and iOS devices.

You can define the storage and notification settings of events that occur on your users' devices and that are sent to Kaspersky Security Center.

You can configure events only when modifying a policy.

Events are distributed by importance level on the following tabs:

  • Critical

    A critical event indicates a problem that may lead to data loss, an operational malfunction, or a critical error.

  • Functional failure

    A functional failure indicates a serious problem, error, or malfunction that occurred during the operation of the app.

  • Warning

    A warning is not necessarily serious, but nevertheless indicates a potential future problem.

  • Info

    An informational event notifies about the successful completion of an operation or a procedure, or of the proper functioning of the app.

In each section, the list shows the types of events and the default event storage term in Kaspersky Security Center (in days).

From the list of events, you can do the following:

  • Add or remove an event type from the list of event types that are sent to Kaspersky Security Center.
  • Define the storage and notification settings for each event type, for example: how long events of this type must be stored in the Administration Server database or whether you will be notified about events of this type by email.

For more details on configuring events in Kaspersky Security Center Web Console and Cloud Console:

Page top

[Topic 224230]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring events about the installation, update, and removal of apps on users' devices

You can define these policy settings for Android and iOS devices.

If you use Kaspersky Security Center Cloud Console, the list of types of events that occur on your users' devices, and that are sent to Kaspersky Security Center, does not include the installation, update, and removal of apps on the devices. This is because such events occur often and these events may replace other important events in the Kaspersky Security Center database when the events count limit is reached. They may also affect the performance of Administration Server or the DBMS, and the bandwidth of the internet connection with Kaspersky Security Center Cloud Console.

If you nevertheless want to store events of this type and be notified about them, proceed as described in this section.

To configure events about the installation, update, and removal of apps on users' devices:

  1. In the settings of a policy, on the Event configuration tab, add the An app has been installed or removed (list of installed apps) informational event type to the list of events that are stored in the Administration Server database.

    For more details on configuring events, please refer to Kaspersky Security Center Cloud Console Help.

  2. Enable the Send a list of installed apps on all mobile devices option.

Events about the installation, update, and removal of apps on users' devices are stored in the Kaspersky Security Center database. You are notified about these events.

Page top

[Topic 214560]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Network load

This section contains information on the volume of network traffic that is exchanged between mobile devices and Kaspersky Security Center.

Traffic volume

Task

Outgoing traffic

Incoming traffic

Total traffic

Initial deployment of the app, MB

0.08

17.76

17.84

Initial update of anti-virus databases (the traffic volume may differ due to the size of anti-virus databases), MB

0.04

2.21

2.25

Synchronization of the mobile device with Kaspersky Security Center, MB

0.03

0.02

0.05

Regular update of anti-virus databases (the traffic volume may differ due to the size of anti-virus databases), MB

0.08

3.06

3.14

Execution of Anti-Theft commands. Locate device (the traffic volume may differ due to the specifications of the embedded camera and the quality of images), MB

0.09

0.8

0.17

Execution of Anti-Theft commands. Mugshot, MB

1.0

0.02

1.02

Execution of Anti-Theft commands. Device lock, MB

0.06

0.05

0.11

Average daily volume, MB

0.22

6.96

7.18

Page top

[Topic 216447]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Working in MMC-based Administration Console

This Help section describes protection and management of mobile devices by using the MMC-based Administration Console of Kaspersky Security Center.

In this section

Key use cases

About Kaspersky Security for Mobile

Deployment

Configuration and Management

Managing the app using third-party EMM systems (Android only)

Network load

Participating in Kaspersky Security Network

Data provision to third-party services

Global acceptance of additional Statements

Samsung KNOX

Appendices

Page top

[Topic 91308]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

About Kaspersky Security for Mobile

Kaspersky Security for Mobile is an integrated solution for protecting and managing corporate mobile devices as well as personal mobile devices used by company employees for corporate purposes.

Kaspersky Security for Mobile includes the following components:

  • Kaspersky Endpoint Security for Android mobile app

    The Kaspersky Endpoint Security for Android app ensures protection of mobile devices against web threats, viruses, and other programs that pose threats.

  • Kaspersky Endpoint Security for Android Administration Plug-in

    The Administration Plug-in of Kaspersky Endpoint Security for Android provides the interface for managing mobile devices and mobile apps installed on them through the Administration Console of Kaspersky Security Center.

  • Kaspersky Device Management for iOS Administration Plug-in

    The Kaspersky Device Management for iOS Administration Plug-in lets you define the configuration settings for devices connected to Kaspersky Security Center via the iOS MDM protocol (hereinafter referred to as "iOS MDM devices"), without using the iPhone Configuration Utility.

The administration plug-ins are integrated into the Kaspersky Security Center remote administration system. The administrator can use a single Administration Console of Kaspersky Security Center to manage all mobile device on the corporate network as well as client computers and virtual systems. After you connect mobile devices to the Administration Server, they become managed. The administrator can remotely monitor managed devices.

The Kaspersky Endpoint Security for Android mobile app may also operate as part of the Kaspersky Endpoint Security Cloud remote administration system. For more details on working with apps through Kaspersky Endpoint Security Cloud, please refer to Kaspersky Endpoint Security Cloud Online Help.

The Kaspersky Endpoint Security for Android mobile app can also operate as part of third-party EMM solutions of AppConfig Community participants.

In this section

Key features of mobile device management in MMC-based Administration Console

About Kaspersky Endpoint Security for Android app

About Kaspersky Device Management for iOS

About the Kaspersky Endpoint Security for Android Administration Plug-in

About the Kaspersky Device Management for iOS Administration Plug-in

Hardware and software requirements

Known issues and considerations

Page top

[Topic 221101]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Key features of mobile device management in MMC-based Administration Console

Kaspersky Security for Mobile provides the following features:

  • Distribution of email messages for connecting Android devices to Kaspersky Security Center by using Google Play links.
  • Remote connection of mobile devices to Kaspersky Security Center and other third-party EMM systems (for example, VMWare AirWatch, MobileIron, IBM Maas360, SOTI MobiControl).
  • Remote configuration of the Kaspersky Endpoint Security for Android app, as well as remote configuration of services, apps, and functions of Android devices.
  • Remote configuration of mobile devices in accordance with the corporate security requirements.
  • Prevention of leakage of corporate information stored on mobile devices, in case they are lost or stolen (Anti-Theft).
  • Control of compliance with corporate security requirements (Compliance Control).
  • Control of internet use on mobile devices (Web Protection).
  • Setup of corporate mail on mobile devices, including organizations with a Microsoft Exchange mail server deployed in the company (only for iOS and Samsung devices).
  • Configuration of the corporate network (Wi-Fi, VPN) allowing VPN to be used on mobile devices. VPN can be configured only on iOS and Samsung devices.
  • Configuration of the mobile device status to be displayed in Kaspersky Security Center when policy rules are violated: Critical, Warning, OK.
  • Setup of notifications shown to the user in the Kaspersky Endpoint Security for Android app.
  • Configuration of settings on devices supporting Samsung KNOX 2.6 or later.
  • Configuration of settings on devices supporting Android work profiles.
  • Configuration of settings of Android mobile devices in device owner mode.
  • Deployment of the Kaspersky Endpoint Security for Android app through the Samsung KNOX Mobile Enrollment console. Samsung KNOX Mobile Enrollment is intended for batch installation and initial configuration of apps on Samsung devices purchased from official vendors.
  • An upgrade of the Kaspersky Endpoint Security for Android app to the specified version can be performed by using Kaspersky Security Center policies.
  • Administrator notifications about the status and events of the Kaspersky Endpoint Security for Android app can be communicated in Kaspersky Security Center or by email.
  • Change Control for policy settings (revision history).
  • Commands for remote mobile device management. For example, if a mobile device is lost or stolen, you can send commands to locate the device or wipe all corporate data from the device.
  • Configuration of screen unlock password settings for mobile devices.
  • Configuration of Wi-Fi network settings for mobile devices.
  • Adding web clips to open websites from the Home screen of mobile devices.

Kaspersky Security for Mobile includes the following protection and management components:

  • Anti-Virus (for Android devices)
  • Anti-Theft (for Android devices)
  • Web Protection (for Android and iOS devices)
  • App Control (for Android devices)
  • Compliance Control (for Android and iOS devices)
  • Detection of root privileges on devices (for Android devices)

Page top

[Topic 99558]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

About Kaspersky Endpoint Security for Android app

The Kaspersky Endpoint Security for Android app ensures protection of mobile devices against web threats, viruses, and other programs that pose threats.

Kaspersky Endpoint Security for Android app includes the following components:

  • Anti-Virus. It allows you to detect and neutralize threats on your device by using the Anti-Virus databases and the Kaspersky Security Network cloud service. Anti-Virus includes the following components:
    • Protection. Detects threats in open files, scans new apps, and prevents device infection in real time.
    • Scan. It is started on demand for the entire file system, only for installed apps, or a selected file or folder.
    • Update. Update allows you to download new Anti-Virus databases for the application.
  • Anti-Theft. This component protects information on the device against unauthorized access in case the device is lost or stolen. This component lets you send the following commands to the device:
    • Locate to get the coordinates of the device's location.
    • Alarm to make the device sound a loud alarm.
    • Mugshot to make the device take pictures with the frontal camera if someone attempts to unlock it.
    • Wipe corporate data to protect sensitive company information.
  • Web Protection. This component blocks malicious sites designed to spread malicious code. Web Protection also blocks fake (phishing) websites designed to steal confidential data of the user (for example, passwords to online banking or e-money systems) and access the user's financial info. Web Protection scans websites before you open them using the Kaspersky Security Network cloud service. After scanning, Web Protection allows trustworthy websites to load and blocks malicious websites. Web Protection also supports website filtering by categories defined in Kaspersky Security Network cloud service. This allows the administrator to restrict user access to certain categories of web pages (for example, web pages from the "Gambling, lotteries, sweepstakes" or "Internet communication" categories).
  • App Control. This component lets you install recommended and required apps to your device via a direct link to the distribution package or a link to Google Play. App Control lets you remove blocked apps that violate corporate security requirements.
  • Compliance Control. This component lets you check managed devices for compliance with corporate security requirements and impose restrictions on certain functions of non-compliant devices.

You can also install the Kaspersky Endpoint Security for Android app in device owner mode. This will give you full control over company-owned Android devices and let you configure a wide range of device settings. In device owner mode, you can:

  • Restrict Android operating system features.
  • Configure Google Chrome settings.
  • Configure app startup settings in App Control.
  • Limit the set of apps that are available to a device user in Kiosk mode.
  • Configure Exchange ActiveSync settings for Gmail.
  • Configure the connection to an NDES/SCEP server.
  • Install root certificates on devices.
Page top

[Topic 136121]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

About Kaspersky Device Management for iOS

Kaspersky Device Management for iOS ensures protection and control of mobile devices that are connected to Kaspersky Security Center and includes device management features, such as:

  • Password protection. This feature allows you to set password complexity requirements so that users use complex passwords compliant with corporate password policy.
  • Network management. This feature allows you to add approved VPN and Wi-Fi networks or restrict access to others.
  • Wipe corporate data. In case the device is lost or stolen, you can send the Wipe command to it to protect sensitive company information.
  • Web Protection. This component blocks malicious sites designed to spread malicious code. Web Protection also blocks fake (phishing)  websites designed to steal confidential data of the user (for example, passwords to online banking or e-money systems) and access the user's financial info. Web Protection scans websites before you open them using the Kaspersky Security Network cloud service. After scanning, Web Protection allows trustworthy websites to load and blocks malicious websites. Web Protection also supports website filtering by categories defined in Kaspersky Security Network cloud service. This allows the administrator to restrict user access to certain categories of web pages (for example, web pages from the "Gambling, lotteries, sweepstakes" or "Internet communication" categories).
  • Application restrictions. This component lets you control whether device native apps, such as iTunes, Safari, or Game Center can be used on a supervised device.
  • Feature restrictions. This component allows to check managed devices for compliance with the corporate security requirements and impose restrictions on certain functions of non-compliant devices.
  • Compliance Control. This component monitors iOS MDM devices for compliance with corporate security requirements and takes actions in case of non-compliance. Compliance control is based on a list of rules. Each rule includes the following components:
    • Status (whether the rule is enabled or disabled).
    • Device check criteria (for example, absence of the specified apps or operating system version).
    • Actions performed on the device in case of non-compliance (for example, wipe corporate data or send an email message to the user).
Page top

[Topic 89640]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

About the Kaspersky Endpoint Security for Android Administration Plug-in

The Administration Plug-in of Kaspersky Endpoint Security for Android provides the interface for managing mobile devices and mobile apps installed on them through the Administration Console of Kaspersky Security Center. The Kaspersky Endpoint Security for Android Administration Plug-in can be used to:

  • Create group security policies for mobile devices.
  • Remotely configure the operating settings of the Kaspersky Endpoint Security for Android app on users' mobile devices.
  • Receive reports and statistics on the operation of the Kaspersky Endpoint Security for Android mobile app on users' devices.

The Kaspersky Endpoint Security for Android Administration Plug-in is installed by default when deploying Kaspersky Security Center. The plug-in does not require individual installation.

Page top

[Topic 89639]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

About the Kaspersky Device Management for iOS Administration Plug-in

The Administration Plug-in of Kaspersky Device Management for iOS provides an interface for managing mobile devices connected by means of the iOS MDM protocol through the Administration Console of Kaspersky Security Center. The Kaspersky Device Management for iOS Administration Plug-in can be used to do the following:

  • Create group security policies for mobile devices.
  • Remotely configure devices connected by using the iOS MDM protocol (hereinafter referred to as "iOS MDM devices").
  • Receive reports and statistics on the operation of users' mobile devices.

For more details on connecting mobile devices to Kaspersky Security Center by using the iOS MDM protocol, please refer to Kaspersky Security Center Help.

The Kaspersky Device Management for iOS Administration Plug-in is installed by default when deploying Kaspersky Security Center. The plug-in does not require separate installation.

Page top

[Topic 102017]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Hardware and software requirements

This section lists the hardware and software requirements for the administrator's computer that is used to deploy the apps on mobile devices, as well as the mobile device operating systems supported by Kaspersky Security for Mobile.

Hardware and software requirements for the administrator's computer

To deploy the comprehensive solution Kaspersky Security for Mobile, the administrator's computer must meet the hardware requirements of Kaspersky Security Center. For more details on using the hardware requirements of Kaspersky Security Center, see the Kaspersky Security Center Help.

To work with the Administration Plug-in of Kaspersky Endpoint Security for Android, the Administration Console of Kaspersky Security Center version 12 or later must be installed on the administrator's computer.

To work with the Kaspersky Device Management for iOS Administration Plug-in, the administrator's computer must meet the following software requirements:

  • Administration Console of Kaspersky Security Center 12 or later
  • iOS MDM Server component
  • Instruction set of version SSE2 or more recent version

To deploy the Kaspersky Endpoint Security for Android mobile app via the Administration Server, the administrator's computer must meet the following software requirements:

  • Kaspersky Security Center 12 or later
  • Administration Plug-in for Kaspersky Endpoint Security for Android

There are no software requirements for the administrator's computer when the Kaspersky Endpoint Security for Android mobile app is deployed from the relevant online stores.

The Kaspersky Endpoint Security for Android mobile app can also be used as part of the Kaspersky Endpoint Security Cloud remote administration system (Version 6.0 and above). For more details on working with apps through Kaspersky Endpoint Security Cloud, please refer to Kaspersky Endpoint Security Cloud Help.

The Kaspersky Endpoint Security for Android mobile app can function within third-party EMM systems:

  • VMware AirWatch 9.3 or later
  • MobileIron 10.0 or later
  • IBM MaaS360 10.68 or later
  • Microsoft Intune 1908 or later
  • SOTI MobiControl 14.1.4 (1693) or later

Hardware and software requirements for the user's mobile device to support installation of the Kaspersky Endpoint Security for Android app

The Kaspersky Endpoint Security for Android app has the following hardware and software requirements:

  • Smartphone or tablet with a screen resolution of 320x480 pixels or higher
  • 65 MB of free disk space in the main memory of the device
  • Android 5.0–13 (including Android 12L, excluding Go Edition)
  • x86, x86-64, Arm5, Arm6, Arm7, or Arm8 processor architecture

The app can be installed only to the main memory of the device.

Hardware and Software Requirements for an iOS MDM Profile

For an iOS MDM profile, the device must meet the following hardware and software requirements:

  • iOS 10–16 or iPadOS 13–15
  • Internet connection
Page top

[Topic 153756]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Known issues and considerations

The following known issues are non-critical for the operation of the solution.

Known issues when installing apps

  • Kaspersky Endpoint Security for Android is installed only in the main memory of the device.
  • On devices running Android 7.0, an error may occur during attempts to disable administrator rights for Kaspersky Endpoint Security for Android in device settings if Kaspersky Endpoint Security for Android is prohibited from overlaying on other windows. This issue is caused by a well-known defect in Android 7.
  • Kaspersky Endpoint Security for Android on devices running Android 7.0 or later does not support multi-window mode.
  • Kaspersky Endpoint Security for Android does not work on Chromebook devices running the Chrome operating system.
  • Kaspersky Endpoint Security for Android does not work on devices running Android (Go edition) operating systems.
  • When using the Kaspersky Endpoint Security for Android app with third-party EMM systems (for example, VMWare AirWatch), only the Anti-Virus and Web Protection components are available. The administrator can configure the settings of Anti-Virus and Web Protection in the EMM system console. In this case, notifications about app operation are available only in the interface of the Kaspersky Endpoint Security for Android app (Reports).

Known issues when upgrading the app version

  • You can upgrade Kaspersky Endpoint Security for Android only to a more recent version of the app. Kaspersky Endpoint Security for Android cannot be downgraded to an older version.
  • To upgrade Kaspersky Endpoint Security for Android using a standalone installation package, installation of apps from unknown sources must be allowed on the user's mobile device.
  • You can update through Google Play if Kaspersky Endpoint Security for Android was installed from Google Play. If the app was installed using another method, you cannot update through Google Play.
  • You can update through Kaspersky Security Center if Kaspersky Endpoint Security for Android was installed through Kaspersky Security Center. If the app was installed from Google Play, you cannot update the app through Kaspersky Security Center.
  • After you upgrade administration plug-ins to Technical Release 33, the Kaspersky Endpoint Security for Android app must also be upgraded to Technical Release 33. Otherwise, you will not be able to activate Samsung KNOX on some of your users' devices.

Known issues in Anti-Virus operation

  • Due to technical limitations, Kaspersky Endpoint Security for Android cannot scan files with a size of 2 GB or more. During a scan, the app skips such files without notifying you that such files were skipped.
  • For additional analysis of a device for new threats whose information has not yet been added to anti-virus databases, you must enable the use of Kaspersky Security Network. Kaspersky Security Network (KSN) is an infrastructure of cloud services providing access to Kaspersky online knowledge base with information about the reputation of files, web resources, and software. To use KSN, the mobile device must be connected to the internet.
  • In some cases, updating anti-virus databases from the Administration Server on a mobile device may fail. In this case, run the anti-virus database update task on the Administration Server.
  • On some devices, Kaspersky Endpoint Security for Android does not detect devices connected over USB OTG. It is not possible to run a virus scan on such devices.
  • On devices running Android 11 or later, the Kaspersky Endpoint Security for Android app can't scan the "Android/data" and "Android/obb" folders and detect malware in them due to technical limitations.
  • On devices running Android 11 or later, the user must grant the "Allow access to manage all files" permission.
  • On devices running Android 7.0 or later, the configuration window for the virus scan run schedule might be incorrectly displayed (management elements are not shown). This issue is caused by a well-known defect in Android 7.
  • On devices running Android 7.0, real-time protection in the extended mode does not detect threats in files that are stored on an external SD card.
  • On devices running Android 6.0, Kaspersky Endpoint Security for Android does not detect the downloading of a malicious file to the device memory. A malicious file may be detected by Anti-Virus when the file is run, or during a virus scan of the device. This issue is caused by a well-known defect in Android 6.0. To ensure device security, it is recommended to configure scheduled virus scans.

Known issues in Web Protection operation

  • Web Protection on Android devices works only in the Google Chrome browser (including the Custom Tabs feature), Huawei Browser, and Samsung Internet Browser. Web Protection for Samsung Internet Browser does not block sites on a mobile device if a work profile is used and Web Protection is enabled only for the work profile.
  • Kaspersky Endpoint Security in the work profile scans only the website domain in HTTPS traffic. Malicious and phishing websites may remain unblocked if the app installed in the work profile. If the domain is trusted, Web Protection can skip a threat (for example, https://trusted.domain.com/phishing/). If the domain is untrusted, Web Protection blocks malicious and phishing websites.
  • For Web Protection to work, you must enable the use of Kaspersky Security Network. Web Protection blocks websites based on the KSN data on the reputation and category of websites.
  • Forbidden websites may remain unblocked by Web Protection on devices running Android 6.0 with Google Chrome version 51 (or any earlier version) installed if the website is opened in the following ways (this issue is caused by a well-known defect in Google Chrome):
    • From search results.
    • From the bookmarks list.
    • From search history.
    • Using the web address autocomplete function.
    • Opening the website in a new tab in Google Chrome.
  • Forbidden websites may remain unblocked in Google Chrome version 50 (or any earlier version) if the website is opened from Google search results while the Merge Tabs and Apps feature is enabled in the browser settings. This issue is caused by a well-known defect in Google Chrome.
  • Websites from blocked categories may remain unblocked in Google Chrome if the user opens them from third-party apps, for example, from an IM client app. This issue is related to how the Accessibility service works with the Chrome Custom Tabs feature.
  • Forbidden websites may remain unblocked in Samsung Internet Browser if the user opens them in background mode from the context menu or from third-party apps, for example, from an IM client app.
  • Kaspersky Endpoint Security for Android must be set as an Accessibility feature to ensure proper functioning of Web Protection.
  • On some Xiaomi devices, the "Display pop-up window" and "Display pop-up windows while running in the background" permissions should be granted for Web Protection to work.
  • When entering a website address in Web Protection settings, adhere to the following rules:
    • For Android devices, specify the address in regular expressions format (for example, https://example.com.*).
    • For iOS MDM devices, specify the HTTP or HTTPS data transport protocol (for example, http://www.example.com).
  • Allowed websites may be blocked in Samsung Internet Browser in the Only listed websites are allowed Web Protection mode when the page is refreshed. Websites are blocked if a regular expression contains advanced settings (for example, ^https?://example.com/pictures/). It is recommended to use regular expressions without additional settings (for example, ^https?://example.com).
  • If Web Protection is set to All websites are blocked, Kaspersky Endpoint Security for Android does not block search in the Google Search widget. Instead, it blocks user access to the search results.
  • In a work profile, if Web Protection is set to All websites are blocked, Kaspersky Endpoint Security for Android endlessly reloads the Google Chrome home page, blocks the browser, and interferes with the device.

Known issues in Anti-Theft operation

  • For timely delivery of commands to Android devices, the app uses the Firebase Cloud Messaging (FCM) service. If FCM is not configured, commands will be delivered to the device only during synchronization with Kaspersky Security Center according to the schedule defined in the policy, for example, every 24 hours.
  • To lock a device, Kaspersky Endpoint Security for Android must be set as the device administrator.
  • To lock devices running Android 7.0 or later, Kaspersky Endpoint Security for Android must be set as an Accessibility feature.
  • On some devices, Anti-Theft commands may fail to execute if Battery Saver mode is enabled on the device. This defect has been confirmed on Alcatel 5080X.
  • To locate devices running Android 10.0 or later, the user must grant the "All the time" permission to device location.
  • To take a mugshot with devices running Android 11.0 or later, the user must grant the "While using the app" permission to access the camera.

Known issues in App Control operation

  • Kaspersky Endpoint Security for Android must be set as an Accessibility feature to ensure proper functioning of App Control. This does not apply to device owner mode.
  • For App Control (app categories) to work, you must enable the use of Kaspersky Security Network. App Control determines the category of an app based on data that is available in KSN. To use KSN, the mobile device must be connected to the internet. For App Control, you can add individual apps to the lists of blocked and allowed apps. In this case, KSN is not required.
  • When configuring App Control, it is recommended to clear the Block system apps check box. Blocking system apps may lead to problems in device operation.
  • On iOS MDM devices, if you specify allowed apps in the list of apps allowed to be installed, all apps except system apps and those added to the list of allowed apps will be hidden on the device screen.

Known issues when configuring certificates in iOS MDM policy

  • When you add a certificate to an iOS MDM policy and attempt to save or close the policy, MMC-based Administration Console of Kaspersky Security Center may crash, but the certificate is saved to the policy settings.

Known issues when configuring email

  • Remote configuration of a mailbox is available only on the following devices:
    • iOS MDM devices.
    • Samsung devices (Exchange ActiveSync).
    • Android devices with the TouchDown mail client installed.

      In previous versions of Kaspersky Endpoint Security for Android, you can use Kaspersky Security Center to remotely configure TouchDown profile settings on a user's device. TouchDown support has been discontinued in Kaspersky Endpoint Security for Android Service Pack 4. For more detail, refer to the Symantec technical support website.

      After upgrading the Kaspersky Endpoint Security for Android Administration Plug-in, the TouchDown settings in the policy are hidden but saved. When new devices are connected, TouchDown settings will be configured after the policy is applied.

      After the policy is modified and saved, TouchDown settings will be deleted. The TouchDown settings on a user's devices will be cleared after a policy is applied.

Known issues when configuring device unlock password strength

  • On devices running Android 10.0 or later, Kaspersky Endpoint Security resolves the password strength requirements into one of the system values: medium or high.

    If the password length required is 1 to 4 symbols, then the app prompts the user to set a medium-strength password. It must be either numeric (PIN), with no repeating or ordered (e.g. 1234) sequences; or alphanumeric. The PIN or password must be at least 4 characters long.

    If the password length required is 5 or more symbols, then the app prompts the user to set a high-strength password. It must be either numeric (PIN), with no repeating or ordered sequences; or alphanumeric (password). The PIN must be at least 8 digits long; the password must be at least 6 characters long.

  • On devices running Android 10.0 or later, using a fingerprint to unlock the screen can be managed for work profile only.
  • On devices running Android 7.1.1, if the unlock password does not meet the corporate security requirements (Compliance Control), the Settings system app may function improperly when an attempt is made to change the unlock password through Kaspersky Endpoint Security for Android. The issue is caused by a well-known defect in Android 7.1.1. In this case, to change the unlock password, use the Settings system app only.
  • On some devices running Android 6.0 or later, an error may occur when screen unlock password is entered, if device data is encrypted. This issue is related to specific features of the Accessibility service with MIUI firmware.

Known issues when configuring Wi-Fi

  • On devices running Android version 8.0 or later, settings of the proxy server for Wi-Fi cannot be redefined with the policy. However, you can manually configure the proxy server settings for a Wi-Fi network on the mobile device.

Known issues when configuring APN

  • Remote configuration of APN is available only on iOS MDM devices or Samsung devices.
  • Configure APN for iOS MDM devices in the Cellular communications section. The APN section is out of date. Before configuring the APN settings, make sure that the Apply on device check box in the APN section is cleared.

Known issues with Firewall

  • Use of Firewall is available only on Samsung devices.

Known issues when configuring VPN

  • Remote configuration of VPN is available only on the following devices:
    • iOS MDM devices.
    • Samsung devices.
  • When you set up a VPN connection for selected domains in Safari, if you change the Connect automatically option, the changes are not applied on the device. The Connect automatically check box is selected by default and we recommend against changing it if you want to activate a VPN automatically for specified domains.

Known issues when working with containers

  • In Kaspersky Security for Mobile Service Pack 3 Maintenance Release 2, there is no longer support for creating containers for mobile apps. However, containers that were created in earlier versions of the application can be added to Android devices.
  • To install containerized apps, installation of apps from unknown sources must be allowed on the user's mobile device. For details about installing apps without Google Play, please refer to the Android Help Guide.
  • App containerization is not supported on Android devices for apps that contain more than 65,536 methods (multidex configuration).

Known issues with App removal protection

  • Kaspersky Endpoint Security for Android must be set as the device administrator.
  • To protect the app from removal on devices running Android 7.0 or later, Kaspersky Endpoint Security for Android must be set as an Accessibility feature.
  • On some Xiaomi and Huawei devices, Kaspersky Endpoint Security for Android removal protection does not work. This issue is caused by the specific features of MIUI 7 and 8 firmware on Xiaomi and EMUI firmware on Huawei.

Known issues when configuring device restrictions

  • On devices running Android 10.0 or later, prohibiting the use of Wi-Fi networks is not supported.
  • On devices running Android 10.0 or later, the use of the camera cannot be completely prohibited.
  • On devices running Android 11 or later, Kaspersky Endpoint Security for Android must be set as an Accessibility feature. Kaspersky Endpoint Security for Android prompts the user to set the app as an Accessibility feature through the Initial Configuration Wizard. The user can skip this step or disable this service in the device settings at a later time. If this is the case, you will not be able to restrict use of the camera.

Known issues when sending commands to mobile devices

  • On devices running Android 12 or later, if the user granted the "Use approximate location" permission, the Kaspersky Endpoint Security for Android app first tries to get the precise device location. If this is not successful, the approximate device location is returned only if it was received not more than 30 minutes earlier. Otherwise, the Locate device command fails.

Known issues with Android work profile

  • If you create an Android work profile by using a policy, the user must grant the "Allow access to manage all files" permission to Kaspersky Endpoint Security for Android that is installed on the devices running Android 11 or later and that is related to the work profile.
  • The Prohibit activation of USB debugging mode Android work profile function does not work on devices with Android 13. This is caused by an issue in Android 13.

Known issues with specific devices

  • On certain devices (for example, Huawei, Meizu, and Xiaomi), you must grant Kaspersky Endpoint Security for Android an autostart permission or manually add it to the list of apps that are started when the operating system starts. If the app is not added to the list, Kaspersky Endpoint Security for Android stops performing all of its functions after the mobile device is restarted. In addition, if the device has been locked, you cannot use a command to unlock the device. You can unlock the device only by using a one-time unlock code.
  • On certain devices (for example, Meizu and Asus) running Android 6.0 or later, after encrypting data and restarting the Android device, you must enter a numeric password to unlock the device. If the user uses a graphic password to unlock the device, you must convert the graphic password to a numeric password. For more details about converting a graphic password into a numeric password, please refer to the Technical Support website of the mobile device manufacturer. This issue is related to the operation of the Accessibility Features service.
  • On some Huawei devices running Android 5.Х, after Kaspersky Endpoint Security for Android is set as an Accessibility feature, an incorrect message about the lack of appropriate rights may be displayed. To hide this message, enable the app as a protected app in the device settings.
  • On some Huawei devices running Android 5.X or 6.X, when Battery Saver mode is enabled for Kaspersky Endpoint Security for Android, the user can manually terminate the app. The user device becomes unprotected after that. This issue is due to some features of Huawei software. To restore the device protection, run Kaspersky Endpoint Security for Android manually. It is recommended to disable Battery Saver mode for Kaspersky Endpoint Security for Android in the device settings.
  • On Huawei devices with EMUI firmware running Android 7.0, the user can hide the notification regarding the protection status of Kaspersky Endpoint Security for Android. This issue is due to some features of Huawei software.
  • On some Xiaomi devices, the user can use the Foreground Services Task Manager to stop Kaspersky Endpoint Security for Android from running in the background. This issue is due to some features of Xiaomi software.
  • On some Xiaomi devices, when setting the password length to more than 5 characters in a policy, the user will be prompted to change the screen unlock password instead of the PIN code. You cannot set a PIN code that has more than 5 characters. This issue is due to some features of Xiaomi software.
  • On Xiaomi devices with MIUI firmware running Android 6.0, the Kaspersky Endpoint Security for Android icon may be hidden in the status bar. This issue is due to some features of Xiaomi software. It is recommended to allow the display of notification icons in Notifications settings.
  • On some Nexus devices running Android 6.0.1, the privileges required for proper operation cannot be granted through the Quick Start Wizard of Kaspersky Endpoint Security for Android. This issue is caused by a well-known defect in Security Patch for Android by Google. To ensure proper operation, the required privileges must be manually granted in the device settings.
  • On certain Samsung devices running Android 7.0 or later, when the user attempts to configure unsupported methods for unlocking the device (for example, a graphical password), the device may be locked if the following conditions are met: Kaspersky Endpoint Security for Android removal protection is enabled and screen unlock password strength requirements are set. To unlock the device, you must send a special command to the device.
  • On certain Samsung devices, it is impossible to block the use of fingerprints for unlocking the screen.
  • Web Protection cannot be enabled on some Samsung devices, if the device is connected to a 3G/4G network, has Battery Saver mode enabled and restricts background data. It is recommended to disable the function that restricts background processes in Battery Saver settings.
  • On certain Samsung devices, if the unlock password does not comply with corporate security requirements, Kaspersky Endpoint Security for Android does not block the use of fingerprints for unlocking the screen.
  • After executing Anti-Theft commands (such as Locate, Device Lock, Unlock, and Mugshot), the mobile certificate and the VPN certificate may be deleted on some Samsung devices. The certificates have to be reinstalled to continue. This issue occurs due to the Mobile Device Fundamentals Protection Profile (MDFPP) security standard.
  • On some Honor and Huawei devices, you cannot restrict the use of Bluetooth. When Kaspersky Endpoint Security for Android attempts to restrict the use of Bluetooth, the operating system shows a notification containing the options to reject or allow this restriction. The user can reject this restriction and continue to use Bluetooth.
  • On some Samsung devices, after Kaspersky Endpoint Security is installed or updated from a standalone installation package, KNOX MDM profile activation is unavailable.
  • On Blackview devices, the user can clear the memory for the Kaspersky Endpoint Security for Android app. As a result, the device protection and management are disabled, all defined settings become ineffective, and the Kaspersky Endpoint Security for Android app is removed from the Accessibility features. This is because this vendor's devices provide the customized Recent screens app with elevated privileges. This app can override Kaspersky Endpoint Security for Android settings and cannot be replaced because it is part of the Android operating system.
  • On some Google Pixel devices running Android 11 or earlier, the Kaspersky Endpoint Security for Android app crashes immediately after the start. This is caused by an issue in Android.
  • On some TECNO devices, the user can unlock the device using face scanning, even if this biometric unlock method is prohibited by the policy.
  • On some Sony and Google Pixel devices running Android 13 or later, the Kaspersky Endpoint Security Help, which has information about enabling accessibility is displayed incorrectly.
  • On Samsung Galaxy S23 and S24 series devices Real-Time Protection may not work.

Known issues in app operation on Android 13

  • On Android 13, the user can use the Foreground Services Task Manager to stop Kaspersky Endpoint Security from running in the background. This is caused by a well-known issue in Android 13.
  • On Android 13, the permission to send notifications is requested when the initial app configuration begins. This is due to specifics of the Android 13 operating system.

Known issues when adding web clips

  • The maximum number of web clips that can be added to an Android device depends on the device type. When this number is reached, web clips are no longer added to the Android device.

Known issues in device owner mode

  • On devices running Android 10 or earlier, if you select Prohibit modification of apps in Settings when configuring restrictions for apps and apply the policy, the user still can clear app defaults and stop apps in app settings. This is due to Android operating system specifics.
  • Managing update settings on mobile devices is vendor-specific. On some Android devices, the restriction on manual installation of operating system updates may work incorrectly.
  • The Kaspersky Endpoint Security for Android app can't be installed in device owner mode on the following devices: Honor 30i (Android 10), Huawei y8p, Huawei Y5 (Android 8), Huawei Mate 40 PRO (Android 10), Xiaomi Redmi 4X (Android 7.1), Honor 5c (Android 7.0, EMUI 5.0). This is due to the device firmware specifics: the QR code scanner is not available after the device is reset to factory settings.
  • On devices with Android 10, location permissions are automatically set to Allow only while using the app instead of Allow all the time and can't be changed by the administrator or users. This issue is caused by a well-known bug in Android 10.
  • The Prohibit screen capture restriction does not block the device user from capturing the device settings screen.
Page top

[Topic 136255]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Deployment

This Help section is intended for specialists who install Kaspersky Security for Mobile, as well as for specialists who provide technical support to organizations that use Kaspersky Security for Mobile.

In this section

Solution architecture

Common integrated solution deployment scenarios

Preparing the Administration Console for deployment of the integrated solution

Installing Kaspersky Endpoint Security for Android

Activating the Kaspersky Endpoint Security for Android app

Installing an iOS MDM profile

Installing administration plug-ins

Updating a previous version of the application

Removal of Kaspersky Endpoint Security for Android

Page top

[Topic 98741]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Solution architecture

Kaspersky Security for Mobile includes the following components:

  • Kaspersky Endpoint Security for Android mobile app

    The Kaspersky Endpoint Security for Android app ensures protection of mobile devices against web threats, viruses, and other programs that pose threats. It supports interaction between the mobile device and the Kaspersky Security Center Administration Server using Firebase Cloud Messaging.

  • Kaspersky Endpoint Security for Android Administration Plug-in

    The Administration Plug-in of Kaspersky Endpoint Security for Android provides the interface for managing mobile devices and mobile apps installed on them through the Administration Console of Kaspersky Security Center.

  • Kaspersky Device Management for iOS Administration Plug-in

    The Administration Plug-in of Kaspersky Device Management for iOS provides an interface for managing mobile devices connected by means of the iOS MDM protocol through the Administration Console of Kaspersky Security Center.

The architecture of the Kaspersky Security for Mobile integrated solution is shown in the figure below.

KSM_schema_architector

The architecture of Kaspersky Security for Mobile

For details on Administration Console, Administration Server, and iOS MDM Server, please refer to Kaspersky Security Center Help.

Page top

[Topic 65441]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Common integrated solution deployment scenarios

This section covers the common deployment scenarios for the Kaspersky Security for Mobile integrated solution.

Different deployment scenarios can be used to deploy the integrated solution on Android devices and iOS devices. If the organization uses mobile devices running various operating systems, apps should be installed for each operating system separately by following the appropriate deployment scenario.

In this section

Deployment scenarios for Kaspersky Endpoint Security for Android

Deployment scenarios for iOS MDM profile

Page top

[Topic 99483]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Deployment scenarios for Kaspersky Endpoint Security for Android

Kaspersky Endpoint Security for Android can be deployed on mobile devices within the corporate network in several ways. You can use the most suitable deployment scenario for your organization or combine several deployment scenarios.

For details on deploying Kaspersky Endpoint Security for Android in Kaspersky Endpoint Security Cloud, please refer to Kaspersky Endpoint Security Cloud help.

Deploying Kaspersky Endpoint Security for Android via Kaspersky Security Center on personal devices

For personal devices, you can deploy Kaspersky Endpoint Security for Android via Kaspersky Security Center by using the following methods:

  • Deliver messages with the Google Play link (recommended)
  • Deliver messages with a link to the installation package in Kaspersky Security Center

Deployment of Kaspersky Endpoint Security for Android using Google Play consists in sending messages containing the Google Play link to users of devices from the Administration Console.

To deploy Kaspersky Endpoint Security for Android via the installation package, do the following:

  1. Create and configure an app installation package.
  2. Create a standalone installation package.
  3. Send messages with a link for downloading a standalone installation package to users of Android devices. Mass mailing is available.

The user installs Kaspersky Endpoint Security for Android on a mobile device after receiving a message with a Google Play link or a link for downloading the installation package from the Kaspersky Security Center server. No additional preparations are needed to begin using the app.

Deploying Kaspersky Endpoint Security for Android via Kaspersky Security Center on company-owned devices (device owner mode)

For company-owned devices (device owner mode), you can deploy Kaspersky Endpoint Security for Android via Kaspersky Security Center by using the following method:

  • Deliver the QR code with a link to a general app version (APK installation file)
  • Deliver the QR code with a link to the installation package in Kaspersky Security Center

To deploy Kaspersky Endpoint Security for Android in device owner mode via the general app version, do the following:

  1. Create a QR code for app installation from the Administration Console.
  2. Pre-configure the mobile device and install Kaspersky Endpoint Security for Android using the QR code.

To deploy Kaspersky Endpoint Security for Android in device owner mode via the installation package, do the following:

  1. Create and configure an app installation package.
  2. Create a standalone installation package.
  3. Create a QR code for app installation via the installation package.
  4. Pre-configure the mobile device and install Kaspersky Endpoint Security for Android using the QR code.

Deploying Kaspersky Endpoint Security for Android from Google Play

Kaspersky Endpoint Security for Android is installed from Google Play independently by the users of devices. Users download the mobile app distribution package from Google Play and install the app on devices. After the app has been installed on the device, you need to make additional preparations before you can begin using it: configure the settings of the connection to the Administration Server and install a mobile certificate.

Deploying Kaspersky Endpoint Security for Android via KNOX Mobile Enrollment

Deployment of Kaspersky Endpoint Security for Android consists of adding a KNOX MDM profile to mobile devices. The KNOX MDM profile contains a link to an app deployed on the Kaspersky Security Center Web Server or another server. After the app is installed on the mobile device, you must also install a mobile certificate.

You can read about installation through KNOX Mobile Enrollment in the Samsung KNOX section.

Page top

[Topic 141784]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Deployment scenarios for iOS MDM profile

An iOS MDM profile is a profile that contains the settings for connecting mobile devices running iOS to Kaspersky Security Center. After installation of an iOS MDM profile and synchronization with Kaspersky Security Center, the device becomes a managed device. Mobile devices are managed through the Apple Push Notification service (APNs). For more details on installing an iOS MDM profile and working with APNs, please refer to Kaspersky Security Center Help.

Using an iOS MDM profile, you can do the following:

  • Remotely configure the settings of iOS MDM devices by using group policies.
  • Send device lock and data wipe commands.
  • Remotely install Kaspersky apps and other third-party apps.

An iOS MDM profile can be deployed on mobile devices within the corporate network in several ways. You can use the most suitable deployment scenario for your organization or combine several deployment scenarios.

Before deploying an iOS MDM profile, the administrator must do the following:

  1. Install an iOS MDM Server.
  2. Obtain an Apple Push Notification Service certificate (APNs certificate).
  3. Install an APNs certificate to the iOS MDM Server.

For more details on installing an iOS MDM Server and working with an APNs certificate, please refer to Kaspersky Security Center help.

For details on deploying an iOS MDM profile in Kaspersky Endpoint Security Cloud, please refer to Kaspersky Endpoint Security Cloud help.

Deploying an iOS MDM profile via Kaspersky Security Center

Deployment of an iOS MDM profile via Kaspersky Security Center can be carried out by sending messages containing a link to download the iOS MDM profile. Mass mailing is available.

The user installs the iOS MDM profile to a mobile device after receiving the message with a link to the Kaspersky Security Center Web Server. No additional preparations for the iOS MDM profile are required.

For more details on creating an iOS MDM profile, please refer to Kaspersky Security Center Help.

Page top

[Topic 99201]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Preparing the Administration Console for deployment of the integrated solution

This section provides instructions on preparing the Administration Console for deployment of the integrated solution.

In this section

Configuring Administration Server settings for connection of mobile devices

Configuring a connection gateway to connect mobile devices to Kaspersky Security Center Administration Server

Displaying the Mobile Device Management folder in the Administration Console

Creating an administration group

Creating a rule for device automatic allocating to administration groups

Creating a mobile certificate

Page top

[Topic 89678]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring Administration Server settings for connection of mobile devices

In order for mobile devices to be able to connect to the Administration Server, before installing the Kaspersky Endpoint Security mobile app configure the mobile device connection settings in the Administration Server properties.

To configure Administration Server settings for connecting mobile devices:

  1. In the context menu of the Administration Server, select Properties.

    The Administration Server settings window opens.

  2. Select Server connection settings → Additional ports.
  3. Select the Open port for mobile devices check box.
  4. In the Port for mobile devices field, specify the port through which mobile devices will connect to the Administration Server.

    Port 13292 is used by default. If the Open port for mobile devices check box is cleared or the wrong connection port is specified, mobile devices will not be able to connect to the Administration Server.

  5. In the Port to activate mobile clients field, specify the port to be used by mobile devices to connect to the Administration Server for activation of the Kaspersky Endpoint Security for Android app. Port 17100 is used by default.
  6. Click OK.
Page top

[Topic 245223_1]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring a connection gateway to connect mobile devices to Kaspersky Security Center Administration Server

This topic describes how to configure a connection gateway to connect mobile devices to Kaspersky Security Center Administration Server. The configuration proceeds in the following steps:

  1. Install Network Agent in the connection gateway role on a host
  2. Configure the connection gateway on Kaspersky Security Center Administration Server

This article contains an overview of the scenario. For detailed instructions, please refer to the Kaspersky Security Center documentation.

Requirements

For a connection gateway to work correctly with mobile devices, the following requirements must be met:

  • Port 13292 must be open on the host with the connection gateway.
  • Port 13000 must be open between the connection gateway and Kaspersky Security Center. It does not need to be open outside the DMZ.
  • The host must have a static address accessible from the internet.

Install Network Agent in the connection gateway role on a host

First, you need to install Network Agent on the selected host device acting in the gateway connection role. You can download a full installation package of Kaspersky Security Center or use a local installation of Kaspersky Security Center.

By default, the installation file is located at: \\<server name>\KLSHARE\PkgInst\NetAgent_<version number>

To install Network Agent in the connection gateway role:

  1. Start the Network Agent Setup Wizard and follow its instructions leaving default values for all of the options until the Select Administration Server window opens.
  2. In the Select Administration Server window, configure the following settings:
    • Enter the address of the device with Administration Server installed.
    • In the Port, SSL port, and UDP port fields, leave the default values.
    • Select the Use SSL to connect to Administration Server check box to establish a connection to the Administration Server through a secure port via SSL.

      We recommend that you do not clear this check box so your connection remains secured.

    • Select the Allow Network Agent to open UDP port check box to manage client devices and receive information about them.
  3. Click Next and proceed through the Wizard with default settings up to the Connection gateway window.
  4. In the Connection gateway window, select Use Network Agent as a connection gateway in DMZ.

    This mode simultaneously activates the connection gateway role and tells Network Agent to wait for connections from Administration Server, rather than establish connections to Administration Server.

  5. Click Next and start the installation.

Network Agent is now installed and configured in the connection gateway role.

Configure the connection gateway on Kaspersky Security Center Administration Server

Once you have installed Network Agent in the connection gateway role, you need to connect it to Administration Server. Administration Server does not yet list the device with the connection gateway among the managed devices because the connection gateway has not tried to connect to Administration Server. Therefore, you need to add the connection gateway as a distribution point to ensure that Administration Server initiates a connection to the connection gateway.

To configure the connection gateway on Administration Server:

  1. Add the connection gateway as a distribution point in Kaspersky Security Center.
    1. In the console tree, select the Administration Server node.
    2. In the context menu of Administration Server, select Properties.
    3. In the Administration Server properties window, select the Distribution points section.
    4. Click the Add button.

      The Add distribution point window opens.

    5. In the Add distribution point window, perform the following actions:
      • Specify the IP address of the device with Network Agent installed in the Device to act as distribution point field. To do this, select Add connection gateway in DMZ by address in the drop-down list.

        Enter the IP address of the connection gateway or enter the name if the connection gateway is accessible by name.

      • In the Distribution point scope field, select the group to which the connection gateway will be distributed from the drop-down list, and then click OK.
    6. In the Distribution points section, click OK to save the changes you have made.

    The connection gateway will be saved as a new entry named Temporary entry for connection gateway.

    Administration Server almost immediately attempts to connect to the connection gateway at the address that you specified. If it succeeds, the entry name changes to the name of the connection gateway device. This process takes up to five minutes.

    While the temporary entry for the connection gateway is being converted to a named entry, the connection gateway also appears in the Unassigned devices group.

  2. Create a new group under the Managed devices group. This new group will contain external managed devices.
  3. Move the connection gateway from the Unassigned devices group to the group that you have created for external devices.
  4. Configure properties of the connection gateway that you have deployed:
    1. In the Distribution points section of the Administration Server properties, select the connection gateway and click Properties.
    2. In the General section, under DNS domain names of the distribution point for access by mobile devices (included in the certificate), specify your connection gateway DNS name that will be used to connect to the mobile device.
    3. In the Connection Gateway section, select the following check boxes and leave the default port numbers:
      • Open port for mobile devices (SSL authentication of the Administration Server only)
      • Open port for mobile devices (two-way SSL authentication)
    4. Click OK to save the changes you have made.

The connection gateway is now configured. You can now add new mobile devices by specifying the connection gateway address. New devices will appear on Administration Server.

Page top

[Topic 89684]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Displaying the Mobile Device Management folder in the Administration Console

By displaying the Mobile Device Management folder in the Administration Console, you can view the list of mobile devices managed by the Administration Server, configure the mobile device management settings, and install certificates on mobile devices of users.

To enable the display of the Mobile Device Management folder in the Administration Console:

  1. In the context menu of the Administration Server, select View → Configuring interface.
  2. In the window that opens, select the Display Mobile Device Management check box.
  3. Click OK.

The Mobile Device Management folder is displayed in the Administration Console tree after the Administration Console is restarted.

Page top

[Topic 89688]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Creating an administration group

To perform centralized configuration of the Kaspersky Endpoint Security for Android app installed on the users' mobile devices, the group policies must be applied to the devices.

To apply the policy to a device group, you are advised to create a separate group for these devices in the Managed devices prior to installing mobile apps on user devices.

After creating an administration group, it is recommended to configure the option to automatically allocate devices on which you want to install the apps to this group. Then configure settings that are common to all devices using a group policy.

To create administration group, follow the steps below:

  1. In the console tree, select the Managed devices folder.
  2. In the workspace of the Managed devices folder or subfolder, select the Devices tab.
  3. Click the New group  button.

    This opens the window in which you can create a new group.

  4. In the Group name window type the group name and click OK.

A new administration group folder with the specified name appears in the console tree. For more detailed information on use of administration groups, see Kaspersky Security Center Help.

Page top

[Topic 89691]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Creating a rule for device automatic allocating to administration groups

You can centrally administer the settings of Kaspersky Endpoint Security for Android app installed on users' mobile devices only if the devices belong to a previously created administration group for which a group policy has been configured.

If the rule to automatically allocate mobile devices detected on the network to the administration group is not configured, during the first synchronization of the device with the Administration Server, the device is automatically sent to the Administration Console in the AdditionalNetwork pollDomainsKES10 folder. A group policy does not apply to this device.

To create the rule for automatic allocating of mobile devices to administration group, follow the steps below:

  1. In the console tree, select the Unassigned devices folder.
  2. From the context menu of the Unassigned devices folder, select Properties.

    The Properties: Unassigned devices window appears.

  3. In the Move devices section, click Add to start the process of creating a rule for automatically allocating devices to an administration group.

    The New rule window appears.

  4. Type the rule name.
  5. Specify the administration group to which mobile devices should be allocated after the Kaspersky Endpoint Security for Android mobile app has been installed on them. To do so, click Browse to the right of the Group to move devices to field and select the group in the window that appears.
  6. In the Rule application section, select Run once for each device.
  7. Select the Move only devices not added to administration groups check box to prevent allocating to the selected group the mobile devices that were allocated to other administration groups when applying the rule.
  8. Select the Enable rule check box, so that the rule can be applied to newly detected devices.
  9. Open the Apps section and do the following:
    1. Select the Operating system version check box.
    2. Select one or several types of operating systems of the devices to be allocated to the specified group: Android or iOS.
  10. Click OK.

The newly created rule is displayed in the list of device allocation rules in the Move devices section in the properties window of the Unassigned devices folder.

According to the rule, Kaspersky Security Center allocates all devices that meet the specified requirements from the Unassigned devices folder to the selected group. The mobile devices which were earlier allocated to the Unassigned devices folder can also be allocated to the required administration group of the Managed devices folder manually. For more detailed information on administration groups management and actions with undistributed devices, see Kaspersky Security Center Help.

Page top

[Topic 89730]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Creating a mobile certificate

You have to create a mobile certificate in Administration Console for the purpose of identifying the user of a mobile device.

To create a mobile certificate:

  1. In the console tree, select the Mobile Device Management → Certificates folder.
  2. In the workspace of the Certificates folder, click the Add certificate button to start the Certificate Installation Wizard.
  3. In the Certificate type window of the Wizard, select the Mobile certificate option.
  4. In the User selection window of the Wizard, specify the users for whom you want to create a mobile certificate.
  5. In the Certificate source window of the Wizard, select the method by which the mobile certificate is created.
    • To create a mobile certificate automatically using Administration Server tools, select Issue certificate through Administration Server tools.
    • To assign a previously created certificate to a user, select the Specify certificate file option. Click the Specify button to open the Certificate window and specify the certificate file in it.

      Clear the Publish certificate check box if you do not want to specify the type of mobile device and the method of notifying the user about certificate creation.

  6. In the Method of user notification window of the Wizard, configure the settings of mobile device user notification about certificate creation using a text message or via email.
  7. In the Generating the certificate window of the Wizard, click Done to finish the Certificate Installation Wizard.

As a result, the Certificate Installation Wizard creates a mobile certificate that the user can install on the mobile device. To get the certificate, start synchronization of the mobile device with the Administration Server. For more information about creating certificates and configuring rules for issuing them, refer to Kaspersky Security Center help.

Page top

[Topic 141433]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Installing Kaspersky Endpoint Security for Android

This section describes the methods for deploying Kaspersky Endpoint Security for Android on a corporate network.

In this section

Permissions

Installation of Kaspersky Endpoint Security for Android using a Google Play link

Installation of Kaspersky Endpoint Security for Android in device owner mode

Other methods of installation of Kaspersky Endpoint Security for Android

Configuring synchronization settings

Page top

[Topic 150051]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Permissions

For all features of apps, Kaspersky Endpoint Security for Android prompts the user for the required permissions. Kaspersky Endpoint Security for Android prompts for the mandatory permissions while completing the Setup Wizard, as well as after installation prior to using individual features of apps. It is impossible to install Kaspersky Endpoint Security for Android without providing the mandatory permissions.

On certain devices (for example, Huawei, Meizu, and Xiaomi), you must manually add Kaspersky Endpoint Security for Android to the list of apps that are started when the operating system starts in the device settings. If the app is not added to the list, Kaspersky Endpoint Security for Android stops performing all of its functions after the mobile device is restarted.

On devices running Android 11 or later, you must disable the Remove permissions if app isn't used system setting. Otherwise, after the app is not used for a few months, the system automatically resets the permissions that the user granted to the app.

Permissions requested by Kaspersky Endpoint Security for Android

Permission

App function

Phone (for Android 5.0 – 9.X)

Connect to Kaspersky Security Center (device ID)

Storage (mandatory)

Anti-Virus

Access to manage all files (for Android 11 or later)

Anti-Virus

Nearby Bluetooth devices (for Android 12 or later)

Restrict use of Bluetooth

Notifications (for Android 13)

Notify the user about security issues and app events

Allow running in the background (for Android 12 or later)

Ensure continuous operation of the app. If permission is not granted, the app may be unloaded from memory and unable to restart.

Device administrator (mandatory)

 

Anti-Theft – lock the device (only for Android 5.0 – 6.X)

Anti-Theft – take a mugshot with frontal camera

Anti-Theft – sound an alarm

Anti-Theft – full reset

Password protection

App removal protection

Install security certificate

App Control

Manage KNOX (only for Samsung devices)

Configure Wi-Fi

Configure Exchange ActiveSync

Restrict use of the camera, Bluetooth, and Wi-Fi

 

 

Camera

Anti-Theft – take a mugshot with frontal camera

On devices running Android 11.0 or later, the user must grant the "While using the app" permission when prompted.

Location

Anti-Theft – locate device

On devices running Android 10.0 or later, the user must grant the "All the time" permission when prompted.

Accessibility

Anti-Theft – lock the device (only for Android 7.0 or later)

Web Protection

App Control

App removal protection (only for Android 7.0 or later)

Display of warnings of Kaspersky Endpoint Security for Android (only for Android 10.0 or later)

Restrict use of the camera (only for Android 11 or later)

 

 

Display pop-up window (for some Xiaomi devices)

Web Protection

Display pop-up windows while running in the background (for some Xiaomi devices)

Web Protection

Page top

[Topic 141434]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Installation of Kaspersky Endpoint Security for Android using a Google Play link

Kaspersky Endpoint Security for Android is installed on the mobile devices of users whose user accounts have been added in Kaspersky Security Center. For more details about user accounts in Kaspersky Security Center, please refer to Kaspersky Security Center Help.

Kaspersky Security for Mobile lets you install the app through Kaspersky Security Center by using a Google Play link (recommended method).

The user will receive a link to Google Play. The app can be installed by following the standard installation procedure on the Android platform. Additional configuration of Kaspersky Endpoint Security for Android after installation is not required.

Some Huawei and Honor devices do not have Google services and therefore an access to apps in Google Play. If some users of Huawei and Honor devices cannot install the app from Google Play, they should be instructed to install the app from Huawei App Gallery.

The link contains the following data:

  • Kaspersky Security Center synchronization settings.
  • Mobile certificate.
  • Indicator of acceptance of the Terms and Conditions of the End User License Agreement for Kaspersky Endpoint Security for Android and additional Statements. If the administrator accepts the terms of License Agreement and additional Statements in the Administration Console, Kaspersky Endpoint Security for Android skips the acceptance step during installation of the app.

To install Kaspersky Endpoint Security for Android through Kaspersky Security Center using a Google Play link:

  1. In the console tree, select the Mobile Device ManagementMobile devices folder.
  2. In the workspace of the Mobile devices folder, click the Add mobile device button.

    This starts the New Mobile Device Connection Wizard. Follow the instructions of the Wizard.

  3. In the Operating system section, select Android.
  4. In the Device type section, select Personal device.

    Kaspersky Security Center checks for administration plug-in updates. If Kaspersky Security Center detects updates, you can install the new version of the administration plug-in. When the administration plug-in is updated, you can accept the Terms and Conditions of the End User of the License Agreement (EULA) and additional Statements for Kaspersky Endpoint Security for Android. If the administrator accepts the License Agreement and additional Statements in Administration Console, Kaspersky Endpoint Security for Android skips the acceptance step during installation of the app. This feature is available in Kaspersky Security Center version 12.

  5. On the Kaspersky Endpoint Security for Android installation method page, select Link to an app version on Google Play.
  6. On the Select users page of the Wizard, select one or more users for installation of Kaspersky Endpoint Security for Android to their mobile devices.

    If a user is not in the list, you can add a new user account without exiting the New Mobile Device Connection Wizard.

  7. On the Certificate source page of the Wizard, select the source of the certificate for protection of data transfer between Kaspersky Endpoint Security for Android and Kaspersky Security Center:
    • Issue certificate through Administration Server tools. In this case, the certificate will be created automatically.
    • Specify certificate file. In this case, your own certificate must be prepared ahead of time and then selected in the window of the Wizard. This option cannot be used if you want to install Kaspersky Endpoint Security for Android to several mobile devices. A separate certificate must be created for each user.
  8. On the User notification method page of the Wizard, select the channel used to forward the app installation link:
    • To send the link by email, select Send link to Kaspersky Endpoint Security and configure the settings in the By email section. Make sure that the email address is specified in the settings of user accounts.
    • To install Kaspersky Endpoint Security for Android using a QR code, select Show link to installation package and scan the QR code using the camera of the mobile device.
    • If none of the listed methods are suitable for you, select Show link to installation packageCopy to copy the link for installing Kaspersky Endpoint Security for Android to the clipboard. Use any available method to deliver the app installation link. You can also use other methods of installation of Kaspersky Endpoint Security for Android.
  9. Click Finish to close the New Mobile Device Connection Wizard.

After installing Kaspersky Endpoint Security for Android on users' mobile devices, you will be able to configure the settings for devices and apps by using group policies. You will also be able to send commands to mobile devices for data protection in case devices are lost or stolen.

Page top

[Topic 241804]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Installation of Kaspersky Endpoint Security for Android in device owner mode

Device owner mode is the device operation mode for company-owned Android devices. This mode lets you have full control over the entire device and configure a wide range of device functions. Device owner mode is supported on Android 7.0 or later.

Kaspersky Security Center lets you install the Kaspersky Endpoint Security for Android app in device owner mode by generating a QR code for app installation on the device.

Kaspersky Endpoint Security for Android is installed on the mobile devices of users whose user accounts have been added in Kaspersky Security Center. For more details about user accounts in Kaspersky Security Center, please refer to Kaspersky Security Center Help.

Ways to install the app

The Kaspersky Endpoint Security for Android app can be installed via a QR code that includes one of the following:

  • Link to a general app version

    Choose this method for mobile devices that can access the internet to download the APK installation file from the Kaspersky website. The app will then be updated using Google Play or Huawei AppGallery.

  • Link to the installation package in Kaspersky Security Center

    Choose this method for mobile devices with no access to the internet. The app's installation package will be downloaded from the Kaspersky Security Center server. The app will also be updated through Kaspersky Security Center using policy settings.

    For this method, follow the steps below before generating a QR-code:

    1. Create and configure an app installation package.
    2. Create a standalone installation package.

Generating QR code for app installation

To generate a QR code for app installation in device owner mode:

  1. In the console tree, select the Mobile Device ManagementMobile devices folder.
  2. In the workspace of the Mobile devices folder, click the Add mobile device button.

    This starts the New Mobile Device Connection Wizard. Follow the instructions of the Wizard.

  3. In the Operating system section, select Android.
  4. In the Device type section, select Company-owned device (device owner mode).
  5. In the Additional section, select the required options:
    • Select the Enable all system apps check box if you want system apps to be active on the device. If the check box is cleared, all system apps are disabled.
    • Select the Allow use of mobile network to download Kaspersky Endpoint Security check box if you want to use mobile data for downloading the Kaspersky Endpoint Security for Android app. The option is supported on devices with Android 8 and later. If the check box is cleared, the app will be downloaded when the device is connected to Wi-Fi.
  6. Click Next.

    Kaspersky Security Center checks for administration plug-in updates. If Kaspersky Security Center detects updates, you can install the new version of the administration plug-in. When the administration plug-in is updated, you can accept the Terms and Conditions of the End User of the License Agreement (EULA) and additional Statements for Kaspersky Endpoint Security for Android. If the administrator accepts the License Agreement and additional Statements in Administration Console, Kaspersky Endpoint Security for Android skips the acceptance step during installation of the app.

  7. On the Method to install Kaspersky Endpoint Security for Android in device owner mode page, select an installation method:
    • Link to a general app version
    • Link to the installation package in Kaspersky Security Center

      If you choose this option, leave the Allow HTTP use for app download in device owner mode check box selected to ensure the app is downloaded. Otherwise, the app will be downloaded via HTTPS only if the Kaspersky Security Center Web Server certificate was issued by a trusted certificate authority.

    For more details about these methods, see the Ways to install the app section above.

  8. On the Select users page of the Wizard, select one or more users for installation of Kaspersky Endpoint Security for Android to their mobile devices.

    If a user is not in the list, you can add a new user account without exiting the New Mobile Device Connection Wizard.

  9. On the Certificate source page of the Wizard, select the source of the certificate for protection of data transfer between Kaspersky Endpoint Security for Android and Kaspersky Security Center:
    • Issue certificate through Administration Server tools. In this case, the certificate will be created automatically.
    • Specify certificate file. In this case, your own certificate must be prepared ahead of time and then selected in the window of the Wizard. This option cannot be used if you want to install Kaspersky Endpoint Security for Android to several mobile devices. A separate certificate must be created for each user.
  10. On the User notification method page, specify email addresses. Make sure that the email address is specified in the user account settings in Kaspersky Security Center.
  11. On the Result page, verify the information and save the QR code.
  12. Click Finish to close the New Mobile Device Connection Wizard.

Additional configuration on the Android device is required to install Kaspersky Endpoint Security for Android in device owner mode.

After installing Kaspersky Endpoint Security for Android on users' mobile devices, you will be able to configure the settings for devices and apps by using group policies. You will also be able to send commands to mobile devices for data protection in case devices are lost or stolen.

Page top

[Topic 209663]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Other methods of installation of Kaspersky Endpoint Security for Android

You can install Kaspersky Endpoint Security for Android using a link to your own web server or instruct the users to install the app manually.

In this section

Manual installation from Google Play or Huawei AppGallery

Creating and configuring an installation package

Creating a standalone installation package

Page top

[Topic 209665]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Manual installation from Google Play or Huawei AppGallery

Users can manually install Kaspersky Endpoint Security for Android from Google Play or Huawei AppGallery. The app can be installed by following the standard installation procedure of the Android platform. Users use their own Google accounts to install the application.

For details on the procedure of installing Kaspersky Endpoint Security for Android from Google Play, see the Google technical support website.

For details on the procedure of installing Kaspersky Endpoint Security for Android from Huawei AppGallery, see the HUAWEI Support website.

Some Huawei and Honor devices do not have Google services and therefore an access to apps in Google Play. If some users of Huawei and Honor devices cannot install the app from Google Play, they should be instructed to install the app from Huawei App Gallery.

After installing Kaspersky Endpoint Security for Android from Google Play or Huawei AppGallery, you must prepare the app for use. The process of preparing the app for use includes the following steps:

  1. The administrator sends the settings of mobile device synchronization with the Administration Server (server address and port number) using any available method (for example, by sending an email message).
  2. The user can configure the settings of mobile device synchronization with the Administration Server during operation of the Initial Configuration Wizard or in the Kaspersky Endpoint Security for Android settings.
  3. The administrator creates a mobile certificate for the mobile device user.
  4. The user receives an automatic notification with a prompt to install the mobile certificate. When installation is confirmed, the mobile certificate is installed on the mobile device.

Internet access should be enabled on the mobile device for synchronization with the Administration Server.

See the Kaspersky Security Center Help for details on how to configure the settings of mobile device synchronization with the Administration Server and receive a mobile certificate.

During the next synchronization of the mobile device with Administration Server, the user's mobile device on which Kaspersky Endpoint Security for Android is installed is moved to the Additional → Network poll → Domains folder in the administration group that was specified during installation of the application (the default group is KES10). You can move a mobile device to the administration group that you created in the Managed devices folder either manually or using automatic allocation rules.

This installation method is convenient if you want to install a specific version of Kaspersky Endpoint Security for Android.

To install Kaspersky Endpoint Security for Android using a link to your own web server:

  1. Create an installation package and configure its settings.

    The installation package is a set of files created for remote installation of the Kaspersky app through Kaspersky Security Center.

  2. Create a standalone installation package.

    A standalone installation package is the installation file of a mobile app that contains the settings of the app connection to the Administration Server and an indicator of acceptance of the Terms and Conditions of the End User License Agreement (EULA) for the Kaspersky Endpoint Security for Android. It is created on the basis of the Kaspersky Endpoint Security for Android installation package. The standalone installation package is a special case of an installation package.

The user will receive a link to the web server hosting the standalone installation package for Kaspersky Endpoint Security for Android. To install the app, the user must run the APK file. Additional configuration of Kaspersky Endpoint Security for Android after installation is not required.

To install Kaspersky Endpoint Security for Android using a link to your own web server, installation of apps from unknown sources must be allowed on the user's mobile device.

Page top

[Topic 89690]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Creating and configuring an installation package

The Kaspersky Endpoint Security for Android installation package is the sc_package.exe self-extracting archive. The archive includes files required for installing mobile app on devices:

  • adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll – Set of files required for installing Kaspersky Endpoint Security for Android.
  • installer.ini – Configuration file that contains the Administration Server connection settings.
  • KES10_xx_xx_xxx.apk – Setup file for Kaspersky Endpoint Security for Android.
  • kmlisten.exe – Utility for delivering the application installation package through a the workstation.
  • kmlisten.ini – Configuration file that contains the settings for the installation package delivery utility.
  • kmlisten.kpd – Application description file.

To create the Kaspersky Endpoint Security for Android installation package:

  1. In the console tree, select the AdditionalRemote installationInstallation packages folder.
  2. In the workspace of the Installation packages  folder, click the Create installation package button.

    The Installation Package Creation Wizard starts. Follow the instructions of the Wizard.

  3. In the Select installation package type window of the Wizard, click the Create installation package for Kaspersky application button.
  4. In the Defining installation package name window of the Wizard, enter the installation package name to be displayed in the workspace of the Installation packages folder.
  5. In the Select application installation package for installation window of the Wizard, select the sc_package.exe self-extracting archive included in the distribution kit.

    If you have already unpacked the archive, choose the application description file, kmlisten.kpd. The application name and the version number appear in the entry field.

  6. In the Accept EULA window of the Wizard, read, understand, and accept the terms and conditions of the End User License Agreement.

    You must accept the terms and conditions of the End User License Agreement for creating the installation package. If you accept the terms of License Agreement in the Administration Console, Kaspersky Endpoint Security for Android skips the acceptance step during installation of the app.

    If you decide to stop the protection of the mobile devices, you can uninstall Kaspersky Endpoint Security for Android app and revoke your End User License Agreement (EULA) for the app. To learn more about revoking EULA, please refer to the Kaspersky Security Center help.

After the Wizard finishes, the created installation package appears in the Installation packages folder workspace. The installation packages are stored in the Packages folder, in the public shared folder on the Administration Server.

To configure the installation package settings:

  1. In the console tree, select the AdditionalRemote installationInstallation packages folder.
  2. In the context menu of the Kaspersky Endpoint Security for Android installation package, select Properties.
  3. On the Settings tab, specify the Administration Server connection settings for mobile devices and the name of the administration group to which the mobile devices will be added automatically after the first synchronization with the Administration Server. Follow the steps below:
    • In the Connection to the Administration Server section, in the Server address field, type the name of the Administration Server for mobile devices in the format that was used for installing Mobile devices support during the Administration Server deployment.

      Depending on the Administration Server name format for the Mobile devices support component, specify the DNS name or the IP address of the Administration Server. In the SSL port number field, specify the number of the port open on the Administration Server for connecting mobile devices. Port 13292 is used by default.

    • In the Allocation of computers to groups section, in the Group name field, type the name of the group to which mobile devices will be added after the first synchronization with the Administration Server (KES10 is used by default).

      The specified group will be automatically created in the AdditionalNetwork pollDomains folder.

    • In the Actions during installation section, select the Request email address check box if you want the app to ask users to provide their corporate email address when the app is started for the first time.

      The user's email address is used to form the name of the mobile device when it is added to the administration group.

  4. To apply the specified settings, click Apply.

Page top

[Topic 89728]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Creating a standalone installation package

To create a standalone installation package, follow the steps below:

  1. In the console tree, select the AdditionalRemote installationInstallation packages folder.
  2. Choose the installation package of Kaspersky Endpoint Security for Android.
  3. In the context menu of the installation package, select Create a standalone installation package.

    The wizard that creates the standalone installation package will be started. Follow the instructions of the Wizard.

  4. Configure ways in which the standalone installation package is distributed:
    • To distribute the path to the created standalone installation package among users via email, in the Further actions section click the link Send the link to the standalone installation package by email.

      The message editor window opens, and the text in the window contains the path to the shared folder with the standalone installation package.

    • To post the link to the created standalone installation package on your corporate website, click the link Sample HTML code for posting link on website.

      A tmp file containing HTML_RJL links opens.

  5. To publish the created standalone installation package on the Kaspersky Security Center Web Server and view the entire list of standalone packages for the selected installation package, in the Standalone installation package wizard completed successfully window select the Open the stand-alone packages list check box.

After the wizard closes, the window List of standalone packages for the installation package <Installation package name> opens.

The List of standalone packages for the installation package <Installation package name> window contains the following information:

  • A list of standalone installation packages.
  • The network path to the shared folder in the Path field.
  • The address of the standalone package on the Kaspersky Security Center Web Server in the URL field.

When sending email notifications, you can specify either the address in the URL field or the path in the Path field as a resource from which users can download the setup file of the app. When sending text message notifications to users, you have to specify the download link appearing in the URL field.

You are advised to copy the address of the created standalone package to clipboard and then paste the link to the required installation package into the email or text message notification for users.

Page top

[Topic 88051]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring synchronization settings

To manage mobile devices and receive reports or statistics from mobile devices of users, you must configure the synchronization settings. Mobile device synchronization with Kaspersky Security Center may be performed in the following ways:

  • By schedule. Synchronization by schedule is performed using the HTTP protocol. You can configure the synchronization schedule in the group policy settings. Modifications to group policy settings, commands and tasks will be performed when the device is synchronizing with Kaspersky Security Center according to the schedule, i.e. with a delay. By default, mobile devices are synchronized with the Kaspersky Security Center automatically every 6 hours.

    On Android 12 or later, the app may perform this task later than specified if the device is in battery saver mode.

  • Forced. Forced synchronization is performed using push notifications of the FCM service (Firebase Cloud Messaging). Forced synchronization is primarily intended for timely delivery of commands to a mobile device. If you want to use forced synchronization, make sure that the GSM settings are configured in Kaspersky Security Center. For more information, refer to Kaspersky Security Center help.

To configure the settings of mobile device synchronization with the Kaspersky Security Center:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Synchronization section.
  5. Select the frequency of synchronization in the Synchronize drop-down list.
  6. To disable synchronization of a device with Kaspersky Security Center while roaming, select the Do not synchronize while roaming check box.

    The device user can manually perform synchronization in the app settings (ks4android_settings_buttonSettingsSynchronizationSynchronize).

  7. To hide synchronization settings (server address, port and administration group) from the user in the app settings, clear the Show synchronization settings on device check box. It is impossible to modify hidden settings.
  8. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center. You can manually synchronize the mobile device by using a special command. To learn more about working with commands for mobile devices, please refer to the Kaspersky Security Center help.

Page top

[Topic 136294]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Activating the Kaspersky Endpoint Security for Android app

In Kaspersky Security Center, the license can cover various groups of features. To ensure that the Kaspersky Endpoint Security for Android app is fully functional, the Kaspersky Security Center license purchased by the organization must provide for the Mobile Device Management functionality. The Mobile Device Management functionality is intended for connecting mobile devices to Kaspersky Security Center and managing them.

For detailed information about the licensing of Kaspersky Security Center and licensing options, please refer to Kaspersky Security Center Help.

Activating the Kaspersky Endpoint Security for Android app on a mobile device is done by providing valid license information to the app. License information is delivered to the mobile device, together with the policy, when the device is synchronized with Kaspersky Security Center.

If the activation of the Kaspersky Endpoint Security for Android app is not completed within 30 days from the time of installation on the mobile device, the app is automatically switched to the limited functionality mode. In this mode, most of the app components are not operational. When switched to the limited functionality mode, the app stops performing automatic synchronization with Kaspersky Security Center. Therefore, if the activation of the app has not been completed within 30 days after the installation, the user must synchronize the device with Kaspersky Security Center manually.

If Kaspersky Security Center is not deployed in your organization or is not accessible to mobile devices, users can activate the Kaspersky Endpoint Security for Android app on their devices manually.

To activate the Kaspersky Endpoint Security for Android app:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Licensing section.
  5. In the Licensing section, open the Key drop-down list, and then select the required application activation key from the key storage of the Kaspersky Security Center Administration Server.

    The details of the app for which the license has been purchased are displayed in the field below.

  6. Select the Activate with a key from Kaspersky Security Center storage check box.

    If the app was activated without a key stored in the Kaspersky Security Center storage, Kaspersky Security for Mobile replaces this key with the activation key selected in the Key drop-down list.

  7. To activate the app on the user's mobile device, block changes to settings.
  8. Click the Apply button to save the changes you have made.

    Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center.

Page top

[Topic 141488]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Installing an iOS MDM profile

This section describes the methods of deploying iOS MDM profiles on a corporate network.

Before deploying an iOS MDM profile, the administrator must do the following:

  1. Install an iOS MDM Server.
  2. Obtain an Apple Push Notification Service certificate (APNs certificate).
  3. Install an APNs certificate to the iOS MDM Server.

For more details on installing an iOS MDM Server and working with an APNs certificate, please refer to Kaspersky Security Center help.

For details on deploying an iOS MDM profile in Kaspersky Endpoint Security Cloud, please refer to Kaspersky Endpoint Security Cloud help.

In this section

About iOS device management modes

Installing via Kaspersky Security Center

Page top

[Topic 135822]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

About iOS device management modes

You can deploy an iOS device management system in several different ways. The management mode depends on the owner of the mobile device (personal or corporate) and corporate security requirements. You can choose the management mode that is most suitable for the company, and use several modes at the same time.

Unsupervised devices

Unsupervised iOS devices are employees' personal devices that are connected to Kaspersky Security Center. In this mode, the user is allowed to use a personal Apple ID, work with any apps, and store personal data on the device. You can use a Kaspersky Device Management for iOS group policy to configure access to corporate resources, security settings, and other settings. By default, all iOS devices are unsupervised.

Supervised devices

Supervised iOS devices are corporate devices that are connected to Kaspersky Security Center. Initial configuration of the mobile device is performed in Apple Configurator. Apple Configurator is an application designed to prepare and configure iOS devices. Apple Configurator is installed on a computer running OS X. For more details about working with Apple Configurator, please refer to the Apple Technical Support website. You can use a Kaspersky Device Management for iOS group policy for further configuration. On supervised devices, you can access an extended selection of settings. For example, you can configure Global HTTP Proxy and additional restrictions (for example, blocked use of iMessage and Game Center), and you can block user account modifications.

To work with supervised and unsupervised iOS devices, the iOS MDM Server must have an APNs certificate installed, and an iOS MDM profile must be installed on the mobile devices of users.

Page top

[Topic 141792]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Installing via Kaspersky Security Center

The iOS MDM profile is installed to the mobile devices of users whose user accounts have been added in Kaspersky Security Center. For more details about user accounts in Kaspersky Security Center, please refer to Kaspersky Security Center help.

To install an iOS MDM profile:

  1. In the console tree, select the Mobile Device ManagementMobile devices folder.
  2. In the workspace of the Mobile devices folder, click the Add mobile device button.

    This starts the New Mobile Device Connection Wizard. Follow the instructions of the Wizard.

  3. In the Operating system section, select iOS.
  4. In the iOS MDM device protection method window of the Wizard, select Use iOS MDM profile of iOS MDM Server and specify the iOS MDM profile from the list.
  5. In the Select users window of the Wizard, select one or several users for installation of the iOS MDM profile to their mobile devices.

    If the user is not in the list, you can add a new user account without exiting the New Mobile Device Connection Wizard.

  6. In the Certificate source window of the Wizard, select the source of the certificate for protection of data transfer between the mobile device and Kaspersky Security Center:
    • Issue certificate through Administration Server tools. In this case, the certificate will be created automatically.
    • Specify certificate file. In this case, your own certificate must be prepared ahead of time and then selected in the window of the Wizard. This option cannot be used if you want to install the iOS MDM profile to several mobile devices. A separate certificate must be created for each user.
  7. In the User notification method window of the Wizard, select the channel used to forward the app installation link:
    • To send the link by email, select Send link to iOS MDM profile and configure the settings in the By email section. Make sure that the email address is specified in the settings of user accounts.
    • To install the iOS MDM profile using a QR code, select Show link to installation package and scan the QR code using the camera of the mobile device.
    • If none of the listed methods are suitable for you, select Show link to installation package Copy to copy the iOS MDM profile installation link to the clipboard. Use any available method to deliver the app installation link.
  8. Finish the New Mobile Device Connection Wizard.

After installing the iOS MDM profile to users' mobile devices, you will be able to configure the app settings by using group policies. You will also be able to send commands to mobile devices for data protection in case devices are lost or stolen.

On mobile devices running iOS 12.1 or later, you must manually confirm installation of an iOS MDM profile on the mobile device. You must also grant permission for remote management of the device.

Page top

[Topic 98776]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Installing administration plug-ins

To manage mobile devices, the following administration plug-ins must be installed to the administrator's workstation:

  • The Administration Plug-in of Kaspersky Endpoint Security for Android provides the interface for managing mobile devices and mobile apps installed on them through the Administration Console of Kaspersky Security Center.
  • The Administration Plug-in of Kaspersky Device Management for iOS provides an interface for managing mobile devices connected by means of the iOS MDM protocol through the Administration Console of Kaspersky Security Center.

You can install administration plug-ins by using the following methods:

  • Install an administration plug-in using Quick Start Wizard of Kaspersky Security Center.

    The application automatically prompts you to run the Quick Start Wizard after Administration Server installation, at the first connection to it. You can also start the Quick Start Wizard manually at any time.

    The Quick Start Wizard allows you to accept the Terms and Conditions of the End User License Agreement (EULA) for the Kaspersky Endpoint Security for the Android app in Administration Console. If the administrator accepts the terms of the License Agreement in Administration Console, Kaspersky Endpoint Security for Android skips the acceptance step during installation of the app. For more details on the Quick Start Wizard for Kaspersky Security Center, please refer to Kaspersky Security Center Help.

  • Install the administration plug-in using the list of available distribution packages in Administration Console of Kaspersky Security Center.

    The list of available distribution packages is updated automatically after new versions of Kaspersky applications are released.

  • Download the distribution package from an external source and install the administration plug-in using the EXE file.

    For example, the distribution package of the administration plug-in can be downloaded on the Kaspersky website.

Installing administration plug-ins from the list in Administration Console

To install the administration plug-ins:

  1. In the console tree, select AdvancedRemote installationInstallation packages.
  2. In the workspace, select Additional actionsView current versions of Kaspersky applications.

    This opens the list of up-to-date versions of Kaspersky applications.

  3. In the Mobile devices section, select the Kaspersky Endpoint Security for Android or Kaspersky Device Management for iOS plug-in.
  4. Click Download distribution packages button.

    A plug-in distribution will be downloaded to the computer memory (EXE file).

  5. Run the EXE file and follow the instructions of the Installation Wizard.

Installing administration plug-ins from the distribution package

To install the Kaspersky Endpoint Security for Android Administration Plug-in,

Copy the plug-in installation file klcfinst.exe from the integrated solution distribution package and run it on the administrator's workstation.

The installation is performed by the Wizard, and you do not have to configure the settings.

To install the Kaspersky Device Management for iOS Administration Plug-in,

Copy the plug-in installation file klmdminst.exe from the integrated solution distribution package and run it on the administrator's workstation.

The installation is performed by the Wizard, and you do not have to configure the settings.

You can make sure that the administration plug-ins are installed by viewing the list of installed app administration plug-ins in the properties window of the Administration Server in the AdvancedDetails of application management plug-ins installed section.

Page top

[Topic 136488]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Updating a previous version of the application

The application upgrade must meet the following requirements:

  • The version of the Kaspersky Endpoint Security Administration Plug-in and the version of the Kaspersky Endpoint Security for Android mobile app must match.

    You can view the build numbers of the versions of the Administration Plug-in and mobile app in the Release Notes for Kaspersky Security for Mobile.

  • Make sure that Kaspersky Security Center satisfies the software requirements of Kaspersky Security for Mobile.
  • The administration plug-ins of Kaspersky Endpoint Security 10.0 Service Pack 2 (Build 10.6.0.1801) and Kaspersky Device Management for iOS 10.0 Service Pack 2 (Build 10.6.0.1767) and later versions can be automatically upgraded to the current version. Upgrades of earlier versions of administration plug-ins are not supported.

    To upgrade administration plug-ins of earlier versions, you must remove the installed administration plug-ins and group policies that were created with them. Then install the new versions of the administration plug-ins. For details on removing administration plug-ins, please visit the Kaspersky Technical Support website.

  • Use the same version of Kaspersky Endpoint Security for Android on all mobile devices of the organization.

The terms and conditions of technical support for Kaspersky Security for Mobile versions are available on the Kaspersky Technical Support website.

To view the version and build number of administration plug-ins:

  1. In the console tree in the context menu of the Administration Server, select Properties.
  2. In the Administration Server properties window, select AdvancedDetails of application management plug-ins installed.

The workspace displays information about installed administration plug-ins in the format <Plug-in name> <Version> <Build>.

You can view the version and build number of the Kaspersky Endpoint Security for Android app by using the following methods:

Updates functionality (including providing anti-virus signature updates and codebase updates), as well as KSN functionality will not be available in the software in the U.S. territory from 12:00 AM Eastern Daylight Time (EDT) on September 10, 2024 in accordance with the restrictive measures.

In this section

Upgrading the previous version of Kaspersky Endpoint Security for Android

Installing an earlier version of Kaspersky Endpoint Security for Android

Upgrading previous versions of administration plug-ins

Page top

[Topic 102240]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Upgrading the previous version of Kaspersky Endpoint Security for Android

Kaspersky Endpoint Security for Android can be updated in the following ways:

  • Using Google Play. The mobile device user downloads the new version of the app from Google Play and installs it on the device.
  • Using Kaspersky Security Center. You can remotely update the version of the app on the device using the Kaspersky Security Center remote administration system.

You can select the app update method that is most suitable for your organization. You can use only one update method.

Updating the app from Google Play

The app can be updated from Google Play by following the standard update procedure of the Android platform. The following conditions must be met in order for the app to be updated:

  • The device user must have a Google account.
  • The device must be linked to your Google account.
  • The device must be connected to the internet.

After downloading the app from Google Play, Kaspersky Endpoint Security for Android checks the Terms and Conditions of the End User License Agreement (EULA). If the terms of the EULA are updated, the app sends a request to the Kaspersky Security Center. If the administrator accepts the EULA in Administration Console, Kaspersky Endpoint Security for Android skips the acceptance step during installation of the app. If the administrator uses an outdated version of the administration plug-in, Kaspersky Security Center prompts you to update the administration plug-in. When updating the administration plug-in, an administrator can accept the terms of the EULA in Administration Console for the Kaspersky Endpoint Security for Android.

You can update the app through Google Play if Kaspersky Endpoint Security for Android was installed from Google Play. If the app was installed using another method, you cannot update the app through Google Play.

Updating the app through Kaspersky Security Center

Kaspersky Endpoint Security for Android can be upgraded using Kaspersky Security Center after application of a group policy. In the group policy settings, you can select the Kaspersky Endpoint Security for the Android standalone installation package of the version that meets the corporate security requirements.

You can update through Kaspersky Security Center if Kaspersky Endpoint Security for Android was installed through Kaspersky Security Center. If the app was installed from Google Play, you cannot update the app through Kaspersky Security Center.

To upgrade Kaspersky Endpoint Security for Android using a standalone installation package, installation of apps from unknown sources must be allowed on the user's mobile device. For details about installing apps without Google Play, please refer to the Android Help Guide.

To update the version of the app:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Additional section.
  5. In the Upgrading Kaspersky Endpoint Security for Android section, click the Select button.

    This opens the Upgrading Kaspersky Endpoint Security for Android window.

  6. In the list of Kaspersky Endpoint Security standalone installation packages, select the package whose version meets the corporate security requirements.

    You can upgrade Kaspersky Endpoint Security only to a more recent application version. Kaspersky Endpoint Security cannot be upgraded to an older application version.

  7. Click the Select button.

    A description of the selected standalone installation package is displayed in the Upgrading Kaspersky Endpoint Security for Android section.

  8. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center. The mobile device user is prompted to install the new version of the app. After the user gives consent, the new app version is installed on the mobile device.

Page top

[Topic 180201]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Installing an earlier version of Kaspersky Endpoint Security for Android

If you want to prevent automatic update of the app and use a specific version of Kaspersky Endpoint Security for Android, disable automatic update of the app in Google Play settings. For more detail, refer to the Google technical support website.

Automatic update of Kaspersky Endpoint Security for Android is available only if the app was installed from Google Play or through Kaspersky Security Center using the Google Play link. If the app was installed through Kaspersky Security Center using a link to your own web server (using the standalone installation package), automatic update is not available. In this case, you can use a group policy to manually update Kaspersky Endpoint Security for Android.

To install an earlier version of Kaspersky Endpoint Security for Android:

  1. Remove Kaspersky Endpoint Security for Android from users' mobile devices.
  2. Install Kaspersky Endpoint Security for Android through Kaspersky Security Center using a link to your own web server. To do so, you will need the installation package for the specific version. You can download the distribution package for earlier versions of Kaspersky Endpoint Security for Android on the Kaspersky Technical Support website.

For details on earlier versions of Kaspersky Endpoint Security for Android, please refer to the Help for the appropriate version of Kaspersky Security for Mobile.

Page top

[Topic 99183]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Upgrading previous versions of administration plug-ins

You can upgrade administration plug-ins by using the following methods:

  • Install new version administration plug-in from the list of available distribution packages in Administration Console of Kaspersky Security Center.

    The list of available distribution packages is updated automatically after new versions of Kaspersky applications are released.

  • Download the distribution package from an external source and install new version administration plug-in using the EXE file.

    To upgrade Kaspersky Endpoint Security for Android and Kaspersky Device Management for iOS Administration Plug-ins, you need to download the latest version of the application from the web page of Kaspersky Security for Mobile and run the Setup Wizard for each of the two plug-ins. Previous versions of plug-ins are removed automatically during operation of the Installation Wizard.

Kaspersky experts recommend using the same version of the app and administration plug-ins. If user upgrades the app from Google Play, the Kaspersky Security Center shows notification with a prompt to upgrade the administration plug-in.

When administration plug-ins are updated, the existing administration groups in the Managed devices folder and rules for the automatic allocation of devices from the Unassigned devices folder to these groups are saved. The existing group policies for mobile devices are also saved. New policy settings that implement the new functions of the Kaspersky Security for Mobile integrated solution will be added to the existing policies and will have the default values.

If new settings have been added or the default values have been changed in the new version of the administration plug-in, the changes will be applied only after a group policy is opened. Until the administrator opens a group policy, the settings of the previous version of the plug-in will be applied on mobile devices even if the plug-in version has been updated.

Upgrading from the list in Administration Console

To upgrade the administration plug-ins:

  1. In the console tree, select AdvancedRemote installationInstallation packages.
  2. In the workspace, select Additional actionsView current versions of Kaspersky applications.

    This opens the list of up-to-date versions of Kaspersky applications.

  3. In the Mobile devices section, select the Kaspersky Endpoint Security for Android or Kaspersky Device Management for iOS plug-in.
  4. Click Download distribution packages button.

    A plug-in distribution will be downloaded to computer memory (EXE file). Run the EXE file. Follow the instructions of the Installation Wizard.

Upgrading from the distribution package

To upgrade the Kaspersky Endpoint Security for Android Administration Plug-in,

Copy the plug-in installation file klcfinst.exe from the integrated solution distribution package and run it on the administrator's workstation.

The installation is performed by the Wizard, and you do not need to configure the settings.

To upgrade the Kaspersky Device Management for iOS Administration Plug-in,

Copy the plug-in installation file klmdminst.exe from the integrated solution distribution package and run it on the administrator's workstation.

Plug-in installation is performed by the Wizard, and you do not need to configure the settings.

You can make sure that the administration plug-ins are upgraded by viewing the list of installed app administration plug-ins in the properties window of the Administration Server, in the AdvancedDetails of application management plug-ins installed section.

Page top

[Topic 98987]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Removal of Kaspersky Endpoint Security for Android

Kaspersky Endpoint Security for Android can be removed in the following ways:

  1. App removal by the user

    The user removes Kaspersky Endpoint Security for Android manually using the app interface. In order for users to be able to remove the app, app removal should be allowed in the policy applied to the device.

  2. App removal by the administrator

    The administrator removes the app remotely using the Administration Console of Kaspersky Security Center. The app can be removed from a separate device or from several devices at once.

To remove Kaspersky Endpoint Security for Android from a device operating in device owner mode:

  1. Send the Reset to factory settings command from Administration Console to the device. This command removes all device data and rolls back device settings to their factory values.
  2. Manually remove the device from the list of managed devices in Administration Console.

    If the device is not removed from Administration Console, there can be problems with further installation of Kaspersky apps on this device.

In this section

Remote app removal

Permitting users to remove the app

App removal by the user

Page top

[Topic 99000]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Remote app removal

You can remove Kaspersky Endpoint Security for Android from users' mobile devices remotely in the following ways:

  • Using a group policy. This method is convenient if you want to remove the app from several devices at once.
  • By configuring local app settings. This method is convenient if you want to remove the app from a separate device.

For information about removing Kaspersky Endpoint Security for Android from devices operating in device owner mode, see the App removal in device owner mode section below.

To remove the app by applying a group policy:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Additional section.
  5. In the Removal of Kaspersky Endpoint Security for Android section, select the Remove Kaspersky Endpoint Security for Android from device check box.

    This setting doesn't apply to devices operating in device owner mode.

  6. Click the Apply button to save the changes you have made.

As a result, Kaspersky Endpoint Security for Android is removed from mobile devices after synchronization with the Administration Server. Users of mobile devices receive a notification that the app has been removed.

To remove the app by configuring local settings:

  1. In the console tree, select Mobile Device ManagementMobile devices.
  2. In the list of devices, select the device on which you want to remove the app.
  3. Open the device properties window double-clicking.
  4. Select AppsKaspersky Endpoint Security for Android.
  5. Open the Kaspersky Endpoint Security properties window by double-clicking.
  6. Select the Additional section.
  7. In the Removal of Kaspersky Endpoint Security for Android section, select the Remove Kaspersky Endpoint Security for Android from device check box.

    This setting doesn't apply to devices operating in device owner mode.

  8. Click the Apply button to save the changes you have made.

As a result, Kaspersky Endpoint Security for Android is removed from mobile device after synchronization with the Administration Server. The mobile device user receives a notification that the app has been removed.

App removal in device owner mode

To remove Kaspersky Endpoint Security for Android from a device operating in device owner mode:

  1. In the console tree, select Mobile Device ManagementMobile devices.
  2. In the list of devices, select the device on which you want to remove the app.
  3. Right-click the device.
  4. In the context menu, select Mobile Device ManagementReset to factory settings.

    The Reset to factory settings command is sent to the device. This command removes all device data and rolls back device settings to their factory values.

  5. In the list of devices, right-click the device and select Delete.

    The device is removed from the list of managed devices in Administration Console.

    If the device is not removed from Administration Console, there can be problems with further installation of Kaspersky apps on this device.

Page top

[Topic 98994]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Permitting users to remove the app

To protect the app from removal on devices running Android 7.0 or later, Kaspersky Endpoint Security for Android must be set as an Accessibility feature. When the Initial Configuration Wizard is running, Kaspersky Endpoint Security for Android prompts the user to grant the application all required permissions. The user can skip these steps or disable these permissions in the device settings at a later time. If this is the case, the app is not protected from removal.

You can allow users to remove Kaspersky Endpoint Security for Android from their mobile devices in the following ways:

  • Using a group policy. This method is convenient if you want to allow users to remove the app from several devices at once.
  • Using local app settings. This method is convenient if you want to allow the user of a separate device to remove the app.

On devices operating in device owner mode, Kaspersky Endpoint Security for Android can be removed only by the administrator. For instructions, please refer to Remote app removal.

To allow removal of the app in a group policy:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Additional section.
  5. In the Removal of Kaspersky Endpoint Security for Android section, set the Allow removal of Kaspersky Endpoint Security for Android check box.

    This setting doesn't apply to devices operating in device owner mode.

  6. Click the Apply button to save the changes you have made.

As a result, removal of the app by users is allowed on mobile devices after synchronization with the Administration Server. The app removal button becomes available in the Kaspersky Endpoint Security for Android settings.

To allow removal of the app in the local app settings:

  1. In the console tree, select AdditionalMobile Device ManagementMobile devices.
  2. In the list of devices, select the device from which you want to allow app removal by the user.
  3. Open the device properties window double-clicking.
  4. Select ApplicationsKaspersky Endpoint Security for Mobile.
  5. Open the Kaspersky Endpoint Security properties window by double-clicking.
  6. Select the section Additional.
  7. In the Removal of Kaspersky Endpoint Security for Android section, set the Allow removal of Kaspersky Endpoint Security for Android check box.

    This setting doesn't apply to devices operating in device owner mode.

  8. Click the Apply button to save the changes you have made.

As a result, removal of the app by the user is allowed on the mobile device after synchronization with the Administration Server. The app removal button becomes available in the Kaspersky Endpoint Security for Android settings.

Page top

[Topic 98992]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

App removal by the user

To independently remove Kaspersky Endpoint Security for Android from a mobile device, the user must do the following:

  1. In the main window of Kaspersky Endpoint Security for Android, tap ks4android_settings_button  → Uninstall the app.

    A confirmation prompt appears on the screen.

    If the Uninstall the app button is missing, this means that the administrator enabled protection against removal of Kaspersky Endpoint Security for Android or the device operates in device owner mode.

    On devices operating in device owner mode, Kaspersky Endpoint Security for Android can be removed only by the administrator. For instructions, please refer to Remote app removal.

  2. Confirm removal of Kaspersky Endpoint Security for Android.

The Kaspersky Endpoint Security for Android app will be removed from the user's mobile device.

Page top

[Topic 136270]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuration and Management

This Help section is intended for specialists who administer Kaspersky Security for Mobile, as well as for specialists who provide technical support to organizations that use Kaspersky Security for Mobile.

In this section

Getting Started

Protection

Control

Management

Device owner mode

Commands for mobile devices

Page top

[Topic 141535]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Getting Started

This section describes the actions that you are recommended to perform when getting started with Kaspersky Security for Mobile.

In this section

Starting and stopping the application

Creating an administration group

Group policies for managing mobile devices

Page top

[Topic 100337]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Starting and stopping the application

Kaspersky Security Center automatically starts and stops administration plug-ins of Kaspersky Endpoint Security and Kaspersky Device Management for iOS.

Kaspersky Endpoint Security for Android launches when the operating system starts up and protects the mobile device during the entire session. The user can stop the app by disabling all Kaspersky Endpoint Security for Android components. You can use group policies to configure user permissions to manage app components.

On certain devices (for example, Huawei, Meizu, and Xiaomi), you must manually add Kaspersky Endpoint Security for Android to the list of apps that are started when the operating system starts (SecurityPermissionsAutorun). If the app is not added to the list, Kaspersky Endpoint Security for Android stops performing all of its functions after the mobile device is restarted.

You must also disable Battery Saver mode for Kaspersky Endpoint Security for Android. This is necessary for the app to run in the background, such as running a scheduled virus scan or synchronizing the device with Kaspersky Security Center. This issue is attributable to the specific features of the embedded software of these devices.

Page top

[Topic 89688_1]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Creating an administration group

To perform centralized configuration of the Kaspersky Endpoint Security for Android app installed on the users' mobile devices, the group policies must be applied to the devices.

To apply the policy to a device group, you are advised to create a separate group for these devices in the Managed devices prior to installing mobile apps on user devices.

After creating an administration group, it is recommended to configure the option to automatically allocate devices on which you want to install the apps to this group. Then configure settings that are common to all devices using a group policy.

To create administration group, follow the steps below:

  1. In the console tree, select the Managed devices folder.
  2. In the workspace of the Managed devices folder or subfolder, select the Devices tab.
  3. Click the New group  button.

    This opens the window in which you can create a new group.

  4. In the Group name window type the group name and click OK.

A new administration group folder with the specified name appears in the console tree. For more detailed information on use of administration groups, see Kaspersky Security Center Help.

Page top

[Topic 99958]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Group policies for managing mobile devices

A group policy is a package of settings for managing mobile devices that belong to an administration group and for managing mobile apps installed on the devices. You can create a group policy using the Policy Wizard.

You can use a policy to configure settings of both individual devices and a group of devices. For a group of devices, administration settings can be configured in the window of group policy properties. For an individual device, they can be configured in the window of local application settings. Individual management settings specified for one device may differ from the values of settings configured in the policy for a group to which this device belongs.

Each parameter represented in a policy has a "lock" attribute, which shows whether the setting is allowed for modification in the policies of nested hierarchy levels (for nested groups and secondary Administration Servers), in local application settings.

The values of settings configured in the policy and in local application settings are saved on the Administration Server, distributed to mobile devices during synchronization, and saved to devices as current settings. If the user has specified other values of settings that have not been "locked", during the next synchronization of the device with the Administration Server the new values of settings are relayed to the Administration Server and saved in the local settings of the application instead of the values that had been previously specified by the administrator.

To keep corporate security of mobile devices up to date, you can monitor users' devices for compliance with the group management policy.

The security level indicator is displayed in the upper part of the group policy window. The security level indicator will help you configure the policy so as to ensure a high level of device protection. The protection level indicator status changes depending on the policy settings:

  • security-level-good High protection level – an appropriate level of device protection is provided. All protection components function according to the settings recommended by Kaspersky.
  • security-level-warning Medium protection level – the protection level is lower than recommended. Some critical protection components are disabled (for example, Web Protection). Important issues are marked with the mark-orange icon.
  • security-level-danger Low protection level – there are problems that may lead to infection of the device and loss of data. Some critical protection components are disabled (for example, real-time protection of devices is disabled). Critical issues are marked with the mark-red icon.

For more details on managing policies and administration groups in the Administration Console of Kaspersky Security Center, see Kaspersky Security Center help.

In this section

Creating a group policy

Configuring synchronization settings

Managing revisions to group policies

Removing a group policy

Restricting permissions to configure group policies

Page top

[Topic 89890]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Creating a group policy

This section describes the process of creating group policies for devices on which Kaspersky Endpoint Security for Android mobile app are installed and policies for iOS MDM devices.

Policies created for an administration group are shown in the group workspace in the Administration Console of Kaspersky Security Center on the Policies tab. The icon indicating the policy status (active / inactive) appears before the policy name. Several policies for different apps can be created in one group. Only one policy for each app can be active. When a new active policy is created, the previous active policy becomes inactive.

You can modify a policy after it is created.

To a policy for managing mobile devices:

  1. From the console tree, select an administration group for which you want to create a policy.
  2. In the workspace of the group, select the Policies tab.
  3. Click the Create policy link to start the Policy Wizard.

This starts the Policy Wizard.

Step 1. Choose an application for creating a group policy

At this step, select the application for which you want to create a group policy in the list of applications:

  • Kaspersky Endpoint Security for Android – for devices using the Kaspersky Endpoint Security for Android mobile app.

It is recommended to create a separate policy for Huawei and Honor devices that do not have Google play services. This way you can send links to Huawei AppGallery to the users of all such devices.

  • Kaspersky Device Management for iOS – for iOS MDM devices.

A policy for mobile devices can be created if the Kaspersky Endpoint Security for Android Administration Plug-in and the Kaspersky Device Management for iOS Administration Plug-in are installed on the administrator's desktop. If the plug-ins are not installed, the name of the relevant application does not appear in the list of applications.

Proceed to the next step of the Policy Wizard.

Step 2. Enter a group policy name

At this step, type the name for the new policy in the Name field. If you specify the name of an existing policy, it will have (1) added at the end automatically.

Proceed to the next step of the Policy Wizard.

Step 3. Create a group policy for the application

At this step, the Wizard prompts you to select the status of the policy:

  • Active policy. The Wizard saves the created policy on the Administration Server. At the next synchronization of the mobile device with the Administration Server, the policy will be used on the device as the active policy.
  • Inactive policy. The Wizard saves the created policy on the Administration Server as a backup policy. This policy can be activated in the future after a specific event. If necessary, an inactive policy can be switched to active state.

    Several policies can be created for one application in the group, but only one of them can be active. When a new active policy is created, the previous active policy automatically becomes inactive.

Exit the Wizard.

Page top

[Topic 88051_1]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring synchronization settings

To manage mobile devices and receive reports or statistics from mobile devices of users, you must configure the synchronization settings. Mobile device synchronization with Kaspersky Security Center may be performed in the following ways:

  • By schedule. Synchronization by schedule is performed using the HTTP protocol. You can configure the synchronization schedule in the group policy settings. Modifications to group policy settings, commands and tasks will be performed when the device is synchronizing with Kaspersky Security Center according to the schedule, i.e. with a delay. By default, mobile devices are synchronized with the Kaspersky Security Center automatically every 6 hours.

    On Android 12 or later, the app may perform this task later than specified if the device is in battery saver mode.

  • Forced. Forced synchronization is performed using push notifications of the FCM service (Firebase Cloud Messaging). Forced synchronization is primarily intended for timely delivery of commands to a mobile device. If you want to use forced synchronization, make sure that the GSM settings are configured in Kaspersky Security Center. For more information, refer to Kaspersky Security Center help.

To configure the settings of mobile device synchronization with the Kaspersky Security Center:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Synchronization section.
  5. Select the frequency of synchronization in the Synchronize drop-down list.
  6. To disable synchronization of a device with Kaspersky Security Center while roaming, select the Do not synchronize while roaming check box.

    The device user can manually perform synchronization in the app settings (ks4android_settings_buttonSettingsSynchronizationSynchronize).

  7. To hide synchronization settings (server address, port and administration group) from the user in the app settings, clear the Show synchronization settings on device check box. It is impossible to modify hidden settings.
  8. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center. You can manually synchronize the mobile device by using a special command. To learn more about working with commands for mobile devices, please refer to the Kaspersky Security Center help.

Page top

[Topic 152432]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Managing revisions to group policies

Kaspersky Security Center lets you track group policy modifications. Every time you save changes made to a group policy, a revision is created. Each revision has a number.

You can manage revisions only for Kaspersky Endpoint Security for Android policies. You cannot manage revisions for a Kaspersky Device Management for iOS policy.

You can perform the following actions on group policy revisions:

  • Compare a selected revision to the current one.
  • Compare selected revisions.
  • Compare a policy with a selected revision of another policy.
  • View a selected revision.
  • Roll back policy changes to a selected revision.
  • Save revisions as a .txt file.

For more details about managing revisions of group policies and other objects (for example, user accounts), please refer to Kaspersky Security Center help.

To view the history of group policy revisions:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Revision history section.

    A list of policy revisions is displayed. It contains the following information:

    • Policy revision number.
    • Date and time the policy was modified.
    • Name of the user who modified the policy.
    • Action performed on the policy.
    • Description of the revision made to policy settings.
Page top

[Topic 89954]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Removing a group policy

To remove a group policy:

  1. In the console tree, select an administration group for which you want to remove a policy.
  2. In the workspace of the administration group on the Policies tab select the policy you want to remove.
  3. In the context menu of the policy, select Delete.

As a result, the group policy is deleted. Before the new group policy is applied, mobile devices belonging to the administration group continue to work with the settings specified in the policy that has been deleted.

Page top

[Topic 100347]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Restricting permissions to configure group policies

Kaspersky Security Center administrators can configure the access permissions of Administration Console users for different functions of the Kaspersky Security for Mobile integrated solution depending on the job duties of users.

In the Administration Console interface, you can configure access rights in the Administration Server properties window on the Security and User roles tabs. The User roles tab lets you add standard user roles with a predefined set of rights. The Security section lets you configure rights for one user or a group of users or assign roles to one user or a group of users. User rights for each application are configured according to functional scopes.

You can also configure user permissions specific to functional areas. Information about the correspondence between functional areas and policy tabs is given in Annex.

For each functional area, the administrator can assign the following permissions:

  • Allow editing. The Administration Console user is allowed to change the policy settings in the properties window.
  • Block editing. The Administration Console user is prohibited from changing the policy settings in the properties window. Policy tabs belonging to the functional scope for which this right has been assigned are not displayed in the interface.

For more details on managing user rights and roles in the Administration Console of Kaspersky Security Center, see the Kaspersky Security Center help.

Page top

[Topic 136503]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring anti-virus protection on Android devices

For the timely detection of threats, viruses, and other malicious applications, you should configure the settings for real-time protection and autorun of virus scans.

Kaspersky Endpoint Security for Android detects the following types of objects:

  • Viruses, worms, Trojans, and malicious tools
  • Adware
  • Apps that can be exploited by criminals to harm your device or personal data

Anti-Virus has a number of limitations:

  • When Anti-Virus is running, a threat detected in the external memory of the device (such as an SD card) cannot be neutralized automatically in the Work profile (Applications with a briefcase icon, Configuring the Android work profile). Kaspersky Endpoint Security for Android does not have access to external memory in the Work profile. Information about detected objects is displayed in app notifications. To neutralize objects detected in the external memory, the object files have to be deleted manually and the device scan restarted.
  • Due to technical limitations, Kaspersky Endpoint Security for Android cannot scan files with a size of 2 GB or more. During a scan, the app skips such files without notifying you that such files were skipped.

To configure the mobile device real-time protection settings:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Protection section.
  5. In the Protection section, configure the settings of mobile device file system protection:
    • To enable real-time protection of the mobile device against threats, select the Enable Protection check box.

      Kaspersky Endpoint Security for Android scans only new apps and files from the Downloads folder.

    • To enable extended protection of the mobile device against threats, select the Extended protection mode check box.

      Kaspersky Endpoint Security for Android will scan all files that the user opens, modifies, moves, copies, installs or saves on the device, as well as newly installed mobile apps.

      On devices running Android 8.0 or later, Kaspersky Endpoint Security for Android scans files that the user modifies, moves, installs and saves, as well as copies of files. Kaspersky Endpoint Security for Android does not scan files when they are opened, or source files when they are copied.

    • To enable additional scanning of new apps before they are started for the first time on the user's device with the help of the Kaspersky Security Network cloud service, select the Cloud protection (KSN) check box.
    • To block adware and apps that can be exploited by criminals to harm the device or user data, select the Detect adware, autodialers, and apps that can be used by criminals to cause harm to the user's device and data check box.
  6. In the Action on threat detection list, select one of the following options:
    • Delete

      Detected objects will be automatically deleted. The user is not required to take any additional actions. Prior to deleting an object, Kaspersky Endpoint Security for Android will display a temporary notification about the detection of the object.

    • Skip

      If the detected objects have been skipped, Kaspersky Endpoint Security for Android warns the user about problems in device protection. For each skipped threat, the app provides actions that the user can perform to eliminate the threat. The list of skipped objects may change, for example, if a malicious file was deleted or moved. To receive an up-to-date list of threats, run a full device scan. To ensure reliable protection of your data, eliminate all detected objects.

    • Quarantine
  7. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center.

To configure autorun of virus scans on the mobile device:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Scan section.
  5. To block adware and apps that can be exploited by criminals to harm the device or user data, select the Detect adware, autodialers, and apps that can be used by criminals to cause harm to the user's device and data check box.
  6. In the Action on threat detection list, select one of the following options:
    • Delete

      Detected objects will be automatically deleted. The user is not required to take any additional actions. Prior to deleting an object, Kaspersky Endpoint Security for Android will display a temporary notification about the detection of the object.

    • Skip

      If the detected objects have been skipped, Kaspersky Endpoint Security for Android warns the user about problems in device protection. For each skipped threat, the app provides actions that the user can perform to eliminate the threat. The list of skipped objects may change, for example, if a malicious file was deleted or moved. To receive an up-to-date list of threats, run a full device scan. To ensure reliable protection of your data, eliminate all detected objects.

    • Quarantine
    • Ask user

      The Kaspersky Endpoint Security for Android app displays a notification prompting the user to choose the action to take on the detected object: Skip or Delete.

      When the app detects several objects, the Ask user option allows the device user to apply a selected action to each file by using the Apply to all threats check box.

      Kaspersky Endpoint Security for Android must be set as an Accessibility feature to ensure the display of notifications on mobile devices running Android 10.0 or later. Kaspersky Endpoint Security for Android prompts the user to set the app as an Accessibility feature through the Initial Configuration Wizard. The user can skip this step or disable this service in the device settings at a later time. In this case, Kaspersky Endpoint Security for Android displays an Android system window prompting the user to choose the action to take on the detected object: Skip or Delete. To apply an action to multiple objects, you need to open Kaspersky Endpoint Security.

  7. The Scheduled scan section lets you configure the settings of the automatic launch of the full scan of the device file system. To do so, click the Schedule button and specify the frequency and start time of the full scan in the Schedule window.

    On Android 12 or later, the app may perform this task later than specified if the device is in battery saver mode.

  8. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center. Kaspersky Endpoint Security for Android scans all files, including the contents of archives.

To keep mobile device protection up to date, configure the anti-virus database update settings.

By default, anti-virus database updates are disabled for when the device is roaming. Scheduled updates of anti-virus databases are not performed.

To configure the settings of anti-virus database updates:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Database update section.
  5. If you want Kaspersky Endpoint Security for Android to download database updates according to the update schedule when the device is in the roaming zone, select the Allow database update while roaming check box in the Database update while roaming section.

    Even if the check box is cleared, the user can manually start an anti-virus database update when the device is roaming.

  6. In the Database update source section, specify the update source from which Kaspersky Endpoint Security for Android receives and installs anti-virus database updates:
    • Kaspersky servers

      Using a Kaspersky update server as an update source for downloading the databases of Kaspersky Endpoint Security for Android on users' mobile devices. To update databases from Kaspersky servers, Kaspersky Endpoint Security for Android transmits data to Kaspersky (for example, the update task run ID). The list of data that is transmitted during database updates is provided in the End User License Agreement.

    • Administration Server

      Using the repository of Kaspersky Security Center Administration Server as an update source for downloading the databases of Kaspersky Endpoint Security for Android on users' mobile devices.

    • Other source

      Using a third-party server as an update source for downloading the databases of Kaspersky Endpoint Security for Android on users' mobile devices. To start an update, you should enter the address of an HTTP server in the field below (e.g., http://domain.com/).

  7. In the Scheduled database update section, configure the settings for automatic anti-virus database updates on the user's device. To do so, click the Schedule button and specify the frequency and start time of updates in the Schedule window.

    On Android 12 or later, the app may perform this task later than specified if the device is in battery saver mode.

  8. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center.

Page top

[Topic 148305]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Protecting Android devices on the internet

To protect the personal data of a mobile device user on the internet, enable Web Protection. Web Protection blocks malicious websites that distribute malicious code, and phishing websites designed to steal your confidential data and gain access to your financial accounts. Web Protection scans websites before you open them using the Kaspersky Security Network cloud service. Web Protection also lets you configure a user's access to websites based on predefined lists of allowed and blocked websites.

Kaspersky Endpoint Security for Android must be set as an Accessibility feature. Kaspersky Endpoint Security for Android prompts the user to set the app as an Accessibility feature through the Initial Configuration Wizard. The user can skip this step or disable this service in the device settings at a later time.

Web Protection on Android devices works only in the Google Chrome browser (including the Custom Tabs feature), Huawei Browser, and Samsung Internet Browser. Web Protection for Samsung Internet Browser does not block sites on a mobile device if a work profile is used and Web Protection is enabled only for the work profile.

To enable Web Protection in Google Chrome, Huawei browser, or Samsung Internet Browser:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Web Protection.
  5. To use the Web Protection, you or device user must read and accept the Statement regarding data processing for the purpose of using Web Protection (Web Protection Statement):
    1. Click the link Web Protection Statement.

      This opens Statement regarding data processing for purpose of using Web Protection window. To accept the Web Protection Statement, you must read and accept Privacy Policy.

    2. Click the Privacy Policy link. Read and accept the Privacy Policy.

      If you do not accept Privacy Policy, mobile device user can accept Privacy Policy in the Initial Configuration Wizard or in the app (ks4android_settings_buttonAboutTerms and conditionsPrivacy Policy).

    3. Select the Web Protection Statement acceptance mode:
      • I have read and accept the Web Protection Statement
      • Request acceptance of the Web Protection Statement from the device user
      • I do not accept the Web Protection Statement
  6. If you select I do not accept the Web Protection Statement, the Web Protection does not block sites on a mobile device. Mobile device user cannot enable Web Protection in the Kaspersky Endpoint Security.
  7. Select the Enable Web Protection check box.
  8. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center.

Page top

[Topic 89901]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Protection of stolen or lost device data

This section describes how you can configure the unauthorized access protection settings on the device in case it gets lost or stolen.

In this section

Sending commands to a mobile device

Unlocking a mobile device

Data encryption

Deleting data on Android devices after failed password entry attempts

Page top

[Topic 89902]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Sending commands to a mobile device

To protect data on a mobile device that is lost or stolen, you can send special commands (see the table below).

Commands for protecting data on a lost or stolen device

Method of connecting to Kaspersky Security Center

Command

Result of command execution

Kaspersky Endpoint Security for Android

 

Lock

The mobile device is locked.

Unlock

After unlocking the mobile device running Android 5.0 – 6.Х, the screen unlock password is reset to "1234". After unlocking a device running Android 7.0 or later, the screen unlock password is not changed.

Locate device

The mobile device's location map coordinates are obtained.

On devices running Android 12 or later, if the user granted the "Use approximate location" permission, the Kaspersky Endpoint Security for Android app first tries to get the precise device location. If this is not successful, the approximate device location is returned only if it was received not more than 30 minutes earlier. Otherwise, the Locate device command fails.

Mugshot

The mobile device is locked. The mugshot photo is taken by the front camera of the device when somebody attempts to unlock the device. On devices with a pop-up front camera, the photo will be black if the camera is stowed.

When attempting to unlock the device, the user automatically consents to the mugshot.

If the permission to use the camera has been revoked, the mobile device displays a notification and prompts to provide the permission. On a mobile device running Android 12 or later, if the permission to use camera has been revoked via Quick Settings, the notification is not displayed but the photo taken is black.

Alarm

The mobile device sounds an alarm. The alarm is sounded for 5 minutes (or for 1 minute if the device battery is low).

Wipe corporate data

Containerized data, the corporate email account, settings for connecting to the corporate Wi-Fi network and VPN, Access Point Name (APN), Android work profile, KNOX container, and the KNOX License Manager key are wiped.

Reset to factory settings

All data is deleted from the mobile device and the settings are rolled back to their factory values. After this command is executed, the device will not be able to receive or execute subsequent commands.

iOS MDM profile

Lock

The mobile device is locked.

Reset password

The mobile device's screen unlock password is reset, and the user is prompted to set a new password in accordance with policy requirements.

Wipe corporate data

All installed configuration profiles, provisioning profiles, the iOS MDM profile, and applications for which the Remove together with iOS MDM profile check box has been selected are removed from the device.

Reset to factory settings

All data is deleted from the mobile device and the settings are rolled back to their factory values. After this command is executed, the device will not be able to receive or execute subsequent commands.

Special rights and permissions are required for the execution of commands of Kaspersky Endpoint Security for Android. When the Initial Configuration Wizard is running, Kaspersky Endpoint Security for Android prompts the user to grant the application all required rights and permissions. The user can skip these steps or disable these permissions in the device settings at a later time. If this is the case, it will be impossible to execute commands.

On devices running Android 10.0 or later, the user must grant the "All the time" permission to access the location. On devices running Android 11.0 or later, the user must also grant the "While using the app" permission to access camera. Otherwise, Anti-Theft commands will not function. The user will be notified of this limitation and will again be prompted to grant the permissions of required level. If the user selects the "Only this time" option for the camera permission, access is considered granted by the app. It is recommended to contact the user directly if the Camera permission is requested again.

For the complete list of available commands, please refer to Commands for mobile devices. To learn more about sending commands from Administration Console, please refer to Kaspersky Security Center help.

Page top

[Topic 138758]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Unlocking a mobile device

You can unlock a mobile device by using the following methods:

On certain devices (for example, Huawei, Meizu, and Xiaomi), you must manually add Kaspersky Endpoint Security for Android to the list of apps that are started when the operating system starts. If the app is not added to the list, you can unlock the device only by using a one-time unlock code. You cannot use commands to unlock the device.

To learn more about sending commands from the list of mobile devices in Administration Console, please refer to Kaspersky Security Center help.

A one-time unlock code is a secret application code for unlocking the mobile device. The one-time code is generated by the application and is unique to each mobile device. You can change the length of the one-time code (4, 8 or 16 digits) in group policy settings in the Anti-Theft section.

To unlock the mobile device using a one-time code:

  1. In the console tree, select Mobile Device ManagementMobile devices.
  2. Select a mobile device for which you want to get a one-time unlock code.
  3. Open the mobile device properties window by double-clicking.
  4. Select AppsKaspersky Endpoint Security for Android.
  5. Open the Kaspersky Endpoint Security properties window by double-clicking.
  6. Select the Anti-Theft section.
  7. A unique code for the selected device is shown in the One-time code field of the One-time device unlock code section.
  8. Use any available method (such as email) to communicate the one-time code to the user of the locked device.
  9. The user enters the one-time code on the screen of the device that is locked by Kaspersky Endpoint Security for Android.

The mobile device will be unlocked. After unlocking the mobile device running Android 5.0 – 6.Х, the screen unlock password is reset to "1234". After unlocking a device running Android 7.0 or later, the screen unlock password is not changed.

Page top

[Topic 145531]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Data encryption

To protect data against unauthorized access, you must enable encryption of all data on the device (for example, account credentials, external devices and apps, as well as email messages, SMS messages, contacts, photos, and other files). For access to encrypted data, you must specify a special key – device unlock password. If data is encrypted, access to it can be obtained only when the device is unlocked.

Data encryption is enabled by default on password-locked iOS devices (SettingsTouch ID / Face ID and PasswordEnable Password).

To encrypt all data on an Android device:

  1. Enable screen lock on the Android device (SettingsSecurityScreen lock).
  2. Set a device unlock password that is compliant with corporate security requirements.

    It is not recommended to use a pattern lock for unlocking the device. On certain Android devices running Android 6.0 or later, after encrypting data and restarting the Android device, you must enter a numeric password to unlock the device instead of a pattern lock. This issue is related to the operation of the Accessibility Features service. To unlock the device screen in this case, convert the pattern lock into a numeric password. For more details about converting a pattern lock into a numeric password, please refer to the Technical Support website of the mobile device manufacturer.

  3. Enable encryption of all data on the device (SettingsSecurityEncrypt data).
Page top

[Topic 243163]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Deleting data on Android devices after failed password entry attempts

You can configure deleting all data on an Android device (that is, resetting the device to factory settings) after the user makes too many failed attempts to enter the screen unlock password.

These settings apply to devices operating in device owner mode and to personal devices on which the Kaspersky Endpoint Security for Android app is enabled as a device administrator.

To configure wiping all data:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Anti-Theft section.
  5. In the Data wipe on device section, select the Wipe all data after failed attempts to enter unlock password check box.
  6. In the Maximum number of attempts to enter unlock password field, specify the number of attempts that the user can make to unlock the device. The default value is 8. The maximum available value is 20.
  7. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with Kaspersky Security Center. If the user exceeds the specified number of attempts to enter the correct screen unlock password, the Kaspersky Endpoint Security for Android app wipes all device data.

Page top

[Topic 136564]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring device unlock password strength

To protect access to a user's mobile device, you should set a device unlock password.

This section contains information about how to configure password protection on Android and iOS devices.

In this section

Configuring a strong unlock password for an Android device

Configuring a strong unlock password for iOS MDM devices

Page top

[Topic 90495]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring a strong unlock password for an Android device

To keep an Android device secure, you need to configure the use of a password for which the user is prompted when the device comes out of sleep mode.

You can impose restrictions on the user's activity on the device if the unlock password is weak (for example, lock the device). You can impose restrictions using the Compliance Control component. To do this, in the scan rule settings, you must select the Unlock password is not compliant with security requirements criterion.

On certain Samsung devices running Android 7.0 or later, when the user attempts to configure unsupported methods for unlocking the device (for example, a graphical password), the device may be locked if the following conditions are met: Kaspersky Endpoint Security for Android removal protection is enabled and screen unlock password strength requirements are set. To unlock the device, you must send a special command to the device.

To configure the use of an unlock password:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Device Management section.
  5. If you want the app to check whether an unlock password has been set, select the Require to set screen unlock password check box in the Screen lock section.

    If the application detects that no system password has been set on the device, it prompts the user to set it. The password is set according to the parameters defined by the administrator.

  6. Specify the following options, if required:
    • Minimum number of characters

      The minimum number of characters in the user password. Possible values: 4 to 16 characters.

      The user's password is 4 characters long by default.

      On devices running Android 10.0 or later, Kaspersky Endpoint Security resolves the password strength requirements into one of the system values: medium or high.

      The values for devices running Android 10.0 or later are determined by the following rules:

      • If the password length required is 1 to 4 symbols, then the app prompts the user to set a medium-strength password. It must be either numeric (PIN) with no repeating or ordered (e.g. 1234) sequences, or alphabetic/ alphanumeric. The PIN or password must be at least 4 characters long.
      • If the password length required is 5 or more symbols, then the app prompts the user to set a high-strength password. It must be either numeric (PIN) with no repeating or ordered sequences, or alphabetic/ alphanumeric (password). The PIN must be at least 8 digits long; the password must be at least 6 characters long.
    • Minimum unlock password requirements (for device owner mode, Android 12 or earlier)

      Specifies minimum unlock password requirements. These requirements apply only to new user passwords. The following values are available:

      • Numeric

        The user can set a password that includes numbers or set any stronger password (for instance, alphabetic or alphanumeric).

        This option is selected by default.

      • Alphabetic

        The user can set a password that includes letters (or other non-number symbols) or set any stronger password (for instance, alphanumeric).

      • Alphanumeric

        The user can set a password that includes both numbers and letters (or other non-number symbols) or set any stronger complex password.

      • Any

        The user can set any password.

      • Complex

        The user must set a complex password according to the specified password properties:

        • Minimum number of letters
        • Minimum number of digits
        • Minimum number of special symbols
        • Minimum number of uppercase letters
        • Minimum number of lowercase letters
        • Minimum number of non-letter characters
      • Complex numeric

        The user can set a password that includes numbers with no repetitions (e.g. 4444) and no ordered sequences (e.g. 1234, 4321, 2468) or set any stronger complex password.

      • Weak biometric

        The user can use biometric unlock methods or set a stronger complex password.

      This option applies only to devices running Android 12 or later in device owner mode.

    • Password lifetime, in days

      Specifies the number of days before the password expires. Applying a new value will set the current password lifetime to the new value.

      The default value is 0. This means that the password won't expire.

    • Number of days to notify before password expires (for device owner mode)

      Specifies the number of days to notify the user before the password expires.

      The default value is 0. This means that the user won't be notified about password expiration.

      This option applies only to devices operating in device owner mode.

    • Password history length

      Specifies the maximum number of previous user passwords that can't be used as a new password.

      The default value is 0. This means that the new user password can match any previous password except the current one.

    • Period of inactivity before device locks, in seconds

      Specifies the period of inactivity before the device locks. After this period, the device will lock.

      The default value is 0. This means that the device won't lock after a certain period.

    • Period for unlocking without password, in minutes (for device owner mode, Android 8.0+)

      Specifies the period for unlocking the device without a password. During this period, the user can use biometric methods to unlock the screen. After this period, the user can unlock the screen only with a password.

      The default value is 0. This means that the user won't be forced to unlock the device with a password after a certain period.

      This option applies only to devices running Android 8 or later in device owner mode.

    • Allow biometric unlock methods (Android 9+)

      If the check box is selected, the use of biometric unlock methods on the mobile device is allowed.

      If the check box is cleared, Kaspersky Endpoint Security for Android blocks the use of biometric methods to unlock the screen. The user can unlock the screen only with a password.

      This check box is selected by default.

      This setting applies only to devices running Android 9 or later.

    • Allow use of fingerprints

      The use of fingerprints to unlock the screen. This check box does not restrict the use of a fingerprint scanner when signing in to apps or confirming purchases.

      On devices running Android 10.0 or later, the use of fingerprints to unlock the screen can be managed for work profiles only.

      If the check box is selected, the use of fingerprints on the mobile device is allowed. If the unlock password does not comply with corporate security requirements, the user cannot use a fingerprint scanner to unlock the screen.

      If the check box is cleared, Kaspersky Endpoint Security for Android blocks the use of fingerprints to unlock the screen. The user can unlock the screen only with a password. In the Android settings, the option to use fingerprints will be unavailable (Android Settings > Security > Screen lock > Fingerprints).

      This check box is available only if the Allow biometric unlock methods (Android 9+) check box is selected.

      This check box is selected by default.

    • Allow face scanning (Android 9+)

      If the check box is selected, the use of face scanning on the mobile device is allowed.

      If the check box is cleared, Kaspersky Endpoint Security for Android blocks the use of face scanning to unlock the screen.

      This check box is available only if the Allow biometric unlock methods (Android 9+) check box is selected.

      This check box is selected by default.

      This setting applies only to devices running Android 9 or later.

    • Allow iris scanning (Android 9+)

      If the check box is selected, the use of iris scanning on the mobile device is allowed.

      If the check box is cleared, Kaspersky Endpoint Security for Android blocks the use of iris scanning to unlock the screen.

      This check box is available only if the Allow biometric unlock methods (Android 9+) check box is selected.

      This check box is selected by default.

      This setting applies only to devices running Android 9 or later.

    • Force use of password at startup

      If the check box is selected, the user is not required to enter the password when the device starts up.

      Once this option is applied, it cannot be reverted without resetting the device to factory defaults.

      If the check box is cleared, the startup requirements remain unchanged.

      This check box is cleared by default.

    • Unlock password

      This option lets you set the password on the user device.

      On devices running Android 11 or later, this option applies only if the device is in device owner mode.

      Once you save the policy, this option applies to the device by sending a command with the specified password. The input is cleared and the specified password is not saved in Administration Console.

      • If the device is not protected with the password or is running Android 10 or earlier, Kaspersky Endpoint Security for Android sets the password immediately.
      • If the device is running Android 11 or later, Kaspersky Endpoint Security for Android prompts the user to apply the new password.

      If you leave this option empty, no changes are applied to the device.

  7. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center.

Page top

[Topic 88130]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring a strong unlock password for iOS MDM devices

To protect iOS MDM device data, configure the unlock password strength settings.

By default, the user can use a simple password. A simple password is a password that contains successive or repetitive characters, such as "abcd" or "2222". The user is not required to enter an alphanumeric password that includes special symbols. By default, the password validity period and the number of password entry attempts are not limited.

To configure the strength settings for an iOS MDM device unlock password:

  1. In the console tree, in the Managed devices folder, select the administration group to which the iOS MDM devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking.
  4. In the policy Properties window, select the Password section.
  5. In the Password settings section, select the Apply settings on device check box.
  6. Configure unlock password strength settings:
    • To allow the user to use a simple password, select the Allow simple password check box.
    • To require use of both letters and numbers in the password, select the Prompt for alphanumeric value check box.
    • In the Minimum password length list, select the minimum password length in characters.
    • In the Minimum number of special characters list, select the minimum number of special characters in the password (such as "$", "&", "!").
    • In the Maximum password lifetime field, specify the period of time in days during which the password will stay current. When this period expires, Kaspersky Device Management for iOS prompts the user to change the password.
    • In the Enable Auto-Lock in list, select the amount of time after which iOS MDM device Auto-Lock should be enabled.
    • In the Password history field, specify the number of used passwords (including the current password) that Kaspersky Device Management for iOS will compare with the new password when the user changes the old password. If passwords match, the new password is rejected.
    • In the Maximum time for unlock without password list, select the amount of time during which the user can unlock the iOS MDM device without entering the password.
    • In the Maximum number of access attempts, select the number of access attempts that the user can make to enter the iOS MDM device unlock password.
  7. Click the Apply button to save the changes you have made.

As a result, once the policy is applied, Kaspersky Device Management for iOS checks the strength of the password set on the user's mobile device. If the strength of the device unlock password does not conform to the policy, the user is prompted to change the password.

Page top

[Topic 141383]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring a virtual private network (VPN)

This section contains information on configuring virtual private network (VPN) settings for secure connection to Wi-Fi networks.

In this section

Configuring VPN on Android devices (only Samsung)

Configuring VPN on iOS MDM devices

Page top

[Topic 90755]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring VPN on Android devices (only Samsung)

To securely connect an Android device to Wi-Fi networks and protect data transfer, you should configure the settings for VPN (Virtual Private Network).

Configuration of VPN is possible only for Samsung devices running Android 11 or earlier.

The following requirements should be considered when using a virtual private network:

  • The app that uses the VPN connection must be allowed in Firewall settings.
  • Virtual private network settings configured in the policy cannot be applied to system applications. The VPN connection for system applications has to be configured manually.
  • Some applications that use the VPN connection need to have additional settings configured at first startup. To configure settings, the VPN connection has to be allowed in application settings.

To configure VPN on a user's mobile device:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Manage Samsung KNOX → Manage Samsung devices section.
  5. In the VPN section, click the Configure button.

    This opens the VPN network window.

  6. In the Connection type drop-down list, select the type of VPN connection.
  7. In the Network name field, enter the name of the VPN tunnel.
  8. In the Server address field, enter the network name or IP address of the VPN server.
  9. In the DNS search domain(s) list, enter the DNS search domain to be automatically added to the DNS server name.

    You can specify several DNS search domains, separating them with blank spaces.

  10. In the DNS server(s) field, enter the full domain name or IP address of the DNS server.

    You can specify several DNS servers, separating them with blank spaces.

  11. In the Routing field, enter the range of network IP addresses with which data is exchanged via the VPN connection.

    If the range of IP addresses is not specified in the Routing field, all internet traffic will pass through the VPN connection.

  12. Additionally configure the following settings for networks of the IPSec Xauth PSK and L2TP IPSec PSK types:
    1. In the IPSec shared key field, enter the password for the preset IPSec security key.
    2. In the IPSec ID field, enter the name of the mobile device user.
  13. For an L2TP IPSec PSK network, additionally specify the password for the L2TP key in the L2TP key field.
  14. For a PPTP network, select the Use SSL connection check box so that the app will use the MPPE (Microsoft Point-to-Point Encryption) method of data encryption to secure data transmission when the mobile device connects to the VPN server.
  15. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center.

Page top

[Topic 90374]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring VPN on iOS MDM devices

To connect an iOS MDM device to a virtual private network (VPN) and protect data during the connection to the VPN, configure the VPN connection settings. The IKEv2 VPN protocol also lets you set up a VPN connection for selected website domains in Safari.

To configure the VPN connection on a user's iOS MDM device:

  1. In the console tree, in the Managed devices folder, select the administration group to which the iOS MDM devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking.
  4. In the policy Properties window, select the VPN section.
  5. Click the Add button in the VPN networks section.

    This opens the VPN network window.

  6. In the Network name field, enter the name of the VPN tunnel.
  7. In the Connection type drop-down list, select the type of VPN connection:
    • L2TP (Layer 2 Tunneling Protocol). The connection supports authentication of iOS MDM mobile device user using MS-CHAP v2 passwords, two-factor authentication, and automatic authentication using a public key.
    • PPTP (Point-to-Point Tunneling Protocol). The connection supports authentication of iOS MDM mobile device user using MS-CHAP v2 passwords and two-factor authentication.
    • IKEv2 (Internet Key Exchange version 2). The connection establishes the Security Association (SA) attribute between two network entities and supports authentication using EAP (Extensible Authentication Protocols), shared secrets, and certificates.
    • IPSec (Cisco). The connection supports password-based user authentication, two-factor authentication, and automatic authentication using a public key and certificates.
    • Cisco AnyConnect. The connection supports the Cisco Adaptive Security Appliance (ASA) firewall of version 8.0(3).1 or later. To configure the VPN connection, install the Cisco AnyConnect app from App Store on the iOS MDM mobile device.
    • Juniper SSL. The connection supports the Juniper Networks SSL VPN gateway, Series SA, of version 6.4 or later with the Juniper Networks IVE package of version 7.0 or later. To configure the VPN connection, install the JUNOS app from App Store on the iOS MDM mobile device.
    • F5 SSL. The connection supports F5 BIG-IP Edge Gateway, Access Policy Manager, and Fire SSL VPN solutions. To configure the VPN connection, install the F5 BIG-IP Edge Client app from App Store on the iOS MDM mobile device.
    • SonicWALL Mobile Connect. The connection supports SonicWALL Aventail E-Class Secure Remote Access devices of version 10.5.4 or later, SonicWALL SRA devices of version 5.5 or later, as well as SonicWALL Next-Generation Firewall devices, including TZ, NSA, E-Class NSA with SonicOS of version 5.8.1.0 or later. To configure the VPN connection, install the SonicWALL Mobile Connect app from App Store on the iOS MDM mobile device.
    • Aruba VIA. The connection supports Aruba Networks mobile access controllers. To configure them, install the Aruba Networks VIA app from App Store on the iOS MDM mobile device.
    • Custom SSL. The connection supports authentication of the iOS MDM mobile device user using passwords and certificates and two-factor authentication.
  8. In the Server address field, enter the network name or IP address of the VPN server.
  9. In the Account name field, enter the account name for authorization on the VPN server. You can use macros from the Macros available drop-down list.
  10. Configure the security settings for the VPN connection according to the selected type of virtual private network. For information about these settings, refer to the context help of the administration plug-in.
  11. For an IKEv2 connection, if necessary, set up a VPN connection for selected domains in Safari:
    1. Select the Set up VPN connection for domains (Safari only) check box to specify the website domains that trigger a VPN connection.
    2. Select the Connect automatically check box if you want the device to automatically activate a VPN connection when associated domains initiate network communication. If the check box is cleared, the user must activate a VPN connection manually before associated domains initiate network communication.
    3. In the table, specify the domains that trigger a VPN connection in Safari. Each domain should be in the "www.example.com" format.
  12. If necessary, configure the settings of the VPN connection via a proxy server:
    1. Select the Proxy server settings tab.
    2. Select the proxy server configuration mode and specify the connection settings.
    3. Click OK.

    As a result, the settings of the device connection to a VPN via a proxy server are configured on the iOS MDM device.

  13. Click OK.

    The new VPN is displayed in the list.

  14. Click the Apply button to save the changes you have made.

As a result, a VPN connection will be configured on the user's iOS MDM device once the policy is applied.

Page top

[Topic 138696]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring Firewall on Android devices (only Samsung)

Configure Firewall settings to monitor network connections on the user's mobile device.

To configure Firewall on a mobile device:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Manage Samsung KNOX → Manage Samsung devices section.
  5. In the Firewall window, click Configure.

    The Firewall window opens.

  6. Select the Firewall mode:
    • To allow all inbound and outbound connections, move the slider to Allow all.
    • To block all network activity except that of apps on the list of exclusions, move the slider up to Block all but exceptions.
  7. If you have set the Firewall mode to Block all but exceptions, create a list of exclusions:
    1. Click Add.

      This opens the Exclusion for Firewall window.

    2. In the App name field, enter the name of the mobile app.
    3. In the Package name field, enter the system name of the mobile app package (for example, com.mobileapp.example).
    4. Click OK.
  8. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center.

Page top

[Topic 90531]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Protecting Kaspersky Endpoint Security for Android against removal

For mobile device protection and compliance with corporate security requirements, you can enable protection against removal of Kaspersky Endpoint Security for Android. In this case, the user cannot remove the app using the Kaspersky Endpoint Security for Android interface. When removing the app using the tools of the Android operating system, you are prompted to disable administrator rights for Kaspersky Endpoint Security for Android. After disabling the rights, the mobile device will be locked.

On certain Samsung devices running Android 7.0 or later, when the user attempts to configure unsupported methods for unlocking the device (for example, a graphical password), the device may be locked if the following conditions are met: Kaspersky Endpoint Security for Android removal protection is enabled and screen unlock password strength requirements are set. To unlock the device, you must send a special command to the device.

To enable protection against removal of Kaspersky Endpoint Security for Android:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Additional section.
  5. In the Removal of Kaspersky Endpoint Security for Android section, clear the Allow removal of Kaspersky Endpoint Security for Android check box.

    To protect the app from removal on devices running Android 7.0 or later, Kaspersky Endpoint Security for Android must be set as an Accessibility feature. When the Initial Configuration Wizard is running, Kaspersky Endpoint Security for Android prompts the user to grant the application all required permissions. The user can skip these steps or disable these permissions in the device settings at a later time. If this is the case, the app is not protected from removal.

  6. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center. If an attempt is made to remove the app, the mobile device will be locked.

Page top

[Topic 136565]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Detecting device hacks (root)

Kaspersky Security for Mobile enables you to detect device hacks (root). System files are unprotected on a hacked device, and therefore can be modified. Moreover, third-party apps from unknown sources could be installed on hacked devices. Upon detection of a hack attempt, we recommend that you immediately restore normal operation of the device.

To detect when a user obtains root privileges, Kaspersky Endpoint Security for Android uses the following services:

  • Embedded service of Kaspersky Endpoint Security for Android is a Kaspersky service that checks whether a mobile device user has obtained root privileges (Kaspersky Mobile Security SDK).
  • SafetyNet Attestation is a Google service that checks the integrity of the operating system, analyzes the device hardware and software, and identifies other security issues. For more details about SafetyNet Attestation, visit the Android Technical Support website.

If the device is hacked, you receive a notification. You can view hacking notifications in the workspace of the Administration Server on the Monitoring tab. You can also disable notifications about hacks in the event notification settings.

On devices running Android, you can impose restrictions on the user's activity on the device if the device is hacked (for example, lock the device). You can impose restrictions by using the Compliance Control component (see the figure below). To do this, in the scan rule settings, select the Device has been rooted criterion.

Page top

[Topic 88664]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring a global HTTP proxy on iOS MDM devices

To protect the user's internet traffic, configure the connection of the iOS MDM device to the internet via a proxy server.

Automatic connection to the internet via a proxy server is available for controlled devices only.

To configure global HTTP proxy settings on the user's iOS MDM device:

  1. In the console tree, in the Managed devices folder, select the administration group to which the iOS MDM devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking.
  4. In the policy Properties window, select the Global HTTP Proxy section.
  5. In the Global HTTP proxy settings section, select the Apply settings on device check box.
  6. Select the type of global HTTP proxy configuration.

    By default, the manual type of global HTTP proxy configuration is selected, and the user is prohibited from connecting to captive networks without connecting to a proxy server. Captive networks are wireless networks that require preliminary authentication on the mobile device without connecting to the proxy server.

    • To specify the proxy server connection settings manually:
      1. In the Proxy settings type drop-down list, select Manual.
      2. In the Proxy server address and port field, enter the name of a host or the IP address of a proxy server and the number of the proxy server port.
      3. In the User name field, set the user account name for proxy server authorization. You can use macros from the Macros available drop-down list.
      4. In the Password field, set the user account password for proxy server authorization.
      5. To allow the user to access captive networks, select the Allow access to captive networks without connecting to proxy check box.
    • To configure the proxy server connection settings using a predefined PAC (Proxy Auto Configuration) file:
      1. In the Proxy settings type drop-down list, select Automatic.
      2. In the URL of PAC file field, enter the web address of the PAC file (for example: http://www.example.com/filename.pac).
      3. To allow the user to connect the mobile device to a wireless network without using a proxy server when the PAC file cannot be accessed, select the Allow direct connection if PAC file cannot be accessed check box.
      4. To allow the user to access captive networks, select the Allow access to captive networks without connecting to proxy check box.
  7. Click the Apply button to save the changes you have made.

As a result, once the policy is applied, the mobile device user will connect to the internet via a proxy server.

Page top

[Topic 88328]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Adding security certificates to iOS MDM devices

To simplify user authentication and ensure data security, add certificates on the user's iOS MDM device. Data signed with a certificate is protected against modification during network exchange. Data encryption using a certificate provides an added level of security for data. The certificate can be also used to verify the user's identity.

Kaspersky Device Management for iOS supports the following certificate standards:

  • PKCS#1 – encryption with a public key based on RSA algorithms.
  • PKCS#12 – storage and transmission of a certificate and a private key.

To add a security certificate on a user's iOS MDM device:

  1. In the console tree, in the Managed devices folder, select the administration group to which the iOS MDM devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking.
  4. In the policy Properties window, select the Certificates section.
  5. Click the Add button in the Certificates section.

    The Certificate window opens.

  6. In the File name field, specify the path to the certificate:

    Files of PKCS#1 certificates have the cer, crt, or der extensions. Files of PKCS#12 certificates have the p12 or pfx extensions.

  7. Click Open.

    If the certificate is password-protected, specify the password. The new certificate appears in the list.

  8. Click the Apply button to save the changes you have made.

As a result, once the policy is applied, the user will be prompted to install certificates from the list that has been created.

Page top

[Topic 90359]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Adding a SCEP profile to iOS MDM devices

You have to add a SCEP profile to enable the iOS MDM device user to automatically receive certificates from the Certification Center via the internet. The SCEP profile enables support of the Simple Certificate Enrollment Protocol.

A SCEP profile with the following settings is added by default:

  • The alternative subject name is not used for registering certificates.
  • Three attempts 10 seconds apart are made to poll the SCEP server. If all attempts to sign the certificate have failed, you have to generate a new certificate signing request.
  • The certificate that has been received cannot be used for data signing or encryption.

You can edit the specified settings when adding the SCEP profile.

To add a SCEP profile:

  1. In the console tree, in the Managed devices folder, select the administration group to which the iOS MDM devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking.
  4. In the policy Properties window, select the SCEP section.
  5. Click the Add button in the SCEP profiles section.

    The SCEP profile window opens.

  6. In the Server web address field, enter the web address of the SCEP server on which the Certification Center is deployed.

    The URL can contain the IP address or the full domain name (FQDN). For example, http://10.10.10.10/certserver/companyscep.

  7. In the Name field, enter the name of the Certification Center deployed on the SCEP server.
  8. In the Subject field, enter a string with the attributes of the iOS MDM device user that are contained in the X.500 certificate.

    Attributes can contain details of the country (С), organization (O), and common user name (CN). For example: /C=RU/O=MyCompany/CN=User/. You can also use other attributes specified in RFC 5280.

  9. In the Type of alternative name of subject drop-down list, select the type of alternative name of the subject of the SCEP server:
    • No – alternative name identification is not used.
    • RFC 822 name – identification using the email address. The email address must be specified according to RFC 822.
    • DNS name – identification using the domain name.
    • URI – identification using the IP address or address in FQDN format.

    You can use an alternative name of the subject for identifying the user of the iOS MDM mobile device.

  10. In the Subject Alternative Name field, enter the alternative name of the subject of the X.500 certificate. The value of the subject alternative name depends on the subject type: the user's email address, domain, or web address.
  11. In the NT subject name field, enter the DNS name of the iOS MDM mobile device user on the Windows NT network.

    The NT subject name is contained in the certificate request sent to the SCEP server.

  12. In the Number of polling attempts on SCEP server field, specify the maximum number of attempts to poll the SCEP server to get the certificate signed.
  13. In the Frequency of attempts (sec) field, specify the period of time in seconds between attempts to poll the SCEP server to get the certificate signed.
  14. In the Registration request field, enter a pre-published registration key.

    Before signing a certificate, the SCEP server requests the mobile device user to supply a key. If this field is left blank, the SCEP does not request the key.

  15. In the Key Size drop-down list, select the size of the registration key in bits: 1024 or 2048.
  16. If you want to allow the user to use a certificate received from the SCEP server as a signing certificate, select the Use for signing check box.
  17. If you want to allow the user to use a certificate received from the SCEP server for data encryption, select the Use for encryption check box.

    It is prohibited to use the SCEP server certificate as a data signing certificate and a data encryption certificate at the same time.

  18. In the Certificate fingerprint field, enter a unique certificate fingerprint for verifying the authenticity of the response from the Certification Center. You can use certificate fingerprints with the SHA-1 or MD5 hashing algorithm. You can copy the certificate fingerprint manually or select a certificate using the Create from certificate button. When the fingerprint is created using the Create from certificate button, the fingerprint is added to the field automatically.

    The certificate fingerprint has to be specified if data exchange between the mobile device and the Certification Center takes place via the HTTP protocol.

  19. Click OK.

    The new SCEP profile appears in the list.

  20. Click the Apply button to save the changes you have made.

As a result, once the policy is applied, the user's mobile device is configured to automatically receive a certificate from the Certification Center via the internet.

Page top

[Topic 136322]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Control

This section contains information about how to remotely monitor mobile devices in the Administration Console of Kaspersky Security Center.

In this section

Configuring restrictions

Configuring user access to websites

Compliance control of Android devices with corporate security requirements

Compliance control of iOS MDM devices with corporate security requirements

App control

Installation and uninstallation of apps on a group of iOS MDM devices

Software inventory on Android devices

Configuring the display of Android devices in Kaspersky Security Center

Page top

[Topic 140646]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring restrictions

This section provides instructions on how to configure user access to the features of mobile devices.

In this section

Special considerations for devices running Android version 10 and later

Configuring restrictions for Android devices

Configuring iOS MDM device feature restrictions

Page top

[Topic 206026]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Special considerations for devices running Android version 10 and later

Android 10 introduced numerous changes and restrictions targeting API 29 or higher. Some of these changes affect the availability or functionality of some of the app's features. These considerations apply only to devices running Android 10 or later.

Ability to enable, disable, and configure Wi-Fi

  • Wi-Fi networks can be added, deleted, and configured in the Administration Console of Kaspersky Security Center. When a Wi-Fi network is added to a policy, Kaspersky Endpoint Security receives this network configuration when it first connects to Kaspersky Security Center.
  • When a device detects a network configured through Kaspersky Security Center, Kaspersky Endpoint Security prompts the user to connect to that network. If the user chooses to connect to the network, all of the settings configured through Kaspersky Security Center are automatically applied. The device then automatically connects to that network when in range, without showing further notifications to the user.
  • If a user's device is already connected to another Wi-Fi network, sometimes the user may not be prompted to approve a network addition. In such cases, the user must turn Wi-Fi off and on again to receive the suggestion.
  • When Kaspersky Endpoint Security suggests a user connect to a Wi-Fi network and the user refuses to do so, the app's permission to change the Wi-Fi state is revoked. Kaspersky Endpoint Security then cannot suggest connecting to Wi-Fi networks until the user grants the permission again by going to Settings → Apps & notifications → Special App access → Wi-Fi Control → Kaspersky Endpoint Security.
  • Only open networks and networks encrypted with WPA2-PSK are supported. WEP and WPA encryption are not supported.
  • If the password for a network previously suggested by the app is changed, the user must manually delete that network from the list of known networks. The device will then be able to receive a network suggestion from Kaspersky Endpoint Security and connect to it.
  • When a device OS is updated from Android version 9 or earlier to Android version 10 or later, and/or Kaspersky Endpoint Security installed on a device running Android version 10 or later is updated, the networks that were previously added via Kaspersky Security Center cannot be modified or deleted through Kaspersky Security Center policies. The user, however, can manually modify or delete such networks in the device settings.
  • On devices running Android 10, a user is prompted for the password during an attempt to connect manually to a protected suggested network. Automatic connection does not require entering the password. If a user's device is connected to some other Wi-Fi network, the user must first disconnect from that network to connect automatically to one of the suggested networks.
  • On devices running Android 11, a user may manually connect to a protected network suggested by the app, without entering the password.
  • When Kaspersky Endpoint Security is removed from a device, the networks previously suggested by the app are ignored.
  • Prohibiting use of Wi-Fi networks is not supported.

Camera access

  • On devices running Android 10, use of the camera cannot be completely prohibited. Prohibiting use of the camera for a work profile is still available.
  • If a third-party app attempts to access the device's camera, that app will be blocked, and the user will be notified about the issue. However, the apps that use the camera while running in background mode cannot be blocked.
  • When an external camera is disconnected from a device, a notification about the camera not being available may be displayed in some cases.

Managing screen unlock methods

  • Kaspersky Endpoint Security now resolves the password strength requirements into one of the system values: medium or high.
    • If the password length required is 1 to 4 symbols, then the app prompts the user to set a medium-strength password. It must be either numeric (PIN), with no repeating or ordered (e.g. 1234) sequences; or alphanumeric. The PIN or password must be at least 4 characters long.
    • If the password length required is 5 or more symbols, then the app prompts the user to set a high-strength password. It must be either numeric (PIN), with no repeating or ordered sequences; or alphanumeric (password). The PIN must be at least 8 digits long; the password must be at least 6 characters long.
  • Using a fingerprint to unlock the screen can be managed for a work profile only.
Page top

[Topic 90496]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring restrictions for Android devices

To keep an Android device secure, configure the Wi-Fi, camera, and Bluetooth usage settings on the device.

By default, the user can use Wi-Fi, camera, and Bluetooth on the device without restrictions.

To configure the Wi-Fi, camera, and Bluetooth usage restrictions on the device:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Device Management section.
  5. In the Restrictions section, configure usage of Wi-Fi, camera, and Bluetooth:
    • To disable the Wi-Fi module on the user's mobile device, select the Prohibit use of Wi-Fi check box.

      On devices running Android 10.0 or later, prohibiting the use of Wi-Fi networks is not supported.

    • To disable the camera on the user's mobile device, select the Prohibit use of camera check box.

      On devices running Android 10.0 or later, the use of the camera cannot be completely prohibited.

      On devices running Android 11 or later, Kaspersky Endpoint Security for Android must be set as an Accessibility feature. Kaspersky Endpoint Security for Android prompts the user to set the app as an Accessibility feature through the Initial Configuration Wizard. The user can skip this step or disable this service in the device settings at a later time. If this is the case, you will not be able to restrict use of the camera.

    • To disable Bluetooth on the user's mobile device, select the Prohibit use of Bluetooth check box.

      On Android 12 or later, the use of Bluetooth can be disabled only if the device user granted the Nearby Bluetooth devices permission. The user can grant this permission during the Initial Configuration Wizard or at a later time.

      On personal devices running Android 13 or later, the use of Bluetooth cannot be disabled.

  6. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center.

Page top

[Topic 88187]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring iOS MDM device feature restrictions

To ensure compliance with corporate security requirements, configure restrictions on the operation of the iOS MDM device. For information about available restrictions, refer to the context help of the administration plug-in.

To configure iOS MDM device feature restrictions:

  1. In the console tree, in the Managed devices folder, select the administration group to which the iOS MDM devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking.
  4. In the policy Properties window, select the Features Restriction section.
  5. In the Features restriction settings section, select the Apply settings on device check box.
  6. Configure iOS MDM device feature restrictions.
  7. Click the Apply button to save the changes you have made.
  8. Select the Restrictions for applications section.
  9. In the Applications restriction settings section, select the Apply settings on device check box.
  10. Configure restrictions for apps on the iOS MDM device.
  11. Click the Apply button to save the changes you have made.
  12. Select the Restrictions for Media Content section.
  13. In the Media content restriction settings section, select the Apply settings on device check box.
  14. Configure restrictions for media content on the iOS MDM device.
  15. Click the Apply button to save the changes you have made.

As a result, once the policy is applied, restrictions on features, apps, and media content will be configured on the user's mobile device.

Page top

[Topic 136563]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring user access to websites

This section contains instructions on how to configure access to websites on Android and iOS devices.

In this section

Configuring access to websites on Android devices

Configuring access to websites on iOS MDM devices

Page top

[Topic 89905]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring access to websites on Android devices

You can use Web Protection to configure access of Android device users to websites. Web Protection supports website filtering by categories defined in Kaspersky Security Network cloud service. Filtering allows you to restrict user access to certain websites or categories of websites (for example, those from the "Gambling, lotteries, sweepstakes", or "Internet communication" categories). Web Protection also protects the personal data of users on the internet.

To enable Web Protection:

  • Kaspersky Endpoint Security must be enabled as an Accessibility Features service.
  • The Statement regarding data processing for the purpose of using Web Protection (Web Protection Statement) should be accepted. Kaspersky Endpoint Security uses Kaspersky Security Network (KSN) to scan websites. The Web Protection Statement contains the terms of data exchange with KSN.

    You can accept the Web Protection Statement for the user in Kaspersky Security Center. In this case, the user is not required to take any action.

    If you have not accepted the Web Protection Statement and prompt the user to do this, the user must read and accept the Web Protection Statement in the app settings.

    If you have not accepted the Web Protection Statement, Web Protection is not available.

Web Protection on Android devices works only in the Google Chrome browser (including the Custom Tabs feature), Huawei Browser, and Samsung Internet Browser. Web Protection for Samsung Internet Browser does not block sites on a mobile device if a work profile is used and Web Protection is enabled only for the work profile.

Web Protection is enabled by default: user access to websites in the Phishing and Malware categories is blocked.

To configure the settings of the device user's access to websites:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Web Protection.
  5. Select the Enable Web Protection check box.
  6. To use the Web Protection, you or device user must read and accept the Statement regarding data processing for the purpose of using Web Protection (Web Protection Statement):
    1. Click the link Web Protection Statement.

      This opens Statement regarding data processing for purpose of using Web Protection window. To accept the Web Protection Statement, you must read and accept Privacy Policy.

    2. Click the Privacy Policy link. Read and accept the Privacy Policy.

      If you do not accept Privacy Policy, mobile device user can accept Privacy Policy in the Initial Configuration Wizard or in the app (ks4android_settings_buttonAboutTerms and conditionsPrivacy Policy).

    3. Select the Web Protection Statement acceptance mode:
      • I have read and accept the Web Protection Statement
      • Request acceptance of the Web Protection Statement from the device user
      • I do not accept the Web Protection Statement

    If you select I do not accept the Web Protection Statement, the Web Protection does not block sites on a mobile device. Mobile device user cannot enable Web Protection in the Kaspersky Endpoint Security.

  7. If you want the app to restrict user access to websites depending on their content, do the following:
    1. In the Web Protection section, in the drop-down list select Websites of selected categories are forbidden.
    2. Create a list of blocked categories by selecting check boxes next to the categories of websites to which the app will block access.
  8. If you want the app to allow user access only to websites specified by the administrator, do the following:
    1. In the Web Protection section, in the drop-down list select Only listed websites are allowed.
    2. Create a list of websites by adding addresses of websites to which the app will not block access. Kaspersky Endpoint Security for Android supports only regular expressions. When entering the address of an allowed website, use the following templates:
      • https://example.com.*—All child pages of the website are allowed (for example, https://example.com/about).
      • https://.*example.com—All subdomain pages of the website are allowed (for example, https://pictures.example.com).

      You can also use the expression https? to select the HTTP and HTTPS protocols. For more details on regular expressions, please refer to the Oracle Technical Support website.

  9. If you want the app to block user access to all websites, in the Web Protection section, in the drop-down list, select All websites are blocked.
  10. To lift content-based restrictions on user access to websites, clear the Enable Web Protection check box.
  11. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center.

Page top

[Topic 88661]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring access to websites on iOS MDM devices

Configure Web Protection settings to control access to websites for iOS MDM device users. Web Protection controls a user's access to websites based on lists of allowed and blocked websites. Web Protection also lets you add website bookmarks on the bookmark panel in Safari.

By default, access to websites is not restricted.

Web Protection settings can be configured for supervised devices only.

To configure access to websites on the user's iOS MDM device:

  1. In the console tree, in the Managed devices folder, select the administration group to which the iOS MDM devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking.
  4. In the policy Properties window, select the Web Protection section.
  5. In the Web Protection settings section, select the Apply settings on device check box.
  6. To block access to blocked websites and allow access to allowed websites:
    1. In the Web Filter Mode drop-down list, select the Limit adult content mode.
    2. In the Allowed websites section, create a list of allowed websites.

      The website address should begin with "http://" or "https://". Kaspersky Device Management for iOS allows access to all websites in the domain. For example, if you have added http://www.example.com to the list of allowed websites, access is allowed to http://pictures.example.com and http://example.com/movies. If the list of allowed websites is empty, the application allows access to all websites other than those included in the list of blocked websites.

    3. In the Forbidden websites section, create a list of blocked websites.

      The website address should begin with "http://" or "https://". Kaspersky Device Management for iOS blocks access to all websites in the domain.

  7. To block access to all websites other than allowed websites on the tab list:
    1. In the Web Filter Mode drop-down list, select the Allow bookmarked websites only mode.
    2. In the Bookmarks section, create a list of bookmarks of allowed websites.

      The website address should begin with "http://" or "https://". Kaspersky Device Management for iOS allows access to all websites in the domain. If the bookmark list is empty, the application allows access to all websites. Kaspersky Device Management for iOS adds websites from the list of bookmarks on the bookmarks tab in Safari in the user's mobile device.

  8. Click the Apply button to save the changes you have made.

As a result, once the policy is applied, Web Protection will be configured on the user's mobile device according to the mode selected and lists created.

Page top

[Topic 89910]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Compliance control of Android devices with corporate security requirements

You can control Android devices for compliance with the corporate security requirements. Corporate security requirements regulate how the user can work with the device. For example, the real-time protection must be enabled on the device, the anti-virus databases must be up-to-date, and the device password must be sufficiently strong. Compliance control is based on a list of rules. A compliance rule includes the following components:

  • Device check criterion (for example, absence of blocked apps on the device).
  • Time period allocated for the user to fix the non-compliance (for example, 24 hours).
  • Action that will be taken on the device if the user does not fix the non-compliance within the set time period (for example, lock device).

    On Android 12 or later, the app may perform this task later than specified if the device is in battery saver mode.

If the user does not fix the non-compliance within the specified time, the following actions are available:

  • Block all applications except system ones. All apps on the user's mobile device, except system apps, are blocked from starting.
  • Lock device. Mobile device is locked. To obtain access to data, you must unlock the device. If the reason for locking the device is not rectified after the device is unlocked, the device will be locked again after the specified time period.
  • Wipe corporate data. Containerized data, the corporate email account, settings for connecting to the corporate Wi-Fi network and VPN, Access Point Name (APN), Android work profile, KNOX container, and the KNOX License Manager key are wiped.
  • Full Reset. All data is deleted from the mobile device and the settings are rolled back to their factory values. After this action is completed, the device will no longer be a managed device. To connect the device to Kaspersky Security Center, you must reinstall Kaspersky Endpoint Security for Android.

To create a scan rule for checking devices for compliance with a group policy:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Compliance control section.
  5. To receive notifications about devices that do not comply with the policy, in the Noncompliance notification section select the Notify administrator check box.

    If the device does not comply with a policy, during device synchronization with the Administration Server, Kaspersky Endpoint Security for Android writes an entry for Violation detected: <name of the criterion checked> in the event log. You can view the Event log on the Events tab in the Administration Server properties or in the local properties of the application.

  6. To notify the device user that the user's device does not comply with the policy, in the Noncompliance notification section select the Notify user check box.

    If the device does not comply with a policy, during device synchronization with the Administration Server, Kaspersky Endpoint Security for Android notifies the user about this.

  7. In the Compliance Rules section, compile a list of rules for checking the device for compliance with the policy. Follow the steps below:
    1. Click Add.

      The Scan Rule Wizard starts.

    2. Follow the instructions of the Scan Rule Wizard.

      When the wizard finishes, the new rule is displayed in the Compliance Rules section in the list of scan rules.

  8. To temporarily disable a scan rule that you have created, use the toggle switch opposite the selected rule.
  9. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center. If the user device does not comply with the rules, the restrictions you have specified in the scan rule list are applied to the device.

Page top

[Topic 241836]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Compliance control of iOS MDM devices with corporate security requirements

Compliance Control allows you to monitor iOS MDM devices for compliance with corporate security requirements and take actions if non-compliance is found. Compliance Control is based on a list of rules. Each rule includes the following components:

  • Status (whether the rule is enabled or disabled).
  • Non-compliance criteria (for example, absence of the specified apps or operating system version).
  • Actions performed on the device if non-compliance is found (for example, wipe corporate data or send an email message to the user).

To create a rule:

  1. In the console tree, in the Managed devices folder, select the administration group to which the iOS MDM devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking.
  4. In the policy Properties window, select the Compliance Control section.
  5. In the Compliance Control rules section, click Add.

    The Compliance Control Rule Wizard starts.

  6. Select the Enable rule check box if you want to activate the rule. If the check box is cleared, the rule is disabled.
  7. In the Non-compliance criteria tab, click Add criterion and select a non-compliance criterion for the rule. You can add multiple criteria. They are combined by the AND logical operator.

    The following criteria are available:

    • List of apps on device

      Checks whether the list of apps on the device contains forbidden apps or does not contain required apps.

      For this criterion, you need to select a check type (Contains or Does not contain) and specify app IDs.

    • Operating system version

      Checks the version of the operating system on the device.

      For this criterion, you need to select a comparison operator (Equal, Not equal, Less than, or Greater than) and specify the iOS version.

      Note that the Equal and Not equal operators check for a full match of the operating system version with the specified value. For instance, if you specify 15 in the rule, but the device is running iOS 15.2, the Equal criterion is not met. If you need to specify a range of versions, you can create two criteria and use the Less than and Greater than operators.

    • Management mode

      Checks the device's management mode.

      For this criterion, you need to select a mode (Supervised device or Non-supervised device).

  8. In the Actions tab, specify actions to be performed on the device if all specified non-compliance criteria are detected. Add an action in one of the following ways:
    • Click the Add action button if the action should be taken on the device immediately after non-compliance is detected.
    • Click the Add postponed action button if you want to also set a time period in which the user can fix the non-compliance. If the non-compliance is not fixed within this period, the action is performed on the device.

    The following actions are available:

    • Send email message to user

      The device user is informed about the non-compliance by email.

      For this action, you need to specify the user's email address(es) and the email message.

    • Install profile

      The configuration profile is installed on the device. This action is performed by sending the Install profile command.

      For this action, you need to specify the ID of the configuration profile to be installed.

    • Delete profile

      The configuration profile is deleted from the device. This action is performed by sending the Remove profile command.

      For this action, you need to specify the ID of the configuration profile to be removed.

    • Delete all profiles

      All previously installed configuration profiles are deleted from the device.

    • Wipe corporate data

      All installed configuration profiles, provisioning profiles, the iOS MDM profile, and applications for which the Remove together with iOS MDM profile check box has been selected are removed from the device. This action is performed by sending the Wipe corporate data command.

  9. Click the Save button to save the rule and close the wizard.

    The new rule appears in the list in the Compliance Control rules section.

  10. Click the Apply button to save the changes you have made to the policy and exit the policy properties window.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center.

Page top

[Topic 141381]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

App control

This section contains instructions on how to configure user access to apps on a mobile device.

In this section

App control on Android devices

App control on iOS MDM devices

Page top

[Topic 90538]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

App control on Android devices

The App Control component allows you to manage apps on Android devices to keep these devices secure.

  • You can impose restrictions on the user's activity on a device on which blocked apps are installed or required apps are not installed (for example, lock the device). You can impose restrictions using the Compliance Control component. To do so, in the scan rule settings, you must select the Forbidden apps are installed, Apps from forbidden categories are installed, or Not all required apps are installed criterion.

Kaspersky Endpoint Security for Android must be set as an Accessibility feature to ensure proper functioning of App Control. Kaspersky Endpoint Security for Android prompts the user to set the app as an Accessibility feature through the Initial Configuration Wizard. The user can skip this step or disable this service in the device settings at a later time. If this is the case, App Control does not run.

In device owner mode, you have extended control over the device. App Control operates without notifying the device user:

  • Required apps are installed automatically in the background. To install apps silently, you need to specify a link to the APK file of the required app in the policy settings.
  • Forbidden apps can be deleted from the device automatically. To delete apps silently, you need to select the Delete blocked apps automatically (in device owner mode only) check box in the policy settings.

To configure the settings of app startup on the mobile device:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the App Control section.
  5. In the Operation mode section, select the mode of app startup on the user's mobile device:
    • To allow the user to start all apps except those specified in the list of categories and apps as blocked apps, select the Blocked apps mode. The app will hide blocked app icons.
    • To allow the user to start only apps specified in the list of categories and apps as allowed, recommended, or required apps, select the Allowed apps mode. The app will hide all app icons except those specified in the list of allowed, recommended, or required apps and system apps.
  6. If you want Kaspersky Endpoint Security for Android to send data on forbidden apps to the event log without blocking them, select the Do not block forbidden apps, write to event log only check box.

    During the next synchronization of the user's mobile device with the Administration Server, Kaspersky Endpoint Security for Android writes an entry for A forbidden app has been installed in the event log. You can view the Event log on the Events tab in the Administration Server properties or in the local properties of the application.

  7. If the device is in device owner mode, select the Delete blocked apps automatically (in device owner mode only) check box to remove forbidden apps from the device in the background without notifying the user.
  8. If you want Kaspersky Endpoint Security for Android to block the startup of system apps on the user's mobile device (such as Calendar, Camera, and Settings) in Allowed apps mode, select the Block system apps check box.

    Kaspersky experts recommend against blocking system apps because this could lead to failures in device operation.

  9. Create a list of categories and apps to configure startup of apps.

    For details on app categories, please refer to the Appendices.

    For a list of the apps that belong to each category, please visit the Kaspersky website.

  10. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center.

Page top

[Topic 242959]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

App control on iOS MDM devices

Kaspersky Security Center allows you to manage apps on iOS MDM devices to keep these devices secure. You can create a list of apps allowed to be installed on devices and a list of apps prohibited from being displayed and launching on devices.

These restrictions apply only to supervised iOS MDM devices.

Open Restrictions for applications section

To open settings for app restrictions on iOS MDM devices:

  1. In the console tree, in the Managed devices folder, select the administration group to which the iOS MDM devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking.
  4. In the policy Properties window, select the Restrictions for applications section.

Restrict app installation

By default, the user can install any apps on the supervised iOS MDM device.

To restrict the apps that can be installed on the device:

  1. Select the Allow installation of apps from the list (supervised only) check box.
  2. In the table, click Add to add an app to the list.
  3. Specify the app's bundle ID. To get the app's bundle ID, you can follow instructions in Apple documentation. Specify the com.apple.webapp value to allow all web clips.
  4. Click the Apply button to save the changes you have made.

Once the policy is applied to a device, the specified restrictions for apps are configured on the device. Only apps from the list and system apps will be available for installation. All other apps can't be installed on the device.

The specified apps can be installed on the device in the following ways (if the corresponding options are enabled in the Features restrictions section):

  • Installation from Apple Configurator or iTunes
  • Installation from App Store
  • Automatic loading

Specify prohibited apps

By default, all apps can be displayed and launched on the supervised iOS MDM device.

To specify prohibited apps:

  1. Select the Prohibit displaying and launching apps from the list (supervised only) check box.
  2. In the table, click Add to add an app to the list.
  3. Specify the app's bundle ID. To get the app's bundle ID, you can follow instructions in Apple documentation. Specify the com.apple.webapp value to restrict all web clips.
  4. Click the Apply button to save the changes you have made.

Once the policy is applied to a device, the specified restrictions for apps are configured on the device. Apps from the list will be prohibited from being displayed and launching on the device. All other apps will be displayed and available to run.

Page top

[Topic 241837]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Installation and uninstallation of apps on a group of iOS MDM devices

Kaspersky Security Center allows you to install and remove apps on iOS MDM devices by sending commands to these devices.

Selecting devices

To select iOS MDM devices on which apps should be installed or removed:

  1. In the Mobile Device Management folder in the console tree, select the Mobile devices subfolder.

    The folder workspace displays a list of managed mobile devices.

  2. In the workspace, filter iOS MDM devices by protocol type (iOS MDM).
  3. Select the iOS MDM device on which apps should be installed or removed.

    You can also select multiple devices and send commands simultaneously. To select a group of devices, do one of the following:

    • To select all devices in the workspace, filter the list of devices as required and press Ctrl+A.
    • To select a range of devices, hold down the Shift key, click the first device in the range, and then click the last device in the range.
    • To select individual devices, hold down the Ctrl key and click devices you want to include in the group.

Installing apps on devices

Before installing an app on an iOS MDM device, you must add that app to an iOS MDM Server. For more information, refer to Adding a managed app.

To install apps on selected iOS MDM devices:

  1. Right-click the selected devices. In the context menu that appears, select All commands, and then select Install app.

    For a single device, you can also select Show command log in the context menu, proceed to the Install app section, and click the Send command button.

    The Select apps window opens showing a list of managed apps.

  2. Select the apps you want to install on iOS MDM devices. To select a range of apps, use the Shift key. To select multiple apps individually, use the Ctrl key.
  3. Click OK to send the command to the devices.

    When the command is executed on a device, the selected apps are installed. If the command is successfully executed, the command log will show its current status as Completed.

Removing apps from devices

To remove apps from selected iOS MDM devices:

  1. Right-click the selected devices. In the context menu that appears, select All commands, and then select Remove app.

    For a single device, you can also select Show command log in the context menu, proceed to the Remove app section, and click the Send command button.

    The Remove apps window opens showing a list of previously installed apps.

  2. Select the apps you want to remove from iOS MDM devices. To select a range of apps, use the Shift key. To select multiple apps individually, use the Ctrl key.
  3. Click OK to send the command to the devices.

    When the command is executed on a device, the selected apps are uninstalled. If the command is successfully executed, the command log will show its current status as Completed.

Page top

[Topic 148312]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Software inventory on Android devices

You can inventory apps on Android devices connected to Kaspersky Security Center. Kaspersky Endpoint Security for Android receives information about all apps installed on mobile devices. Information acquired during inventory is displayed in the device properties in the Events section. You can view detailed information on each installed app, including its version and publisher.

To enable software inventory:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the App Control section.
  5. In the Software inventory section, select the Send data on installed apps check box.
  6. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center. Kaspersky Endpoint Security for Android sends data to the event log each time an app is installed or removed from the device.

Page top

[Topic 136797]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring the display of Android devices in Kaspersky Security Center

For convenient operations with the list of mobile devices, you should configure the settings for displaying devices in Kaspersky Security Center. By default, the list of mobile devices is displayed in the AdditionalMobile Device ManagementMobile devices console tree. Device information is updated automatically. You can also manually update the list of mobile devices by clicking the Update button in the upper right corner.

After connecting the device to Kaspersky Security Center, devices are added to the mobile device list automatically. The mobile device list may contain detailed information about that device: model, operation system, IP address, and others.

You can configure the device name format and select the device status. The device status informs you about how the components of Kaspersky Endpoint Security for Android are operating on the user's mobile device.

Kaspersky Endpoint Security for Android components could be non-operational for the following reasons:

  • The user disabled the component in the device settings.
  • The user did not grant the app the necessary permissions for the component to operate (for example, there is no permission to determine the device location for the corresponding Anti-Theft command).

To display the device status, you must enable the Determined by the application condition in the administration group properties (PropertiesDevice statusSet device status to Critical if and Set device status to Warning if). In the administration group properties, you can also select other criteria for forming the mobile device status.

To configure the display of Android devices in Kaspersky Security Center:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Device information section.
  5. In the Device name in Kaspersky Security Center section, select the device name format for the device name in the Administration Console:
    • Device model [email, device ID]
    • Device model [email (if any) or device ID]

    A device ID is a unique ID that Kaspersky Endpoint Security for Android generates from the data received from a device. For mobile devices running Android 10 or later, Kaspersky Endpoint Security for Android uses the SSAID (Android ID) or checksum of other data received from the device. For earlier versions of Android, the app uses the IMEI.

  6. Set the Lock attribute in the locked position (Значок закрытого замка.).
  7. In the Device status in Kaspersky Security Center section, select the appropriate device status if a component of Kaspersky Endpoint Security for Android is not working: ks4android_status_Warning (Critical), ks4android_status_Attantion (Warning) or ks4android_status_OK (OK).

    In the list of mobile devices, the device status will be changed according to the selected status.

  8. Set the Lock attribute in the locked position.
  9. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center.

Page top

[Topic 142052]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring connection to a Wi-Fi network

This section provides instructions on how to configure automatic connection to a corporate Wi-Fi network on Android and iOS MDM devices.

In this section

Connecting Android devices to a Wi-Fi network

Connecting iOS MDM devices to a Wi-Fi network

Page top

[Topic 90533]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Connecting Android devices to a Wi-Fi network

For an Android device to automatically connect to an available Wi-Fi network and protect data during the connection, you should configure the connection settings.

To connect the mobile device to a Wi-Fi network:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Wi-Fi section.
  5. In the Wi-Fi networks section, click Add.

    This opens the Wi-Fi network window.

  6. In the Service set identifier (SSID) field, enter the name of the Wi-Fi network that includes the access point (SSID).
  7. Select the Hidden network check box if you want the Wi-Fi network to be hidden in the list of available networks on the device. In this case, to connect to the network the user needs to manually enter the Service set identifier (SSID) specified in the settings of the Wi-Fi router on the mobile device.
  8. Select the Automatic connection to network check box if you want the device to connect to the Wi-Fi network automatically.
  9. In the Network protection section, select the type of Wi-Fi network security (open or secure network protected with the WEP, WPA/WPA2 PSK, or 802.1.x EAP protocol).

    The 802.1.x EAP security protocol is supported only in the Kaspersky Endpoint Security for Android app version 10.48.1.1 or later. The WEP protocol is supported only on Android 9 or earlier.

  10. If you selected the 802.1.x EAP security protocol, specify additional network protection settings (EAP method, Root certificate and other). For information about these settings, refer to the context help of the administration plug-in.
  11. In the Password field, set a network access password if you selected a secure network at step 9.
  12. Select the Use proxy server option if you want to use a proxy server to connect to a Wi-Fi network. Otherwise, select the Do not use proxy server option.
  13. If you selected Use proxy server, in the Proxy server address and port field, enter the IP address or DNS name of the proxy server and port number, if necessary.

    On devices running Android version 8.0 or later, settings of the proxy server for Wi-Fi cannot be redefined with the policy. However, you can manually configure the proxy server settings for a Wi-Fi network on the mobile device.

    If you are using a proxy server to connect to a Wi-Fi network, you can use a policy to configure the settings for connecting to the network. On devices running Android 8.0 or later, you must manually configure the proxy server settings. On devices running Android 8.0 or later, you cannot use a policy to change the Wi-Fi network connection settings, except for the network access password.

    If you are not using a proxy server to connect to a Wi-Fi network, there are no limitations on using policies to manage a Wi-Fi network connection.

  14. In the Do not use proxy server for addresses field, generate a list of web addresses that can be accessed without the use of the proxy server.

    For example, you can enter the address example.com. In this case, the proxy server will not be used for the addresses pictures.example.com, example.com/movies, etc. The protocol (for example, http://) can be omitted.

    On devices running Android version 8.0 or later, the proxy server exclusion for web addresses does not work.

  15. Click OK.

    The added Wi-Fi network is displayed in the list of Wi-Fi networks.

    You can modify or delete Wi-Fi networks in the list of networks using the Edit and Delete buttons at the top of the list.

  16. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center. After the policy is applied on the mobile device, the user can connect to the Wi-Fi network that has been added, without specifying the network settings.

On devices running Android version 10.0 or later, if a user refuses to connect to the suggested Wi-Fi network, the app's permission to change Wi-Fi state is revoked. The user must grant this permission manually.

Page top

[Topic 88185]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Connecting iOS MDM devices to a Wi-Fi network

For an iOS MDM device to automatically connect to an available Wi-Fi network and protect data during the connection, you should configure the connection settings.

To configure the connection of an iOS MDM device to a Wi-Fi network:

  1. In the console tree, in the Managed devices folder, select the administration group to which the iOS MDM devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking.
  4. In the policy Properties window, select the Wi-Fi section.
  5. Click the Add button in the Wi-Fi networks section.

    This opens the Wi-Fi network window.

  6. In the Service set identifier (SSID) field, enter the name of the Wi-Fi network that includes the access point (SSID).
  7. If you want the iOS MDM device to connect to the Wi-Fi network automatically, select the Automatic connection check box.
  8. To make it impossible to connect iOS MDM devices to a Wi-Fi network requiring preliminary authentication (captive network), select the Disable captive networks detection check box.

    To use a captive network, you must subscribe, accept an agreement, or make a payment. Captive networks may be deployed in cafes and hotels, for example.

  9. If you want the Wi-Fi network to be hidden in the list of available networks on the iOS MDM device, select the Hidden Network check box.

    In this case, to connect to the network the user needs to manually enter the Service set identifier (SSID) specified in the settings of the Wi-Fi router on the mobile device.

  10. In the Network protection drop-down list, select the type of protection of the Wi-Fi network connection:
    • Disabled. User authentication is not required.
    • WEP. The network is protected using Wireless Encryption Protocol (WEP).
    • WPA/WPA2 (Personal). The network is protected using WPA / WPA2 protocol (Wi-Fi Protected Access).
    • WPA2 (Personal). The network is protected using WPA2 protocol (Wi-Fi Protected Access 2.0). WPA2 protection is available on devices running iOS version 8 or later. WPA2 is not available on Apple TV devices.
    • Any (Personal). The network is protected using the WEP, WPA or WPA2 encryption protocol depending on the type of Wi-Fi router. An encryption key unique to each user is used for authentication.
    • WEP (Dynamic). The network is protected using the WEP protocol with the use of a dynamic key.
    • WPA/WPA2 (Enterprise). The network is protected using the WPA/WPA2 encryption protocol with use of the 802.1X protocol.
    • WPA2 (Enterprise). The network is protected using the WPA2 encryption protocol with the use of one key shared by all users (802.1X). WPA2 protection is available on devices running iOS version 8 or later. WPA2 is not available on Apple TV devices.
    • Any (Enterprise). The network is protected using WEP or WPA / WPA2 protocol depending on the type of Wi-Fi router. One encryption key shared by all users is used for authentication.

    If you have selected WEP (Dynamic), WPA/WPA2 (Enterprise), WPA2 (Enterprise) or Any (Enterprise) in the Network protection list, in the Protocols section you can select the types of EAP protocols (Extensible Authentication Protocol) for user identification on the Wi-Fi network.

    In the Trusted certificates section, you can also create a list of trusted certificates for authentication of the iOS MDM device user on trusted servers.

  11. Configure the settings of the account for user authentication upon connection of the iOS MDM device to the Wi-Fi network:
    1. In the Authentication section, click the Configure button.

      The Authentication window opens.

    2. In the User name field, enter the account name for user authentication upon connection to the Wi-Fi network.
    3. To require the user to enter the password manually upon every connection to the Wi-Fi network, select the Prompt for password at each connection check box.
    4. In the Password field, enter the password of the account for authentication on the Wi-Fi network.
    5. In the Authentication certificate drop-down list, select a certificate for user authentication on the Wi-Fi network. If the list does not contain any certificates, you can add them in the Certificates section.
    6. In the User ID field, enter the user ID displayed during data transmission upon authentication instead of the user's real name.

      The user ID is designed to make the authentication process more secure, as the user name is not displayed openly, but transmitted via an encrypted TLS tunnel.

    7. Click OK.

    As a result, the settings of the account for user authentication upon connection to the Wi-Fi network will be configured on the iOS MDM device.

  12. If necessary, configure the settings of the Wi-Fi network connection via a proxy server:
    1. In the Proxy server section, click the Configure button.
    2. In the Proxy server window that opens, select the proxy server configuration mode and specify the connection settings.
    3. Click OK.

    As a result, the settings of the device connection to the Wi-Fi network via a proxy server are configured on the iOS MDM device.

  13. Click OK.

    The new Wi-Fi network is displayed in the list.

  14. Click the Apply button to save the changes you have made.

As a result, a Wi-Fi network connection will be configured on the user's iOS MDM device once the policy is applied. The user's mobile device will automatically connect to available Wi-Fi networks. Data security during a Wi-Fi network connection is ensured by the authentication technology.

Page top

[Topic 140750]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring email

This section contains information on configuring mailboxes on mobile devices.

In this section

Configuring a mailbox on iOS MDM devices

Configuring an Exchange mailbox on iOS MDM devices

Configuring an Exchange mailbox on Android devices (only Samsung)

Page top

[Topic 88332]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring a mailbox on iOS MDM devices

To enable an iOS MDM device user to work with email, add the user's email account to the list of accounts on the iOS MDM device.

By default, the email account is added with the following settings:

  • Email protocol – IMAP.
  • The user can move email messages between the user's accounts and synchronize account addresses.
  • The user can use any email clients (other than Mail) to use email.
  • The SSL connection is not used during transmission of messages.

You can edit the specified settings when adding the account.

To add an email account of the iOS MDM device user:

  1. In the console tree, in the Managed devices folder, select the administration group to which the iOS MDM devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking.
  4. In the policy Properties window, select the Email.
  5. Click the Add button in the Email account section.

    The Email account window opens.

  6. In the Description field, enter a description of the user's email account.
  7. Select the email protocol:
    • POP
    • IMAP
  8. If necessary, specify the IMAP path prefix in the IMAP path prefix field.

    The IMAP path prefix must be entered using upper-case letters (for example: GMAIL for Google Mail). This field is available if the IMAP account protocol is selected.

  9. In the User name as displayed in messages field, enter the user name to be displayed in the From: field for all outgoing messages.
  10. In the Email address field, specify the email address of the iOS MDM device user.
  11. Configure Additional Settings of the email account:
    • To allow the user to move email messages between the user's accounts, select the Allow movement of messages between accounts check box.
    • To allow the email addresses used to be synchronized among user accounts, select the Allow sync of recent addresses check box.
    • To allow a user to use the Mail Drop service to forward large-sized attachments, select the Allow Mail Drop check box.
    • To allow the user to use only the standard iOS mail client, select the Allow use of only Mail app check box.
  12. Configure the settings for using the S/MIME protocol in the Mail app. S/MIME is a protocol for transmitting digitally signed encrypted messages.
    • To use the S/MIME protocol to sign outgoing mail, select the Sign messages check box and select a certificate for the signature. A digital signature confirms the authenticity of the sender and indicates that the contents of the message have not been modified during transmission to the recipient. A message signature is available on devices running iOS version 10.3 or later.
    • To use the S/MIME protocol to encrypt outgoing mail, select the Encrypt messages by default check box and select a certificate for encryption (public key). Message encryption is available on devices running iOS version 10.3 or later.
    • To enable a user to encrypt individual messages, select the Show toggle button for encrypting messages check box. To send encrypted messages, the user must click the mail_lock icon in the Mail app in the To field.
  13. In the Inbound mail server and Outbound mail server sections, click the Settings button to configure the server connection settings:
    • Server address and port: Names of hosts or IP addresses of inbound mail servers and outbound mail servers and server port numbers.
    • Account name: Name of the user's account for inbound and outbound mail server authorization.
    • Authentication type: Type of user's email account authentication on inbound mail servers and outbound mail servers.
    • Password: Account password for authentication on the inbound and outbound mail server protected using the selected authentication method.
    • Use one password for incoming and outgoing mail servers: use one password for user authentication on incoming and outgoing mail servers.
    • Use SSL connection: usage of the SSL (Secure Sockets Layer) data transport protocol that uses encryption and certificate-based authentication to secure data transmission.
  14. Click OK.

    The new email account appears in the list.

  15. Click the Apply button to save the changes you have made.

As a result, once the policy is applied, email accounts from the compiled list will be added on the user's mobile device.

Page top

[Topic 88340]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring an Exchange mailbox on iOS MDM devices

To enable the iOS MDM device user to use corporate email, calendar, contacts, notes, and tasks, add the user's Exchange ActiveSync account on the Microsoft Exchange server.

By default, an account with the following settings is added on the Microsoft Exchange server:

  • Email is synchronized once per week.
  • The user can move messages between the user's accounts and synchronize account addresses.
  • The user can use any email clients (other than Mail) to use email.
  • The SSL connection is not used during transmission of messages.

You can edit the specified settings when adding the Exchange ActiveSync account.

To add the Exchange ActiveSync account of the iOS MDM device user:

  1. In the console tree, in the Managed devices folder, select the administration group to which the iOS MDM devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking.
  4. In the policy Properties window, select the Exchange ActiveSync section.
  5. Click the Add button in the Exchange ActiveSync accounts section.

    The Exchange ActiveSync account window opens on the General tab.

  6. In the Account name field, enter the account name for authorization on the Microsoft Exchange server. You can use macros from the Macros available drop-down list.
  7. In the Server address field, enter the network name or IP address of the Microsoft Exchange server.
  8. To use the SSL (Secure Sockets Layer) data transport protocol to secure the transmission of data, select the Use SSL connection check box.
  9. In the Domain field, enter the name of the iOS MDM device user's domain. You can use macros from the Macros available drop-down list.
  10. In the Account User Name field, enter the name of the iOS MDM device user.

    If you leave this field blank, Kaspersky Device Management for iOS prompts the user to enter the user name when applying the policy on the iOS MDM device. You can use macros from the Macros available drop-down list.

  11. In the Email address field, specify the email address of the iOS MDM device user. You can use macros from the Macros available drop-down list.
  12. In the Password field, enter the password of the Exchange ActiveSync account for authorization on the Microsoft Exchange server.
  13. Select the Additional tab and configure the additional settings of the Exchange ActiveSync account:
    • Number of Days to Sync Mail for <time period>.
    • Authentication type.
    • Allow movement of messages between accounts.
    • Allow sync of recent addresses.
    • Allow use of only Mail app.
  14. Configure the settings for using the S/MIME protocol in the Mail app. S/MIME is a protocol for transmitting digitally signed encrypted messages.
    • To use the S/MIME protocol to sign outgoing mail, select the Sign messages check box and select a certificate for the signature. A digital signature confirms the authenticity of the sender and indicates that the contents of the message have not been modified during transmission to the recipient. A message signature is available on devices running iOS version 10.3 or later.
    • To use the S/MIME protocol to encrypt outgoing mail, select the Encrypt messages by default check box and select a certificate for encryption (public key). Message encryption is available on devices running iOS version 10.3 or later.
    • To enable a user to encrypt individual messages, select the Show toggle button for encrypting messages check box. To send encrypted messages, the user must click the mail_lock icon in the Mail app in the To field.
  15. Click OK.

    The new Exchange ActiveSync account appears in the list.

  16. Click the Apply button to save the changes you have made.

As a result, once the policy is applied, Exchange ActiveSync accounts from the compiled list will be added on the user's mobile device.

Page top

[Topic 138694]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring an Exchange mailbox on Android devices (only Samsung)

To work with corporate mail, contacts, and the calendar on the mobile device, you should configure the Exchange mailbox settings (available only on Android 9 and earlier).

Configuration of an Exchange mailbox is possible only for Samsung devices.

To configure an Exchange mailbox on a mobile device:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Manage Samsung KNOX → Manage Samsung devices section.
  5. In the Exchange ActiveSync window, click the Configure button.

    The Exchange mail server settings window opens.

  6. In the Server address field, enter the IP address or DNS name of the server hosting the mail server.
  7. In the Domain field, enter the name of the mobile device user's domain on the corporate network.
  8. In the Synchronization interval drop-down list, select the desired interval for mobile device synchronization with the Microsoft Exchange server.
  9. To use the SSL (Secure Sockets Layer) data transport protocol, select the Use SSL connection check box.
  10. To use digital certificates to protect data transfer between the mobile device and the Microsoft Exchange server, select the Verify server certificate check box.
  11. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center.

Page top

[Topic 241826]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Installing root certificates on Android devices

A root certificate is a public key certificate issued by a trusted certificate authority (CA). Root certificates are used to verify custom certificates and guarantee their identity.

Kaspersky Security Center lets you add root certificates for Android devices operating in device owner mode. These root certificates are automatically installed to a trusted certificate store on devices.

To add a root certificate in Kaspersky Security Center:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Root certificates section.
  5. In the Root certificates section, click Add.

    The file explorer opens.

  6. Select a certificate file (.cer, .pem, or .key) and click Open.

    The Certificate window opens.

  7. View the certificate information and click Install Certificate...

    This starts the standard Certificate Import Wizard.

  8. Follow the wizard's instructions.

    After the wizard is finished, the root certificate appears in the list of certificates.

The added root certificates will be installed on Android devices in device owner mode after the next synchronization with Kaspersky Security Center.

Page top

[Topic 92963]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Managing third-party mobile apps

You can use containers to monitor the activity of mobile applications launched on the user's device. A container is a special shell for mobile apps which makes it possible to control the activity of the containerized app, thereby protecting the user's personal and corporate data on the device.

In Kaspersky Security for Mobile Service Pack 3 Maintenance Release 2, there is no longer support for creating containers for mobile apps. However, containers that were created in earlier versions of the application can be added to Android devices.

You can install a containerized app on the user's device in one of the following ways:

  • By sending the user an email message with a link to the installation package of the containerized app.
  • By specifying a containerized app as a required or allowed app in the App Control section of the policy properties window. After the mobile device is synchronized with Kaspersky Security Center, the app distribution package in the container is automatically copied to the user's device.

To install containerized apps, installation of apps from unknown sources must be allowed on the user's mobile device. To protect your device and data after installing containerized apps, it is recommended to prohibit installation of apps from unknown sources. For details about installing apps without Google Play, please refer to the Android Help Guide.

Page top

[Topic 133611]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring notifications for Kaspersky Endpoint Security for Android

If you do not want the mobile device user to be distracted by Kaspersky Endpoint Security for Android notifications, you can disable certain notifications.

The Kaspersky Endpoint Security uses the following tools to display the device protection status:

  • Protection status notification. This notification is pinned to the notification bar. Protection status notification cannot be removed. The notification displays the device protection status (for example, ) and number of issues, if any. You can tap the device protection status and see the list issues in the app.
  • App notifications. These notifications inform the device user about the application (for example, threat detection).
  • Pop-up messages. Pop-up messages require action from the device user (for example, action to take when a threat is detected).

All Kaspersky Endpoint Security for Android notifications are enabled by default.

On Android 13, the device user should grant permission to send notifications during the Initial Configuration Wizard or later.

An Android device user can disable all notifications from Kaspersky Endpoint Security for Android in the settings on the notification bar. If notifications are disabled, the user does not monitor the operation of the app and can ignore important information (for example, information about failures during device synchronization with Kaspersky Security Center). In this case, to find out the app operating status, the user must open Kaspersky Endpoint Security for Android.

To configure the display of notifications about the operation of Kaspersky Endpoint Security for Android:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Additional section.
  5. In the App notifications section, click the Configure button.

    The Device notification settings window opens.

  6. Select the Kaspersky Endpoint Security for Android issues that you want to hide on the user's mobile device and click the OK button.

    The Kaspersky Endpoint Security for Android will not display issues in the protection status notification. The Kaspersky Endpoint Security for Android will continue to display protection status notification and app notifications.

    Certain Kaspersky Endpoint Security for Android issues are mandatory and impossible to disable (such as issues about license expiration).

  7. To hide all notifications and pop-up messages, select the Disable notifications and pop-ups when app is background mode.

    Kaspersky Endpoint Security for Android will display the protection status notification only. The notification displays device protection status (for example, ) and number of issues. Also the app display notifications when user is working with the app (the user updates anti-virus databases manually, for example).

    Kaspersky experts recommended that you enable notifications and pop-up messages. If you disable notifications and pop-up messages when the app is in background mode, the app will not warn users about threats in real time. Mobile device users can learn about the device protection status only when they open the app.

  8. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center. The Kaspersky Endpoint Security for Android notifications that you disable will not be displayed on the user's mobile device.

Page top

[Topic 90313]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Connecting iOS MDM devices to AirPlay

Configure the connection to AirPlay devices to enable streaming of music, photos, and videos from the iOS MDM device to AirPlay devices. To be able to use AirPlay technology, the mobile device and AirPlay devices must be connected to the same wireless network. AirPlay devices include Apple TV devices (of the second and third generations), AirPort Express devices, speakers or radio sets with AirPlay support.

Automatic connection to AirPlay devices is available for controlled devices only.

To configure the connection of an iOS MDM device to AirPlay devices:

  1. In the console tree, in the Managed devices folder, select the administration group to which the iOS MDM devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking.
  4. In the policy Properties window, select the AirPlay section.
  5. In the AirPlay devices section, select the Apply settings on device check box.
  6. Click the Add button in the Passwords section.

    An empty row is added in the password table.

  7. In the Device name column, enter the name of the AirPlay device on the wireless network.
  8. In the Password column, enter the password to the AirPlay device.
  9. To restrict access of iOS MDM devices to AirPlay devices, create a list of allowed devices in the Allowed devices section. To do so, add the MAC addresses of AirPlay devices to the list of allowed devices.

    Access to AirPlay devices that are not on the list of allowed devices is blocked. If the list of allowed devices is left blank, Kaspersky Device Management for iOS will allow access to all AirPlay devices.

  10. Click the Apply button to save the changes you have made.

As a result, once the policy is applied, the user's mobile device will automatically connect to AirPlay devices to stream media content.

Page top

[Topic 90312]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Connecting iOS MDM devices to AirPrint

To enable printing of documents from the iOS MDM device wirelessly using AirPrint technology, configure automatic connection to AirPrint printers. The mobile device and printer must be connected to the same wireless network. Shared access for all users has to be configured on the AirPrint printer.

To configure the connection of an iOS MDM device to an AirPrint printer:

  1. In the console tree, in the Managed devices folder, select the administration group to which the iOS MDM devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking.
  4. In the policy Properties window, select the AirPrint section.
  5. Click the Add button in the AirPrint printers section.

    The Printer window opens.

  6. In the IP address field, enter the IP address of the AirPrint printer.
  7. In the Resource Path field, enter the path to the AirPrint printer.

    The path to the printer corresponds to the rp (resource path) key of the Bonjour protocol. For example:

    • printers/Canon_MG5300_series
    • ipp/print
    • Epson_IPP_Printer
  8. Click OK.

    The newly added AirPrint printer appears on the list.

  9. Click the Apply button to save the changes you have made.

As a result, once the policy is applied, the mobile device user can wirelessly print documents on the AirPrint printer.

Page top

[Topic 141382]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring the Access Point Name (APN)

To connect a mobile device to data transfer services on a mobile network, you should configure the APN (Access Point Name) settings.

In this section

Configuring APN on Android devices (only Samsung)

Configuring APN on iOS MDM devices

Page top

[Topic 90651]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring APN on Android devices (only Samsung)

Configuration of APN is possible only for Samsung devices.

A SIM card must be inserted to be able to use an access point on the user's mobile device. Access point settings are provided by the mobile telephony operator. Incorrect access point settings may result in additional mobile telephony charges.

To configure the Access Point Name (APN) settings:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Manage Samsung KNOX APN section.
  5. In the APN section, click the Configure button.

    The APN settings window opens.

  6. On the General tab, specify the following access point settings:
    1. In the APN type drop-down list, select the type of access point.
    2. In the APN name field, specify the name of the access point.
    3. In the MCC field, enter the mobile country code (MCC).
    4. In the MNC field, enter the mobile network code (MNC).
    5. If you have selected MMS or Internet and MMS as the type of access point, specify the following additional MMS settings:
      • In the MMS server field, specify the full domain name of the mobile carrier's server used for MMS exchange.
      • In the MMS proxy server field, specify the network name or IP address of the proxy server and the port number of the mobile carrier's server used for MMS exchange.
  7. On the Additional tab, configure the additional settings of the Access Point Name (APN):
    1. In the Authentication type drop-down list, select the type of mobile device user's authentication on the mobile carrier's server for network access.
    2. In the Server address field, specify the network name of the mobile carrier's server through which data transmission services are accessed.
    3. In the Proxy server address field, specify the network name or IP address and port number of the mobile carrier's proxy server for network access.
    4. In the User name field, enter the user name for authorization on the mobile network.
    5. In the Password field, enter the password for user authorization on the mobile network.
  8. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center.

Page top

[Topic 90309]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring APN on iOS MDM devices

The Access Point Name (APN) has to be configured in order to enable the mobile network data transmission service on the user's iOS MDM device.

The APN section is out of date. It is recommended to configure APN settings in the Cellular communications section. Before configuring cellular communication settings, make sure that the settings of the APN section have not been applied on the device (the Apply settings on device check box is cleared). The settings of the APN and Cellular communications sections cannot be used concurrently.

To configure an access point on a user's iOS MDM device:

  1. In the console tree, in the Managed devices folder, select the administration group to which the iOS MDM devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking.
  4. In the policy Properties window, select the Cellular communications section.
  5. In the Cellular communication settings section, select the Apply settings on device check box.
  6. In the APN type list, select the type of access point for data transfer on a GPRS/3G/4G mobile network:
    • Built-in APN – configuration of cellular communication settings for data transfer via a mobile network operator that supports operation with a built-in Apple SIM. For more details about devices with a built-in Apple SIM, please visit the Apple Technical Support website.
    • APN – configuration of cellular communication settings for data transfer via the mobile network operator of the inserted SIM card.
    • Built-in APN and APN – configuration of cellular communication settings for data transfer via the mobile network operators of the inserted SIM card and the built-in Apple SIM. For more details about devices with a built-in Apple SIM and a SIM card slot, please visit the Apple Technical Support website.
  7. In the APN name field, specify the name of the access point.
  8. In the Authentication type drop-down list, select the type of device user authentication on the mobile operator's server for network access (internet and MMS):
  9. In the User name field, enter the user name for authorization on the mobile network.
  10. In the Password field, enter the password for user authorization on the mobile network.
  11. In the Proxy server address and port field, enter the name of a host or the IP address of a proxy server and the number of the proxy server port.
  12. Click the Apply button to save the changes you have made.

As a result, the access point name (APN) is configured on the user's mobile device after the policy is applied.

Page top

[Topic 140467]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring the Android work profile

This section contains information about working with an Android work profile.

In this section

About Android work profile

Configuring the work profile

Page top

[Topic 140468]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

About Android work profile

Android Enterprise is a platform for managing the corporate mobile infrastructure, which provides company employees with a work environment in which they can use mobile devices. For details on using Android Enterprise, see the Google support website.

You can create the Android work profile (hereinafter also "work profile") on the user's mobile device. Android work profile is a safe environment on the user's device in which the administrator can manage apps and user accounts without restricting the user's use of his/her own data. When a work profile is created on the user's mobile device, the following corporate apps are automatically installed to it: Google Play Market, Google Chrome, Downloads, Kaspersky Endpoint Security for Android, and others. Corporate apps installed in the work profile and notifications of these apps are marked with a KSM_afw_box icon. You have to create a separate Google corporate account for the Google Play Market app. Apps installed in the work profile appear in the common list of apps.

Page top

[Topic 102298]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring the work profile

To configure the settings of the Android work profile:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Android work profile.
  5. In the Android work profile workspace, select the Create work profile check box.
  6. Specify the work profile settings:
    • To enable App Control in the Android work profile and disable it in the personal profile, select the Enable App Control in work profile only check box.

      In the Users section you can select App Control and use the workspace to create lists of allowed, blocked, recommended, and required apps, as well as allowed and blocked app categories in the section.

    • To enable Web Protection in the work profile and disable it in the personal profile for the Google Chrome browser, select the Enable Web Protection in work profile only check box.

      For Samsung Internet Browser and Huawei Browser, leave the Enable Web Protection in work profile only check box unselected. These browsers do not allow you to enable Web Protection only in the work profile. If you select this check box, Web Protection in these browsers will not work.

      You can specify website access settings (create a list of blocked website categories or a list of allowed websites) in the Web Protection section.

    • To prohibit the user from copying data by means of the Clipboard from work profile apps to personal apps, select the Prohibit data transfer from work profile to personal profile check box.
    • To block the user from using USB debugging mode on the mobile device in the work profile, select the Prohibit activation of USB debugging mode check box.

      In USB debugging mode, the user can download an app by using a workstation, for example.

    • To prohibit the user from installing apps in the Android work profile from all sources except Google Play, select the Prohibit installation of apps in work profile from unknown sources check box.
    • To prohibit the user from removing apps from the Android work profile, select the Prohibit removal of apps from work profile check box.
    • To also install the VPN-certificate in the personal profile, select the Duplicate installation of the VPN-certificate in personal profile check box. By default, VPN-certificates received from Kaspersky Security Center are installed in the work profile. This setting is applied when a new VPN-certificate is issued.
  7. To configure work profile settings on the user's mobile device, block changes to settings.
  8. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center. The space of the user's mobile device is divided into a work profile and a personal profile.

Page top

[Topic 88355]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Adding an LDAP account

To enable the iOS MDM device user to access corporate contacts on the LDAP server, add the LDAP account.

To add the LDAP account of the iOS MDM device user:

  1. In the console tree, in the Managed devices folder, select the administration group to which the iOS MDM devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking.
  4. In the policy Properties window, select the LDAP section.
  5. Click the Add button in the LDAP accounts section.

    The LDAP account window opens.

  6. In the Description field, enter a description of the user's LDAP account. You can use macros from the Macros available drop-down list.
  7. In the Account name field, enter the account name for authorization on the LDAP server. You can use macros from the Macros available drop-down list.
  8. In the Password field, enter the password of the LDAP account for authorization on the LDAP server.
  9. In the Server address field, enter the name of the LDAP server domain. You can use macros from the Macros available drop-down list.
  10. To use the SSL (Secure Sockets Layer) data transport protocol to secure the transmission of messages, select the Use SSL connection check box.
  11. Compile a list of search queries for the iOS MDM mobile device user access to corporate data on the LDAP server:
    1. Click the Add button in the Search settings section.

      A blank row appears in the table with search queries.

    2. In the Name column, enter the name of a search query.
    3. In the Search scope column, select the nesting level of the folder for the corporate data search on the LDAP server:
      • Base – search in the base folder of the LDAP server.
      • One level – search in folders on the first nesting level counting from the base folder.
      • Subtree – search in folders on all nesting levels counting from the base folder.
    4. In the Search base column, enter the path to the folder on the LDAP server with which the search begins (for example: "ou=people", "o=example corp").
    5. Repeat steps a-d for all search queries that you want to add to the iOS MDM device.
  12. Click OK.

    The new LDAP account appears in the list.

  13. Click the Apply button to save the changes you have made.

As a result, once the policy is applied, LDAP accounts from the compiled list will be added on the user's mobile device. The user can access corporate contacts in the standard iOS apps: Contacts, Messages, and Mail.

Page top

[Topic 90278]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Adding a calendar account

To enable the iOS MDM device user to access the user's calendar events on the CalDAV server, add the CalDAV account. Synchronization with the CalDAV server enables the user to create and receive invitations, receive event updates, and synchronize tasks with the Reminders app.

To add the CalDAV account of the iOS MDM device user:

  1. In the console tree, in the Managed devices folder, select the administration group to which the iOS MDM devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking.
  4. In the policy Properties window, select the Calendar section.
  5. Click the Add button in the CalDAV accounts section.

    The CalDAV account window opens.

  6. In the Description field, enter a description of the user's CalDAV account.
  7. In the Server address and port field, enter the name of a host or the IP address of a CalDAV server and the number of the CalDAV server port.
  8. In the Main URL field, specify the URL of the CalDAV account of the iOS MDM device user on the CalDAV server (for example: http://example.com/caldav/users/mycompany/user).

    The URL should begin with "http://" or "https://".

  9. In the Account name field, enter the account name for authorization on the CalDAV server.
  10. In the Password field, set the CalDAV account password for authorization on the CalDAV server.
  11. To use the SSL (Secure Sockets Layer) data transport protocol to secure the transmission of event data between the CalDAV server and the mobile device, select the Use SSL connection check box.
  12. Click OK.

    The new CalDAV account appears in the list.

  13. Click the Apply button to save the changes you have made.

As a result, once the policy is applied, CalDAV accounts from the compiled list will be added on the user's mobile device.

Page top

[Topic 90315]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Adding a contacts account

To enable the iOS MDM device user to synchronize data with the CardDAV server, add the CardDAV account. Synchronization with the CardDAV server enables the user to access the contact details from any device.

To add the CardDAV account of the iOS MDM device user:

  1. In the console tree, in the Managed devices folder, select the administration group to which the iOS MDM devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking.
  4. In the policy Properties window, select the Contacts section.
  5. Click the Add button in the CardDAV accounts section.

    The CardDAV account window opens.

  6. In the Description field, enter a description of the user's CardDAV account. You can use macros from the Macros available drop-down list.
  7. In the Server address and port field, enter the name of a host or the IP address of a CardDAV server and the number of the CardDAV server port.
  8. In the Main URL field, specify the URL of the CardDAV account of the iOS MDM device user on the CardDAV server (for example: http://example.com/carddav/users/mycompany/user).

    The URL should begin with "http://" or "https://".

  9. In the Account name field, enter the account name for authorization on the CardDAV server. You can use macros from the Macros available drop-down list.
  10. In the Password field, set the CardDAV account password for authorization on the CardDAV server.
  11. To use the SSL (Secure Sockets Layer) data transport protocol to secure the transmission of contacts between the CardDAV server and the mobile device, select the Use SSL connection check box.
  12. Click OK.

    The new CardDAV account appears in the list.

  13. Click the Apply button to save the changes you have made.

As a result, once the policy is applied, CardDAV accounts from the compiled list will be added on the user's mobile device.

Page top

[Topic 90316]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring calendar subscription

To enable the iOS MDM device user to add events of shared calendars (such as the corporate calendar) to the user's calendar, add subscription to this calendar. Shared calendars are calendars of other users who have a CalDAV account, iCal calendars, and other openly published calendars.

To add calendar subscription:

  1. In the console tree, in the Managed devices folder, select the administration group to which the iOS MDM devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking.
  4. In the policy Properties window, select the Calendar subscription section.
  5. Click the Add button in the Calendar subscriptions section.

    The Calendar Subscription window opens.

  6. In the Description field, enter a description of the calendar subscription.
  7. In the Server web address field, specify the URL of the third-party calendar.

    In this field, you can enter the mail URL of the CalDAV account of the user to whose calendar you are subscribing. You can also specify the URL of an iCal calendar or a different openly published calendar.

  8. In the User name field, enter the user account name for authentication on the server of the third-party calendar.
  9. In the Password field, enter the calendar subscription password for authentication on the server of the third-party calendar.
  10. To use the SSL (Secure Sockets Layer) data transport protocol to secure the transmission of event data between the CalDAV server and the mobile device, select the Use SSL connection check box.
  11. Click OK.
  12. The new calendar subscription appears in the list.
  13. Click the Apply button to save the changes you have made.

As a result, once the policy is applied, events from shared calendar on the list will be added to the calendar on the user's mobile device.

Page top

[Topic 90308]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Adding web clips

A web clip is an app that opens a website from the Home screen of the mobile device. By clicking web clip icons on the home screen of the device, the user can quickly open websites (such as the corporate website).

You can add web clips to user devices and specify web clip icons displayed on the screen.

Adding web clips to Android devices

To add a web clip on a user's Android device:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Device management section.
  5. In the Adding web clips to device home screen section, click Add.

    The Add web clip window opens.

  6. In the Name field, enter the name of the web clip to be displayed on the home screen of the Android device.
  7. In the URL field, enter the web address of the website that will open when the web clip icon is clicked. The address should begin with "http://" or "https://".
  8. In the Icon field, specify the image for the web clip icon: click Browse... and select an image file. The PNG and JPEG file formats are supported. If you do not select an image for the web clip, a blank square is displayed as the icon.
  9. Click OK.

    The new web clip appears in the list.

  10. Click the Apply button to save the changes you have made.

Once the policy is applied to a device, the Kaspersky Endpoint Security for Android app shows notifications to prompt the user to install the web clips you created. After the user installs these web clips, the corresponding icons are added on the home screen of the device.

The maximum number of web clips that can be added to an Android device depends on the device type. When this number is reached, web clips are no longer added to the Android device.

Adding web clips to iOS MDM devices

By default, the following restrictions on web clip usage apply:

  • The user cannot manually remove web clips from the mobile device.
  • Websites that open when the user clicks a web clip icon do not open in full-screen mode.
  • The corner rounding, shadow, and gloss visual effects are applied to the web clip icon on the screen.

To add a web clip on a user's iOS MDM device:

  1. In the console tree, in the Managed devices folder, select the administration group to which the iOS MDM devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking.
  4. In the policy Properties window, select the Web Clips section.
  5. Click the Add button in the Web Clips section.

    The Web Clip window opens.

  6. In the Name field, enter the name of the web clip to be displayed on the home screen of the iOS MDM device.
  7. In the URL field, enter the web address of the website that will open when the web clip icon is clicked. The address should begin with "http://" or "https://".
  8. To allow the user to remove a web clip from the iOS MDM device, select the Allow removal check box.
  9. Click the Select button and specify the file with the image for the web clip icon.

    The icon is displayed on the home screen of the iOS MDM device. The image must meet the following requirements:

    • Image size no greater than 400 х 400 pixels.
    • File format: GIF, JPEG, or PNG.
    • File size no greater than 1 MB.

    The web clip icon is available for preview in the Icon field. If you do not select an image for the web clip, a blank square is displayed as the icon.

    If you want the web clip icon to be displayed without special visual effects (rounding of icon corners and gloss effect), select the Precomposed icon check box.

  10. If you want the website to open in full-screen mode on the iOS MDM device when you click the icon, select the Full screen Web Clip check box.
  11. Click OK.

    The new web clip appears in the list.

  12. Click the Apply button to save the changes you have made.

As a result, once the policy is applied, web clip icons from the list you have created are added on the home screen of the user's mobile device.

Page top

[Topic 90275]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Adding fonts

To add a font on a user's iOS MDM device:

  1. In the console tree, in the Managed devices folder, select the administration group to which the iOS MDM devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking.
  4. In the policy Properties window, select the Fonts section.
  5. Click the Add button in the Fonts section.

    The Font window opens.

  6. In the File name field, specify the path to the font file (a file with the .ttf or .otf extension).

    Fonts with the ttc or otc extension are not supported.

    Fonts are identified using the PostScript name. Do not install fonts with the same PostScript name even if their content is different. Installing fonts with the same PostScript name will result in an undefined error.

  7. Click Open.

    The new font appears in the list.

  8. Click the Apply button to save the changes you have made.

As a result, once the policy is applied, the user will be prompted to install fonts from the list that has been created.

Page top

[Topic 241818]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Device owner mode

This section contains information about how to manage the settings of Android mobile devices in device owner mode. For information about device owner mode deployment, see here.

Device owner mode offers the following features and control options for Android mobile devices:

In this section

Restricting Android features on devices

Managing Google Chrome settings

Configuring Kiosk mode

Managing Exchange ActiveSync for Gmail

Connecting to an NDES/SCEP server

Page top

[Topic 241819]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Restricting Android features on devices

You can restrict Android operating system features in device owner mode. For example, you can restrict factory reset, changing credentials, use of Google Play and Google Chrome, file transfer over USB, changing location settings, and manage system updates.

You can restrict Android features in the Feature restrictions section.

To open the Feature restrictions section:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Device owner mode > Feature restrictions section.

Restrict device features

On the Device Features tab of the Feature restrictions section, you can enable or disable the following features:

  • Prohibit factory reset

    Selecting or clearing this check box specifies whether the device user is allowed to perform a factory reset from device settings.

    This check box is cleared by default.

  • Prohibit screen capture

    Selecting or clearing this check box specifies whether the device user is allowed to take screenshots or capture the device screen.

    This check box is cleared by default.

  • Prohibit outgoing phone calls

    Selecting or clearing this check box specifies whether the device user is allowed to make outgoing phone calls on this device.

    This check box is cleared by default.

  • Prohibit sending and receiving SMS messages

    Selecting or clearing this check box specifies whether the device user is allowed to send and receive SMS messages on this device.

    This check box is cleared by default.

  • Prohibit changing credentials

    Selecting or clearing this check box specifies whether the device user is allowed to change user credentials in the operating system.

    This check box is cleared by default.

  • Prohibit status bar (Android 6.0 or later)

    Preventing the status bar from being displayed.

    If the check box is selected, the status bar is not displayed on the device. Notifications and quick settings accessible via the status bar are also blocked.

    If the check box is cleared, the status bar can be displayed on the device.

    The restriction is supported on devices with Android 6.0 or later.

    This check box is cleared by default.

  • Prohibit safe boot (Android 6.0 or later)

    Selecting or clearing this check box specifies whether the device user is allowed to boot the device in safe mode.

    The restriction is supported on devices with Android 6.0 or later.

    This check box is cleared by default.

  • Force screen on when plugged in to AC charger (Android 6.0 or later)

    Selecting or clearing the check box specifies if the device screen will be on while the device is charging with an AC charger.

    The restriction is supported on devices with Android 6.0 or later.

    This check box is cleared by default.

  • Force screen on when plugged in to USB charger (Android 6.0 or later)

    Selecting or clearing of the check box specifies whether the device screen will be on while the device is charging via a USB charger.

    The restriction is supported on devices with Android 6.0 or later.

    This check box is cleared by default.

  • Force screen on when plugged in to wireless charger (Android 6.0 or later)

    Selecting or clearing this check box specifies whether the device screen will be on while the device is charging via a wireless charger.

    The restriction is supported on devices with Android 6.0 or later.

    This check box is cleared by default.

Restrict app features

On the Apps tab of the Feature restrictions section, you can enable or disable the following features:

  • Prohibit use of camera

    Selecting or clearing the check box specifies whether the device user is allowed to use all cameras on the device.

    This check box is cleared by default.

  • Prohibit camera toggle (Android 12.0 or later)

    Preventing the device user from toggling the camera.

    If the check box is selected, the device user cannot block the camera access via the system toggle.

    If the check box is cleared, the device user is allowed to use the camera toggle.

    The restriction is supported on devices with Android 12.0 or later.

    This check box is cleared by default.

  • Prohibit use of Google Play

    Selecting or clearing the check box specifies whether the device user is allowed to use Google Play.

    This check box is cleared by default.

  • Prohibit use of Google Chrome

    Preventing use of Google Chrome.

    If the check box is selected, the device user cannot start Google Chrome or configure it in system settings.

    If the check box is cleared, the device user is allowed to use Google Chrome on the device.

    The check box is cleared by default.

  • Prohibit use of Google Assistant

    Selecting or clearing the check box specifies whether the device user is allowed to use Google Assistant on the device.

    This check box is cleared by default.

  • Prohibit installation of apps from unknown sources

    Selecting or clearing the check box specifies whether the device user is allowed to install apps from unknown sources.

    This check box is cleared by default.

  • Prohibit modification of apps in Settings

    Preventing modifying apps in Settings.

    If the check box is selected, the device user is disallowed to perform the following actions:

    • Uninstalling apps
    • Disabling apps
    • Clearing app caches
    • Clearing app data
    • Force stopping apps
    • Clearing app defaults

      If the check box is cleared, the device user is allowed to modify apps in Settings.

      This check box is cleared by default.

  • Prohibit installation of apps

    Selecting or clearing the check box specifies whether the device user is allowed to install apps on the device.

    This check box is cleared by default.

  • Prohibit uninstallation of apps

    Selecting or clearing the check box specifies whether a device user is allowed to uninstall apps from this device.

    This check box is cleared by default.

  • Prohibit disabling app verification

    Selecting or clearing the check box specifies whether the device user is allowed to disable app verification.

    This check box is cleared by default.

Restrict storage features

On the Storage tab of the Feature restrictions section, you can enable or disable the following features:

  • Prohibit debugging features

    Preventing use of debugging features.

    If the check box is selected, the device user cannot use USB debugging features and developer mode.

    If the check box is cleared, the device user is allowed to enable and access debugging features and developer mode.

    This check box is cleared by default.

  • Prohibit mounting physical external media

    Selecting or clearing the check box specifies whether the device user is allowed to mount physical external media, such as SD cards and OTG adapters.

    This check box is cleared by default.

  • Prohibit file transfer over USB

    Selecting or clearing this check box specifies whether the device user is allowed to transfer files over USB.

    This check box is cleared by default.

  • Prohibit backup service (Android 8.0 or later)

    Selecting or clearing the check box specifies whether the device user is allowed to enable or disable the backup service.

    The restriction is supported on devices with Android 8.0 or later.

    This check box is cleared by default.

Restrict network features

On the Network tab of the Feature restrictions section, you can enable or disable the following features:

  • Prohibit use of Wi-Fi

    Selecting or clearing the check box specifies whether the device user is allowed to use Wi-Fi and configure it in Settings.

    This check box is cleared by default.

  • Prohibit use of Bluetooth (Android 8.0 or later)

    Preventing use of Bluetooth.

    If the check box is selected, the device user cannot turn on and configure Bluetooth via Settings.

    If the check box is cleared, the device user is allowed to use Bluetooth.

    The restriction is supported on devices with Android 8.0 and later. For earlier versions of Android, select the Prohibit use of Bluetooth check box in the Device Management section.

    This check box is cleared by default.

  • Prohibit changing Wi-Fi settings

    Selecting or clearing the check box specifies whether the device user is allowed to configure Wi-Fi access points via Settings. The restriction does not affect Wi-Fi tethering settings.

    This check box is cleared by default.

  • Prohibit changing pre-configured Wi-Fi networks

    Selecting or clearing the check box specifies whether the device user is allowed to change Wi-Fi configurations added by the administrator in the Wi-Fi section.

    This check box is cleared by default.

  • Prohibit changing Bluetooth settings

    Selecting or clearing the check box specifies whether the device user is allowed to configure Bluetooth via Settings.

    This check box is cleared by default.

  • Prohibit changing VPN settings

    Preventing changing VPN settings.

    If the check box is selected, the device user cannot configure a VPN in Settings and VPNs are prohibited from starting.

    If the check box is cleared, the device user is allowed to modify a VPN in Settings.

    This check box is cleared by default.

  • Prohibit changing mobile network settings

    Selecting or clearing the check box specifies whether the device user is allowed to change mobile network settings.

    This check box is cleared by default.

  • Prohibit use of Android Beam via NFC

    Selecting or clearing the check box specifies whether beaming out data from apps via NFC is allowed on the device. However, the device user can enable or disable NFC.

    This check box is cleared by default.

  • Prohibit use of tethering

    Selecting or clearing the check box specifies whether the device user is allowed to configure tethering and hotspots.

    This check box is cleared by default.

  • Prohibit outgoing data sharing over Bluetooth (Android 8.0 or later)

    Selecting or clearing the check box specifies whether outgoing Bluetooth data sharing is allowed on the device.

    The restriction is supported on devices with Android 8.0 or later.

    This check box is cleared by default.

Restrict location services

On the Location Services tab of the Feature restrictions section, you can configure the following settings:

  • Prohibit use of location

    Preventing turning location on and off.

    If the check box is selected, the device user cannot turn location on or off. Search in Anti-Theft mode becomes unavailable.

    If the check box is cleared, the device user can turn location on or off.

    This check box is cleared by default.

    If both the Prohibit use of location and Prohibit changing location settings (Android 9.0 and later) check boxes are selected, location is disabled and the device user cannot enable it.

  • Prohibit changing location settings (Android 9.0 or later)

    Preventing changing location settings.

    If the check box is selected, the device user cannot change location settings or disable location.

    If the check box is cleared, the device user can change location settings.

    The restriction is supported on devices with Android 9.0 or later.

    This check box is cleared by default.

    If both the Prohibit use of location and Prohibit changing location settings (Android 9.0 and later) check boxes are selected, location is disabled and the device user cannot enable it.

Restrict system updates

Managing update settings on mobile devices is vendor-specific. On some Android devices, the restriction on manual installation of operating system updates may work incorrectly.

On the Updates tab of the Feature restrictions section, you can configure the following settings:

  • Set system update policy

    Type of system update policy.

    If the check box is selected, one of the following system update policies is set:

    • Install updates automatically. Installs system updates immediately without user interaction. This option is selected by default.
    • Install updates during daily window. Installs system updates during a daily maintenance window without user interaction.

      The administrator also needs to set the start and end of the daily maintenance window in the Start time and End time fields respectively.

    • Postpone updates for 30 days. Postpones the installation of system updates for 30 days.

      After the specified period, the operating system prompts the device user to install the updates. The period is reset and starts again if a new system update is available.

      If the check box is cleared, a system update policy is not set.

      This check box is selected by default.

      Managing update settings on mobile devices is vendor-specific. On some Android devices, the restriction on manual installation of operating system updates may work incorrectly.

  • System update freeze periods (Android 9.0 and later)

    The System update freeze periods (Android 9.0 and later) block lets you set one or more freeze periods of up to 90 days during which system updates will not be installed on the device. When the device is in a freeze period, it behaves as follows:

    • The device does not receive any notifications about pending system updates.
    • System updates are not installed.
    • The device user cannot check for system updates manually.

      To add a freeze period, click Add period and enter the start and end of the freeze period in the Start time and End time fields respectively.

    Note: Each freeze period can be at most 90 days long, and the interval between adjacent freeze periods must be at least 60 days.

    The restriction is supported on devices with Android 9.0 and later.

    Managing update settings on mobile devices is vendor-specific. On some Android devices, the restriction on manual installation of operating system updates may work incorrectly.

Page top

[Topic 241820]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Managing Google Chrome settings

You can manage Google Chrome settings in the Google Chrome settings section in device owner mode.

To open the Google Chrome settings section:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Device owner mode > Google Chrome settings section.

Manage content settings

On the Content tab of the Google Chrome settings section, you can specify the following content settings:

  • Set default cookie settings

    Default cookie settings.

    If the check box is selected, one of the following options will be applied to all sites by default:

    • Allow all sites to set local data (default)
    • Do not allow any site to set local data
    • Keep cookies for duration of session

      If the check box is cleared, the user's personal settings will be applied.

      The setting is supported in Google Chrome version 30 or later.

      This check box is selected by default.

      There must be no conflicting URL patterns that you specify in the Allow cookies on these sites, Block cookies on these sites, and Allow cookies on these sites for one session only fields. If no URL is specified and the Set default cookies settings check box is selected, the option selected in the drop-down list will be applied to all sites.

  • Allow cookies on these sites

    A list of sites that are allowed to set cookies. You can also set URL patterns, for example: [*.]example.com.

    The setting is supported in Google Chrome version 30 or later.

  • Block cookies on these sites

    A list of sites that are prohibited to set cookies. You can also set URL patterns, for example: [*.]example.com.

    The setting is supported in Google Chrome version 30 or later.

  • Allow cookies on these sites for one session only

    A list of sites that are allowed to set cookies only for one session. You can also set URL patterns, for example: [*.]example.com.

    The setting is supported in Google Chrome version 30 or later.

  • Set default JavaScript settings

    Default JavaScript settings.

    If the check box is selected, one of the following options will be applied and the device user will not be able to change it:

    • Allow all sites to run JavaScript (default)
    • Do not allow any site to run JavaScript

      If the check box is cleared, user personal settings will be applied.

      The setting is supported in Google Chrome version 30 or later.

      This check box is cleared by default.

      If the Allow JavaScript on these sites and Block JavaScript on these sites settings are not specified and the Set default JavaScript settings check box is selected, the selected option will be applied to all sites.

  • Allow JavaScript on these sites

    A list of sites that are allowed to run JavaScript. You can also set URL patterns, for example: [*.]example.com.

    The setting is supported in Google Chrome version 30 or later.

    If the Allow JavaScript on these sites and Block JavaScript on these sites settings are not specified and the Set default JavaScript settings check box is selected, the selected option will be applied to all sites.

  • Block JavaScript on these sites

    A list of sites that are prohibited to run JavaScript. You can also set URL patterns, for example: [*.]example.com.

    The setting is supported in Google Chrome version 30 or later.

    If the Allow JavaScript on these sites and Block JavaScript on these sites settings are not specified and the Set default JavaScript settings check box is selected, the selected option will be applied to all sites.

  • Set default pop-up settings

    Default pop-up setting.

    If the check box is selected, one of the following options applies to pop-ups:

    • Allow all sites to show pop-ups. Lets all sites open pop-up windows. This value is selected by default.
    • Do not allow any site to show pop-ups. Prohibits all sites to open pop-up windows.

      If the check box is cleared, pop-ups are blocked, but a device user can change this behavior in Settings.

      The setting is supported in Google Chrome version 33 or later.

      The check box is cleared by default.

      If the Allow pop-ups on these sites and Block pop-ups on these sites settings are not specified and the Set default pop-up settings check box is selected, the selected option will be applied to all sites.

  • Allow pop-ups on these sites

    A list of sites that are allowed to show pop-ups. You can also set URL patterns, for example: [*.]example.com.

    The setting is supported in Google Chrome version 34 or later.

    If the Allow pop-ups on these sites and Block pop-ups on these sites settings are not specified and the Set default pop-up settings check box is selected, the selected option will be applied to all sites.

  • Block pop-ups on these sites

    A list of sites that are prohibited to show pop-ups. You can also set URL patterns, for example: [*.]example.com.

    The setting is supported in Google Chrome version 34 or later.

    If the Allow pop-ups on these sites and Block pop-ups on these sites settings are not specified and the Set default pop-up settings check box is selected, the selected option will be applied to all sites.

  • Set user location tracking settings

    The default geographic location settings.

    If the check box is selected, one of the following options will be applied to all sites by default:

    • Allow all sites to track location
    • Do not allow any site to track location
    • Ask whenever site wants to track location (default)

      If the check box is cleared, user personal settings will be applied.

      The setting is supported in Google Chrome version 30 or later.

      This check box is cleared by default.

Manage proxy settings

On the Proxy tab of the Google Chrome settings section, you can specify the following proxy settings:

  • Set proxy mode

    Proxy settings for Google Chrome and ARC-apps.

    If the check box is selected, one of the following options will be applied and the device user is prevented from changing proxy settings:

    • Never use proxy. Prohibits use of proxies and all other proxy settings are ignored. This option is selected by default.
    • Detect proxy settings automatically. Detects proxy settings automatically and all other options are ignored.
    • Use PAC file. Uses the proxy PAC file specified in the PAC file URL field.
    • Use fixed proxy servers. Uses the data specified in the Proxy server URL and Bypass list fields.
    • Use system proxy settings. Uses the system proxy settings.

      If the check box is cleared, user personal settings will be applied.

      The setting is supported in Google Chrome version 30 or later.

      This check box is selected by default.

  • Proxy server URL

    A URL of the proxy server.

    The setting is supported in Google Chrome version 30 or later.

  • PAC file URL

    A URL to a proxy .PAC file.

    The setting is supported in Google Chrome version 30 or later.

  • Bypass list

    A list of hosts for which the proxy will be bypassed.

    The setting is supported in Google Chrome version 30 or later.

Manage search settings

On the Search tab of the Google Chrome settings section, you can specify the following search settings:

  • Enable Touch to Search

    Selecting or clearing this check box specifies whether the device user is allowed to use Touch to Search and turn the feature on or off.

    The setting is supported in Google Chrome version 40 or later.

    This check box is selected by default.

  • Enable default search provider

    Default search provider settings.

    If the check box is selected, a default search provider is used when a user enters non-URL text in the address bar. The default search provider depends on search provider settings below this check box:

    • If you leave search provider settings empty, the device user can choose the search provider in the browser settings.
    • If you configure settings of the default search provider, this search provider is always used, and the device user can't choose the search provider in the browser.

    This check box is selected by default, but the default search provider settings are not configured.

    If you want to disable search in Google Chrome, we recommend that you leave the Enable default search provider check box selected and set the Search provider name parameter to the site of a non-search system. On some Google Chrome versions, there can be problems in Google Chrome operation if the check box is cleared.

    The setting is supported in Google Chrome version 30 or later.

    The default search provider parameters are:

    • Search provider name
    • Keyword
    • Search URL
    • Suggest URL
    • Icon URL
    • Encodings
    • Alternate URLs
    • Image URL
    • New tab URL
    • Parameters for search URL that uses POST
    • Parameters for suggest URL that uses POST
    • Parameters for image URL that uses POST
  • Search provider name

    The default search provider name.

    The setting is supported in Google Chrome version 30 or later.

  • Keyword

    A keyword or shortcut used in the address bar to trigger the search for the search provider.

    The setting is supported in Google Chrome version 30 or later.

  • Search URL

    The URL of the search engine used during default searches.

    The setting is supported in Google Chrome version 30 or later.

  • Suggest URL

    The URL of the search engine to provide search suggestions.

    The setting is supported in Google Chrome version 30 or later.

  • Icon URL

    The URL of the default search provider's favicon.

    The setting is supported in Google Chrome version 30 or later.

  • Encodings

    Character encodings supported by the search provider. The supported encodings are:

    • UTF-8
    • UTF-16
    • GB2312
    • ISO-8859-1

      The setting is supported in Google Chrome version 30 or later.

  • Alternate URLs

    A list of alternate URLs to retrieve search terms from the search engine.

    The setting is supported in Google Chrome version 30 or later.

  • Image URL

    The URL of the search engine used for image search.

    The setting is supported in Google Chrome version 30 or later.

  • New tab URL

    The URL of the search engine used to provide a New Tab page.

    The setting is supported in Google Chrome version 30 or later.

  • Parameters for search URL that uses POST

    URL parameters when searching a URL with the POST method. The parameters are comma-separated key-value pairs. If a value is a template parameter, for example, '{searchTerms}', it is replaced with real search terms. For example:

    q={searchTerms},ie=utf-8,oe=utf-8

    The setting is supported in Google Chrome version 30 or later.

  • Parameters for suggest URL that uses POST

    URL parameters for search suggestions using the POST method. The parameters are comma-separated key-value pairs. If a value is a template parameter, for example, '{searchTerms}', it is replaced with real search terms. For example:

    q={searchTerms},ie=utf-8,oe=utf-8

    The setting is supported in Google Chrome version 30 or later.

  • Parameters for image URL that uses POST

    URL parameters for image search using the POST method. The parameters are comma-separated key-value pairs. If a value is a template parameter, for example, '{imageThumbnail}', it is replaced with the real image thumbnail. For example:

    content={imageThumbnail},url={imageURL},sbisrc={SearchSource}

    The setting is supported in Google Chrome version 30 or later.

Manage password settings

On the Passwords tab of the Google Chrome settings section, you can specify the following password settings:

  • Enable saving passwords

    Selecting or clearing the check box specifies whether Google Chrome will remember the passwords the device user enters and also offer them the next time the device user signs in.

    The setting is supported in Google Chrome version 30 or later.

    This check box is selected by default.

Manage page settings

On the Pages tab of the Google Chrome settings section, you can specify the following page settings:

  • Enable alternate error pages

    Selecting the check box specifies whether Google Chrome is allowed to use built-in error pages, such as "Page not found".

    The setting is supported in Google Chrome version 30 or later.

    This check box is selected by default.

  • Enable AutoFill for addresses

    Autofill settings for addresses.

    If the check box is selected, the device user is allowed to manage AutoFill for addresses in the user interface.

    If the check box is cleared, AutoFill never suggests or fills in address information, nor does it save additional address information that the device user submits while browsing the web.

    The setting is supported in Google Chrome version 69 or later.

    This check box is selected by default.

  • Enable AutoFill for credit cards

    Autofill settings for credit cards.

    If the check box is selected, the device user is allowed to manage AutoFill suggestions for credit cards in the user interface.

    If the check box is cleared, AutoFill never suggests or fills in credit card information, nor does it save additional credit card information that the device user might submit while browsing the web.

    The setting is supported in Google Chrome version 63 or later.

    This check box is selected by default.

Manage other settings

On the Other tab of the Google Chrome settings section, you can specify the following settings:

  • Enable printing

    Selecting or clearing this check box specifies whether the device user is allowed to print in Google Chrome.

    The setting is supported in Google Chrome version 39 or later.

    This check box is selected by default.

  • Set Google Safe Browsing settings

    Google Safe Browsing protection level.

    If the check box is selected, the device user is allowed to manage the Google Safe Browsing settings in Google Chrome, as well as select the protection level. The protection levels are:

    • Google Safe Browsing is never active. Disables Google Safe Browsing completely.
    • Google Safe Browsing is active in standard mode. Makes Google Safe Browsing always enabled in standard protection mode. This option is selected by default.
    • Google Safe Browsing is active in enhanced mode. Makes Google Safe Browsing always enabled in enhanced protection mode, but device user browsing experience data will be sent to Google.

      If the check box is cleared, Google Safe Browsing will operate in standard protection mode and the device user is allowed to change Google Safe Browsing settings.

      The setting is supported in Google Chrome version 87 or later.

      This check box is selected by default.

  • Disable saving browser history

    Selecting or clearing this check box specifies whether browsing history is saved and tab syncing is on.

    The setting is supported in Google Chrome version 30 or later.

    This check box is cleared by default.

  • Disable proceeding from Google Safe Browsing warning page

    Selecting or clearing this check box specifies whether the device user is allowed to proceed to the flagged site on Google Safe Browsing warnings, such as malware and phishing. The restriction does not apply to issues related to SSL certificate, such as invalid or expired certificates.

    The setting is supported in Google Chrome version 30 or later.

    This check box is cleared by default.

  • Enable network prediction

    Selecting or clearing this check box specifies whether Google Chrome will predict such network actions as DNS prefetching, TCP and SSL preconnection and prerendering of webpages.

    If the check box is cleared, network prediction is disabled, but the device user can enable it.

    The setting is supported in Google Chrome version 38 or later.

    This check box is cleared by default.

  • Force Google SafeSearch

    Selecting or clearing this check box specifies whether Google Search queries will be performed via Google SafeSearch.

    The setting is supported in Google Chrome version 41 or later.

    This check box is cleared by default.

  • Set Restricted Mode for YouTube

    Minimum required Restricted Mode level for YouTube.

    If the check box is selected, a minimum required Restricted Mode level for YouTube is set and the device user cannot pick a less restricted mode. Restricted mode levels are:

    • Do not enforce Restricted Mode. Specifies that Google Chrome does not force Restricted mode. However, external policies might still enforce Restricted mode. This option is selected by default.
    • Enforce at least Moderate Restricted Mode. Lets a device user enable the Moderate and Strict Restricted mode on YouTube, but prohibits turning Restricted mode off.
    • Enforce Strict Restricted Mode. Makes Strict Restricted mode on YouTube be always active.

      If the check box is cleared, Google Chrome does not require use of Restricted mode for YouTube, but Restricted mode can be enforced by external rules, such as YouTube rules.

      The setting is supported in Google Chrome version 55 or later.

      This check box is selected by default.

  • Set availability of Incognito mode

    Availability of Incognito mode in Google Chrome.

    If the check box is selected, the admin can specify whether the device user is allowed to open pages in Incognito mode by selecting one of the following options:

    • Incognito mode is available (default)
    • Incognito mode is disabled

      If the check box is cleared, the device user cannot open pages in Incognito mode in Google Chrome.

      The setting is supported in Google Chrome version 30 or later.

      This check box is selected by default.

  • Enable search suggestions

    Selecting or clearing this check box specifies whether search suggestions are enabled in Google Chrome's address bar.

    The setting is supported in Google Chrome version 30 or later.

    This check box is selected by default.

  • Set Translate settings

    Enabling translation functionality.

    If the check box is selected, the administrator can set the following translation options:

    • Always offer translation. Shows the integrated translation toolbar and a translate option on the right-click context menu. This option is selected by default.
    • Never offer translation. Disables all built-in translation functionality.

      If the check box is cleared, the user's personal settings will be applied.

      The setting is supported in Google Chrome version 30 or later.

      This check box is cleared by default.

  • Enable bookmark editing

    Selecting or clearing this check box specifies whether the device user is allowed to add, remove, or modify bookmarks.

    The setting is supported in Google Chrome version 30 or later.

    This check box is selected by default.

  • Managed bookmarks

    An admin-managed list of bookmarks. The list is a dictionary where the keys are the "name" and "url". In other words, the key holds a bookmark's name and target. You can also set up a subfolder with a "children" key, which also has a list of bookmarks.

    By default, the folder name for managed bookmarks is "Managed bookmarks". You can change it by adding a new sub-dictionary. To do this, specify the "toplevel_name" key with the required folder name as its value.

    If you enter an incomplete URL as a bookmark's target, Google Chrome will substitute it with a URL as if it was submitted through the address bar. For example, "kaspersky.com" becomes "https://www.kaspersky.com".

    For example:

    "ManagedBookmarks": [{

    //Changes the default folder name

    "toplevel_name": "My managed bookmarks folder"

    },

    {

    //Adds a bookmark to the managed bookmarks folder

    "name": "Kaspersky",

    "url": "kaspersky.com"

    },

    {

    "name": "Kaspersky products",

    "children": [{

    "name": "Kaspersky Endpoint Security",

    "url": "kaspersky.com/enterprise-security/endpoint"

    },

    {

    "name": "Kaspersky Security for Mail Server",

    "url": "kaspersky.com/enterprise-security/mail-server-security"

    }

    ]

    }

    ]

    The setting is supported in Google Chrome version 37 or later.

  • Block access to these URLs

    A list of forbidden URLs. You can also set URL patterns, for example: [*.]example.com.

    The setting is supported in Google Chrome version 86 or later.

  • Allow access to these URLs (exceptions to blocked URLs)

    A list of URLs that are exceptions to the list specified in Block access to these URLs. You can also set URL patterns, for example: [*.]example.com.

    The setting is supported in Google Chrome version 86 or later.

  • Set minimum SSL version

    Minimum allowed SSL version.

    If the check box is selected, Google Chrome will not use SSL and TLS older than the selected version. Available version are:

    • TLS 1.0 (default)
    • TLS 1.1
    • TLS 1.2

      If the check box is cleared, Google Chrome will report an error for TLS 1.0 and TLS 1.1 protocols, but the device user will be able to bypass it.

      The setting is supported in Google Chrome version 66 or later.

      This check box is cleared by default.

Page top

[Topic 241821]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring Kiosk mode

Kiosk mode is a Kaspersky Endpoint Security for Android feature that lets you limit the set of apps available to a device user, whether a single app or multiple apps. You can also efficiently manage some device settings.

The kiosk mode settings apply to devices managed via Kaspersky Endpoint Security for Android in device owner mode.

Kiosk mode types

The following kiosk mode types are available in Kaspersky Endpoint Security:

  • Single-app mode - Kiosk mode with only a single app. In this mode, a device user can open only one app that is allowed on the device and specified in the kiosk mode settings.

    If the app that you want to add to kiosk mode is not installed on the device, kiosk mode activates after the app is installed.

    On devices with Android 9.0 or later, an app must support kiosk mode functionality and call the startLockTask() method itself to launch the app.

    On devices with Android 9.0 or earlier, the app launches directly in kiosk mode.

  • Multi-app mode - Kiosk mode with multiple apps. In this mode, a device user can open only the set of apps that are allowed on the device and specified in the kiosk mode settings.

Presettings

Pre-configuration for kiosk mode includes the following:

  • Before specifying apps that are allowed to be run on the device in kiosk mode, you need first to add these apps in App Control > List of categories and apps and mark them as required. Then, they will appear in the App package list of the kiosk mode.

    Recently added required apps may not appear in the App package list. To view all added apps and select the app for single-app mode, you need to save and close the policy, and then reopen it. All added apps will appear in the list.

  • Before activating kiosk mode, we recommend that you prohibit launching of Google Assistant by enabling the corresponding restriction in Policy > Device owner mode > Feature restrictions > Apps > Prohibit use of Google Assistant. Otherwise, Google Assistant launches in kiosk mode and allows non-trusted apps to be opened.

Open the kiosk mode settings

To open the kiosk mode settings:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Device owner mode > Kiosk mode section.

Configure single-app mode

To configure single-app mode:

  1. In the Kiosk mode drop-down list, select Single-app mode.
  2. In the App package drop-down list, select an app package with the app that is allowed to be run on the device.
  3. Specify any required restrictions. For available restrictions, see Kiosk mode restrictions below.
  4. Select the Trusted apps check box if you want to add additional apps that are allowed on the device. To learn how to do this, see Add trusted apps below.
  5. Click the Apply button to save the changes you have made.

Configure multi-app mode

To configure multi-app mode:

  1. In the Kiosk mode drop-down list, select Multi-app mode.
  2. Click Add, select apps that are allowed to be run on the device, and then click OK.
  3. Specify any required restrictions. For available restrictions, see Kiosk mode restrictions below.
  4. Select the Allow navigation to trusted apps check box if you want to add additional apps that are allowed on the device. To learn how to do this, see Add trusted apps below.
  5. Click the Apply button to save the changes you have made.

Kiosk mode restrictions

You can set the following restrictions in kiosk mode:

  • Prohibit Overview button (Android 9.0 or later)

    Selecting or clearing this check box specifies whether the Overview button is hidden. This restriction is supported on devices with Android 9.0 or later.

    The check box is selected by default.

  • Prohibit Home button (Android 9.0 or later)

    Selecting or clearing this check box specifies whether the Home button is hidden. This restriction is supported on devices with Android 9.0 or later.

    The check box is selected by default.

  • Prohibit status bar (Android 9.0 or later)

    Selecting or clearing this check box specifies whether the status bar is blank with notifications and indicators such as connectivity, battery, and sound and vibrate options. This restriction is supported on devices with Android 9.0 or later.

    The check box is selected by default.

  • Prohibit displaying system notifications (Android 9.0 or later)

    Selecting or clearing this check box specifies whether system notifications are hidden. This restriction is supported on devices with Android 9.0 or later.

    The check box is selected by default.

  • Add Kaspersky Endpoint Security for Android as trusted app

    Selecting or clearing this check box specifies whether Kaspersky Endpoint Security for Android will be added to the list of trusted apps. This option is available if the Allow navigation to trusted apps check box is selected.

    The check box is selected by default.

Add trusted apps

Besides locking the device to a single app or set of apps, you can also add trusted apps that a device user can navigate to. To do this, in the Kiosk mode section:

  1. Select the Allow navigation to trusted apps check box. The Trusted Apps list appears.
  2. Click Add, select the desired app package name, and then click OK.
  3. Click the Apply button to save the changes you have made.
Page top

[Topic 242220]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Managing Exchange ActiveSync for Gmail

You can manage Exchange ActiveSync settings for Gmail in device owner mode.

To open the Exchange ActiveSync section:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Device owner mode > Exchange ActiveSync section.
  5. Specify the following settings:
    • Exchange ActiveSync server address

      The Exchange ActiveSync email server URL. You don't need to use HTTP:// or HTTPS:// in front of the URL.

    • Force use of SSL

      Selecting or clearing this check box specifies whether SSL communication to the server port that you specified in the Exchange ActiveSync server address field will be used.

      The checkbox is selected by default.

    • Disable SSL certificate validation

      Selecting or clearing this check box specifies whether validation checks on SSL certificates used on Exchange ActiveSync servers will be performed. Performing a check is useful if certificates are self-signed.

      The checkbox is cleared by default.

    • Allow unmanaged accounts

      Selecting or clearing the check box specifies whether the device user is allowed to add other accounts to Gmail.

      The checkbox is selected by default.

    • Authentication type

      The authentication type used to verify a device user's email credential. Possible values:

      • Modern token-based authentication. Uses a token-based identity management method. This value is selected by default.
      • Basic authentication. Prompts the device user for their password and stores it for future use.
    • Device ID

      A string used by Kaspersky Security Center proxy or a third-party gateway to identify the device and connect it to Exchange ActiveSync. You can either enter the value or select it from the Available macros drop-down list.

    • Username

      A username that will be used to pull the username from Microsoft Active Directory. It might be different from a user's email address. You can either enter the value or select it from the Available macros drop-down list.

    • Email address

      An email address that will be used to pull the user's email address from Microsoft Active Directory. You can either enter the value or select it from the Available macros drop-down list.

    • Available macros

      A macro that will be used to replace values in the corresponding fields. Possible values:

      • %email%. Specifies the email address of the user to whom the device is registered. The value is retrieved from a mobile certificate.
      • %email_domain%. Specifies the email address domain of the user to whom the device is registered. The value is retrieved from a mobile certificate.
      • %email_user_name%. Specifies the username from the email address to which the device is registered. The value is retrieved from a mobile certificate.
      • %user_name%. Specifies the username under which the device is registered. The value is retrieved from a mobile certificate.
      • %device_id%. Specifies the ID of the device.
      • %group_id%. Specifies the ID of the administration group to which the device belongs to.
      • %device_platform%. Specifies the device platform.
      • %device_model%. Specifies the device model.
      • %os_version%. Specifies the operating system version on the device.
    • User certificate

      The string alias that represents a certificate with a private key. The certificate can be a user certificate for authentication to the Exchange ActiveSync servers.

    • Default synchronization interval

      The default time interval when the Exchange ActiveSync servers synchronize mail items to Gmail. Possible values:

      • 1 day
      • 3 days
      • 1 week (default)
      • 2 weeks
      • 1 month
    • Default email signature

      The default email signature that is automatically added at the bottom of emails.

  6. Click Apply to save the changes you have made.

Page top

[Topic 241827]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Connecting to an NDES/SCEP server

You can configure a connection to an NDES/SCEP server to obtain a certificate from a certificate authority (CA) using Simple Certificate Enrollment Protocol (SCEP). To do this, you need to set up a connection to the CA using SCEP and specify a certificate profile.

To add a connection to a certificate authority and specify a certificate profile:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Device owner mode > NDES and SCEP section.
  5. In the Connection to certificate authority (CA) section, click Add.

    The Connection to certificate authority dialog appears.

  6. Specify the following settings, and then click OK:
    • Connection name

      A unique connection name.

    • Protocol type

      A protocol version. Possible values:

      • SCEP
      • NDES (default)
    • SCEP server URL

      The URL of the SCEP server.

      For NDES, the URL has the http://<ServerName>/certsrv/mscep/mscep.dll format.

    • Challenge phrase type

      A type of challenge phrase required for authentication. Possible values:

      • None - Does not require authentication data.
      • Static - Requires entering an authentication phrase in the Static challenge phrase field. This is the default value.
    • Static challenge phrase

      Specifies the authentication phrase that is used to authenticate the device with the certificate with the SCEP server URL.

  7. In the Certificate profiles section, click Add.

    The Certificate profile dialog appears.

  8. Specify the following certificate profile settings and click OK:
    • Profile name

      A unique certificate profile name.

    • Certificate authority (CA)

      A certificate authority that you created in the Connection to certificate authority (CA) section.

    • Subject name

      A unique identifier that is the subject of the certificate. It includes information about what is being certified, including common name, organization, organizational unit, country code, and so on. You can either enter the value or select it from the Available macros drop-down list.

    • Private key length

      A length of the certificate private key. Possible values:

      • 1024
      • 2048 (default)
      • 4096
    • Private key type

      A type of the certificate private key. Possible values:

      • Signature (default)
      • Encryption
      • Signature and encryption
    • Subject Alternative Names (SAN)

      An alternative name that represents the certificate subject name. You can specify multiple subject alternative names. To do this, click Add, and then specify the SAN type and SAN value options.

  9. Click Apply to save the changes you have made.

Manage connections and certificate profiles

You can later edit or remove the added connections and certificate profile.

To edit a connection or certificate profile:

  1. Select the needed connection or certificate profile in the corresponding section.
  2. Click Edit, make the required changes, and click OK.
  3. Click Apply to save the changes you have made.

To remove a connection or certificate profile:

  1. Select the needed connection or certificate profile in the corresponding section.
  2. Click Delete, and then click OK.

    Note: If you remove a certificate authority connection, all certificate profiles that use this connection will be also removed.

  3. Click Apply to save the changes you have made.
Page top

[Topic 243014]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Commands for mobile devices

Kaspersky Security Center supports commands for remote mobile device management. For instance, if a mobile device is lost or stolen, you can send commands to locate the device or wipe all corporate data from the device.

You can send commands to the following types of managed mobile devices:

  • Android devices managed via the Kaspersky Endpoint Security for Android app
  • iOS MDM devices

Each device type supports a dedicated set of commands. For information about sending commands from Administration Console, please refer to Kaspersky Security Center help.

Commands for Android devices

Commands

Command execution result

Lock

The mobile device is locked.

Unlock

After unlocking the mobile device running Android 5.0 – 6.Х, the screen unlock password is reset to "1234". After unlocking a device running Android 7.0 or later, the screen unlock password is not changed.

Reset to factory settings

All data is deleted from the mobile device and the settings are rolled back to their factory values. After this command is executed, the device will not be able to receive or execute subsequent commands.

Wipe corporate data

Containerized data, the corporate email account, settings for connecting to the corporate Wi-Fi network and VPN, Access Point Name (APN), Android work profile, KNOX container, and the KNOX License Manager key are wiped.

Synchronize device

The mobile device data is synchronized with the Administration Server.

Locate device

The mobile device's location map coordinates are obtained.

On devices running Android 12 or later, if the user granted the "Use approximate location" permission, the Kaspersky Endpoint Security for Android app first tries to get the precise device location. If this is not successful, the approximate device location is returned only if it was received not more than 30 minutes earlier. Otherwise, the Locate device command fails.

 

Mugshot

The mobile device is locked. The mugshot photo is taken by the front camera of the device when somebody attempts to unlock the device. On devices with a pop-up front camera, the photo will be black if the camera is stowed.

When attempting to unlock the device, the user automatically consents to the mugshot.

If the permission to use the camera has been revoked, the mobile device displays a notification and prompts to provide the permission. On a mobile device running Android 12 or later, if the permission to use camera has been revoked via Quick Settings, the notification is not displayed but the photo taken is black.

Alarm

The mobile device sounds an alarm. The alarm is sounded for 5 minutes (or for 1 minute if the device battery is low).

Commands for iOS MDM devices

Commands

Command execution result

Lock

The mobile device is locked.

Reset password

The mobile device's screen unlock password is reset, and the user is prompted to set a new password in accordance with policy requirements.

Reset to factory settings

All data is deleted from the mobile device and the settings are rolled back to their factory values. After this command is executed, the device will not be able to receive or execute subsequent commands.

Wipe corporate data

All installed configuration profiles, provisioning profiles, the iOS MDM profile, and applications for which the Remove together with iOS MDM profile check box has been selected are removed from the device.

Synchronize device

The mobile device data is synchronized with the Administration Server.

Install profile

The configuration profile is installed on the mobile device.

Remove profile

The configuration profile is deleted from the mobile device.

Install provisioning profile

The provisioning profile is installed on the mobile device.

Remove provisioning profile

The provisioning profile is deleted from the mobile device.

Install app

The app is installed on the mobile device.

Remove app

The app is removed from the mobile device.

Enter redemption code

Redemption code entered for a paid app.

Schedule operating system update

Operating system updates are scheduled on the mobile device according to the specified update settings.

This command is supported only for supervised devices.

Configure roaming

Data roaming and voice roaming enabled or disabled.

Set Bluetooth state

Bluetooth is enabled or disabled on the mobile device.

This command is supported only for supervised devices running iOS 11.3 or later.

Permissions for execution of commands

Special rights and permissions are required for the execution of commands of Kaspersky Endpoint Security for Android. When the Initial Configuration Wizard is running, Kaspersky Endpoint Security for Android prompts the user to grant the application all required rights and permissions. The user can skip these steps or disable these permissions in the device settings at a later time. If this is the case, it will be impossible to execute commands.

On devices running Android 10.0 or later, the user must grant the "All the time" permission to access the location. On devices running Android 11.0 or later, the user must also grant the "While using the app" permission to access camera. Otherwise, Anti-Theft commands will not function. The user will be notified of this limitation and will again be prompted to grant the permissions of required level. If the user selects the "Only this time" option for the camera permission, access is considered granted by the app. It is recommended to contact the user directly if the Camera permission is requested again.

Page top

[Topic 155903]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Managing the app using third-party EMM systems (Android only)

You can use the Kaspersky Endpoint Security for Android app without Kaspersky Administration Systems. Use solutions of other EMM (Enterprise Mobility Management) service providers to deploy and manage the Kaspersky Endpoint Security for Android app. Kaspersky participates in the AppConfig Community to ensure that the app operates with third-party EMM solutions.

You can manage the Kaspersky Endpoint Security for Android app through third-party EMM solutions only on devices running Android.

You can use the third-party EMM solutions to deploy the Kaspersky Endpoint Security for Android app only. Connect the device to Kaspersky Security Center and manage the app in the Administration Console. In this case, managing Kaspersky Endpoint Security for Android app in the EMM console will be unavailable.

If you deployed the Kaspersky Endpoint Security for Android app using the third-party EMM system, it is impossible to manage the app in the Kaspersky Endpoint Security Cloud. You can manage the Kaspersky Endpoint Security for Android app in the EMM Console.

The following EMM solutions support the use of the Kaspersky Endpoint Security for Android app:

  • VMware AirWatch
  • MobileIron
  • IBM Maas360
  • Microsoft Intune
  • SOTI MobiControl

You can perform the following actions in the EMM Console:

  • Deploy the app to an Android work profile on users' devices.
  • Activate the app.
  • Configure app settings:
    • Enable protection against malicious and phishing websites on the internet.
    • Configure settings for connecting the device to Kaspersky Security Center.
    • Configure Anti-Virus settings.
    • Configure the schedule for running a virus scan on the device.
    • Enable detection of adware and apps that could be exploited by criminals to harm the user's device or personal data.
    • Configure the schedule for app database updates.

In this section

Getting Started

How to install the app

How to activate the app

How to connect a device to Kaspersky Security Center

AppConfig File

Page top

[Topic 155912]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Getting Started

To deploy the app on users' mobile devices, you must add Kaspersky Endpoint Security for Android to the EMM app store. You can add Kaspersky Endpoint Security for Android to the EMM app store by using a Google Play link. For more details about working with apps in the EMM Console, visit the technical support website of the EMM service provider.

The Kaspersky Endpoint Security for Android app is deployed in an Android work profile. The app is isolated from the user's personal data and protects only corporate data in the work profile. It is recommended to ensure that Kaspersky Endpoint Security for Android is protected from removal by EMM Console tools.

Page top

[Topic 156203]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

How to install the app

Depending on the EMM Console, select the method for installing the app to devices: silent installation, send an email containing a link to the app in Google Play, or another available method.

The following permissions are required for the app to work:

  • Storage permission for accessing files when Anti-Virus is running (only for Android 6.0 or later).
  • Phone permission for identifying the device, for example, when activating the app.
  • Request to add Kaspersky Endpoint Security for Android to the list of apps that are started at operating system startup (on certain devices, such as Huawei, Meizu, and Xiaomi). If the add request is not displayed, manually add Kaspersky Endpoint Security for Android to the list of startup apps. The request may not be displayed if the Security app is not installed in the work profile.

You can grant the required permissions in the EMM Console before deploying the Kaspersky Endpoint Security for Android app. For more details about granting the permissions in the EMM Console, visit the technical support website of the EMM service provider. You can also grant the permissions while completing the Initial Configuration Wizard of Kaspersky Endpoint Security for Android on device.

The Kaspersky Endpoint Security for Android app will be installed in the Android work profile.

For operation of Web Protection, you must also configure a proxy server in Google Chrome settings:

  • Proxy server configuration mode: manual.
  • Proxy server address and port: 127.0.0.1:3128.
  • SPDY protocol support: disabled.
  • Data compression through proxy server: disabled.
Page top

[Topic 156199]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

How to activate the app

Information about the license is transmitted to the mobile device together with the other settings in the configuration file.

If the app is not activated within 30 days after its installation on the mobile device, the trial license expires. When the trial license expires, all features of the Kaspersky Endpoint Security for Android mobile app are disabled.

When the commercial license expires, the mobile app continues running with limited functionality (for example, Kaspersky Endpoint Security for Android database updates are not available). To continue using the app in fully functional mode, you must renew your commercial license.

To activate Kaspersky Endpoint Security for Android:

  1. In the EMM Console, open the settings of the Kaspersky Endpoint Security for Android app.
  2. In the LicenseActivationCode field, enter the app activation code.

    To activate the app on a device, you must have access to Kaspersky activation servers.

Page top

[Topic 184071]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

How to connect a device to Kaspersky Security Center

After Kaspersky Endpoint Security for Android is installed on a mobile device, you can connect the device to Kaspersky Security Center. The data necessary for connecting the device to Kaspersky Security Center is transmitted to the mobile device together with the other settings listed in the configuration file. After connecting the device to Kaspersky Security Center, you can use group policies to centrally configure the app settings. You can also receive reports and statistics on the performance of Kaspersky Endpoint Security for Android.

Prior to connecting devices to Kaspersky Security Center, make sure that the following conditions are fulfilled:

Prior to connecting devices to Kaspersky Security Center, it is recommended to do the following:

To connect a device to Kaspersky Security Center:

  1. In the EMM Console, open the settings of the Kaspersky Endpoint Security for Android app.
  2. In the KscServer field, enter the DNS name or IP address of the Kaspersky Security Center Administration Server. The default port is 13292.
  3. If you do not want the user to be distracted by Kaspersky Endpoint Security for Android notifications, disable app notifications. To do so, set the DisableNotification = True setting.

    After connecting, the app shows all notifications. You can disable certain app notifications in the policy settings.

    Do not disable app notifications if you do not use Kaspersky Security Center. This could cause a user to not receive notifications about the license expiring. As a result, the app will stop performing its functions.

After the connection settings are configured, Kaspersky Endpoint Security for Android displays a notification prompting you to grant the following additional rights and permissions:

  • Permission to use the Camera for Anti-Theft operation (Mugshot command).
  • Permission to use Location for Anti-Theft operation (Locate device command).
  • Device administrator rights (Android work profile owner) for operation of the following app functions:
    • Install security certificate.
    • Configure Wi-Fi.
    • Configure Exchange ActiveSync.
    • Restrict use of the camera, Bluetooth, and Wi-Fi.

    Due to the specific characteristics of an Android work profile (absence of the Accessibility service), the App Control and Anti-Theft features are unavailable in the app.

When the user grants the necessary rights and permissions, the device will be connected to Kaspersky Security Center. If a rule for automatically moving devices to an administration group has not been created, the device will be automatically added to the Unassigned devices folder. If a rule for automatically moving devices to an administration group has been created, the device will be automatically added to the defined group.

Kaspersky Endpoint Security provides the following devices name format:

  • Device model [email, device ID]
  • Device model [email (if any) or device ID]

A device ID is a unique ID that Kaspersky Endpoint Security for Android generates from the data received from a device. For mobile devices running Android 10 or later, Kaspersky Endpoint Security for Android uses the SSAID (Android ID) or checksum of other data received from the device. For earlier versions of Android, the app uses the IMEI. You can configure device name format in the group policy.

In SOTI MobiControl, you can use the %DEVICENAME% macro in the KscDeviceName field. This macro allows you automatically get the device name from the SOTI MobiControl console to Kaspersky Security Center.

You can also add a tag to the device name. This makes it easier to find and sort devices in Kaspersky Security Center. The tag is available only for VMware AirWatch.

To add the tag to the device name:

  1. In the EMM Console, open the settings of the Kaspersky Endpoint Security for Android app.
  2. In the KscDeviceNameTag field, select the values:
    • {DeviceSerialNumber} – Serial number of the device.
    • {DeviceUid} – Unique device identifier (UDID).
    • {DeviceAssetNumber} – Device asset number. This number is created internally from within your organization.

    We recommend using only these values. VMware AirWatch supports other values, but Kaspersky Endpoint Security cannot guarantee work these values.

You can add some values (for example, {DeviceSerialNumber} {DeviceUid}). The tag will be added to the device name in Kaspersky Security Center. A space separates the tag and the device name. For example, if the device name is Google Pixel 2 a10c6b75f7b31de9 22:7D:78:9E:C5:1E, then 22:7D:78:9E:C5:1E is UDID tag. If you use Kaspersky Security Center and VMwareAirWatch, the tag allows you to identify devices in both consoles. To match the device, select the same values for the device name (for example, the serial number of the device).

After the device is connected to Kaspersky Security Center, the app settings will be changed according to the group policy. Kaspersky Endpoint Security for Android ignores the app settings from the configuration file that was configured in the EMM Console. You can configure all sections of the policy except the following sections:

  • Anti-Theft (Device lock)
  • Device management (Screen lock)
  • App Control (Block forbidden apps)
  • Android work profile
  • Manage Samsung KNOX

Due to the method used to deploy a work profile, you cannot apply group policy settings from the Android work profile section. These settings can be applied only if the work profile was created using Kaspersky Security Center.

Page top

[Topic 155920]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

AppConfig File

A configuration file is generated to configure the app in an EMM Console. The app settings in the configuration file are presented in the table below.

Configuration file settings

Configuration key

Description

Type

Value

Default value

LicenseActivationCode

App activation code

String

App activation code consisting of 20 Latin letters and numerals. To activate the app with an activation code, you need internet access to connect to Kaspersky activation servers.

If you leave the field blank, the app will be activated with a trial license. The trial license is valid for 30 days. When the trial license expires, all features of the Kaspersky Endpoint Security for Android mobile app are disabled. To continue using the app, you must purchase a commercial license.

 

EulaAcceptanceConfirmationV1

<License Agreement link>

Choice

This setting is available only for VMware AirWatch.

Accepted – I confirm that I have fully read, understand, and accept the terms and conditions of this End User License Agreement.

Declined – I do not accept the terms and conditions of this End User License Agreement (EULA).

To accept the terms and conditions of the EULA for all mobile devices, you need internet access to connect to Kaspersky servers.

If you chose Declined, the app will ask the user to accept the terms and conditions of the EULA. Mobile device users can accept the conditions in the Initial Configuration Wizard.

 

EulaAcceptanceCodeV1

License Agreement code

String

These settings are available only for VMware AirWatch.

Use EulaAcceptanceCodeV1 if you want to accept a single End User License Agreement (EULA). Use EulaAcceptanceCodesV2 if you want to accept several EULAs at the same time. The EulaAcceptanceCodesV2 field must contain a semicolon-separated list of EULA codes: "<EULAid1>;<EULAid2>;<EULAid3>;...".

License Agreement code is contained in the End User License Agreement.

To learn License Agreement code:

  1. Copy the License Agreement link (EulaAcceptanceConfirmationV1) from the EMM Console.
  2. Paste the link into the browser.

    The End User License Agreement (EULA) opens.

  3. Read the terms and conditions of this EULA and find the License Agreement code.

    To accept the terms and conditions of the EULAs for all mobile devices, you need internet access to connect to Kaspersky servers.

If you leave the fields blank, the app will ask the user to accept the terms and conditions of the EULAs. Mobile device user can accept the conditions in the Initial Configuration Wizard.

If you specify the values of both fields, the terms and conditions of all EULAs specified in them will be accepted.

 

EulaAcceptanceCodesV2

License Agreement codes

String

 

KscServer

Kaspersky Security Center Administration Server address and port

String

DNS name or IP address of the Kaspersky Security Center Administration Server and port number. Enter the address as follows: <server address>:<port>. If you enter the server address without specifying the port, the app will use the default port 13292.

<server address>:13292

DisableNotification

Disable app notifications before connecting to Kaspersky Security Center

Boolean

True – Kaspersky Endpoint Security for Android hides all app notifications. Kaspersky Endpoint Security for Android hides notifications until the device connects to Kaspersky Security Center. After connecting, the app shows all notifications. You can disable certain app notifications in the policy settings.

Do not disable app notifications if you do not use Kaspersky Security Center. This could cause a user to miss receiving notifications about a license expiration. In this case, the app would stop performing its functions.

False – Kaspersky Endpoint Security for Android shows all app notifications.

False

ScanScheduleType

Scan run mode

Choice

AfterUpdate – Start a virus scan after a database update. The app updates anti-virus databases according to the defined schedule (UpdateScheduleType).

Daily – Start a virus scan once a day. Configure the scan start time (ScanScheduleTime).

Weekly – Start a virus scan once a week. Select the day of the week to start a virus scan (ScanScheduleDay) and configure the time (ScanScheduleTime).

Off – Autostart of a virus scan is disabled.

Irrespective of which value is set, the device user can manually start a virus scan.

AfterUpdate

ScanScheduleDay

Day of scan

Choice

Monday / Tuesday / Wednesday / Thursday / Friday / Saturday / Sunday

You can select only one value for this setting.

Monday

ScanScheduleTime

Time of scan

String

The time can be indicated in 24-hour format (for example, 13:00) or 12-hour format (for example, 10:30 P.M.).

8:00

ScanScheduleLock

Block configuration of the scan run mode

Boolean

True – The user cannot access the virus scan run mode settings within the app settings.

False – The user can configure the virus scan run mode and, for example, disable autostart of a virus scan.

True

ScanOnlyExecutableFiles

Types of files to scan (Virus Scan)

Choice

AllFiles – Scan all files.

OnlyExecutables – Scan only executable files. Executable files are files with the .apk (.zip), .dex, or .so extension.

In Kaspersky Endpoint Security for Android Service Pack 4 Maintenance Release 1, you cannot enable scanning of executable files only.

AllFiles

ScanArchives

Scan archives with unpacking

Boolean

True – The app unpacks archives and scans their contents.

False – The app scans only the archive files.

The app scans only archives with the .zip (.apk) extension.

In Kaspersky Endpoint Security for Android Service Pack 4 Maintenance Release 1, you cannot disable scanning of contents of archives.

True

ScanActionOnThreatFound

Action on threat detection (Virus Scan)

Choice

Quarantine – The app puts detected objects in Quarantine. Quarantine stores files as archives, so they cannot harm the device. The Quarantine lets you delete or restore the files that were moved to isolated storage.

Delete – The app deletes the detected objects.

Skip – The app leaves the detected objects unchanged. If the detected objects have been skipped, Kaspersky Endpoint Security for Android warns the user about problems in device protection. When there is an attempt to access an object on the device (such as an attempt to copy or open it), the app blocks access to the object.

AskUser – The app prompts the user to select an action for each detected object: skip, quarantine, or delete. When multiple objects are detected, the user can apply a selected action to all objects.

Information about detected threats and the actions taken on them is logged in app reports.

Quarantine

ScanLock

Block configuration of scan settings

Boolean

True – The following scan settings cannot be accessed by the user in the app settings: the type of files to scan, scanning of archives, and the action to take when a threat is detected.

False – The user can configure scan settings and, for example, select the Skip action for detected threats.

True

ScanAndProtectionAdwareRiskware

Block adware, autodialers, and apps that can be used by criminals to cause harm to the user's device and data

Boolean

True – The app detects adware and other apps that can be used by criminals to cause harm to the user's device and data.

False – The app skips adware and other apps that can be used by criminals to cause harm to the user's device and data.

True

ProtectionMode

Real-time protection mode

Choice

Recommended – The app only scans new apps once, immediately after they have been installed, as well as files from the Downloads folder.

Extended – The app scans all files that the user opens, modifies, copies, runs and saves on the device. The app also scans new apps and files from the Downloads folder.

Disabled – Real-time protection is disabled.

Recommended

UseKsnMode

Kaspersky Security Network mode

Choice

Recommended – The app exchanges data with Kaspersky Security Network (KSN). Kaspersky Endpoint Security for Android uses KSN for real-time protection of the device against threats (Cloud Protection) and the operation of Web Protection on the internet.

Extended – The app exchanges data with Kaspersky Security Network and also sends the Virus Laboratory certain performance statistics from Kaspersky Endpoint Security for Android. This information makes it possible to keep track of threats in real time. No personal data is collected, processed, or stored by KSN services.

Disabled – The app does not use data from Kaspersky Security Network. You cannot enable Web Protection (EnableWebFilter). The Cloud Protection component is not available for Anti-Virus.

Recommended

ProtectScanOnlyExecutableFiles

Types of files to scan (Real-time Protection)

Boolean

AllFiles – Scan all files.

OnlyExecutables – Scan only executable files. Executable files are files with the .apk (.zip), .dex, or .so extension.

In Kaspersky Endpoint Security for Android Service Pack 4 Maintenance Release 1, you cannot enable scanning of executable files only.

AllFiles

ProtectionActionOnThreatFound

Action on threat detection (Real-time Protection)

Choice

Quarantine – The app puts detected objects in Quarantine. Quarantine stores files as archives, so they cannot harm the device. Quarantine lets you delete or restore the files that were moved to isolated storage.

Delete – The app deletes detected objects.

Skip – The app leaves the detected objects unchanged. If the detected objects have been skipped, Kaspersky Endpoint Security for Android warns the user about problems in device protection. When an attempt is made to access an object on the device (such as an attempt to copy or open it), the app blocks access to the object.

Information about detected threats and the actions taken on them is logged in app reports.

Quarantine

ProtectionLock

Block configuration of real-time protection settings

Boolean

True – The following real-time protection settings cannot be accessed by the user in the app settings: real-time protection mode, types of files to scan, and the action to take when a threat is detected.

False – The user can configure real-time protection settings and, for example, can select the Skip action for detected threats.

True

UpdateScheduleType

Databases update run mode

Choice

Daily – Check for new anti-virus databases and download them to devices once a day. Configure the database update start time (UpdateScheduleTime).

Weekly – Check for new anti-virus databases and download them to devices once a week. Select the day of the week to start a database update (UpdateScheduleDay) and configure the time (UpdateScheduleTime).

Off – Automatic update of antivirus databases is disabled.

Irrespective of which value is set, the device user can manually start an update of anti-virus databases.

Daily

UpdateScheduleDay

Day to start a database update

Choice

Monday / Tuesday / Wednesday / Thursday / Friday / Saturday / Sunday

You can select only one value for this setting.

Monday

UpdateScheduleTime

Database update start time

String

The time can be indicated in 24-hour format (for example, 13:00) or 12-hour format (for example, 10:30 P.M.).

8:00

UpdateScheduleLock

Block configuration of the database update run mode

Boolean

True – The user cannot access the database update run mode settings within the app settings.

False – The user can configure the database update run mode and, for example, disable autostart of anti-virus database updates.

True

AllowUpdateInRoaming

Update databases in roaming

Boolean

True – The app downloads anti-virus databases if the device is in the roaming zone. The app downloads anti-virus databases according to the defined schedule (UpdateScheduleType).

False – The app downloads anti-virus databases only if the device is in the home network.

False

EnableWebFilter

Web Protection

Boolean

True – The app uses the Web Protection component to block malicious and phishing websites on the internet. Web Protection supports Google Chrome only.

Malicious and phishing websites using the HTTPS protocol are allowed to remain unblocked if the domain is trusted. If the domain is untrusted, Web Protection blocks malicious and phishing websites.

False – Protection against malicious and phishing websites is disabled.

For the Web Protection component to work, the following conditions must be met:

  • Device users accept the Privacy Policy and the Web Protection Statement in the Initial Configuration Wizard or app settings.
  • A proxy server is configured in the browser settings:

    ProxyMode = "fixed_servers"

    ProxyServer = "127.0.0.1:3128"

    DisableSpdy = true

    DataCompressionProxyEnabled = false

    Proxy server configuration may vary depending on the Google Chrome version. For more details about configuring Google Chrome, visit the Chromium project website.

    After the Kaspersky Endpoint Security for Android app is removed from the mobile device, reset the proxy server settings.

  • Use of KSN is enabled in the app settings: UseKsnMode = Recommended or UseKsnMode = Extended.
  • It is recommended to select Google Chrome as the default browser in the operating system settings.

False

EnableWebFilterLock

Block configuration of Web Protection

Boolean

True – The user cannot access Web Protection settings within the app settings.

False – The user can configure Web Protection settings and, for example, disable protection against malicious and phishing websites on the internet.

True

UpdateServer

Database update source server address

String

Address of the server hosting the database updates, for example, http://update.server.com.

If you leave the field blank, Kaspersky Endpoint Security for Android uses the Kaspersky database update servers.

 

AllowGoogleAnalytics

Submit data to the Google Analytics for Firebase, SafetyNet Attestation, Firebase Performance Monitoring, and Crashlytics services

Boolean

True – The app automatically submits Kaspersky Endpoint Security for Android operating data to the Google Analytics for Firebase, SafetyNet Attestation, Firebase Performance Monitoring, and Crashlytics services. This data is necessary in order to improve the performance of the app and to analyze user satisfaction. Data is transferred to the Google Analytics for Firebase, SafetyNet Attestation, Firebase Performance Monitoring, and Crashlytics services over a secure connection. Access to and protection of data is regulated by the relevant terms of use of the Google Analytics for Firebase, SafetyNet Attestation, Firebase Performance Monitoring, and Crashlytics services.

False – Submission of data to the Google Analytics for Firebase, SafetyNet Attestation, Firebase Performance Monitoring, and Crashlytics services is disabled.

True

KscDeviceNameTag

Device Name Tag for Kaspersky Security Center

String

This setting is available only for VMware AirWatch.

The tag will be added to the device name in Kaspersky Security Center. A space separates the tag and the device name. This makes it easier to find and sort devices in Kaspersky Security Center.

  • {DeviceSerialNumber} – Serial number of the device.
  • {DeviceUid} – Unique device identifier (UDID).
  • {DeviceAssetNumber} – Device asset number. This number is created internally within your organization.

You can add some values (for example, {DeviceSerialNumber} {DeviceUid}).

We recommend using only these values. VMware AirWatch supports other values, but Kaspersky Endpoint Security cannot guarantee that these values work.

 

KscGroup

Device group name

String

You can specify device groups in an EMM console. When a device is connected to Kaspersky Security Center, it will be automatically added to a subfolder of the of Unassigned devices folder. The name of the subfolder will match the group name specified in this parameter. You can then create rules for automatically moving devices from subfolders of the Unassigned devices folder to administration groups in the Managed devices folder.

If you leave the field blank, the device will be automatically added to the root of the Unassigned devices folder.

KES10

KscCorporateEmail

User's corporate email

String

You can specify users' corporate email addresses in an EMM console. These emails will be displayed in Kaspersky Security Center.

The string must be a valid email address. Other values are ignored.

 

KscDeviceName

Device name in Kaspersky Security Center

String

This setting is available only for SOTI MobiControl.

You can specify the device name displayed in Kaspersky Security Center. You can type any name or use the %DEVICENAME% macro to automatically get the device name from the SOTI MobiControl console. If you leave the field blank, the device name will be generated according to the format specified in the Kaspersky Security Center group policy.

 

Page top

[Topic 150909]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Network load

This section contains information on the volume of network traffic that is exchanged between mobile devices and Kaspersky Security Center.

Traffic volume

Task

Outgoing traffic

Incoming traffic

Total traffic

Initial deployment of the app, Mb

0.08

17.76

17.84

Initial update of anti-virus databases (the traffic volume may differ due to the size of anti-virus databases), MB

0.04

2.21

2.25

Synchronization of the mobile device with Kaspersky Security Center, MB

0.03

0.02

0.05

Regular update of anti-virus databases (the traffic volume may differ due to the size of anti-virus databases), MB

0.08

3.06

3.14

Execution of Anti-Theft commands. Locate device (the traffic volume may differ due to the specifications of the embedded camera and the quality of images), MB

0.09

0.8

0.17

Execution of Anti-Theft commands. Mugshot, MB

1.0

0.02

1.02

Execution of Anti-Theft commands. Device lock, MB

0.06

0.05

0.11

Average daily volume, MB

0.22

6.96

7.18

Page top

[Topic 101851]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Participating in Kaspersky Security Network

To protect mobile devices more effectively, Kaspersky Endpoint Security for Android uses data acquired from users around the globe. Kaspersky Security Network is designed to process such data.

Kaspersky Security Network (KSN) is an infrastructure of cloud services providing access to Kaspersky online knowledge base with 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 performance of some protection components, and reduces the likelihood of false alarms.

Your participation in Kaspersky Security Network helps Kaspersky to acquire real-time information about the types and sources of new threats, develop methods of neutralizing them, and reduce the number of false alarms of Kaspersky Endpoint Security for Android. Participation in Kaspersky Security Network also lets you access reputation statistics for applications and websites.

When you participate in Kaspersky Security Network, some statistics are acquired while Kaspersky Endpoint Security for Android are running and are automatically sent to Kaspersky. This information makes it possible to keep track of threats in real time. Files or their parts which may be exploited by intruders to harm the computer or user's content can be also sent to Kaspersky to be examined additionally.

Use of Kaspersky Security Network is required for the operation of Kaspersky Endpoint Security for Android. KSN is used by the main components of the app: Anti-Virus, Web Protection, and App Control. Refusal to participate in KSN reduces the level of device protection, which may lead to infection of the device and loss of data. To start using Kaspersky Security Network, you must accept the terms of the End User License Agreement when installing the app. By reading the End User License Agreement, you can learn which data is transmitted to Kaspersky Security Network by Kaspersky Endpoint Security for Android.

To improve the performance of the app, you can additionally provide statistical data to Kaspersky Security Network. Providing the above information to the KSN is voluntary. To start using Kaspersky Security Network, you have to accept the terms of a special agreement – the Kaspersky Security Network Statement. You can opt out of participating in Kaspersky Security Network at any time. The Kaspersky Security Network Statement describes the types of data that Kaspersky Endpoint Security for Android transmits to Kaspersky Security Network.

Updates functionality (including providing anti-virus signature updates and codebase updates), as well as KSN functionality will not be available in the software in the U.S. territory from 12:00 AM Eastern Daylight Time (EDT) on September 10, 2024 in accordance with the restrictive measures.

In this section

Information exchange with Kaspersky Security Network

Enabling and disabling the use of Kaspersky Security Network

Using Kaspersky Private Security Network

Page top

[Topic 89961]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Information exchange with Kaspersky Security Network

To improve real-time protection, Kaspersky Security for Mobile uses the Kaspersky Security Network cloud service for the operation of the following components:

  • Anti-Virus. The app obtains access to the Kaspersky online knowledge base regarding the reputation of files and apps. The scan is performed for threats whose information has not yet been added to Anti-Virus databases but is already available in KSN. Kaspersky Security Network cloud service provides full operation of Antivirus and reduces the likelihood of false alarms.
  • Web Protection. The app uses data received from KSN to run scan of websites before they are opened. The app also determines the website category to control internet access to users based on lists of allowed and blocked categories (for example, the "Internet communication" category).
  • App Control. The app determines the app category to restrict the startup of apps that do not meet corporate security requirements based on lists of allowed and blocked categories (for example, the "Games" category).

Information on the type of data submitted to Kaspersky when using KSN during operation of Anti-Virus and App Control is available in the End User License Agreement. By accepting the terms and conditions of the License Agreement, you agree to transfer this information.

Information on the type of data submitted to Kaspersky when using KSN during operation of Web Protection is available in the Statement regarding data processing for Web Protection. By accepting the terms and conditions of the Statement, you agree to transfer this information.

For the purposes of identifying emerging information security threats, intrusion threats, and threats that are hard to detect (along with their respective sources), and to improve the protection of information stored and processed on a device, you can extend your participation in Kaspersky Security Network.

To exchange data with KSN for the purposes of improving the performance of the app, the following conditions must be fulfilled:

  • You or the device user must read and accept the terms of the Kaspersky Security Network Statement. If you choose for the Statement to be accepted by users, they will be prompted by a notification on the main app screen to accept the terms of the Statement. Users can also accept the Statements in the About the app section in the Kaspersky Endpoint Security for Android settings.

    If you choose to accept the statements globally, the versions of the statements accepted via Kaspersky Security Center must match the versions already accepted by users. Otherwise, the users will be informed about the issue and prompted to accept the version of a statement that matches the version accepted globally by the administrator. The device status in the Kaspersky Security for Mobile (Devices) plug-in will also change to Warning.

  • You must configure the group policy settings to allow statistics to be sent to KSN.

You can opt out of sending statistic data to Kaspersky Security Network at any time. Information on the type of statistic data submitted to Kaspersky when using KSN during operation of the Kaspersky Endpoint Security for Android mobile app is available in the Kaspersky Security Network Statement.

For more information about data provision to KSN, refer to the "Data provision" section.

Providing data to KSN is voluntary. If you want, you can disable data exchange with KSN.

Page top

[Topic 101854]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Enabling and disabling the use of Kaspersky Security Network

For the operation of Kaspersky Endpoint Security for Android components that use Kaspersky Security Network, the app sends requests to cloud services. Requests contain the data as described in the "Data provision" section.

If the use of Kaspersky Security Network is disabled on the device, the Cloud Protection, Web Protection, and App Control components are disabled automatically.

To enable or disable the use of Kaspersky Security Network:

  1. Open the window with the settings of the management policy for mobile devices on which Kaspersky Endpoint Security for Android is installed.
  2. In the policy Properties window, select the Additional section.
  3. In the Kaspersky Security Network (KSN) settings section, configure the settings for using Kaspersky Security Network:
    • Select the Use Kaspersky Security Network check box for operation of the following components: Anti-Virus (Cloud Protection), Web Protection, and App Control (App categories).
    • Select the Allow statistics to be sent to KSN check box to submit data to Kaspersky. This data will help the Kaspersky Endpoint Security for Android app more quickly respond to threats, improve the performance of protection components, and decrease the likelihood of false alarms.
  4. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center. Once the policy has been applied, the components that use Kaspersky Security Network are disabled and component settings become unavailable.

Page top

[Topic 212391]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Using Kaspersky Private Security Network

Kaspersky Private Security Network (hereinafter also referred to as KPSN) is a solution that grants access to the reputation databases of Kaspersky Security Network (KSN), without sending data from users' devices to Kaspersky Security Network.

A database of the reputations of objects (files or URLs) is stored on the Kaspersky Private Security Network server, but not on Kaspersky Security Network servers. KPSN reputation databases are stored within the corporate network and are managed by the company administrator.

When KPSN is enabled, Kaspersky Endpoint Security does not send any statistical data from users' devices to KSN.

To enable use of KPSN via Kaspersky Security Center:

  1. In the main window of Kaspersky Security Center Web Console or Cloud Console, click Settings (NWC_settings_icon).

    The Administration Server properties window opens.

  2. On the General tab, select the KSN Proxy settings section.
  3. Switch the toggle button to the Use Kaspersky Private Security Network Enabled position.
  4. Click the Select file with KSN Proxy settings button, and then browse for the configuration file that has the pkcs7 or pem extension (provided by Kaspersky).
  5. Click Open.
  6. If you have the proxy server settings configured in the Administration Server properties, but your network architecture requires that you use KPSN directly, enable the Ignore proxy server settings when connecting to Private KSN option. Otherwise, requests from the managed applications cannot reach KPSN.
  7. Click the Save button.

After the settings are downloaded, the interface displays the provider's name and contacts, as well as the creation date of the file with the settings of KPSN. KPSN settings are applied to mobile devices.

When you switch to KPSN, App Control does not support the app categories available when using KSN. App categorization will be available if you choose to switch back to KSN.

Page top

[Topic 149378]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Data provision to third-party services

Kaspersky Endpoint Security for Android uses the Google services known as Firebase Cloud Messaging, Google Analytics for Firebase, SafetyNet Attestation, Firebase Performance Monitoring, and Crashlytics. Kaspersky Endpoint Security for Android uses the Firebase Cloud Messaging (FCM) service to ensure timely delivery of commands to mobile devices and forced synchronization when policy settings are changed. Kaspersky Endpoint Security for Android uses the Google Analytics for Firebase, SafetyNet Attestation, Firebase Performance Monitoring, and Crashlytics services to improve the performance of the app and to help Kaspersky create more effective marketing materials.

In this section

Exchanging information with Firebase Cloud Messaging

Exchanging information with Google Analytics for Firebase, SafetyNet Attestation, Firebase Performance Monitoring, and Crashlytics

Page top

[Topic 149413]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Exchanging information with Firebase Cloud Messaging

Kaspersky Endpoint Security for Android uses the Firebase Cloud Messaging (FCM) service to ensure timely delivery of commands to mobile devices and forced synchronization when policy settings are changed. The app also uses push notifications.

To use the Firebase Cloud Messaging service, you must configure the service settings in Kaspersky Security Center. For more details about configuring Firebase Cloud Messaging in Kaspersky Security Center, please refer to Kaspersky Security Center help. If Firebase Cloud Messaging settings are not configured, commands on the mobile device and policy settings will be delivered when the device is synchronized with Kaspersky Security Center according to the schedule set in the policy (for example, every 24 hours). In other words, commands and policy settings will be delivered with a delay.

For the purposes of supporting the main functionality of the product, you agree to automatically provide the Firebase Cloud Messaging service with the unique ID of the app installation (Instance ID), and the following data:

  • Information about the installed software: app version, app ID, app build version, app package name.
  • Information about the computer on which the software is installed: OS version, device ID, version of Google services.
  • Information about FCM: app ID in FCM, FCM user ID, protocol version.

Data is transmitted to Firebase services over a secure connection. Access to and protection of information is regulated by the relevant terms of use of the Firebase services: https://firebase.google.com/terms/data-processing-terms/, https://firebase.google.com/support/privacy/.

To prevent the exchange of information with the Firebase Cloud Messaging service:

  1. In the console tree, select Mobile Device ManagementMobile devices.
  2. From the context menu of the Mobile devices folder, select Properties.
  3. In the properties window of the Mobile devices folder, select the Google Firebase Cloud Messaging settings section.
  4. Click the Reset settings button.
Page top

[Topic 149418]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Exchanging information with Google Analytics for Firebase, SafetyNet Attestation, Firebase Performance Monitoring, and Crashlytics

If you use the Administration Plug-in of an earlier version and have enabled data exchange with the Google Analytics service, Kaspersky Endpoint Security for Android Service Pack 4 Maintenance Release 3 will perform exchange data with the Google Analytics for Firebase service. Google Analytics support has been discontinued.

Kaspersky Security for Mobile exchanges data with the Google Analytics for Firebase, SafetyNet Attestation, Firebase Performance Monitoring, and Crashlytics services for the following purposes:

  • To improve the performance of the app.

    To exchange data with the Google Analytics for Firebase, SafetyNet Attestation, Firebase Performance Monitoring, and Crashlytics services for the purposes of improving the performance of the app, the following conditions must be fulfilled:

    • The administrator or the device user must read and accept the terms of the Kaspersky Security Network Statement. If you choose for the Statement to be accepted by users, they will be prompted by a notification on the main app screen to accept the terms of the Statement. Users can also accept the Statements in the About the app section in the Kaspersky Endpoint Security for Android settings.

      If you choose to accept the statements globally, the versions of the statements accepted via Kaspersky Security Center must match the versions already accepted by users. Otherwise, the users will be informed about the issue and prompted to accept the version of a statement that matches the version accepted globally by the administrator. The device status in the Kaspersky Security for Mobile (Devices) plug-in will also change to Warning.

    • The administrator must configure the group policy settings to allow statistics to be sent to KSN (see below).
  • To help Kaspersky create more effective marketing materials.

    To exchange data with the Google Analytics for Firebase, SafetyNet Attestation, Firebase Performance Monitoring, and Crashlytics services for the purposes of helping Kaspersky create effective marketing materials, the following conditions must be fulfilled:

    • The administrator or the device user must read and accept the terms of the Statement regarding data processing for marketing purposes. If you choose the Statement to be accepted by users, they can accept the terms of the Statement when installing the app or in the About the app section in the Kaspersky Endpoint Security for Android settings.
    • The administrator must configure the group policy settings to allow data to be sent to Google Analytics for Firebase, SafetyNet Attestation, Firebase Performance Monitoring, and Crashlytics (see below).

Data provision to Google Analytics for Firebase, SafetyNet Attestation, Firebase Performance Monitoring, and Crashlytics under the Statement regarding data processing for marketing purposes

The Rightholder uses third-party information systems to process data. Their data processing is governed by the privacy statements of such third-party information systems. The following are the services that the Rightholder uses and the data they process:

Google Analytics for Firebase

During use of the Software, the following data will be sent to Google Analytics for Firebase automatically and on a regular basis in order to achieve the declared purpose:

  • app info (app version, app ID, and the ID of the app in the Firebase service, instance ID in the Firebase service, name of the store where the application was obtained, timestamp of the first launch of the Software)
  • ID of app installation on the device and method of installation on the device
  • information about the region and language localization
  • information about the device screen resolution
  • information about the user obtaining root
  • diagnostic information about the device from the service SafetyNet Attestation
  • information about setting Kaspersky Endpoint Security for Android as an Accessibility feature
  • information about transitions between application screens, session duration, beginning and end of a screen session, screen name
  • information about the protocol used to submit data to the Firebase service, its version, and ID of the data submission method used
  • details on the type and parameters of the event for which data is submitted
  • information about the app license, its availability, the number of devices
  • information about the frequency of anti-virus database updates and synchronization with Administration Server
  • information about the Administration Console (Kaspersky Security Center or third-party EMM systems)
  • Android ID
  • advertising ID
  • information about the User: age category and gender, identifier of the country of residence, and list of interests
  • information about the User’s computer where the Software is installed: computer manufacturer name, type of computer, model, version and the language (locale) of the operating system, information about the application first opened in the last 7 days and the application first opened more than 7 days ago

    Data is forwarded to Firebase over a secure channel. Information about how data is processed in Firebase is published at: https://firebase.google.com/support/privacy.

SafetyNet Attestation

During the use of the Software, the following data will be sent to SafetyNet Attestation automatically and on a regular basis in order to achieve the declared purpose:

  • device check time
  • information about the software, name and data about the software certificates
  • device check results
  • random ID checks to verify the results of the check device

    Data is forwarded to SafetyNet Attestation over a secure channel. Information about how data is processed in SafetyNet Attestation is published at: https://policies.google.com/privacy.

Firebase Performance Monitoring

During the use of the Software, the following data will be sent to Firebase Performance Monitoring automatically and on a regular basis in order to achieve the declared purpose:

  • unique installation ID
  • application package name
  • version of the installed software
  • battery level and battery-charging state
  • carrier
  • app foreground or background state
  • geography
  • IP address
  • device language code
  • information about the radio/network connection
  • pseudonymous Software instance ID
  • RAM and disk size
  • flag indicating whether the device is jailbroken or rooted
  • signal strength
  • duration of automated traces
  • network, and the following corresponding information: response code, payload size in bytes, response time
  • device description

    Data is forwarded to Firebase Performance Monitoring over a secure channel. Information about how data is processed in Firebase Performance Monitoring is published at: https://firebase.google.com/support/privacy.

Crashlytics

During the use of the Software, the following data will be sent to Crashlytics automatically and on a regular basis in order to achieve the declared purpose:

  • Software ID
  • version of the installed software
  • flag indicating whether the Software was running in the background
  • CPU architecture
  • unique event ID
  • event date and time
  • device model
  • total disk space and amount currently used
  • name and version of the OS
  • total RAM and amount currently used
  • flag indicating whether the device is rooted
  • screen orientation at the time of the event
  • product/hardware manufacturer
  • unique installation ID
  • version of the statistics being sent
  • the Software exception type
  • text of the error message
  • a flag indicating that the Software exception was caused by a nested exception
  • thread ID
  • a flag indicating whether the frame was the cause of the Software error
  • a flag indicating that the thread caused the Software to terminate unexpectedly
  • information about the signal that caused the Software to terminate unexpectedly: signal name, signal code, signal address
  • for each frame associated with a thread, exception, or error: the name of the frame file, line number of the frame file, debug symbols, address and offset in the binary image, display name of the library with the frame, type of the frame, flag indicating whether the frame was the cause of the error
  • OS ID
  • ID of the issue associated with the event
  • information about events that happened before the Software terminated unexpectedly: event identifier, event date and time, event type and value
  • CPU register values
  • event type and value

    Data is forwarded to Crashlytics over a secure channel. Information about how data is processed in Crashlytics is published at: https://firebase.google.com/terms/crashlytics-app-distribution-data-processing-terms.

Providing the above information for processing for marketing purposes is voluntary.

To disable data exchange with the Google Analytics for Firebase, SafetyNet Attestation, Firebase Performance Monitoring, and Crashlytics services:

  1. Open the configuration window of the management policy for mobile devices on which the Kaspersky Endpoint Security for Android app is installed.
  2. In the policy Properties window, select the Additional section.
  3. In the Data transfer section, clear the Allow data transfer to help improve the quality, appearance, and performance of the app check box.
  4. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center.

Page top

[Topic 210936]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Global acceptance of additional Statements

To enable the protection provided by Kaspersky Endpoint Security for Android, the terms of the End User License Agreement, as well as additional Statements (see below), have to be accepted. You configure a policy to accept the Statements listed below globally, for all users. The users will not be prompted to read and accept the terms of the following Agreements and Statements that have already been accepted globally:

  • Kaspersky Security Network Statement
  • Statement regarding data processing for Web Protection
  • Statement regarding data processing for marketing purposes

If you choose to accept the statements globally, the versions of the statements accepted via Kaspersky Security Center must match the versions already accepted by users. Otherwise, the users will be informed about the issue and prompted to accept the version of a statement that matches the version accepted globally by the administrator. The device status in the Kaspersky Security for Mobile (Devices) plug-in will also change to Warning.

To choose whether the terms must be accepted globally or by users by applying a group policy:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Additional section.
  5. In the Data Transfer section, choose whether the Statement regarding data processing for marketing purposes will be accepted globally or by users.
  6. In the Kaspersky Security Network (KSN) settings section, choose whether Kaspersky Security Network Statement will be accepted globally or by users.
  7. Click the Apply button to save the changes you have made.

The user may accept the terms of a Statement or decline them at any time in the About the app section in the settings of Kaspersky Endpoint Security for Android.

Page top

[Topic 206997]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Samsung KNOX

Samsung KNOX is a mobile solution for configuring and protecting Samsung mobile devices running the Android operating system. For more details about Samsung KNOX, please visit the Samsung technical support website.

In this section

Installation of the Kaspersky Endpoint Security for Android app via KNOX Mobile Enrollment

Configuring KNOX containers

Page top

[Topic 157023]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Installation of the Kaspersky Endpoint Security for Android app via KNOX Mobile Enrollment

KNOX Mobile Enrollment (KME) is part of the Samsung KNOX mobile solution. It is used for batch installation and initial configuration of apps on new Samsung devices purchased from official vendors.

Installation of the Kaspersky Endpoint Security for Android app via KNOX Mobile Enrollment consists of the following steps:

  1. Creating a KNOX MDM profile with the Kaspersky Endpoint Security for Android app
  2. Adding devices in KNOX Mobile Enrollment
  3. Installing the Kaspersky Endpoint Security for Android app on the user's mobile devices

For more details about working with KNOX Mobile Enrollment, please refer to the KNOX Mobile Enrollment User Guide.

Deployment via KNOX Mobile Enrollment is possible only for Samsung devices. For the list of supported devices, visit the Samsung technical support website.

In this section

Creating a KNOX MDM profile

Adding devices in KNOX Mobile Enrollment

Installing the app

Page top

[Topic 160806]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Creating a KNOX MDM profile

A KNOX MDM profile is a profile that contains links to apps for their quick deployment and initial configuration on mobile devices.

To create a KNOX MDM profile:

  1. Sign in to the Samsung KNOX consoleKNOX Mobile Enrollment.
  2. Select the MDM profiles section.
  3. Click Add.

    The New KNOX MDM Profile Wizard starts.

  4. At the MDM server connection step, select Server URI is not required for my MDM service and click Next.
  5. At the MDM profile info step:
    1. Enter general information about the KNOX MDM profile: Profile name and Description.
    2. Click the Add MDM apps button and enter the path to the APK installation file.

      The installation file for Kaspersky Endpoint Security for Android is included in the Kaspersky Security for Mobile distribution kit. Beforehand, place the APK installation file on the Kaspersky Security Center Web Server or on another server that is accessible for downloading from the device.

    3. Enter the settings for connecting the device to Kaspersky Security Center in the JSON user data field in the following format: {"serverAddress":"ksc.server.com","serverPort":"12345","groupName":"MOBILE GROUP"}.

      The device must be connected to Kaspersky Security Center to activate the app, configure the device, and send commands.

    4. Select the Add Knox agreements check box.

      To install Kaspersky Endpoint Security for Android via KNOX Mobile Enrollment, the mobile device user must accept the terms of the Samsung License Agreement. You can view the terms of the Samsung License Agreement in the section named End User License Agreements, Terms of Service, and User Agreements. You can also add other legal documents of your company that are necessary for deploying a KNOX MDM profile by clicking the Add user agreement button.

    5. Clear the Bind Knox license to this profile check box.

      Samsung KNOX license information is delivered to the mobile device together with the policy when the device is synchronized with Kaspersky Security Center.

  6. Click the Save button.

As a result, the new KNOX MDM profile with the Kaspersky Endpoint Security for Android app will be added to the list in the KME console.

Page top

[Topic 158031]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Adding devices in KNOX Mobile Enrollment

Devices can be added in the KNOX Mobile Enrollment (KME) console in the following ways:

  • The vendor automatically adds devices in the KME console after the devices are purchased.

    Select this method if your organization is working with an official vendor of Samsung devices.

  • The administrator installs the KNOX Deployment app from Google Play on their mobile device and migrates the KNOX MDM profile to users' devices using Bluetooth, NFC (Near Field Communication), or a QR code. After deployment of the KNOX MDM profile, the device will be automatically added in the KME console.

    Select this method if the Samsung devices were not purchased from an official vendor.

Adding a device through the vendor

An official vendor of Samsung devices is registered in Samsung KNOX. For the list of official vendors, visit the Samsung technical support website. The vendor automatically adds devices in the KME console for your Samsung account immediately after the devices are purchased. To have the devices added by the vendor, you must register the vendor in the KME console for your Samsung account. You will need a reseller ID to add the vendor of Samsung devices in the KME console. To receive the reseller ID, you must send a request to the vendor. In the request, specify your KNOX client ID.

To view your KNOX client ID:

  1. Sign in to the Samsung KNOX consoleKNOX Mobile Enrollment.
  2. Select the Resellers section.
  3. Your ID is displayed in the KNOX client ID field.

After you receive a response from the vendor with the reseller ID, register the vendor in the KME console. Prior to registering the vendor, you can create a KNOX MDM profile so that the profile can be automatically deployed when adding new devices.

To register an official vendor in the KME console:

  1. Sign in to the Samsung KNOX consoleKNOX Mobile Enrollment.
  2. Select the Resellers section.
  3. Click the Register reseller button.

    This opens a window for registering the device vendor.

  4. In the Reseller ID field, enter the ID received from the official vendor of Samsung devices.
  5. If you created a KNOX MDM profile, select the KNOX MDM profile in the vendor registration window.

    When you add new devices, the KNOX MDM profile is automatically installed.

  6. In the Preferred download confirmation method list, select a method for confirming the addition of a device for a vendor.
    • All downloads must be confirmed. When a device is added by the vendor, you will need to confirm the operation.
    • Automatically confirm all downloads of this reseller. Devices of the vendor will be automatically added in the KME console.
  7. Click OK.

The vendor of Samsung devices will be added to the list of vendors in the KME console.

After new devices are purchased from the official vendor, the Kaspersky Endpoint Security for Android app will be automatically installed to the devices after the devices are connected to the internet. For more details about working with KNOX Mobile Enrollment, please refer to the KNOX Mobile Enrollment User Guide. If you already have a list of devices in the KME console, add the KNOX MDM profile with the KNOX MDM app to the device.

To deliver a KNOX MDM profile to devices:

  1. Sign in to the Samsung KNOX consoleKNOX Mobile Enrollment.
  2. Select DevicesAll devices.
  3. Select the devices on which you want to install the KNOX MDM profile.
  4. Click the Configure button.

    The Device info window opens.

  5. In the MDM profile list, select the KNOX MDM profile with the Kaspersky Endpoint Security for Android app.
  6. In the Tags field, enter tags for grouping and labeling devices, and for search optimization in the KME console.
  7. Enter the user account credentials of the device into the User ID and Password fields.

    Account credentials are required for receiving a mobile certificate. The user ID and password must match the user account credentials in Kaspersky Security Center (Full name and Password in user account properties).

  8. Select the KNOX MDM profile for the remaining devices.
  9. Click the Save button.

After the device is connected to the internet, the user will be prompted to install the KNOX MDM profile.

Adding a device through the KNOX Deployment app

If you did not purchase your Samsung device from an official vendor, you can add the device to KNOX Mobile Enrollment using Bluetooth, NFC, or a QR code. This will require the administrator's mobile device that will be used to deliver KNOX MDM profiles to users' mobile devices.

To add devices using the KNOX Deployment app, the following conditions must be met:

  • Depending on the selected delivery mode, Bluetooth or NFC modules must be enabled on the mobile devices.
  • The mobile devices must be connected to the internet.

To deliver a KNOX MDM profile using the KNOX Deployment app:

  1. Install the KNOX Deployment app from Google Play on the administrator's mobile device.
  2. Start the KNOX Deployment app.
  3. Enter your Samsung account credentials.
  4. In the KNOX Deployment window, configure the settings for deploying a KNOX MDM profile:
    • Select the KNOX MDM profile.
    • Select the deployment mode: Bluetooth or NFC.

      When using Bluetooth, you can add a KNOX MDM profile to several devices at the same time.

  5. Click Start deployment:
    • Bluetooth. On the user's mobile device, open the website https://configure.samsungknox.com.

      This starts the Samsung KNOX Device Registration Wizard. Follow the instructions on the screen.

      After the KNOX MDM profile is installed, the new device with the Bluetooth tag will be added in the KME console.

    • NFC. Bring the administrator's mobile device close to the user's mobile device and transfer the KNOX MDM profile.

      On the user's mobile device, there will be a prompt to install the KNOX MDM profile. The new device with the NFC tag will be added in the KME console.

Page top

[Topic 158115]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Installing the app

Prior to installing the Kaspersky Endpoint Security for Android app, issue a mobile certificate for mobile device users in the Kaspersky Security Center Administration Console. A mobile certificate is required for identifying the mobile device user in the Kaspersky Security Center Administration Console.

After deployment of the KNOX MDM profile is started, the APK installation file will be automatically downloaded on the mobile device. Installation of the Kaspersky Endpoint Security for Android app is started automatically. The user must accept the Samsung KNOX License Agreement and the Kaspersky Endpoint Security for Android License Agreement. No additional configuration of the app is required. After the app is installed, synchronization with Kaspersky Security Center will be performed automatically. The mobile device will be added to the Kaspersky Security Center Administration Console to the administration group specified in the KNOX MDM profile settings (groupName).

Page top

[Topic 90650]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring KNOX containers

This section contains information about working with KNOX containers on Samsung devices running Android.

Use of KNOX containers is available only on Samsung devices running Android version 6.0 or later.

In this section

About KNOX containers

Activating Samsung KNOX

Configuring Firewall in KNOX

Configuring an Exchange mailbox in KNOX

Page top

[Topic 138645]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

About KNOX containers

A KNOX container is a safe environment on a user's device that has its own desktop, launch panel, apps, and widgets. A KNOX container lets you isolate corporate apps and data from personal apps and data. A KNOX container is a component of the Samsung KNOX mobile solution.

Samsung KNOX is a mobile solution for configuring and protecting Samsung mobile devices running the Android operating system. For more details about Samsung KNOX, please visit the Samsung technical support website.

KNOX containers let you separate personal and corporate data on a mobile device. For example, it is impossible to use a personal mailbox to send a file that is located in a KNOX container. It is recommended to deploy a KNOX container if personal mobile devices of employees are used for working with corporate data.

To use KNOX containers, you must activate Samsung KNOX. After synchronizing a device with Kaspersky Security Center, the user of the mobile device will be prompted to install the KNOX container. Before installing the KNOX container, the user must accept the terms of the End User License Agreement from Samsung.

After installing the KNOX container, the KNOX icon KSM_knox_icon will be added to the desktop of the mobile device. Or the workspace will be added to the app list on the mobile device. To work with corporate data, the user needs to start the app from KNOX container.

Kaspersky Endpoint Security for Android is not installed to the KNOX container and does not protect corporate data. Kaspersky Endpoint Security for Android does not detect the downloading of malicious files and block malicious sites in the KNOX container. You cannot control app launch or prohibit the use of the camera in the KNOX container. Kaspersky Endpoint Security for Android protects private data only. You can protect corporate data with the Samsung KNOX tools. For more details about Samsung KNOX, please visit the Samsung technical support website.

Page top

[Topic 93640]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Activating Samsung KNOX

To use a KNOX container on the user's mobile device, you must activate Samsung KNOX. The procedure of activating Samsung KNOX depends on the Kaspersky Endpoint Security for Android version installed on your users' devices:

  • If the current version of Kaspersky Endpoint Security for Android is installed on the devices, you do not need any keys to activate Samsung KNOX.
  • If an old version Kaspersky Endpoint Security for Android (10.8.3.174 or earlier) is installed on the devices, you need to obtain a KNOX License Manager key (hereinafter referred to as a KLM key) from Samsung. A KNOX License Manager key is a unique code that is used by the Samsung KNOX licensing system. For detailed information about a KLM key, please refer to the Samsung KNOX Technical Support website.

Use of KNOX containers is possible only on Samsung devices.

To activate Samsung KNOX:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.

    Complete the following steps within 15 minutes. Otherwise, you may face an error when saving changes to the policy.

  4. In the policy Properties window, select the Manage Samsung KNOX KNOX containers section.
  5. In the KNOX License Manager key field, specify the following:
    • If the current version of Kaspersky Endpoint Security for Android is installed on the devices, type any character.
    • If an old version Kaspersky Endpoint Security for Android (10.8.3.174 or earlier) is installed on the devices, enter the KLM key received from Samsung.
  6. Set the Lock attribute in the locked position Значок закрытого замка..
  7. Click the Apply button to save the changes you have made.

Samsung KNOX will be activated after the next device synchronization with Kaspersky Security Center. The user will be prompted to accept the terms of the End User License Agreement from Samsung and install the KNOX container.

To deactivate Samsung KNOX:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.

    Complete the following steps within 15 minutes. Otherwise, you may face an error when saving changes to the policy.

  4. In the policy Properties window, select the Manage Samsung KNOX KNOX containers section.
  5. Clear the KNOX License Manager key field value.
  6. Click the Apply button to save the changes you have made.

Samsung KNOX will be deactivated after the next device synchronization with Kaspersky Security Center. Access to the KNOX container will be blocked.

Samsung KNOX limitations

  • Use of KNOX containers is available only on Samsung devices.
  • On Samsung devices that support KNOX 2.6, 2.7 and 2.7.1, Web Protection and App Control do not work in a KNOX container. This issue is related to the lack of required permissions in the KNOX container (Accessibility service). On devices that support KNOX 2.8 or later, all components of the app operate without limitations.
  • Kaspersky Endpoint Security for Android versions prior to Service Pack 4 Maintenance Release 3 Update 2 may work unstable on Samsung Android 10 devices due to Samsung KNOX updates. It is recommended to update Kaspersky Endpoint Security for Android to Service Pack 4 Maintenance Release 3 Update 2 version.
Page top

[Topic 90652]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring Firewall in KNOX

You should configure the Firewall settings to monitor network connections in a KNOX container.

To configure Firewall in a KNOX container:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Manage Samsung KNOX  → KNOX containers section.
  5. In the Firewall window, click Configure.

    The Firewall window opens.

  6. Select the Firewall mode:
    • To allow all inbound and outbound connections, move the slider to Allow all.
    • To block all network activity except that of apps on the list of exclusions, move the slider up to Block all but exceptions.
  7. If you have set the Firewall mode to Block all but exceptions, create a list of exclusions:
    1. Click Add.

      This opens the Exclusion for Firewall window.

    2. In the App name field, enter the name of the mobile app.
    3. In the Package name field, enter the system name of the mobile app package (for example, com.mobileapp.example).
    4. Click OK.
  8. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center.

Page top

[Topic 90653]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Configuring an Exchange mailbox in KNOX

To work with corporate mail, contacts, and the calendar in a KNOX container, you should configure the Exchange mailbox settings (available only on Android 9 and earlier).

To configure an Exchange mailbox in a KNOX container:

  1. In the console tree, in the Managed devices folder, select the administration group to which the Android devices belong.
  2. In the workspace of the group, select the Policies tab.
  3. Open the policy properties window by double-clicking any column.
  4. In the policy Properties window, select the Manage Samsung KNOX KNOX containers section.
  5. In the Exchange ActiveSync window, click the Configure button.

    The Exchange mail server settings window opens.

  6. In the Server address field, enter the IP address or DNS name of the server hosting the mail server.
  7. In the Domain field, enter the name of the mobile device user's domain on the corporate network.
  8. In the Synchronization interval drop-down list, select the desired interval for mobile device synchronization with the Microsoft Exchange server.
  9. To use the SSL (Secure Sockets Layer) data transport protocol, select the Use SSL connection check box.
  10. To use digital certificates to protect data transfer between the mobile device and the Microsoft Exchange server, select the Verify server certificate check box.
  11. Click the Apply button to save the changes you have made.

Mobile device settings are configured after the next device synchronization with the Kaspersky Security Center.

Page top

[Topic 36215]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Appendices

This section provides information that complements the document text.

In this section

Permissions to configure group policies

App categories

Page top

[Topic 101728]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Permissions to configure group policies

Kaspersky Security Center administrators can configure the access rights of Administration Console users for different application functions, depending on the job duties of users.

For each functional area, the administrator can assign the following permissions:

  • Allow editing. The Administration Console user is allowed to change the policy settings in the properties window.
  • Block editing. The Administration Console user is prohibited from changing the policy settings in the properties window. Policy tabs belonging to the functional scope for which this right has been assigned are not displayed in the interface.

    Permissions to access sections of the Kaspersky Endpoint Security Administration Plug-in

    Functional scope

    Policies section

    Android Enterprise

    Android work profile

    Anti-Theft

    Anti-Theft

    App Control

    App Control

    Protection

    Protection, Scan, Update

    Compliance control

    Compliance control

    Device settings

    Device Control, Synchronization

    Managing Samsung devices

    APN, Managing Samsung devices, KNOX containers

    System management

    Advanced, Wi-Fi

    Web Protection

    Web Protection

    Permissions to access sections of the Kaspersky Device Management for iOS Administration Plug-in

    Functional scope

    Policies section

    Additional

    Web clips, Fonts, AirPlay, AirPrint

    Exchange ActiveSync

    General, Password, Synchronization, Features restrictions, Applications restrictions

    General

    General, Single Sign-On, Web Protection, Wi-Fi, Access Point Name (APN), Exchange ActiveSync, Email, Custom Payloads

    LDAP (calendar / contacts)

    LDAP, Calendar, Contacts, Calendar subscriptions

    Limitations and security

    Feature Restriction, Restrictions for Applications, Restrictions for Media Content, Password, VPN, Global HTTP proxy, Certificates, SCEP

Page top

[Topic 111293]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

App categories

App Control supports categorization of apps. The operation mode configured for the app category is applied to all apps in this category. The category of each app is determined by the Kaspersky Security Network cloud service.

App categories

Category

Description

Entertainment

Apps for interactive entertainment.

IM Clients, Mobile Messaging Apps

Apps for instant messaging, voice and video communication over IP.

Social networks

Apps for using social networks and blogs.

Business software

Apps for tax calculation, management of banking operations, handling spreadsheets, accounting, and other business-oriented apps. Text editors.

Home, Family, Hobbies, Health

Apps with recipes, style tips. Apps for exercising, keeping a schedule of workouts, receiving tips on dieting, healthy nutrition, safety, and accident prevention.

Medical

Apps containing catalogs of symptoms and medications, apps for healthcare professionals, healthcare magazines and news.

Multimedia

Services for movie subscription, media players and video players. Musical services, players, radio broadcasts.

Graphic design software

Apps for use with a camera, graphics editors, apps for managing and publishing photos.

Plug-ins for reading news and RSS feeds

Apps for reading newspapers, magazines, blogs, news aggregators.

Weather

Apps displaying the weather forecast.

Education apps

Book readers, manuals, textbooks, dictionaries, thesauruses, encyclopedias. Apps helping to study for exams, training materials, dictionaries, developmental games, language study tools.

Online shopping

Apps for making online purchases and bidding in auctions, gift coupons, price comparison tools, shopping list apps, apps for reading feedback about products.

Startup utilities

Apps aimed at redesigning the desktop, widgets, shortcuts.

Operating systems and utilities

System apps that provide the operating system management, user interaction, and RAM management.

Map viewers

City guides, information about local businesses, trip planning tools.

Other apps

Software libraries, technical demo versions of apps. Apps not included in any category.

Transportation

Apps for using public transport, navigation tools, apps for drivers.

Games

Arcades, Sweepstakes, Racing, Other, Casino, Card Games, Music, Board Games, Tutorials, Puzzles, Adventures, RPG, Simulators, Word Games, Sports Games, Strategies, Action.

Browsers

Apps for viewing websites, the contents of web documents and files. Apps for managing web applications.

Development tools

Apps intended for developing software. Debuggers, compilers, code editors, graphic user interface editors.

OS Apps

Apps delivered together with the operating system and required for the proper functioning of the operating system.

Internet apps

Download managers, mail clients, web search apps, and other apps for convenient internet browsing.

Network infrastructure software

Apps for managing servers, data storage devices, network equipment, software within a corporate network, automation and integration of the complete infrastructure.

Networking software

Apps for organizing collaboration of a group of users on multiple devices, communication among devices.

System utilities

Apps supplied concurrently with the operating system: file managers, archiving tools, utilities for hardware and software diagnostics, memory optimization tools, uninstallers, processor management utilities.

Security software

Device data protection apps. Apps that detect and neutralize threats on the device. Firewalls. Data encryption apps.

Download managers

Apps for downloading files from external sources.

Apps for storing files on the internet

Apps for managing online storage of files, notes, and multimedia.

Reference systems

Book readers, manuals, textbooks, dictionaries, thesauruses, wiki-encyclopedias.

Email applications

Apps used for sending and receiving email messages.

Page top

[Topic 216449]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Using the Kaspersky Endpoint Security for Android app

This Help section describes features and operations that are available to users of the Kaspersky Endpoint Security for Android app.

Articles in this section comprise all the options that can be available or visible on a mobile device. The actual layout and behavior of the app depends on the remote administration system that is implemented and how the administrator configures your device in accordance with corporate security requirements. Some functions and options described in this section may not apply to your actual experience with the app. If you have any questions about the app on your specific device, contact your administrator.

In this section

App features

Main window at a glance

Status bar icon

Device scan

Running a scheduled scan

Changing the Protection mode

Anti-virus database updates

Scheduled database update

Things to do if your device gets lost or stolen

Web Protection

Get Certificate

Synchronizing with Kaspersky Security Center

Activating the Kaspersky Endpoint Security for Android app without Kaspersky Security Center

Installing the app in device owner mode

Enabling accessibility on Android 13

Updating the app

Removing the app

Applications with a briefcase icon

KNOX app

Page top

[Topic 84085]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

App features

Kaspersky Endpoint Security offers the following key features.

Protection against viruses and other malware

The app uses the Anti-Virus component to protect the device against viruses and other malware.

Anti-Virus performs the following functions:

  • Scans the entire device, installed apps, or selected folders for threats
  • Protects the device in real time
  • Scans newly installed apps before they are launched for the first time
  • Updates anti-virus databases

If an application that collects information and sends it to be processed is installed on a mobile device, Kaspersky Endpoint Security for Android may classify this application as malware.

Protection of stolen or lost device data

The Anti-Theft component protects your data against unauthorized access and helps you to locate the device if it gets lost or stolen.

Anti-Theft lets you perform the following operations remotely:

  • Lock the device.

    To prevent a hacker from having the capability to unlock the device, Kaspersky Endpoint Security must be enabled as an Accessibility Features service on mobile devices running Android 7.0 or later.

  • Turn on a loud alarm on the device even if the device sound is disabled.
  • Get the device location map coordinates.
  • Wipe data stored on the device.
  • Reset to factory settings.
  • Secretly take a mugshot of the person using your device.

To enable Anti-Theft operations, Kaspersky Endpoint Security must be enabled as a device administrator. If you did not grant device administrator rights during the initial configuration of apps, you can grant administrator rights to Kaspersky Endpoint Security using the appropriate notification or in the device settings (Android SettingsSecurityDevice administrators).

Protection against online threats

The Web Protection component provides protection against online threats.

Web Protection blocks malicious websites that distribute malicious code, and phishing websites designed to steal your confidential data and gain access to your financial accounts. Web Protection scans websites before you open them by using the Kaspersky Security Network cloud service. Learn more.

App Control

According to corporate security requirements, the administrator of the remote administration system (hereinafter also "administrator") creates lists of recommended, blocked, and required apps. The App Control component is used to install recommended and required apps, update them, and remove blocked apps.

App Control lets you install recommended and required apps to your device via a direct link to the distribution package or a link to Google Play. App Control lets you remove blocked apps that violate corporate security requirements.

Kaspersky Endpoint Security must be enabled as an Accessibility Features service to ensure proper functioning of App Control. If you did not enable this service during the Initial Configuration Wizard for the app, you can enable Kaspersky Endpoint Security as an Accessibility Features service using the appropriate notification or in the device settings (Android SettingsAccessibilityServices).

Compliance Control

The Compliance Control component automatically checks whether the device conforms to corporate security requirements. If your device does not meet corporate security requirements, the app shows a notification with the following information:

  • Reason for the non-compliance (for example, blocked apps were detected on the device or Anti-Virus databases are out of date).
  • Time period within which you must eliminate the non-compliance (for example, 24 hours).
  • Action that will be taken on the device if you do not eliminate the non-compliance within the specified time period (for example, device will be locked).
  • Action performed to fix the device's non-compliance with corporate security requirements.

Page top

[Topic 85422]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Main window at a glance

The appearance of the main window slightly differs for different screen resolutions.

The main window displays the overall protection status of your device. This status determines the color of the window:

  • Green indicates that device protection is at an optimal level.
  • Red indicates critical problems with device security.

In the main app window, you can also do the following:

  • View notifications by clicking the button at the top right corner. They inform you about security issues, problems in app operation, compliance with corporate security requirements, and the status of your license.
  • Navigate between the main window and app settings using the buttons at the bottom.
Page top

[Topic 238899]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Status bar icon

After the first launch wizard finishes, the icon of Kaspersky Endpoint Security appears in the status bar.

The icon reflects the operation of the app and provides access to the main window of Kaspersky Endpoint Security.

The icon signals the operation of Kaspersky Endpoint Security and reflects the protection status of your device:

Значок программы – Device is protected.

– There are problems with protection (for example, the anti-virus databases are out of date or a newly installed app has not been scanned).

Page top

[Topic 85648]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Device scan

Anti-Virus has a number of limitations:

  • When Anti-Virus is running, a threat detected in the external memory of the device (such as an SD card) cannot be neutralized automatically in the Work profile (Applications with a briefcase icon, Configuring the Android work profile). Kaspersky Endpoint Security for Android does not have access to external memory in the Work profile. Information about detected objects is displayed in app notifications. To neutralize objects detected in the external memory, the object files have to be deleted manually and the device scan restarted.
  • Due to technical limitations, Kaspersky Endpoint Security for Android cannot scan files with a size of 2 GB or more. During a scan, the app skips such files without notifying you that such files were skipped.

To start a device scan:

  1. In the main window of Kaspersky Endpoint Security, tap SettingsApp settingsAnti-VirusStart scan.
  2. Select the device scan scope:
    • Scan entire device. The app scans the entire file system of the device.
    • Scan installed apps. The app scans only installed apps.
    • Custom Scan. The app scans the selected folder or individual file. You can select an individual object (folder or file) or one of the following partitions of device memory:
      • Device memory. Read-accessible memory of the entire device. This also includes the system memory partition that stores operating system files.
      • Internal memory. Device memory partition intended for installation of apps and storage of media content, documents, and other files.
      • External memory. External SD card memory. If no external SD card is installed, this option is hidden.

Access to virus scan settings may be restricted by your administrator.

To configure the virus scan:

  1. In the main window of Kaspersky Endpoint Security, tap SettingsApp settingsAnti-VirusScan settings.
  2. If you want the app to detect adware and apps that could be used by hackers to cause harm to your device or data when the app performs a scan, switch on the Adware, dialers, and other toggle button.
  3. Click Action on threat detection, and then select the action taken by the app by default:
    • Quarantine

      Quarantine stores files as archives, so they cannot harm the device. The Quarantine lets you delete or restore the files that were moved to isolated storage.

    • Request action

      The app prompts you to select an action for each detected object: skip, quarantine, or delete. When multiple objects are detected, you can apply a selected action to all objects.

    • Delete

      Detected objects will be automatically deleted. No additional actions are required. Prior to deleting an object, Kaspersky Endpoint Security will display a temporary notification about the detection of the object.

    • Skip

      If the detected objects have been skipped, Kaspersky Endpoint Security warns you about problems in device protection. For each skipped threat, the app provides actions that you can perform to eliminate the threat. The list of skipped objects may change, for example, if a malicious file was deleted or moved. To receive an up-to-date list of threats, run a full device scan. To ensure reliable protection of your data, eliminate all detected objects.

Information about detected threats and the actions taken on them is logged in app reports (SettingsReports). You can choose to display reports on Anti-Virus operations.

Page top

[Topic 85649]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Running a scheduled scan

Anti-Virus has a number of limitations:

  • When Anti-Virus is running, a threat detected in the external memory of the device (such as an SD card) cannot be neutralized automatically in the Work profile (Applications with a briefcase icon, Configuring the Android work profile). Kaspersky Endpoint Security for Android does not have access to external memory in the Work profile. Information about detected objects is displayed in app notifications. To neutralize objects detected in the external memory, the object files have to be deleted manually and the device scan restarted.
  • Due to technical limitations, Kaspersky Endpoint Security for Android cannot scan files with a size of 2 GB or more. During a scan, the app skips such files without notifying you that such files were skipped.

To configure the full scan schedule for a device:

  1. In the main window of Kaspersky Endpoint Security, tap SettingsApp settings → Anti-VirusScan settings.
  2. Tap Schedule, and then select the full scan frequency:
    • Weekly
    • Daily
    • Disabled
    • After database update
  3. Click Start day, and then select the day of the week when you want to start the full scan.
  4. Click Start time, and then select the time for starting the full scan.

A full scan of the device is started according to schedule.

On Android 12 or later, the app may perform this task later than specified if the device is in battery saver mode.

Page top

[Topic 85650]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Changing the Protection mode

Real-Time Protection lets you detect threats in files being opened, and scan apps while they are being installed on the device in real time. The anti-virus databases and the Kaspersky Security Network cloud service (Cloud Protection) are used to ensure security automatically.

To change the device protection mode:

  1. In the main window of Kaspersky Endpoint Security, tap SettingsApp settingsAnti-VirusReal-time protection mode.
  2. Select the device Protection mode:
    • Disabled. Protection is disabled.
    • Recommended. Anti-Virus scans only installed apps and files from the Downloads folder. Anti-Virus scans new apps as soon as they are installed.
    • Extended. Anti-Virus scans all device files for malicious objects when any operation is performed with them (for example, when they are saved, moved, or modified). Anti-Virus also scans new apps as soon as they are installed.

Information about the current Protection mode is displayed under the description of the component.

Access to Real-Time Protection settings may be restricted by your administrator.

To enable Cloud Protection (KSN):

  1. Tap SettingsApp settingsAnti-Virus in the main window of Kaspersky Endpoint Security.
  2. Switch on the Cloud Protection (KSN) toggle button.

    The Cloud Protection (KSN) toggle button manages the use of Kaspersky Security Network only for real-time protection of a device. If the check box is cleared, Kaspersky Endpoint Security continues to use KSN for the operation of other components of the app.

As a result, the app obtains access to the Kaspersky online knowledge base regarding the reputation of files and apps. The scan is performed for threats whose information has not yet been added to Anti-Virus databases but is already available in KSN. Kaspersky Security Network cloud service provides full operation of Antivirus and reduces the likelihood of false alarms. Only your administrator can fully disable the use of Kaspersky Security Network.

To configure Real-Time Protection:

  1. In the main window of Kaspersky Endpoint Security, tap SettingsApp settingsAnti-VirusScan settings.
  2. If you want the app to detect adware and apps that could be used by hackers to cause harm to your device or data when the app performs a scan, switch on the Adware, dialers, and other toggle button.
  3. Click Action on threat detection, and then select the action taken by the app by default:
    • Quarantine

      Quarantine stores files as archives, so they cannot harm the device. Quarantine lets you delete or restore the files that were moved to isolated storage.

    • Delete

      Detected objects will be automatically deleted. No additional actions are required. Prior to deleting an object, Kaspersky Endpoint Security will display a temporary notification about the detection of the object.

    • Skip

      If the detected objects have been skipped, Kaspersky Endpoint Security warns you about problems in device protection. For each skipped threat, the app provides actions that you can perform to eliminate the threat. The list of skipped objects may change, for example, if a malicious file was deleted or moved. To receive an up-to-date list of threats, run a full device scan. To ensure reliable protection of your data, eliminate all detected objects.

Information about detected threats and the actions taken on them is logged in the app reports (SettingsReports). You can choose to display reports on Anti-Virus operations.

Page top

[Topic 85651]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Anti-virus database updates

To update anti-virus databases of the app:

In the main window of Kaspersky Endpoint Security, tap SettingsApp settingsAnti-VirusStart database update.

Page top

[Topic 85652]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Scheduled database update

The app can automatically update the anti-virus databases according to the schedule you specify.

To configure the update schedule:

  1. In the main window of Kaspersky Endpoint Security, tap SettingsApp settingsAnti-VirusDatabase update settings.
  2. Click Schedule, and then select the update frequency:
    • Weekly
    • Daily
    • Disabled
  3. Click Start day, and then select the day of the week when you want to run the update.
  4. Click Start time, and then select the time for starting the update.

Anti-virus database updates are started according to schedule.

On Android 12 or later, the app may perform this task later than specified if the device is in battery saver mode.

Updates functionality (including providing anti-virus signature updates and codebase updates), as well as KSN functionality will not be available in the software in the U.S. territory from 12:00 AM Eastern Daylight Time (EDT) on September 10, 2024 in accordance with the restrictive measures.

Page top

[Topic 85653]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Things to do if your device gets lost or stolen

If your device gets lost or stolen, contact your system administrator. The administrator can execute Anti-Theft commands on your device remotely according to corporate security requirements.

If a Full reset command is sent to the device, control over the device will be lost, and the remaining Anti-Theft commands will not work.

Page top

[Topic 85654]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Web Protection

The following conditions must be met to enable Web Protection:

  • Kaspersky Endpoint Security must be enabled as an Accessibility Features service.
  • The Statement regarding data processing for the purpose of using Web Protection (Web Protection Statement) should be accepted. Kaspersky Endpoint Security uses Kaspersky Security Network (KSN) to scan websites. The Web Protection Statement contains the terms of data exchange with KSN.

    Your administrator can accept the Web Protection Statement for you in Kaspersky Security Center. In this case, you are not required to take any action.

    If your administrator has not accepted the Web Protection Statement and has sent you the request to do this, you must read and accept the Web Protection Statement in the app settings.

    If your administrator has not accepted the Web Protection Statement, Web Protection is not available.

To use Web Protection in Telegram, disable opening links in the In-App Browser in Telegram settings.

Web Protection on Android devices works only in the Google Chrome browser (including the Custom Tabs feature), Huawei Browser, and Samsung Internet Browser. Web Protection for Samsung Internet Browser does not block sites on a mobile device if a work profile is used and Web Protection is enabled only for the work profile.

To use Web Protection at all times when you browse the web, set Google Chrome or Samsung Internet Browser as the default browser.

To set a supported browser as the default browser and use Web Protection for website scanning at all times:

  1. In the main window of Kaspersky Endpoint Security, tap SettingsApp settingsWeb Protection.
  2. Switch the Web Protection toggle button to On.
  3. Tap Set default browser.

    This button is displayed when Web Protection is enabled and a supported browser has not been set as the default browser.

    The default browser selection wizard starts.

  4. Follow the wizard instructions.

The wizard sets Google Chrome, Huawei Browser, or Samsung Internet Browser as the default browser. Web Protection continuously scans websites while you browse the web.

Page top

[Topic 85659]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Get Certificate

To obtain a certificate for accessing corporate network resources:

  1. In the main window of Kaspersky Endpoint Security, tap SettingsApp settingsAdditionalGet certificate.
  2. Specify your corporate network account credentials.
  3. If you have received a one-time password from the administrator, select the One-time password check box, and then enter the password you received.

    The Certificate Installation Wizard starts.

  4. Follow the wizard's instructions.
Page top

[Topic 85662]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Synchronizing with Kaspersky Security Center

Synchronization of the mobile device with the Kaspersky Security Center remote administration system is required for protecting and configuring your device in accordance with corporate security requirements. The device is automatically synchronized with Kaspersky Security Center, and you can also start synchronization manually. After the first synchronization, your device is added to the list of mobile devices managed via Kaspersky Security Center. The administrator can then configure your device in accordance with corporate security requirements.

You can configure synchronization settings while running the Initial Configuration Wizard or in the settings of Kaspersky Endpoint Security. Synchronization settings have to be configured if you have installed Kaspersky Endpoint Security by using Google Play. Request the values of synchronization settings from your system administrator.

Modify the settings of device synchronization with the Kaspersky Security Center remote administration system only when instructed to do so by the administrator.

To synchronize your device with Kaspersky Security Center:

  1. In the main window of Kaspersky Endpoint Security, tap SettingsApp settingsSynchronization.
  2. In the Synchronization settings section, specify the values of the following settings:
    • Server
    • Port
    • Group
    • Corporate email address

    Synchronization settings can be hidden by the administrator.

  3. Tap Synchronize.
Page top

[Topic 98862]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Activating the Kaspersky Endpoint Security for Android app without Kaspersky Security Center

In most cases, the Kaspersky Endpoint Security for Android app that is installed on your device is activated by the administrator centrally in the Kaspersky Security Center remote administration system. If your device is not connected to Kaspersky Security Center, you can enter the activation code manually. To get the activation code, contact the administrator.

Activate the app manually only when instructed to do so by the administrator.

To enter the activation code:

  1. In the error message that says that your license will soon expire or has expired and that your device is not connected to the Administration Server, tap Activate.
  2. In the activation window, enter the activation code that the administrator gave you, and then tap Activate.
  3. If the activation code is correct, a notification is displayed saying that the app has activated, along with the license expiration date.

The Kaspersky Endpoint Security for Android app on your device is activated.

Page top

[Topic 241802]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Installing the app in device owner mode

Device owner mode is the device operation mode for company-owned Android devices. This mode allows the administrator to have full control over the entire device and configure a wide range of device functions. Device owner mode is supported on Android 7.0 or later.

To deploy the app in device owner mode, you need to reset the device to factory settings and install the app using the QR code generated in Kaspersky Security Center. The QR code contains all the necessary data for app configuration.

To install the Kaspersky Endpoint Security for Android app on the device in device owner mode:

  1. Reset the device to factory settings.

    The device reboots, and the welcome screen appears.

  2. Tap six times on an empty space of the device's welcome screen.

    The QR code reader appears.

  3. Scan the QR code generated in Kaspersky Security Center for app installation.
  4. Perform the initial setup of the device. The operating system installs the Kaspersky Endpoint Security for Android app in the background.

    Once the device setup completes, Kaspersky Endpoint Security for Android starts on the device.

  5. Activate the app by following the instructions in the app's Initial Configuration Wizard.

The Kaspersky Endpoint Security for Android app is installed and activated on the device in device owner mode.

Page top

[Topic 237468]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Enabling accessibility on Android 13 or later

On Android 13 or later, accessibility services are restricted for apps not downloaded from Google Play or HUAWEI AppGallery. You must manually allow accessibility services if you downloaded Kaspersky Endpoint Security for Android from the Kaspersky Security Center server or the Kaspersky website.

If you update the Kaspersky Endpoint Security for Android app using a Kaspersky Security Center installation package or APK file from the Kaspersky website, accessibility services will be disabled. You must manually enable accessibility services again.

Accessibility is used for the following purposes:

  • Check websites and apps in Kaspersky Security Network
  • Lock the device in case of theft
  • Display warnings
  • Block the camera when restricted by the administrator

To enable accessibility for Kaspersky Endpoint Security:

  1. Open the Accessibility page in the device settings and find Kaspersky Endpoint Security.
  2. Turn on the Kaspersky Endpoint Security switch. In the dialog that says that accessibility services are restricted, tap OK.

    Now you can give Kaspersky Endpoint Security access to the restricted settings.

  3. Open the Kaspersky Endpoint Security info page in the device settings. For example, go to Settings > Apps and then find the app in the list of apps.
  4. On the Kaspersky Endpoint Security info page, tap 3 dots menu in the top right corner and select the Allow restricted settings menu item.

    Kaspersky Endpoint Security now has access to the restricted settings.

  5. Go back to the Accessibility page in the device settings and find Kaspersky Endpoint Security.
  6. Turn on the Kaspersky Endpoint Security switch. In the dialog that opens, allow the app to have full control of your device.

Accessibility services are now enabled for Kaspersky Endpoint Security.

Page top

[Topic 237476]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

To enable accessibility for Kaspersky Endpoint Security:

  1. In the dialog that asks you to turn on accessibility services, tap Turn On.

    The Accessibility page in the device settings opens.

  2. Turn on the Kaspersky Endpoint Security switch. In the dialog that says that accessibility services are restricted, tap OK.

    Now you can give Kaspersky Endpoint Security access to the restricted settings.

  3. Open the Kaspersky Endpoint Security info page in the device settings. For example, go to Settings > Apps and then find the app in the list of apps.
  4. On the Kaspersky Endpoint Security info page, tap 3 dots menu in the top right corner and select the Allow restricted settings menu item.

    Kaspersky Endpoint Security now has access to the restricted settings.

  5. Go back to the app and in the dialog that asks you to turn on accessibility services, tap Turn On.

    The Accessibility page in the device settings opens.

  6. Turn on the Kaspersky Endpoint Security switch. In the dialog that opens, allow the app to have full control of your device.

Accessibility services are now enabled for Kaspersky Endpoint Security.

Page top

[Topic 102487]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Updating the app

Kaspersky Endpoint Security can be updated in the following ways:

  • Manually by using Google Play. You can download the new version of the app from Google Play and install it on your device.
  • With the help of the administrator. The administrator can remotely update the version of the app on your device by using the Kaspersky Security Center remote administration system.

Updating the app from Google Play

The administrator can block you from updating the app from Google Play.

The app can be updated from Google Play by following the standard update procedure of the Android platform. The following conditions must be met in order for the app to be updated:

  • You must have a Google account.
  • The device must be linked to your Google account.
  • The device must be connected to the internet.

To learn more about creating a Google account, linking your device to your account, or working with Google Play Store, see Google's support website.

Updating the app via Kaspersky Security Center

Updating the app via Kaspersky Security Center consists of the following steps:

  1. The administrator sends to your mobile device the distribution package of the app whose version meets the corporate security requirements.

    A prompt to install Kaspersky Endpoint Security on your device is displayed.

  2. Accept the update terms and conditions.

    The new version of the app will be installed to your device. The app does not require additional configuration after the update.

Updates functionality (including providing anti-virus signature updates and codebase updates), as well as KSN functionality will not be available in the software in the U.S. territory from 12:00 AM Eastern Daylight Time (EDT) on September 10, 2024 in accordance with the restrictive measures.

Page top

[Topic 85660]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Removing the app

The administrator can block you from removing the app on your own. If this is the case, you cannot remove Kaspersky Endpoint Security.

Kaspersky Endpoint Security can be removed by the following methods:

  • Manually in the device settings.
  • With the help of the administrator. The administrator can remotely remove the app from your device by using the Kaspersky Security Center remote administration system.

On devices operating in device owner mode, Kaspersky Endpoint Security for Android can be removed only by the administrator by resetting the device to factory settings.

Removal in the device settings

The app is removed by following the standard procedure for the Android platform. To remove the app, administrator rights for Kaspersky Endpoint Security must be disabled in the device security settings.

On devices running Android 7.0 or later, if the administrator has blocked removal, the device will be locked if an attempt is made to remove the app in the Android settings. To unlock the device, contact your administrator.

Removal via Kaspersky Security Center

App removal by using Kaspersky Security Center consists of the following steps:

  1. The administrator sends the app removal command to your mobile device.

    Your mobile device displays a prompt to confirm removal of Kaspersky Endpoint Security.

  2. Confirm app removal.

    The app will be removed from your device.

Page top

[Topic 102493]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Applications with a briefcase icon

KSM_afw_icon

Application icon in the Android work profile

Apps marked with a briefcase icon (corporate apps) are stored on your device in the Android work profile (hereinafter also referred to as the "work profile"). Android work profile is a safe environment on your device in which the administrator can manage apps and accounts without restricting your capabilities to work with personal data.

The work profile lets you store corporate data separately from personal data. This keeps corporate data confidential and protects it against malware. When a work profile is created on your device, the following corporate apps are automatically installed in the work profile: Google Play Market, Google Chrome, Downloads, Kaspersky Endpoint Security for Android, and others.

Page top

[Topic 138689]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

KNOX app

KSM_knox_icon

KNOX icon

The KNOX app opens a KNOX container on your device. A KNOX container is a safe environment on your device that has its own desktop, launch panel, apps, and widgets. The administrator can manage apps and accounts in a KNOX container without restricting your capabilities to work with personal data.

A KNOX container lets you store corporate data separately from personal data. This keeps corporate data confidential and protects it against malware.

In a KNOX container, you can access your company mailbox, the contact information of enterprise employees, file storage, and other applications.

For more details about working with KNOX, please visit the Samsung technical support website.

Page top

[Topic 234916]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Using the Kaspersky Security for iOS app

This Help section describes features and operations that are available to users of the Kaspersky Security for iOS app.

Articles in this section comprise all the options that can be available or visible on a mobile device. The actual layout and behavior of the app depends on the remote administration system that is implemented and how the administrator configures your device in accordance with corporate security requirements. Some functions and options described in this section may not apply to your actual experience with the app. If you have any questions about the app on your specific device, contact your administrator.

In this section

App features

Installing the app

Activating the app

Activating the app with an activation code

Main window at a glance

Updating the app

Removing the app

Page top

[Topic 231423]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

App features

Kaspersky Security for iOS offers the following key features.

Protection against online threats

The Web Protection component provides protection against online threats.

Web Protection blocks malicious websites that distribute malicious code, and phishing websites designed to steal your confidential data and gain access to your financial accounts. Web Protection scans websites before you open them by using the Kaspersky Security Network cloud service. Web Protection also checks the online activity of the apps on your device.

For Web Protection to work, you must allow the app to add a VPN configuration.

Jailbreak detection

When Kaspersky Security for iOS detects a jailbreak, it displays a critical message and informs your administrator about the issue.

The app cannot guarantee the security of your device, because a jailbreak bypasses security features and can cause numerous issues, including:

  • Security vulnerabilities
  • Stability issues
  • Disruption of Apple services
  • Potential crashes and freezes
  • Shortened battery life
  • Inability to apply iOS updates
Page top

[Topic 231857]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Installing the app

To install the Kaspersky Security for iOS app:

  1. Find the email message with the administrator’s invitation to install the Kaspersky Security for iOS app from the App Store.
  2. Go to the App Store in one of the following ways:
    • Tap the link in the message if you are reading it on the iOS device on which you want to install the app.
    • Scan the QR code using the iOS device on which you want to install the app, if you are reading the message on a computer.

    The invitation link is valid for 24 hours. If you don’t manage to install the app in time, contact your administrator for a new invitation.

  3. Download and install the app from the App Store by following the standard installation procedure on the iOS platform.

The Kaspersky Security for iOS app is installed on your device. To protect the device, active the app.

Page top

[Topic 233458]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Activating the app

To activate the Kaspersky Security for iOS app:

  1. Start the app on your device.
  2. Accept the agreements and statements by selecting the End User License Agreement and Products and Services Privacy Policy checkboxes.

    Optionally, accept the Kaspersky Security Network Statement to allow statistics to be sent to Kaspersky Security Network. This improves the performance of the app and ensures its uninterrupted operation.

  3. Tap Next. The app connects to the Kaspersky Security Center remote administration system and gets license information.
  4. Allow the app to add a VPN configuration. The app uses the VPN configuration to check websites for phishing and protect your device from web threats.
  5. Allow the app to send push notifications. The app uses notifications to inform you about security issues and the status of your license.

The Kaspersky Security for iOS app on your device is activated.

Page top

[Topic 231467]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Activating the app with an activation code

When you install the Kaspersky Security for iOS app on your device, the app connects to the Kaspersky Security Center remote administration system and gets license information automatically. If your device is not connected to Kaspersky Security Center, you can enter the activation code manually. To get the activation code, contact the administrator.

Activate the app manually only when instructed to do so by the administrator.

To enter the activation code:

  1. In the message that says that the app is not activated, tap Activate the app.
  2. In the activation window, enter the activation code that the administrator gave you, and then tap Activate.

    If the activation code is correct, a notification is displayed saying that the app has activated, along with the license expiration date.

The Kaspersky Security for iOS app on your device is activated.

Page top

[Topic 231460]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Main window at a glance

The appearance of the main window slightly differs for different screen resolutions.

The main window displays:

  • Overall protection status of your device.
  • Messages that indicate app component statuses and protection issues.

There are three types of messages:

  • Highlighted in green. Status messages that inform you that protection is active in the specified area.
  • Highlighted in yellow. Information messages that inform you about events that may affect device security.
  • Highlighted in red. Critical messages that inform you about events of critical importance to device security.

You can tap a message for details.

Page top

[Topic 231468]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Updating the app

You can download the latest version of the Kaspersky Security for iOS app from the App Store and install it on your device by following the standard update procedure on the iOS platform. You can also turn on automatic updates. The app does not require any additional configuration after the update.

The following conditions must be met in order for the app to be updated:

  • You must have an Apple ID.
  • The device must be linked to your Apple ID.
  • The device must be connected to the internet.

To learn more about creating an Apple ID, linking your device to your Apple ID, or working with the App Store, see the Apple support website.

Updates functionality (including providing anti-virus signature updates and codebase updates), as well as KSN functionality will not be available in the software in the U.S. territory from 12:00 AM Eastern Daylight Time (EDT) on September 10, 2024 in accordance with the restrictive measures.

Page top

[Topic 231471]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Removing the app

To remove the Kaspersky Security for iOS app, follow the standard procedure on the iOS platform:

  1. On the Home screen, touch and hold the app icon.
  2. Remove the app.

The Kaspersky Security for iOS app is removed from your device.

Page top

[Topic 96628]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Application licensing

This section provides information about the general terms related to licensing Kaspersky Security for Mobile.

In this section

About the End User License Agreement

About the license

About the subscription

About the key

About the activation code

About the key file

Data provision in Kaspersky Endpoint Security for Android

Data provision in Kaspersky Security for iOS

Page top

[Topic 95499]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

About the End User License Agreement

The End User License Agreement (EULA) is a binding agreement between you and AO Kaspersky Lab, stipulating the Terms and Conditions on which you may use Kaspersky Security for Mobile.

We recommend carefully reading the Terms and Conditions of the EULA before using Kaspersky Security for Mobile.

You can view the Terms and Conditions of the EULA in the following ways:

  • During installation of components of Kaspersky Security for Mobile.
  • By reading the license.txt file included in the self-extracting archive of the distribution kit for installing the Kaspersky Endpoint Security for Android app.
  • In the About the app section in Kaspersky Endpoint Security for Android.
  • In the About the AppAgreements and Statements section in Kaspersky Security for iOS.
  • In the AdvancedAccepted License Agreements section in the Administration Server properties. This feature is available in Kaspersky Security Center version 12.1 and later.

By confirming that you agree with the End User License Agreement (EULA) when installing the components of Kaspersky Security for Mobile, you signify your acceptance of the Terms and Conditions of the End User License Agreement. If you do not accept the terms of the End User License Agreement, you must cancel installation of Kaspersky Security for Mobile components and refrain from using them.

Page top

[Topic 95885]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

About the license

A license is a time-limited right to use the integrated solution Kaspersky Security for Mobile provided to you on the terms of the End User License Agreement.

A current license entitles you to the following kinds of services:

  • Use apps on mobile devices in accordance with the terms of the End User License Agreement.
  • Receive technical support.

The scope of available services and the app usage term depend on the type of license under which the app has been activated.

The following license types are provided:

  • Trial.

    A free license intended for trying out the Kaspersky Security for Mobile.

    The trial license is valid for 30 days. When the trial license expires, the Kaspersky Endpoint Security for Android mobile app and the Kaspersky Security for iOS mobile app stop performing most functions, except for synchronization with the Administration Server. To continue using the app, you must purchase a commercial license.

  • Commercial.

    A license provided when you purchase Kaspersky Security for Mobile.

    When the commercial license expires, the mobile app continues to work, but with limited functionality.

    In limited functionality mode, the following components are available depending on the app.

    • Kaspersky Endpoint Security for Android app:
      • Anti-Virus. Real-time Protection and Virus Scan of the device are available, but anti-virus database updates are not available.
      • Anti-Theft. Only sending commands to mobile device is available.
      • Synchronization with the Administration Server.

      Kaspersky Endpoint Security for Android stops exchanging information with Kaspersky Security Network, Google Analytics for Firebase, SafetyNet Attestation, Firebase Performance Monitoring, and Crashlytics if the Kaspersky key is blocked, if the trial license expires, or if a license is missing (the activation code is removed from the group policy).

    • Kaspersky Security for iOS app:
      • Synchronization with the Administration Server.

      Kaspersky Security for iOS stops exchanging information with Kaspersky Security Network if the trial license expires or if a license is missing (the activation code is removed from the group policy).

    The remaining components of the mobile app are not available to the device user. The administrator can use group policies to manage these components in limited functionality mode. You cannot use group policies to configure the other components of the app.

    To continue using the app in fully functional mode, you must renew your commercial license. We recommend renewing the license term or buying a new license before the current one expires, in order to ensure maximum protection of your computer against all security threats.

Page top

[Topic 96676]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

About the subscription

Subscription for Kaspersky Security for Mobile is an order for using the mobile app with the selected parameters (subscription expiry date, number of mobile devices protected). You can order subscription for Kaspersky Security for Mobile from your service provider (such as your ISP). Subscription can be renewed manually or automatically, or you may cancel your subscription. You can manage your subscription on the website of the service provider.

Subscription can be limited (for example, one-year) or unlimited (with no expiration date). To keep Kaspersky Security for Mobile working after expiry of the limited subscription term, you have to renew your subscription. Unlimited subscription is renewed automatically provided a prepayment to the service provider was timely.

If the subscription is limited, when it expires you may be offered a grace period for renewing the subscription, during which time the apps will retain their functionality. The availability and duration of such grace period are at the discretion of the service provider.

To use Kaspersky Security for Mobile under subscription, you have to apply the activation code received from the service provider. After the activation code is applied, the key is installed for the license for using the application under subscription.

The possible subscription management options may vary with each service provider. The service provider may not offer a subscription renewal grace period during which the apps will retain their functionality.

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

Page top

[Topic 96715]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

About the key

A key is a sequence of bits that you can apply to activate and then use the integrated solution Kaspersky Security for Mobile in accordance with the terms of the End User License Agreement. Keys are generated by Kaspersky specialists.

You can add a key for the mobile app using a key file or activation code:

  • If your organization has deployed the Kaspersky Security Center software suite, you have to apply the key file and distribute it to Android mobile apps. They key is displayed in the interface of Kaspersky Security Center and the interface of the Android mobile app as a unique alphanumeric sequence.

    After adding keys, you can replace them with other keys.

    You can't activate the Kaspersky Security for iOS app with a key file.

  • If your organization does not use Kaspersky Security Center, you have to share the activation code with the user. The user enters this activation code in the Android or iOS mobile app. The key is displayed in the mobile app interface as a unique alphanumeric sequence.

The key may be blocked by Kaspersky if, for example, the terms of the End User License Agreement have been violated. If the key is blocked, the mobile app stops performing all its functions except for synchronization with the Administration Server. To continue using the app, you need to add a different key.

Page top

[Topic 96713]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

About the activation code

Activation code is a unique sequence of 20 alphanumeric characters. You enter an activation code to add a key that activates the Kaspersky Endpoint Security for Android mobile app or the Kaspersky Security for iOS mobile app. You receive the activation code at the email address that you have specified after purchasing the integrated solution Kaspersky Security for Mobile or after ordering the trial version of Kaspersky Security for Mobile.

To activate the mobile app with an activation code, you need internet access to connect to Kaspersky activation servers.

If you have lost your activation code after you activated the app, it can be restored. You may need your activation code, e.g., to register with Kaspersky CompanyAccount. To restore the activation code, contact Kaspersky Technical Support.

Page top

[Topic 96817]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

About the key file

A key file is a file with the .key extension that you receive from Kaspersky. The purpose of a key file is to add a key that activates the Kaspersky Endpoint Security for Android app.

You can't activate the Kaspersky Security for iOS app with a key file.

You receive the key file at the email address that you specified after purchasing the integrated solution Kaspersky Security for Mobile or after ordering the trial version of Kaspersky Security for Mobile.

You do not need to connect to Kaspersky activation servers in order to activate the application with a key file.

You can recover a key file if it has been accidentally deleted. You may need a key file to register a Kaspersky CompanyAccount, for example.

To recover a key file, do one of the following:

  • Contact the license seller.
  • Receive a key file through Kaspersky website by using your available activation code.
Page top

[Topic 96712]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Data provision in Kaspersky Endpoint Security for Android

Kaspersky Security for Mobile complies with the General Data Protection Regulations (GDPR).

To install the app, either you or a device user must read and accept the terms of the End User License Agreement. In addition, you can configure a policy to accept the Statements listed below globally, for all users. Otherwise, users will be prompted by a notification on the main app screen to accept the following Statements regarding the processing of the user's personal data:

  • Kaspersky Security Network Statement
  • Statement regarding data processing for Web Protection
  • Statement regarding data processing for marketing purposes

If you choose to accept the statements globally, the versions of the statements accepted via Kaspersky Security Center must match the versions already accepted by users. Otherwise, the users will be informed about the issue and prompted to accept the version of a statement that matches the version accepted globally by the administrator. The device status in the Kaspersky Security for Mobile (Devices) plug-in will also change to Warning.

The user may accept the terms of a Statement or decline them at any time in the About the app section in the settings of Kaspersky Endpoint Security for Android.

Information exchange with Kaspersky Security Network

To improve real-time protection, Kaspersky Endpoint Security for Android uses the Kaspersky Security Network cloud service for operating the following components:

  • Anti-Virus. The app obtains access to the Kaspersky online knowledge base regarding the reputation of files and apps. The scan is performed for threats whose information has not yet been added to Anti-Virus databases but is already available in KSN. Kaspersky Security Network cloud service provides full operation of Anti-Virus and reduces the likelihood of false alarms.
  • Web Protection. The app uses data received from KSN to scan websites before they are opened. The app also determines the website category to control internet access to users, based on lists of allowed and blocked categories (for example, the "Internet communication" category).
  • App Control. The app determines the app category to restrict the startup of apps that do not meet corporate security requirements, based on lists of allowed and blocked categories (for example, the "Games" category).

Information on the type of data submitted to Kaspersky when using KSN during operation of Anti-Virus and App Control is available in the End User License Agreement. By accepting the terms and conditions of the License Agreement, you agree to transfer this information.

Information on the type of data submitted to Kaspersky when using KSN during operation of Web Protection is available in the Statement regarding data processing for Web Protection. By accepting the terms and conditions of the Statement, you agree to transfer this information.

Information on the type of statistic data submitted to Kaspersky when using KSN during operation of the Kaspersky Endpoint Security for Android mobile app is available in the Kaspersky Security Network Statement. By accepting the terms and conditions of the Statement, you agree to transfer this information.

Data provision under the End User License Agreement

Where the Activation Code is used to activate the Software, in order to verify legitimate use of the Software, the End User agrees to periodically provide the Rightholder the following information:

  • format of the data in the request to Rightholder infrastructure; accessed IPv4 address of the web service; size of the content of the request to Rightholder infrastructure; protocol ID; Software activation code; data compression type; Software ID; set of IDs of Software that can be activated on the user's device; Software localization; full version of the Software; unique device ID; date and time on the user's device; Software installation ID (PCID); OS version, OS build number, OS update number, OS edition, extended information about the OS edition; device model; operating system family; format of the data in the request to Rightholder infrastructure; checksum type for the object being processed; Software license header; ID of a regional activation center; Software license key creation date and time; Software license ID; ID of the information model used to provide the Software license; Software license expiration date and time; current status of the Software license key; type of Software license used; type of the license used to activate the Software; Software ID derived from the license.

In order to protect the Computer against information security threats, the End User agrees to periodically provide the Rightholder the following information:

  • checksum type for the object being processed; checksum of the object being processed; the Software component ID;
  • ID of the triggered record in the Software's anti-virus databases; timestamp of the triggered record in the Software's anti-virus databases; type of the triggered record in the Software's anti-virus databases; name of the detected malware or legitimate software that can be used to damage the user's device or data;
  • name of store from which the application was installed; application package name; public key used to sign the APK file; checksum of the certificate used to sign the APK file; digital certificate timestamp;
  • full version of the Software; Software update ID; type of installed Software; the config identifier; the result of the Software action; error code;
  • numbers that are derived from the Android application APK file according to certain mathematical rules and that do not allow restoration of the original file content; this data does not contain file names, file paths, addresses, phone numbers, or other personal information of users.

If You use the Rightholder’s update servers to download the Updates, the End User, in order to increase the efficiency of the update procedure, agrees to periodically provide the Rightholder the following information:

  • Software ID derived from the license; full version of the Software; Software license ID; type of Software license used; Software installation ID (PCID); ID of the Software update start; web address being processed.

The Rightholder can use such information also for receiving statistical information about the distribution and use of the Software.

The received information is protected by Kaspersky in accordance with the requirements established by law. The original received information is stored in encrypted form and is destroyed as it is accumulated (twice per year) or at the request of the User. General statistics are stored indefinitely.

Data provision under the Kaspersky Security Network Statement

Use of the KSN could lead to increase the effectiveness of protection provided by the Software, against information and network security threats.

If you use a license for 5 or more nodes, the Rightholder will automatically receive and process the following data during use of the KSN:

  • ID of the triggered record in the Software's anti-virus databases; timestamp of the triggered record in the Software's anti-virus databases; type of the triggered record in the Software's anti-virus databases; release date and time of the Software's databases; OS version, OS build number, OS update number, OS edition, extended information about the OS edition; OS Service Pack version; detect characteristics; checksum (MD5) of the object being processed; name of the object being processed; flag indicating whether the object being processed is a PE file; checksum (MD5) of the mask that blocked the web service; checksum (SHA256) of the object being processed; size of the object being processed; object type code; the Software's decision on the object being processed; path to the object being processed; directory code; version of the Software's component; version of the statistics being sent; accessed address of the web service (URL, IP); type of client used to access the web service; accessed IPv4 address of the web service; accessed IPv6 address of the web service; web address of the source of the web service request (referer); web address being processed;
  • information about scanned objects (application version from AndroidManifest.xml; the Software's decision on the application; method used to get the Software's decision on the application; store installer package name; package name (or bundle name) from AndroidManifest.xml; Google SafetyNet category; flag indicating whether the SafetyNet is enabled on the device; SHA256 value from Google SafetyNet response; APK Signature Scheme for the APK certificate; version code of the installed Software; serial number of the certificate that was used to sign the APK file; name of the APK file that is being installed; path to the APK file that is being installed; issuer of the certificate that was used to sign the APK file; public key used to sign the APK file; checksum of the certificate used to sign the APK file; date and time when the certificate expires; date and time when the certificate was issued; version of the statistics being sent; algorithm for calculating the digital certificate thumbprint; MD5 hash of the installed APK file; MD5 hash of the DEX file located within the APK file; permissions granted dynamically to the application; third-party software version; flag indicating whether the application is the default SMS messenger; flag indicating whether the application has Device Administrator rights; flag indicating whether the application is in the system catalog; flag indicating whether the application uses accessibility services);
  • information about all potentially malicious objects and activities (fragment content of the object being processed; date and time when the certificate expires; date and time when the certificate was issued; ID of the key from the keystore used for encryption; protocol used to exchange data with KSN; fragment order in the object being processed; data of the internal log, generated by the anti-virus Software module for an object being processed; certificate issuer name; public key of the certificate; calculation algorithm of public key of the certificate; certificate serial number; date and time of signing the object; certificate owner name and settings; digital certificate thumbprint of the scanned object and hashing algorithm; date and time of the last modification of the object being processed; date and time of creating an object being processed; objects or its parts being processed; description of an object being processed as defined in the object properties; format of the object being processed; checksum type for the object being processed; checksum (MD5) of the object being processed; name of the object being processed; checksum (SHA256) of the object being processed; size of the object being processed; Software vendor name; the Software's decision on the object being processed; version of the object being processed; source of the decision made for the object being processed; checksum of the object being processed; parent application name; path to the object being processed; information about file signature check results; logon session key; encryption algorithm for the logon session key; storage time for object being processed; algorithm for calculating the digital certificate thumbprint);
  • build type, for example, "user" or "eng"; full product name; product/hardware manufacturer; whether apps can be installed from outside of Google Play; status of the cloud service for verification of Google apps; status of the cloud service for verification of Google apps being installed through ADB; current development codename or "REL" for production builds; incremental build number; user-visible version string; user device name; user-visible Software's build ID; firmware fingerprint; firmware ID; flag indicating whether the device is rooted; operating system; Software name; type of Software license used;
  • information about the quality of KSN services (protocol used to exchange data with KSN; ID of the KSN service accessed by the Software; date and time when statistics stopped being received; number of KSN connections taken from the cache; number of requests for which a response was found in the local request database; number of unsuccessful KSN connections; number of unsuccessful KSN transactions; temporal distribution of cancelled requests to KSN; temporal distribution of unsuccessful KSN connections; temporal distribution of unsuccessful KSN transactions; temporal distribution of successful KSN connections; temporal distribution of successful KSN transactions; temporal distribution of successful requests to KSN; temporal distribution of requests to KSN that timed out; number of new KSN connections; number of unsuccessful requests to KSN caused by routing errors; number of unsuccessful requests caused by KSN being disabled in the Software settings; number of unsuccessful requests to KSN caused by network problems; number of successful KSN connections; number of successful KSN transactions; total number of requests to KSN; date and time when statistics started being received);
  • device ID; full version of the Software; Software update ID; Software installation ID (PCID); type of installed Software;
  • device screen height; device screen width; information about the overlapping application: MD5 hash of the APK file; information about the overlapping application: MD5 hash of the classes.dex file; information about the overlapping application: name of the APK file; information about the overlapping application: path to the APK file without the file name; overlap height; information about the overlapped Software: MD5 hash of the APK file; overlapped application information: classes.dex file MD5 hash; overlapped application information: APK file name; overlapped application information: path to APK file without file name; overlapped application information: application package name (for the overlapped application: if the advertisement is shown on an empty desktop, the value should be "launcher"); overlap date and time; information about the overlapping application: application package name; overlap width;
  • settings of the Wi-Fi access point in use (detected device type; DHCP settings (checksums of gateway local IPv6, DHCP IPv6, DNS1 IPv6, DNS2 IPv6; checksum of network prefix length; checksum of local address IPv6); DHCP settings (checksums of the local IP address of the gateway, DHCP IP, DNS1 IP, DNS2 IP, and subnet mask); flag indicating whether the DNS domain exists; checksum of the assigned local IPv6 address; checksum of the assigned local IPv4 address; flag indicating whether the device is plugged in; Wi-Fi network authentication type; list of available Wi-Fi networks and their settings; checksum (MD5 with salt) of the MAC address of the access point; checksum (SHA256 with salt) of the MAC address of the access point; connection types supported by the Wi-Fi access point; Wi-Fi network encryption type; local time of the start and end of the Wi-Fi network connection; Wi-Fi network ID based on the MAC address of the access point; Wi-Fi network ID based on the Wi-Fi network name; Wi-Fi network ID based on the Wi-Fi network name and the MAC address of the access point; Wi-Fi signal strength; Wi-Fi network name; set of authentication protocols supported by this configuration; authentication protocol used for a WPA-EAP connection; internal authentication protocol; set of group ciphers supported by this configuration; set of key management protocols supported by this configuration; the network's final privacy category in the Software; the network's final security category in the Software; set of block ciphers for WPA that are supported by this configuration; set of security protocols supported by this configuration);
  • installation date and time for the Software; Software activation date; identifier of the partner organization via which the Software license order was placed; Software ID derived from the license; serial number of the Software license key; Software localization; flag indicating whether participation in KSN is enabled; ID of the licensed Software; Software license ID; OS ID; operating system bit version.

Also, in order to achieve the declared purpose of increasing the effectiveness of protection provided by the Software, the Rightholder may receive objects that could be exploited by intruders to harm the Computer and create information security threats.

Providing the above information to the KSN is voluntary. You can opt out of participating in Kaspersky Security Network at any time.

Data provision under the Statement regarding data processing for Web Protection

According to Web Protection Statement the Rightholder processes data in order for Web Protection functionality. The stated purpose includes detecting web threats and determining the categories of visited websites using the cloud service Kaspersky Security Network (KSN).

With Your consent, the following data will be automatically sent on a regular basis to the Rightholder under the Web Protection Statement:

  • Product version; Unique device identifier; Installation ID; Product type.
  • URL address of the page, port number, URL protocol, URL, which refers to the requested information.

Data provision under the Statement regarding data processing for marketing purposes

The Rightholder uses third-party information systems to process data. Their data processing is governed by the privacy statements of such third-party information systems. The following are the services that the Rightholder uses and the data they process:

Google Analytics for Firebase

During use of the Software, the following data will be sent to Google Analytics for Firebase automatically and on a regular basis in order to achieve the declared purpose:

  • app info (app version, app ID, and the ID of the app in the Firebase service, instance ID in the Firebase service, name of the store where the application was obtained, timestamp of the first launch of the Software)
  • ID of app installation on the device and method of installation on the device
  • information about the region and language localization
  • information about the device screen resolution
  • information about the user obtaining root
  • diagnostic information about the device from the service SafetyNet Attestation
  • information about setting Kaspersky Endpoint Security for Android as an Accessibility feature
  • information about transitions between application screens, session duration, beginning and end of a screen session, screen name
  • information about the protocol used to submit data to the Firebase service, its version, and ID of the data submission method used
  • details on the type and parameters of the event for which data is submitted
  • information about the app license, its availability, the number of devices
  • information about the frequency of anti-virus database updates and synchronization with Administration Server
  • information about the Administration Console (Kaspersky Security Center or third-party EMM systems)
  • Android ID
  • advertising ID
  • information about the User: age category and gender, identifier of the country of residence, and list of interests
  • information about the User’s computer where the Software is installed: computer manufacturer name, type of computer, model, version and the language (locale) of the operating system, information about the application first opened in the last 7 days and the application first opened more than 7 days ago

    Data is forwarded to Firebase over a secure channel. Information about how data is processed in Firebase is published at: https://firebase.google.com/support/privacy.

SafetyNet Attestation

During the use of the Software, the following data will be sent to SafetyNet Attestation automatically and on a regular basis in order to achieve the declared purpose:

  • device check time
  • information about the software, name and data about the software certificates
  • device check results
  • random ID checks to verify the results of the check device

    Data is forwarded to SafetyNet Attestation over a secure channel. Information about how data is processed in SafetyNet Attestation is published at: https://policies.google.com/privacy.

Firebase Performance Monitoring

During the use of the Software, the following data will be sent to Firebase Performance Monitoring automatically and on a regular basis in order to achieve the declared purpose:

  • unique installation ID
  • application package name
  • version of the installed software
  • battery level and battery-charging state
  • carrier
  • app foreground or background state
  • geography
  • IP address
  • device language code
  • information about the radio/network connection
  • pseudonymous Software instance ID
  • RAM and disk size
  • flag indicating whether the device is jailbroken or rooted
  • signal strength
  • duration of automated traces
  • network, and the following corresponding information: response code, payload size in bytes, response time
  • device description

    Data is forwarded to Firebase Performance Monitoring over a secure channel. Information about how data is processed in Firebase Performance Monitoring is published at: https://firebase.google.com/support/privacy.

Crashlytics

During the use of the Software, the following data will be sent to Crashlytics automatically and on a regular basis in order to achieve the declared purpose:

  • Software ID
  • version of the installed software
  • flag indicating whether the Software was running in the background
  • CPU architecture
  • unique event ID
  • event date and time
  • device model
  • total disk space and amount currently used
  • name and version of the OS
  • total RAM and amount currently used
  • flag indicating whether the device is rooted
  • screen orientation at the time of the event
  • product/hardware manufacturer
  • unique installation ID
  • version of the statistics being sent
  • the Software exception type
  • text of the error message
  • a flag indicating that the Software exception was caused by a nested exception
  • thread ID
  • a flag indicating whether the frame was the cause of the Software error
  • a flag indicating that the thread caused the Software to terminate unexpectedly
  • information about the signal that caused the Software to terminate unexpectedly: signal name, signal code, signal address
  • for each frame associated with a thread, exception, or error: the name of the frame file, line number of the frame file, debug symbols, address and offset in the binary image, display name of the library with the frame, type of the frame, flag indicating whether the frame was the cause of the error
  • OS ID
  • ID of the issue associated with the event
  • information about events that happened before the Software terminated unexpectedly: event identifier, event date and time, event type and value
  • CPU register values
  • event type and value

    Data is forwarded to Crashlytics over a secure channel. Information about how data is processed in Crashlytics is published at: https://firebase.google.com/terms/crashlytics-app-distribution-data-processing-terms.

Providing the above information for processing for marketing purposes is voluntary.

Page top

[Topic 233958]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Data provision in Kaspersky Security for iOS

Kaspersky Security for Mobile complies with the General Data Protection Regulations (GDPR).

To install the app, a device user must read and accept the terms of the following statements regarding the processing of the user's personal data:

  • End User License Agreement
  • Products and Services Privacy Policy

Optionally, the user may read and accept the terms of the following statement:

  • Kaspersky Security Network Statement

The user can view the terms of these documents at any time in the About the AppAgreements and Statements section in the settings of Kaspersky Security for iOS. In this section, the user can also accept or decline the terms of the KSN Statement.

Information exchange with Kaspersky Security Network

To improve real-time protection, Kaspersky Security for iOS uses the Kaspersky Security Network cloud service for operating the Web Protection component. The app uses data received from KSN to scan web resources before they are opened.

Information on the type of data submitted to Kaspersky when using KSN during operation of Web Protection is available in the End User License Agreement. By accepting the terms and conditions of the License Agreement, you agree to transfer this information.

Information on the type of statistic data submitted to Kaspersky when using KSN during operation of the Kaspersky Security for iOS mobile app is available in the Kaspersky Security Network Statement. By accepting the terms and conditions of the Statement, you agree to transfer this information.

Data provision under the End User License Agreement

Where the Activation Code is used to activate the Software, in order to verify legitimate use of the Software, the End User agrees to periodically provide the Rightholder the following information:

  • Format of the data in the request to Rightholder's infrastructure; accessed IPv4 address of the web service; size of the content of the request to Rightholder infrastructure; protocol ID; Software activation code; data compression type; Software ID; set of IDs of Software that can be activated on the user's device; Software localization; full version of the Software; unique device ID; date and time on the user's device; Software installation ID (PCID); currently used Software activation code; OS version, OS build number, OS update number, OS edition, extended information about the OS edition; device model; mobile carrier code; operating system family; Software ID derived from the license; list of agreements presented to the user by the Software; type of legal agreement accepted by the user while using the Software; version of the legal agreement accepted by the user while using the Software; flag indicating whether the user has accepted the terms of the legal agreement while using the Software; checksum type for the object being processed; Software license header; ID of a regional activation center; Software license key creation date and time; Software license ID; ID of the information model used to provide the Software license; Software license expiration date and time; current status of the Software license key; type of Software license used; type of the license used to activate the Software; Software ID derived from the license.

The Rightholder can use such information also for gathering statistical information about the distribution and use of the Rightholder's Software.

In order to protect the Computer against information security threats, the End User agrees to periodically provide the Rightholder the following information:

  • Format of the data in the request to Rightholder's infrastructure; accessed address of the web service (URL, IP); port number; web address of the source of the web service request (referrer).
  • Full version of the Software; Software update ID; type of the installed Software; Software ID; the configuration identifier; the result of the Software action; error code.
  • Web address being processed; accessed IPv4 address of the web service; digital certificate thumbprint of the scanned object and hashing algorithm; certificate type; contents of the digital certificate being processed.

Data provision under the Kaspersky Security Network Statement

When the KSN Statement is accepted, the Rightholder automatically receives and processes the following data:

  • Information about the quality of KSN services (protocol used to exchange data with KSN; ID of the KSN service accessed by the Software; date and time when statistics stopped being received; number of KSN connections taken from the cache; number of requests for which a response was found in the local request database; number of unsuccessful KSN connections; number of unsuccessful KSN transactions; temporal distribution of cancelled requests to KSN; temporal distribution of unsuccessful KSN connections; temporal distribution of unsuccessful KSN transactions; temporal distribution of successful KSN connections; temporal distribution of successful KSN transactions; temporal distribution of successful requests to KSN; temporal distribution of requests to KSN that timed out; number of new KSN connections; number of unsuccessful requests to KSN caused by routing errors; number of unsuccessful requests caused by KSN being disabled in the Software settings; number of unsuccessful requests to KSN caused by network problems; number of successful KSN connections; number of successful KSN transactions; total number of requests to KSN; date and time when statistics started being received).
  • Device ID; full version of the Software; Software update ID; Software installation ID (PCID); type of the installed Software.
  • Installation date and time for the Software; Software activation date; Software localization; flag indicating whether participation in KSN is enabled; ID of the licensed Software; Software license ID; OS ID; version of the operating system installed on the user's computer; operating system bit version.

Providing the above information to the KSN is voluntary. You can opt out of participating in Kaspersky Security Network at any time.

Page top

[Topic 241127]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

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

Page top

[Topic 235115]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

How to get technical support

If you can't find a solution to your issue in the Kaspersky Security for Mobile documentation or in any of the sources of information about Kaspersky Security for Mobile, contact Technical Support. Technical Support specialists will answer all your questions about installing and using Kaspersky Security for Mobile.

Kaspersky provides support of Kaspersky Security for Mobile during its lifecycle (see the product 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]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

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 91120]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Sources of information about the application

Kaspersky Security for Mobile web page on the Kaspersky website

On the Kaspersky Security for Mobile page you can find general information about the application, its features and operation parameters.

The web page of Kaspersky Security for Mobile provides a link to eStore. There you can purchase or renew the application.

Kaspersky Security for Mobile web page in the Knowledge Base

Knowledge Base is a section on the Technical Support website.

On the Kaspersky Security for Mobile page in the Knowledge Base you can find articles that contain useful information, recommendations and answers to frequently asked questions on the application purchasing, installation, and use.

Knowledge Base articles can answer questions relating to not only to Kaspersky Security for Mobile but also to other Kaspersky applications. Knowledge Base articles can also include Technical Support news.

Online help

The online help of the application comprises help files.

The context help of administration plug-ins for Kaspersky Security for Mobile provides information about the windows of Kaspersky Security Center: a description of Kaspersky Security for Mobile settings and links to descriptions of the tasks that use these settings.

Full help of the Kaspersky Endpoint Security for Android and Kaspersky Security for iOS apps provides information on how to configure and use mobile apps.

Discussing Kaspersky applications on Kaspersky Support Forum

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.

Page top

[Topic 95897]

Glossary

Activating the application

Switching the application to fully functional mode. Application activation is performed by the user during or after installation of the application. You should have an activation code or key file to activate the application.

Activation code

A code that you receive when purchasing a license for Kaspersky Endpoint Security. This code is required for activation of the application.

The activation code is a unique sequence of twenty letters and numbers in the format xxxxx-xxxxx-xxxxx-xxxxx.

Administration group

A set of managed devices, such as mobile devices grouped according to the functions they perform and the set of apps installed on them. Managed devices are grouped so that they can be managed as a single whole. For example, mobile devices running the same operating system can be combined into an administration group. A group may include other administration groups. It is possible to create group policies and group tasks for group devices.

Administration Server

A component of Kaspersky Security Center that centrally stores information about all Kaspersky applications that are installed within the corporate network. It can also be used to manage these applications.

Administrator's workstation

The computer on which Kaspersky Security Center Administration Console has been deployed. If the application administration plug-in is installed on the administrator's workstation, the administrator can manage Kaspersky Endpoint Security mobile apps deployed on user devices.

Android work profile

A safe environment on the user's device in which the administrator can manage apps and user accounts without restricting the use of personal data by the user. When a work profile is created on the user's mobile device, the following corporate apps are automatically installed in the work profile: Google Play Market, Google Chrome, Downloads, Kaspersky Endpoint Security for Android, and others. Corporate apps installed in the work profile and notifications of these apps are marked with a red briefcase icon. You have to create a separate Google corporate account for the Google Play Market app. Apps installed in the work profile appear in the common list of apps.

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.

Apple Push Notification service (APNs) certificate

Certificate signed by Apple, which allows you to use Apple Push Notification. Through Apple Push Notification, an iOS MDM Server can manage iOS devices.

Application management plug-in

A dedicated component that provides the interface for managing Kaspersky applications through Administration Console. Each application that can be managed through Kaspersky Security Center SPE has its own management plug-in. The management plug-in is included in all Kaspersky applications that can be managed via Kaspersky Security Center.

Certificate Signing Request

File with the settings of an Administration Server, which is approved by Kaspersky and then sent to Apple to obtain an APNs certificate.

Compliance control

Verification that the settings of a mobile device and Kaspersky Endpoint Security for Android comply with corporate security requirements. Corporate security requirements regulate the device usage. For example, real-time protection must be enabled on the device, the anti-virus databases must be up-to-date, and the device password must be strong enough. Compliance control is based on a list of rules. A compliance rule includes the following components:

  • Device check criterion (for example, absence of prohibited apps on the device)
  • Time interval allocated for the user to fix the noncompliance (for example, 24 hours)
  • Action that will be taken on the device if the user does not fix the noncompliance within the time set (for example, locking the device)
Device administrator

A set of app rights on an Android device that enables the app to use device management policies. It is necessary to implement full functionality of Kaspersky Endpoint Security on Android devices.

End User License Agreement

Binding agreement between you and AO Kaspersky Lab that stipulates the terms on which you may use the application.

Group task

A task intended for an administration group and performed on all managed devices included in the group.

IMAP

Protocol for accessing email. In contrast to the POP3 protocol, IMAP provides extended capabilities for working with mailboxes, such as managing folders and handling messages without copying their contents from the mail server. The IMAP protocol uses port 134.

Installation package

A set of files created for remote installation of a Kaspersky application by using the remote administration system. An installation package is created on the basis of dedicated files included in the application distribution package. The installation package contains a range of settings needed to install the application and get it running immediately after installation. The values of settings in the distribution kit correspond to default values of application settings.

iOS MDM device

An iOS mobile device controlled by the iOS MDM Server.

iOS MDM profile

A profile that contains a set of settings for connecting iOS mobile devices to the Administration Server. An iOS MDM profile makes it possible to distribute iOS configuration profiles in background mode using the iOS MDM Server, and also receive extended diagnostic information about mobile devices. A link to the iOS MDM profile needs to be sent to a user in order to enable the iOS MDM Server to discover and connect the user's iOS mobile device.

iOS MDM Server

A component of Kaspersky Endpoint Security that is installed on a client device, allowing connection of iOS mobile devices to the Administration Server and management of iOS mobile devices through Apple Push Notifications (APNs).

Kaspersky categories

Predefined data categories developed by Kaspersky experts. Categories can be updated during application database updates. A security officer cannot modify or delete predefined categories.

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 Administrator

The person managing application operations through the Kaspersky Security Center remote centralized administration system.

Kaspersky Security Center Web Server

A component of Kaspersky Security Center that is installed together with Administration Server. Web Server is designed for transmission, over a network, of stand-alone installation packages, iOS MDM profiles, and files from a shared folder.

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. The application generates the key file based on the activation code. You may use the application only when you have a key file.

License

A time-limited right to use the app, granted under the End User License Agreement.

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.

Manifest file

A file in PLIST format containing a link to the app file (ipa file) located on a web server. It is used by iOS devices to locate, download, and install apps from a web server.

Phishing

A type of internet fraud aimed at obtaining unauthorized access to users' confidential data.

Policy

A set of settings of the application and Kaspersky Endpoint Security mobile apps applied to devices in administration groups or to individual devices. Different policies can be applied to different administration groups. A policy includes the configured settings of all functions of Kaspersky Endpoint Security mobile apps.

POP3

Network protocol used by a mail client to receive messages from a mail server.

Provisioning profile

Collection of settings for applications' operation on iOS mobile devices. A provisioning profile contains information about the license; it is linked to a specific application.

Proxy server

A computer network service which allows users to make indirect requests to other network services. First, a user connects to a proxy server and requests a resource (e.g., a file) located on another server. Then the proxy server either connects to the specified server and obtains the resource from it or returns the resource from its own cache (if the proxy has its own cache). In some cases, a user's request or a server's response can be modified by the proxy server for certain purposes.

Quarantine

The folder to which the Kaspersky application moves probably infected objects that have been detected. Objects are stored in Quarantine in encrypted form in order to avoid any impact on the computer.

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.

Standalone installation package

An installation file of Kaspersky Endpoint Security for the Android operating system, which contains the settings of application connection to the Administration Server. It is created on the basis of the installation package of this application and is a particular case of mobile app package.

Subscription

Enables use of the application within the selected parameters (expiration date and number of devices). You can pause or resume your subscription, renew it automatically, or cancel it.

Supervised device

iOS device whose settings are monitored by Apple Configurator, a program for group configuration of iOS devices. A supervised device has the supervised status in Apple Configurator. Every time a supervised device connects to the computer, Apple Configurator checks the device configuration against the specified reference settings, and then redefines them if necessary. A supervised device cannot be synchronized with Apple Configurator installed on a different computer.

Every supervised device provides more settings to redefine through the Kaspersky Device Management for iOS policy than a non-supervised device. For example, you can configure an HTTP proxy server to monitor internet traffic on a device within the corporate network. By default, all mobile devices are non-supervised.

Unlock code

A code that you can get in Kaspersky Security Center. It is needed to unlock a device after the Lock & Locate, Alarm, or Mugshot commands have been executed, and when Self-Defense is triggered.

Virus

A program that infects other ones, by adding its code to them in order to gain control when infected files are run. This simple definition allows identifying the main action performed by any virus: infection.

Page top

[Topic 67964]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Information about third-party code

You can download and read information about third-party code in the following files:

On mobile devices, information about third-party code is available in the About the App section of the mobile apps.

Page top

[Topic 65607]

The help for this version of the solution is no longer updated, so it may contain outdated information. For up-to-date information about the solution refer to the Kaspersky Secure Mobility Management 4.1 Help.

Trademark notices

Registered trademarks and service marks are the property of their respective owners.

PostScript is either a registered trademark or a trademark of Adobe in the United States and/or other countries.

Apple, Apple Configurator, AirDrop, AirPlay, AirPort, AirPort Express, AirPrint, Aperture, App Store, Apple Music, Apple TV, Apple Watch, Bonjour, Face ID, FaceTime, FileVault, Find My, Handoff, iBooks, iBooks Store, iCal, iCloud, iCloud Keychain, iMessage, iPad, iPadOS, iPhone, iPhoto, iTunes, iTunes Store, iTunes U, Keychain, OS X, Safari, Siri, Spotlight, and Touch ID are trademarks of Apple Inc.

Aruba Networks is a trademark of Aruba Networks, Inc. in the United States and certain other countries.

The Bluetooth word, mark and logos are owned by Bluetooth SIG, Inc.

Aironet, Cisco, Cisco AnyConnect, and IOS are registered trademarks or trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

Dell Technologies, Dell, SecurID, and other trademarks are trademarks of Dell Inc. or its subsidiaries.

Google, Android, Chrome, Chromebook, Chromium, Crashlytics, Firebase, Gmail, Google Analytics, Google Assistant, Google Chrome, Google Mail, Google Maps, Google Play, Google Safe Browsing, Google SafeSearch, Google Translate, Nexus, SPDY, and YouTube are trademarks of Google LLC.

HTC is a trademark of HTC Corporation.

Huawei, HUAWEI, and EMUI are trademarks of Huawei Technologies Co., Ltd.

IBM and Maas360 are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide.

Juniper Networks, Juniper, and JUNOS are trademarks or registered trademarks of Juniper Networks, Inc. in the United States and other countries.

Microsoft, Active Directory, ActiveSync, Microsoft Intune, Tahoma, Windows, Windows Mobile, and Windows Phone are trademarks of the Microsoft group of companies.

MOTOROLA and the Stylized M Logo are trademarks or registered trademarks of Motorola Trademark Holdings, LLC.

Oracle, JavaScript are registered trademarks of Oracle and/or its affiliates.

The BlackBerry trademark 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.

SonicWALL, Aventail, and SonicWALL Mobile Connect are trademarks of SonicWall, Inc.

SOTI and MobiControl are registered trademarks of SOTI Inc. in the United States and in other jurisdictions.

Symantec is a trademark or registered trademark of Symantec Corporation or its affiliates in the U.S. and other countries.

Symbian trademark is owned by the Symbian Foundation Ltd.

AirWatch, VMware, and VMware Workspace ONE are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions.

Mozilla and Firefox are trademarks of the Mozilla Foundation in the U.S. and other countries.

F5 is a trademark of F5 Networks, Inc. in the U.S. and in certain other countries.

Page top