BrightCloud Web Filtering Architecture

The architecture used by BrightCloud to enable the integration of web filtering into a variety of OEM solutions benefits from ease of use and robustness. The key elements of the architecture are depicted in the diagram at the bottom of this page.

BrightCloud Agent

On the appliance is the BrightCloud Agent, which handles the day to day interaction with the BrightCloud Services, as well as administrative items such as device initiation and licensing. BrightCloud provides reference models for various implementations of the BrightCloud Agent, but the OEM designs the type of agent appropriate for their device, including their method for directory integration, policy administration, and reporting.

BCAP Protocol

The hosted BrightCloud Web Filtering Services are accessed by an OEM's solution via the BrightCloud Application Protocol (BCAP), a protocol very similar to ICAP, although it has been enhanced to support a broader type of XML over HTTP.

BrightCloud Web Filtering Services

The BrightCloud Web Filtering Services interact with the BrightCloud Agent to field category requests for uncached URLs, as well as providing real time updates for key security categories such as phishing and spyware. These services also enable device initiation, conduct real time URL classification where necessary, and provide a strong feedback mechanism of URLs visited to ensure that the BrightCloud Master Database is as up to date with end user browsing habits as possible.

In summary, the BrightCloud Web Filtering Services provide OEMs with a robust, scalable, and easy to deploy means for enriching the feature set of their security solutions for their end customers.