Choose from several options for complete web, email and data security.
Evaluate Websense products by watching demos and installing evaluation software.
Learn how Websense solutions help keep our customer safe, secure and productive
Get information on product updates, support resources and more.
Get the most out of support in five simple steps.
Find tools and assets to help sell Websense solutions.
Come work for the global leader in unified information security.
We have an office of say 80 people remotely. We want to bring in their own DSL for web traffic. What is the most cost effective way to send web sense data back to the data center across the WAN yet allow the clients to use the additional web pipe. Currently we back haul all data across the costly and restrictive MPLS.
An entirely separate appliance was recommended so far- very expensive.
Can you give us an idea what equipment you have in the remote sites (routers, switches and server equipment and virtual infrastructure)? That will dictate what we and your peers can recommend.
JACOB SLOAN, CCNA, WCSE
Gig enterprise switches and routers at the remote site. Probably a small cisco firewall would be brought in for the DSL. Websense is running on physical servers.
With that generic idea, you probably can stand up a second policy server, filter service, etc on a system in that network, and then use the same Policy Broker.
ok that jives with what I found on my own. Are there licenses associates with that distributed format? I think we own 1000 seats, so do we need to additionally re-license the 80 folks that would run through this server?
I'm certainly price sensitive -especially when we already own the seats.
You can have a support case split your key so you use different keys for the differnet policy servers.