Local database (LDB) configuration and persistence behavior on the EdgeSWG

Products

• ISG Proxy
• ProxySG Software - SGOS

Issue/Introduction

The Local Database (LDB) feature allows administrators to define custom URL categories for content filtering. This article describes the requirements for hosting the database file and explains how the appliance maintains filtering data across system restarts.

Environment

EdgeSWG

Resolution

A local database must be hosted on an external server; it cannot be stored locally on the EdgeSWG file system.

Hosting Requirements:

• Store the LDB text file on a web server (HTTP/HTTPS) or an FTP server.
• Management Center (MC): Many environments use MC to host the LDB file.
• The EdgeSWG must have network access to the host server's IP and port.

Behavior on Restart:

1. Persistence: The EdgeSWG stores the last successfully compiled version of the local database in its internal storage.
2. Appliance Reboot: Upon restart, the EdgeSWG immediately loads the stored, compiled version of the database so that policy enforcement begins without delay.
3. Synchronization: Once the network stack is active, the EdgeSWG initiates a connection to the configured URL to check for updates based on the Check for updates frequency (defaulting to 5 minutes).

Configuration Steps:

1. Create a text file with the following syntax: define category My_Custom_Category example.com training.broadcom.com end
2. Upload the file to an external server (e.g., http://####/ldb/custom.txt).
3. In the Management Console, navigate to Configuration > Content Filtering > Local Database.
4. Enter the URL of the text file.
5. Click Download Now and select View Download Status to confirm successful compilation.
6. Enable the database under Configuration > Content Filtering > General > Use Local Database.

Additional Information

• Hosting a local database on Management Center
• How-to set up a customized list of content filtering URLs

For assistance with connectivity issues, see Contact Support.