About Protection Server and Light Agent dump files

A dump file contains information about the operation memory of Kaspersky Security processes at the time the dump file was created.

A dump file can also contain personal data. It is recommended that you ensure that information is protected against unauthorized access before it is sent to Kaspersky.

Protection Server dump files

By default, Protection Server dump files are not created. You can enable or disable logging of dump files.

To enable logging of Protection Server dump files:

1. Create an etc/opt/kaspersky/la/dumps_enabled file.
2. Restart the scanserver service by running the systemctl restart la-scanserver command.

By default, all created dump files are located in the /var/opt/kaspersky/la/dumps directory. The name of each *.dmp file contains the date and time when the file was created, the process identifier (PID), and the dump number in the session.

You can change the dump logging settings in the ScanServer.conf configuration file (in the [dumps] section).

Access to the dump files requires the password of the SVM root account assigned during Protection Server installation. If you change the default directory for storing dump files, Kaspersky Security does not control access to dump files. If the file system where the specified directory is located supports appropriate access control, the root account permissions are required to access the dump files.

Protection Server dump files are not automatically sent to Kaspersky. Dump files are automatically deleted when uninstalling the application.

To disable logging of Protection Server dump files:

1. Delete the etc/opt/kaspersky/la/dumps_enabled file.
2. Restart the scanserver service by running the systemctl restart la-scanserver command.

About Light Agent for Windows dump files

Light Agent for Windows dump files (*.dmp) are created automatically when an application failure occurs and are saved to the %ProgramData%\Kaspersky Lab folder.

Saved dump files can contain sensitive data. The files are saved in readable format, access to files is not restricted. To control access to data, you need to protect the dump files on your own.

Light Agent for Windows dump files are not automatically sent to Kaspersky. Dump files are automatically deleted when uninstalling the application.

About Light Agent for Linux dump files

By default, Light Agent for Linux dump files are not created. You can enable or disable logging of dump files.

To enable logging of dumps for Light Agent for Linux:

1. Create a /etc/opt/kaspersky/lightagent/dumps_enabled file.
2. Restart the lightagent service by executing one of the following commands:
   • systemctl restart lightagent – for systems with systemd support
   • /etc/init.d/lightagent restart – for systems with SysV init support

By default, all created dump files are located in the /var/opt/kaspersky/lightagent/dumps directory. The name of each *.dmp file contains the date and time when the file was created, the process identifier (PID), and the dump number in the session.

You can change the dump logging settings in the LightAgent.conf configuration file (in the [dumps] section).

If you changed the default directory for dump files, the dump files will not be automatically deleted when you uninstall Light Agent for Linux. You can delete the files manually.

The root account permissions are required to access the dump files. If you change the default directory for storing dump files, Kaspersky Security does not control access to dump files. If the file system where the specified directory is located supports appropriate access control, the root account permissions are required to access the dump files.

Light Agent for Linux dump files are not automatically sent to Kaspersky. Dump files are automatically deleted when uninstalling the application, unless you changed the default dump file storage directory.

To disable logging of dumps for Light Agent for Linux:

1. Delete the /etc/opt/kaspersky/lightagent/dumps_enabled file.
2. Restart the lightagent service by executing one of the following commands:
   • systemctl restart lightagent – for systems with systemd support
   • /etc/init.d/lightagent restart – for systems with SysV init support