Kaspersky Next XDR Expert
1.2
Managing Kaspersky Unified Monitoring and Analysis Platform  >  Administrator's guide  >  KUMA services  >  AI services  >  AI score and asset status  >  Settings of the AI score and asset status service
Settings of the AI score and asset status service

Available AI service settings

Setting

Description

cert_file_path

Path to the directory that contains the certificate generated by the installer.

Default path:

/opt/kaspersky/mlservice/service.crt

You can specify a different path. In this case, make sure that the user that starts the service has access to the specified directory.

key_file_path

Path to the directory that contains the key generated by the installer.

Default path:

/opt/kaspersky/mlservice/service.key

You can specify a different path. In this case, make sure that the user that starts the service has access to the specified directory.

kuma_address

FQDN of the host on which the KUMA Core is installed and port on which the KUMA Core is to listen for the AI service. To install in a high availability configuration, you must specify port 7226.

Example:

<FQDN of the host on which KUMA Core is installed>:7226

 

kuma_cert_file_path

Path to the directory where the KUMA Core certificate is located.

Default path:

/opt/kaspersky/mlservice/core-external-ca.cert

event_storage_path

Path to the directory where the service is to place received correlation events.

Default path:

/var/mlservice/events

model_storage_path

Path to the directory where the service is to place the trained model.

Default path:

/var/mlservice/models

period_for_train_days

The number of days for which you want to get correlation events that involve your assets from the available storage clusters in order to train the model.

The default setting is 12 days.

This means that the directory will contain events for the past <N> days. The oldest events are deleted.

events_overlap_in_seconds

Overlap time. When events for assessing the scores of assets are downloaded on a schedule, they are retrieved from the time of the last downloaded event for the current day minus the value of the events_overlap_in_seconds setting.

The default value is 60 seconds.

Example: the time when the last event was received is 8:58. The starting time for the next batch of events to be downloaded is 8:57.

Article ID: 292787, Last review: Apr 14, 2025
Page top