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 a situation where we need to filter traffic originating from 192.168.0.0/24, but we do not want to log it as this subnet is our "guest" network.
While we need to filter the traffic (enforce our policies), we do not want or need to run reports on this subnet.
How would I accomplish this?
what integration are you using? If you filter the traffic its not trivial not to log it. Why don't you want to log it?
Thanks for your question/followup. It is the "universal" integration.
The reason that we don't want to log this traffic is that since this is the "guest" subnet, we do not need or care about the individual users who use it. Plus, we only see their IP addresses and not their details since these are all personally owned laptops.
That said, we are logging way too much info about these users, and that is consuming resources that are needed for logging users that we do need to run reports on.
the short answer of this issue is: You can't. If you filter it, it's going to be logged.
There are ways around it, but these are require more resources (additional firewalls, and another policy server/filter service for that public lan).
There is no easy software only way of ignoring traffic specifically from one network range.
JACOB SLOAN, CCNA, WCSE