By Stephen Spalluto
Now more than ever it is more difficult to provide end-users with the resources they need and yet comply with organizational acceptable use policy(-ies) and maintain network integrity and security. Many school districts that have used BorderManager and third party filtering solutions, such as SurfControl, for a number of years are used to end-user complaints of being blocked out of sites that have legitimate organizational benefits. In the past, an Admin could open NWAdmin, drill down to the user, the logs and find out what rule number was triggering the block.
Since the release of BM 3.8 and subsequent BM 3.9, the use of NWAdmin has been lost and with it, so has the ability to determine what rule was triggered when a user requested that a particular site be open for access.
After searching user groups for many months, I decided it was time to contact Novell Engineers to see how to determine what rule was triggered. The engineer I spoke with confirmed my findings and reported CSAudit no longer handles the logging of the rules triggered so there is no longer a direct way to determine what rule is triggering an event…or is there?
Here’s what I’ve discovered as a solution that can be as quick and easy as the old NWAdmin way. Our District uses BM 3.9 and SurfControl from WebSense with iManager as the Admin utility.
Here’s how it works when you get that call to release a site and it’s not obvious what rule would be triggering the event.
One of those two resources should reveal the source of the denial. If not, open your log file and see if there are redirects that are denying the access rather than the site they are trying to access. Follow the same procedure as in Steps 6 and 7.
Other third party filtering solutions may have similar capabilities to search their lists. See their documentation for availability.
Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment. It just worked for at least one person, and perhaps it will be useful for you too. Be sure to test in a non-production environment.