<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Suspected Credential Phishing Detected in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/suspected-credential-phishing-detected/m-p/518159#M107499</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/228820"&gt;@BrianMacha&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can you verify the category of your in-house website? I would go to&amp;nbsp;Monitor -&amp;gt; Logs -&amp;gt; URL Filtering and find the traffic with the destination being the in-house website. Verify that the "credential theft detected" is set to yes and the category that is associated with it. Once the category is verified, you can go into the url filtering profile applied to your policy and set credential theft detection to not block the category associated with your in-house website.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If that doesn't work,&amp;nbsp; you can enter the domain into a whitelist. Whitelisting the site will bypass URL-filtering thus not being checked for credentials.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;LI-WRAPPER&gt;&lt;/LI-WRAPPER&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 17 Oct 2022 20:14:08 GMT</pubDate>
    <dc:creator>JayGolf</dc:creator>
    <dc:date>2022-10-17T20:14:08Z</dc:date>
    <item>
      <title>Suspected Credential Phishing Detected</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/suspected-credential-phishing-detected/m-p/518138#M107496</link>
      <description>&lt;P&gt;Hi!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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".&amp;nbsp; &amp;nbsp;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.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any insight is welcome!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks!&amp;nbsp;&lt;/P&gt;
&lt;H1&gt;&amp;nbsp;&lt;/H1&gt;</description>
      <pubDate>Mon, 17 Oct 2022 18:51:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/suspected-credential-phishing-detected/m-p/518138#M107496</guid>
      <dc:creator>BrianMacha</dc:creator>
      <dc:date>2022-10-17T18:51:05Z</dc:date>
    </item>
    <item>
      <title>Re: Suspected Credential Phishing Detected</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/suspected-credential-phishing-detected/m-p/518159#M107499</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/228820"&gt;@BrianMacha&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can you verify the category of your in-house website? I would go to&amp;nbsp;Monitor -&amp;gt; Logs -&amp;gt; URL Filtering and find the traffic with the destination being the in-house website. Verify that the "credential theft detected" is set to yes and the category that is associated with it. Once the category is verified, you can go into the url filtering profile applied to your policy and set credential theft detection to not block the category associated with your in-house website.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If that doesn't work,&amp;nbsp; you can enter the domain into a whitelist. Whitelisting the site will bypass URL-filtering thus not being checked for credentials.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;LI-WRAPPER&gt;&lt;/LI-WRAPPER&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 17 Oct 2022 20:14:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/suspected-credential-phishing-detected/m-p/518159#M107499</guid>
      <dc:creator>JayGolf</dc:creator>
      <dc:date>2022-10-17T20:14:08Z</dc:date>
    </item>
    <item>
      <title>Re: Suspected Credential Phishing Detected</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/suspected-credential-phishing-detected/m-p/518170#M107502</link>
      <description>&lt;P&gt;Thanks for the reply, Jay.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'd like to add that users in-house/local are able to access the website without issue.&amp;nbsp; 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).&amp;nbsp; It is as if there's something beyond the the Actions|Profile Setting in the VPN rule that's overriding everything.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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.&amp;nbsp; For VPN users, "credential detected" is "yes" and "source user" is occupied by the full username.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 17 Oct 2022 21:07:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/suspected-credential-phishing-detected/m-p/518170#M107502</guid>
      <dc:creator>BrianMacha</dc:creator>
      <dc:date>2022-10-17T21:07:33Z</dc:date>
    </item>
    <item>
      <title>Re: Suspected Credential Phishing Detected</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/suspected-credential-phishing-detected/m-p/518259#M107531</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;If the website is internal to your company, eg inside your network. Do Not perform URL filtering.&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Tue, 18 Oct 2022 20:54:11 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/suspected-credential-phishing-detected/m-p/518259#M107531</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2022-10-18T20:54:11Z</dc:date>
    </item>
    <item>
      <title>Re: Suspected Credential Phishing Detected</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/suspected-credential-phishing-detected/m-p/518359#M107547</link>
      <description>&lt;P&gt;I ended up whitelisting the site in the URL filtering profile.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for the help!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-Brian M.&lt;/P&gt;</description>
      <pubDate>Wed, 19 Oct 2022 13:33:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/suspected-credential-phishing-detected/m-p/518359#M107547</guid>
      <dc:creator>BrianMacha</dc:creator>
      <dc:date>2022-10-19T13:33:57Z</dc:date>
    </item>
  </channel>
</rss>

