You may configure IMSVA to display the detailed reason by setting the hidden key in the tb_global_setting table:
"EnableComplianceDetailMatchResult = yes"
The default value is "no" if it is not defined.
The following SQL statement can set this parameter (if it does not exist):
insert into tb_global_setting values ('general', 'EnableComplianceDetailMatchResult', 'yes', 'imss.ini', '');
After inserting this parameter, the command "S99IMSS restart" should be executed.
The logs would then show the following:
Sensitive information which trigger the compliance template would be marked in asterisks:
If the administrator wants to unmark the sensitive information, he can set another hidden key:
"EnableSensitiveInfoMaskInComplianceMatchedContent = no"
The default value is "yes" if not defined.
The following SQL statement can set this parameter (if it does not exist):
insert into tb_global_setting values ('general', 'EnableSensitiveInfoMaskInComplianceMatchedContent', 'no', 'imss.ini', '');
After inserting this parameter, the command "S99IMSS restart" should be executed.
The logs would then show the following: