Websense Version 7 has introduced a number of benefits over the previous release, but crucially there is an underlying architecture change that customers need to be aware of. In version 6, Websense configuration was managed by the policy server, which stored the configuration in a flat xml file. This is still true with version 7, however the core configuration is now stored within a policy database, controlled by the new policy broker service. This allows for multiple policy servers to run and filter web traffic with the same configuration/policy. Additional policy servers are then updated from the policy broker service, via the individual policy server that has received configuration changes.
So updates happen in this order:
- Change made on Websense Manager.
- Configuration modified within the local Websense policy server
- Policy Server updates the configuration within the policy broker/database.
- Configuration in other policy servers are then updated from the policy broker service.
In short you no longer need to manually push out configuration changes between multiple Websense servers. Additionally even if the policy broker service goes down, policy servers will continue to filter traffic. The idea is to allow Websense to more easily scale for contingency and fail over proxy servers or clustered solutions. There is also a backup tool in Version 7 for ensuring you can restore your Websense configuration much more easily.
Please note the architecture and feature enhancements within Websense have resulted in a notable change in hardware specification required to operate Websense V7 (see next item below if you use Celestix web appliances).
Contact Foursys on 01223 810 910 or websense@foursys.co.uk if you want to discuss these Websense V7 changes in more detail and ask for our PDF briefing on "Websense V7 Architecture Changes".