In order to meet the performance and operational needs of our customers, starting Deep Security Manager version 20.0.503 the capability to remove the baseline data from the database has been introduced. This does not impact the capability of the Integrity Monitoring module to detect change.
Minimum version:
- Deep Security Manager - 20.0.503 ( 20 LTS Update 2021-09-23)
- Deep Security Agent - 20.0.0-2740 (20 LTS Update 2021-07-29)
How to enable this setting on Windows:
Run the following command to adjust the hidden setting:
- In the Windows command line, go to the Deep Security Manager's working folder, for example,
cd "\Program Files\Trend Micro\Deep Security Manager"
- Use the dsm_c command with parameters to change to the new settings:
dsm_c.exe -action changesetting -name settings.configuration.enableDenormalizedIM -value true
dsm_c command returns 0 value indicating successful execution
How to enable this setting on Linux:
- In the Linux command line, go to the Deep Security Manager's working folder, for example,
cd /opt/dsm
- Use the dsm_c command with parameters to change to the new settings:
./dsm_c.exe -action changesetting -name settings.configuration.enableDenormalizedIM -value true
dsm_c command returns 0 value indicating successful execution
In addition, all security events related to integrity monitoring and forwarding these events (through SNS or syslog) are not affected by this change.
The following features will not be available when the baseline data is removed from the database:
- Unable to see the complete baseline in the web administration interface through the 'view baseline' button.
- Unable to use the "Trusted Common Baseline" as the source of Auto-Tagging.
- Unable to generate the "Integrity Monitoring Baseline Report"