Kaspersky Endpoint Security for Linux

Deploying the application using the command line

Kaspersky Endpoint Security is distributed in the DEB and RPM packages. There are separate packages for the application and for the graphical user interface.

You can perform the following actions when installing the application:

  • Install only the application package, without the graphical user interface.
  • Install the graphical user interface package.

    It is not possible to install the graphical user interface package on a client device that does not have the application package installed.

    If Kaspersky Endpoint Security is used in Light Agent mode to protect virtual environments (as part of Kaspersky Hybrid Cloud Security for Virtualization Light Agent), the graphical user interface is not supported. You need to install only the application package without the graphical user interface.

If the version of the apt package manager is lower than 1.1.X, use the dpkg/rpm package manager (depending on the operating system) for installation.

After the application installation using the command line is completed, perform the post-installation configuration of the application by running the post-installation configuration script or in the automatic mode.

In this section

Installing the application using the command line

Post-installation configuration of the application in interactive mode

Post-installation configuration of the application in automatic mode

Settings in the configuration file for post-installation configuration

Page top
[Topic 198107]

Installing the application using the command line

Installing the application without the graphical interface.

To install Kaspersky Endpoint Security from an RPM package on a 32-bit operating system, execute the following command:

# rpm -i kesl-12.0-<build number>.i386.rpm

To install Kaspersky Endpoint Security from an RPM package on a 64-bit operating system, execute the following command:

# rpm -i kesl-12.0-<build number>.x86_64.rpm

To install Kaspersky Endpoint Security from an RPM package on a 64-bit operating system for the Arm architecture, execute the following command:

# rpm -i kesl-12.0-<build number>.aarch64.rpm

To install Kaspersky Endpoint Security from a DEB package on a 32-bit operating system, execute the following command:

# apt-get install ./kesl_12.0-<build number>_i386.deb

To install Kaspersky Endpoint Security from a DEB package on a 64-bit operating system, execute the following command:

# apt-get install ./kesl_12.0-<build number>_amd64.deb

To install Kaspersky Endpoint Security from a DEB package on a 64-bit operating system for the Arm architecture, execute the following command:

# apt-get install ./kesl_12.0-<build number>_arm64.deb

Installing the graphical interface of the application

To install the graphical interface from the RPM package to a 32-bit operating system, execute the following command:

# rpm -i kesl-gui-12.0-<build number>.i386.rpm

To install the graphical interface from the RPM package to a 64-bit operating system, execute the following command:

# rpm -i kesl-gui-12.0-<build number>.x86_64.rpm

To install the graphical interface from an RPM package on a 64-bit operating system for the Arm architecture, execute the following command:

# rpm -i kesl-gui-12.0-<build number>.aarch64.rpm

To install the graphical interface from the DEB package to a 32-bit operating system, execute the following command:

# apt-get install ./kesl-gui_12.0-<build number>_i386.deb

To install the graphical interface from the DEB package to a 64-bit operating system, execute the following command:

# apt-get install ./kesl-gui_12.0-<build number>_amd64.deb

To install the graphical interface from a DEB package on a 64-bit operating system for the Arm architecture, execute the following command:

# apt-get install ./kesl-gui_12.0-<build number>_arm64.deb

Page top
[Topic 233694]

Post-installation configuration of the application in interactive mode

After installing Kaspersky Endpoint Security using the command line, perform the initial configuration of the application by running the initial configuration script. The initial configuration script is included in the Kaspersky Endpoint Security distribution kit.

Performing the post-installation configuration after installing the application using the command line is required to enable the protection of the client device.

To run the Kaspersky Endpoint Security initial configuration script, execute the following command:

# /opt/kaspersky/kesl/bin/kesl-setup.pl

The initial configuration script must be run with the root privileges after the installation of Kaspersky Endpoint Security package is finished. The script requests the values of Kaspersky Endpoint Security settings step-by-step. The script finishing and the console being released indicate that the post-installation configuration is completed.

To check the return code, execute the following command:

echo $?

If the command returns 0, the post-installation configuration of the application is completed successfully.

Kaspersky Endpoint Security protects the device only after the application databases are updated.

In this section

Selecting the application usage mode

Defining the role of the virtual machine

Enabling VDI protection mode

Selecting the locale

Viewing the End User License Agreement and the Privacy Policy

Accepting the End User License Agreement

Accepting the Privacy Policy

Using Kaspersky Security Network

Removing users from privileged groups

Assigning the Administrator role to a user

Determining the file operation interceptor type

Enabling automatic configuration of SELinux

Configuring the update source

Configuring proxy server settings

Starting an application database update

Enabling automatic application database update

Application activation

Page top
[Topic 197897]

Selecting the application usage mode

At this step, select the Kaspersky Endpoint Security usage mode:

  • Enter yes if you want to use Kaspersky Endpoint Security in Light Agent mode to protect virtual environments.
  • Enter no if you want to use Kaspersky Endpoint Security in standalone mode.

After the initial configuration is complete, you cannot change the application usage mode.

Page top
[Topic 82654]

Defining the role of the virtual machine

This step is displayed only if at the first step you selected to use Kaspersky Endpoint Security in Light Agent mode for protecting virtual environments.

At this step, specify the role of the virtual machine (server or workstation) on which you are installing Kaspersky Endpoint Security:

  • Enter yes if you are using the virtual machine as a server.
  • Enter no if you are using a virtual machine as a workstation.

The role of a virtual machine determines the license under which the application will be used on this virtual machine as well as the available functionality.

Page top
[Topic 90255]

Enabling VDI protection mode

This step is displayed only if at the first step you selected to use Kaspersky Endpoint Security in Light Agent mode for protecting virtual environments.

At this step, you can enable VDI protection mode. This mode optimizes the operation of Kaspersky Endpoint Security on temporary virtual machines. If VDI protection mode is enabled, updates that require restarting the virtual machine are not installed. When receiving updates that require a restart, the Light Agent installed on the virtual machine sends a message to Kaspersky Security Center about the need to update the protected virtual machine template.

Specify yes if you want to enable VDI protection mode. This is recommended if you are installing Kaspersky Endpoint Security on a virtual machine template that will be used to create temporary virtual machines.

Specify no if you do not want to enable VDI protection mode. This is recommended if you are installing Kaspersky Endpoint Security on a persistent virtual machine or on a virtual machine template that will be used to create persistent virtual machines.

Page top
[Topic 85820]

Selecting the locale

At this step, the application displays the list of supported locales in RFC 3066 format.

Specify the locale as it is listed here. This locale is used for the following purposes:

  • Localization of the texts of the End User License Agreement, Privacy Policy, and Kaspersky Security Network Statement, which are displayed during the installation.
  • Localization of application events sent to Kaspersky Security Center.

The locale of the graphical interface and the application command line is taken from the LANG environment variable. If the application does not support this localization, it defaults to the English localization.

Page top
[Topic 197898]

Viewing the End User License Agreement and the Privacy Policy

At this step, read the End User License Agreement concluded between you and Kaspersky, and the Privacy Policy describing the handling and transmission of data.

Page top
[Topic 199016]

Accepting the End User License Agreement

At this step, you must either accept or decline the terms of the End User License Agreement.

After exiting viewing mode, enter one of the following values:

  • yes (or y), if you accept the terms of the End User License Agreement.
  • no (or n), if you do not accept the terms of the End User License Agreement.

If you did not accept the terms and conditions of the End User License Agreement, the Kaspersky Endpoint Security setup process is aborted.

Page top
[Topic 197899]

Accepting the Privacy Policy

At this step, you must either accept or decline the terms of the Privacy Policy.

After exiting viewing mode, enter one of the following values:

  • yes (or y), if you accept the terms of the Privacy Policy.
  • no (or n), if you do not accept the terms of the Privacy Policy.

If you did not accept the terms and conditions of the Privacy Policy, the Kaspersky Endpoint Security setup process is aborted.

Page top
[Topic 197900]

Using Kaspersky Security Network

At this step, you must either accept or decline the terms of use of the Kaspersky Security Network Statement. The file ksn_license.<language ID> containing the text of the Kaspersky Security Network Statement is located in the directory /opt/kaspersky/kesl/doc/.

Enter one of the following values:

  • yes (or y), if you accept the terms of the Kaspersky Security Network Statement. This enables the extended KSN mode.
  • no (or n), if you do not accept the terms of the Kaspersky Security Network Statement.

Refusal to participate in Kaspersky Security Network does not interrupt the initial configuration of Kaspersky Endpoint Security. You can enable, disable, or change the Kaspersky Security Network mode at any time.

If Kaspersky Endpoint Security is used in standalone mode and you have enabled the use of Kaspersky Security Network, the application's cloud mode is automatically enabled. In this mode, Kaspersky Endpoint Security uses a lightweight version of the malware databases. In Light Agent mode for protecting virtual environments, use of the lightweight malware databases is not supported.

Page top
[Topic 197901]

Removing users from privileged groups

This step is displayed only if users are detected in the kesladmin group and/or in the keslaudit group.

At this step, specify whether or not to remove users from the kesladmin and keslaudit privileged groups. Users included in the kesladmin and keslaudit groups receive privileged access to the application's functions.

Enter yes to remove all detected users from the kesladmin and/or keslaudit group. Users whose primary group is kesladmin or keslaudit will be moved to the nogroup group. If there is no nogroup group, the installation will fail and you will be prompted to manually remove users from privileged groups.

Enter no if you do not want the application to remove users from the privileged groups.

Page top
[Topic 93536]

Assigning the Administrator role to a user

At this step, you can grant the administrator (admin) role to the user.

Enter the name of the user to whom you want to grant the administrator role. You need the Administrator role to manage application settings and task settings in the graphical interface of the application and on the command line without using the sudo command.

You can assign the administrator role to a user later, after completing the initial configuration.

Page top
[Topic 206406]

Determining the file operation interceptor type

At this step, the file operation interceptor type for the utilized operating system is determined. For operating systems that do not support fanotify technology, kernel module compilation will begin.

If all the required packages are available, the kernel module will be automatically compiled when the File Threat Protection task starts.

If, during the compilation of the kernel module, any dependencies are not found on the device, the Kaspersky Endpoint Security application suggests installing the relevant packages. If the package download fails, an error message will be displayed.

Page top
[Topic 197903]

Enabling automatic configuration of SELinux

This step is displayed only if SELinux is installed on your operating system.

At this step, you can enable automatic configuration of SELinux for working with Kaspersky Endpoint Security.

Enter yes to enable automatic configuration of SELinux. If SELinux cannot be configured automatically, the application displays an error message and prompts the user to configure SELinux manually.

Enter no if you do not want the application to automatically configure SELinux.

By default, the application suggests yes.

If necessary, you can manually configure SELinux to work with the application later, after the initial configuration of the application is complete.

Page top
[Topic 237159]

Configuring the update source

This step is displayed only if you selected to use Kaspersky Endpoint Security in standalone mode at the first step. If Kaspersky Endpoint Security is used in Light Agent mode, Kaspersky Endpoint Security receives updates of databases and application modules for the Light Agent from the Protection Server.

At this step, specify the update sources for databases and application modules.

Enter one of the following values:

  • KLServers: the application receives updates from one of the Kaspersky update servers.
  • SCServer: the application downloads updates to the protected device from Kaspersky Security Center Administration Server installed in your organization. You can select this update source if you use Kaspersky Security Center for centralized administration of device protection in your organization.
  • <URL>: the application downloads updates from a custom source. You can specify the address of the custom source of updates in the local area network or on the Internet.
  • <path> – the application receives updates from the specified directory.
Page top
[Topic 197904]

Configuring proxy server settings

This step is displayed only if you selected to use Kaspersky Endpoint Security in standalone mode at the first step.

At this step, you must specify the proxy server settings if you are using a proxy server to access the Internet. Internet connection is required to download the application databases from the update servers.

To configure proxy server settings, perform one of the following actions:

  • If you use a proxy server to connect to the Internet, specify the address of the proxy server using one of the following formats:
    • <IP address of the proxy server>:<port number>, if the proxy server connection does not require authentication;
    • <user name>:<password>@<IP address of the proxy server>:<port number>, if the proxy server connection requires authentication.

      When connecting via an HTTP proxy, we recommend to use a separate account that is not used to sign in to other systems. An HTTP proxy uses an insecure connection, and the account may be compromised.

  • If you do not use a proxy server to connect to the Internet, enter no as your answer.

By default, the application suggests no.

You can configure the proxy server settings later without using the post-installation configuration script.

Page top
[Topic 197905]

Starting an application database update

This step is displayed only if you selected to use Kaspersky Endpoint Security in standalone mode at the first step. If Kaspersky Endpoint Security is used in Light Agent mode, Kaspersky Endpoint Security receives updates of databases and application modules for the Light Agent from the Protection Server.

At this step, you can run the application database update task on the client device. The application databases contain descriptions of the threat signatures and methods of countering them. The application uses these records when searching and neutralizing threats. Kaspersky virus analysts regularly add new records about threats.

If you do not want to start to download the application databases, enter no.

If you want to start the database update task on the device, enter yes.

By default, the application suggests yes.

If yes is selected, the application will be automatically restarted after the databases are updated.

Kaspersky Endpoint Security protects the device only after the application databases are updated.

You can start the Update task without using the initial configuration script.

Page top
[Topic 197906]

Enabling automatic application database update

This step is displayed only if you selected to use Kaspersky Endpoint Security in standalone mode at the first step. If Kaspersky Endpoint Security is used in Light Agent mode, Kaspersky Endpoint Security receives updates of databases and application modules for the Light Agent from the Protection Server.

At this step, you can enable automatic update of the application databases.

Enter yes to enable automatic application database update. By default, the application checks for available database updates every 60 minutes. If updates are available, the application downloads the updated databases.

Enter no if you do not want the application to automatically update the databases.

You can enable automatic database update without using the initial configuration script by configuring the update task schedule.

Page top
[Topic 197907]

Application activation

This step is displayed only if you selected to use Kaspersky Endpoint Security in standalone mode at the first step. If Kaspersky Endpoint Security is used in Light Agent mode, Kaspersky Endpoint Security receives information about the license from the Protection Server; there is no need to activate Kaspersky Endpoint Security separately.

At this step, activate the application using an activation code or a key file.

To activate the application using an activation code, enter the activation code.

To activate the application using a key file, specify the full path to the key file.

If no activation code or key file is specified, the application is activated using a trial key for one month.

You can activate the application later without using the post-installation configuration script.

Page top
[Topic 197908]

Post-installation configuration of the application in automatic mode

You can perform post-installation configuration of the application in automatic mode.

To launch the automatic initial setup of the application, carry out the following command:

# /opt/kaspersky/kesl/bin/kesl-setup.pl --autoinstall=<initial configuration file>

where <post-installation configuration file> is a path to the configuration file that contains post-installation configuration settings. You can create this file or copy the necessary structure from the autoinstall.ini configuration file used for remote installation of the application using Kaspersky Security Center.

When the post-installation configuration script is finished and releases the console, the post-installation configuration of the application is complete.

To check the return code, execute the following command:

echo $?

If the command returns 0, the post-installation configuration of the application is completed successfully.

Kaspersky Endpoint Security protects the device only after the application databases are updated.

To correctly update application modules after the script has finished, you may need to restart the application. Check the status of updates for the application using the kesl-control --app-info command.

Page top
[Topic 197909]

Settings in the configuration file for post-installation configuration

In the post-installation configuration file, you can specify the settings shown in the table below. The set of applicable settings depends on the application usage mode.

Settings in the configuration file for post-installation configuration

Setting

Description

Values

KSVLA_MODE

Kaspersky Endpoint Security usage mode.

yes - Kaspersky Endpoint Security is used in Light Agent mode to protect virtual environments (as part of Kaspersky Hybrid Cloud Security for Virtualization Light Agent).

no - Kaspersky Endpoint Security is used in standalone mode.

SERVER_MODE

The role of the protected virtual machine (server or workstation).

The setting is applied only if the application is used in Light Agent mode.

yes - the protected virtual machine is used as a server.

no - the protected virtual machine is used as a workstation.

VDI_MODE

Enabling VDI protection mode to optimize application performance on temporary virtual machines.

The setting is applied only if the application is used in Light Agent mode.

yes – enable VDI protection mode. This is recommended if you are installing Kaspersky Endpoint Security on a virtual machine template that will be used to create temporary virtual machines.

no – do not enable VDI protection mode.

EULA_AGREED

Required setting.

Acceptance of the terms of the End User License Agreement.

yes: accept the terms of the End User License Agreement to continue the application installation.

no – do not accept the End User License Agreement. The application installation will be terminated.

PRIVACY_POLICY_AGREED

Required setting.

Acceptance of the terms of the Privacy Policy.

yes: accept the Privacy Policy to continue installing the application.

no – do not accept the terms and conditions of the Privacy Policy. The application installation will be terminated.

USE_KSN

Required setting.

Enabling Kaspersky Security Network usage: To enable the use of KSN, the terms of the Kaspersky Security Network Statement must be accepted.

yes – accept the terms of the Kaspersky Security Network Statement and enable the use of KSN.

no – do not accept the Kaspersky Security Network Statement.

If Kaspersky Endpoint Security is used in standalone mode and you have enabled the use of KSN, the application's cloud mode is automatically enabled. In this mode, Kaspersky Endpoint Security uses a lightweight version of the malware databases.

GROUP_CLEAN

Required setting.

Removing users from the kesladmin and keslaudit privileged groups.

yes - Remove users from the privileged groups. If the value is yes and there is no nogroup group, the installation will fail and you will be prompted to manually remove users from privileged groups.

no - Do not remove users from the privileged groups.

LOCALE

Optional setting.

The locale used for the application events sent to Kaspersky Security Center.

The locale in the format specified by RFC 3066.

If the Locale setting is not specified, the operating system locale is used. If the application fails to determine the operating system localization language or the operating system localization is not supported, the default value will be used – en_US.utf8.

The locale of the graphical interface and the application command line depends on the value of the LANG environment variable. If the locale that is not supported by Kaspersky Endpoint Security is specified as the value of the LANG environment variable, the graphical interface and the command line are displayed in English.

INSTALL_LICENSE

Activation code or path to the key file for adding a license key to the application.

This setting applies only if the application is used in standalone mode.

<activation code> if you want to activate the application using an activation code during installation.

<full path to key file> if you want to activate the application using a key file during installation.

none if you do not want to activate the application during installation, for example, if you are installing the application in an isolated network segment without internet access.

UPDATER_SOURCE

Update source.

This setting applies only if the application is used in standalone mode.

SCServer – use the Kaspersky Security Center Administration Server as the update source.

KLServers – use Kaspersky servers as the update source.

Update source address

PROXY_SERVER

Address of the proxy server used to connect to the Internet.

This setting applies only if the application is used in standalone mode.

Proxy server address

UPDATE_EXECUTE

Start application database update task during setup.

This setting applies only if the application is used in standalone mode.

yes – start update task.

no – do not start update task.

KERNEL_SRCS_INSTALL

Automatic start of kernel module compilation.

yes – compile kernel module.

no – do not compile kernel module.

ADMIN_USER

A user assigned the administrator role (admin).

 

CONFIGURE_SELINUX

Automatic configuration of SELinux for working with Kaspersky Endpoint Security.

yes – automatically configure SELinux to work with Kaspersky Endpoint Security.

no – do not automatically configure SELinux to work with Kaspersky Endpoint Security.

DISABLE_PROTECTION

Disable protection components and scan tasks after the application is installed.

An installation with protection components disabled can be convenient, for example, in order to reproduce a problem in the operation of the application and create a trace file.

If you enable the necessary components and tasks after installing the application with the DISABLE_PROTECTION=yes parameter, the enabled components and tasks will continue to work after the application is restarted.

yes - Disable protection components and scan tasks when the application is started after installation.

no - Do not disable protection components and scan tasks when the application is started after installation.

If you want to change the settings in the configuration file for initial setup of the application, specify the values of settings in the following format: <setting_name>=<setting_value> (the application does not process spaces between the name of a setting and its value).

Page top
[Topic 236947]