Feature Requests

When someone submits a whitelisting request, the email is sent from [email protected] . Since I have my email configured to route to our help desk system, this triggers an automatic response with a ticket number and details. As a result, your system generates a new request and sends it back to us via [email protected] , creating an unnecessary loop. To resolve this, I suggest using a non-reply email address, such as [email protected] , for outgoing whitelisting requests. This would prevent help desk systems from automatically responding and creating a feedback loop.

The Blocked Page's Network Status should be a clickable button that displays the organizations it is being used on. We currently have to go through every single organization to verify if that org is using a particular block page which is tedious.

It would be great if you could have Multiple Bypass passwords per policy. That way the passwords isn't shared. Then you can also see when a user needed to use it.

The ability to create a custom block page that will only block by a specific category. Meaning that when you create the block page, you would have the ability to select an option that would display the category you wish to block it on rather than creating multiple polices with different block pages.

Update filter policy to allow a user to specify a web service url. The url will be called when a block or threat is logged. The call will be a POST to the url which included information such as time, deployment, fqdn, category. This will allow the user to create customized reporting or alerting based on real time threat data.