Port for listening to REST API

8085

Event severity level

debug

info

warning

error

critical

noset

noset

Authorization key

If the KRAS4D_XAPIKEY setting is specified, each request is verified for the presence of the x-api-key header and if its content matches the value of the KRAS4D_XAPIKEY setting. If these conditions are not met, the request is rejected. If this setting is missing, verification is not performed.

Activation code or key file

To activate a KESL container using an activation code, when running the KESL container specify the activation code in the configuration file or pass the activation code in an environment variable:

docker run ... -e KRAS4D_ACTIVATION='<activation code>'

To activate a KESL container using a key file, when running the KESL container specify the key file in the configuration file or pass the key file in an environment variable:

docker run ... -e KRAS4D_ACTIVATION='<key file>' -e KRAS4D_KEYPATH=/root/kesl-service/keys -v <path to the directory with keys>:/root/kesl-service/keys

To activate a KESL container using a key file, the /root/kesl-service/keys mount point is required.

Additional scan settings

The optional KRAS4D_SCANOPTIONS setting allows you to configure the settings of the Container Scan task:

docker run ... -e KRAS4D_SCANOPTIONS='<settings>'

where <settings> are the settings of the Container Scan task.

Additional update settings

The optional KRAS4D_UPDATEOPTIONS setting allows you to configure the settings of the Update task.

docker run ... -e KRAS4D_UPDATEOPTIONS='<settings>'

where <settings> are the Update task settings SourceType and ApplicationUpdateMode, as well as the settings in the CustomSources.item_# section.

Update the application databases when KESL container starts

By default, the application databases are downloaded to the /var/opt/kaspersky/kesl/private/updates directory when the KESL container is started.

To implement the joint operation of several KESL containers with one instance of the application databases and to speed up the launch of the KESL container, it is recommended to move this directory to the device where the KESL container is installed by means of mounting:

docker run ... -v <path to database directory>:/var/opt/kaspersky/kesl/private/updates

True

Do not process the image if it already exists in the target repository.

False

Maximum time to wait for application commands to run, in seconds

600

Maximum time to wait for application database update tasks to run, in seconds

600

Name of the KESL container configuration file

kesl-service.config