Configuring the DLP database

To configure the connection to the DLP database:

1. In the Management Console tree, select the DLP Module settings node.
2. In the DLP database configuration section, define the following settings:
   • SQL server address and instance. SQL server address in the following format: <SQL server name>\<instance>. The SQL server can be deployed on one of the Security Servers or on a dedicated computer on the corporate LAN.
   • Database name. The name of the DLP database that exists on the specified SQL server or a new DLP database.
   • Additional connection parameters. Additional settings for connecting the database to the server. For a description of the settings for connecting the database to a server, please refer to the Microsoft website via the following link: connection string settings. Optional field. Example: Connection Timeout=30;Integrated Security=SSPI;MultiSubnetFailover=true.

   Redundant partner server. The redundant partner server address in the format <SQL server name>\<instance> is read-only. The field displays the value that is received from the SQL server and that is used only by the SQL server with database mirroring (Failover).

3. Click Save to save the changes.

   A confirmation window opens with a description of the actions that the application plans to implement.

4. Click OK in the confirmation window.

   If the specified database exists, the application connects to it. Upon establishing a connection, the application checks the structure of the database and, if necessary, creates the missing tables. The structure of existing tables is not checked.

   If the specified database is missing, the application creates a new database with the specified name.

   To be able to successfully create a database and missing tables, your account must have the required permissions on the specified SQL server, presented in the table of privileges.

After successfully saving the changes made, the application starts using the database with the specified parameters as a DLP database. The application starts saving information about incidents, categories, and policies in this database.

When switching to a new DLP database, consider the following specifics:

• Incidents generated in the old DLP database remain in this database. Incidents are not copied to the new DLP database.
• Categories are not copied from the old DLP database to the new one. If the configured categories are missing in the new DLP database, any policies created on the basis of such categories are deleted.
• It takes 15 minutes to migrate to the new DLP database. During this time, some of the incidents that are generated may be saved in the old DLP database.

If your account does not have the permissions required to create the database and tables, the new DLP database can be created in advance by an employee with appropriate permissions, such as the database administrator. You can retrieve a ready script for creating the DLP database from the application and make it available to the relevant staff member to execute it.

To get the DLP database creation script,

Click the Get DLP database creation script link.

The script opens in the window of the Notepad text editor.

Page top