This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies. For details on cookie usage on our site, read our Privacy Policy
Thanks for the reply, Jay.
I'd like to add that users in-house/local are able to access the website without issue. The rule associated with in-house user access utilizes the same URL filtering profile as the rule that is utilized for the VPN users (except the VPN users are given the Suspected Credential... message). It is as if there's something beyond the the Actions|Profile Setting in the VPN rule that's overriding everything.
Another thing I noticed in the URL Filtering log is that "credential detected" is "no" and source user is blank for entries in which there is successful interaction with the website by in-house/local users. For VPN users, "credential detected" is "yes" and "source user" is occupied by the full username.
Thanks!
... View more
Hi!
Users connecting to our network via VPN receive "Suspected Credential Phishing Detected" when attempting to log into our in-house equipment reservation webpage. The URL filtering log indicates a blocked URL action on category "government". I've tried to adjust the group profile item in the associated rule for the "government" category from "block" to "continue" or "allow" but it doesn't seem to matter.
Any insight is welcome!
Thanks!
... View more