Gateway Cleanup of Data
The complete data of UserCheck incidents are held in quarantine on the DLP Gateway. Thus, if an email is caught, and it contains a large attachment, it takes up the necessary space on the Security Gateway Dedicated Check Point server that runs Check Point software to inspect traffic and enforce Security Policies for connected network resources. until the incident is handled or expires.
Gateway Cleanup of Expired Data
The DLP Gateway automatically cleans itself of expired incident data. Incident data that is held for the backend:expiration:db
number of days gets deleted.
Changing How Often and When the Gateway Checks for Data to Delete
-
On the DLP Gateway, open the $FWDIR/conf/mail_security_config file.
-
Find the expiration interval parameter:
-
Change the value of
expiration_interval
(minutes), to have the Security Gateway search for expired data on a different interval. The default is 1440 minutes, which is one day. -
Change the value of
expiration_execution_time
(24 hour clock), to change the time of day that the Security Gateway is cleaned. Be default, this is 3:45 AM, to ensure that Security Gateway maintenance does affect performance during usual working hours. -
Save mail_security_config and install the policy on the DLP Gateway.
Gateway Cleanup of All Captured Data
DLP automatically cleans its Security Gateway periodically of temporary files, to make sure that disk use does not unduly build over time. But sometimes unnecessary files are left on the disk.
You can customize the cleanup with these configuration files:
-
$FWDIR/conf/mail_security_config
-
$DLPDIR/config/dlp_cleanup_files_list.conf
|
Important - It is not recommended to de-activate the cleanup. If you must do so, set the value of |

scan
[ CHECK_DB
| -
] path mask scale age
|
Best Practice - Contents of this file explain more options, such as how to use macros for file age. It is recommended that you read the file comments before changing anything here. |
The default age values of scan commands in the file are macros that pull values from mail_security_config. You can use numeric values instead of macros.