<?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 Corporate Credential Submission / Phishing protection in PANOS 8.0 in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/corporate-credential-submission-phishing-protection-in-panos-8-0/m-p/142333#M48525</link>
    <description>&lt;P&gt;Good Morning,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm lucky enough to work with a few early adopters and have PANOS8.0 running in several production locations on VM and 3000 series appliances.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So far, business as usual with the "old" feature set....&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've now setup Credential Protection on two of these sites, using the RODC method to spot username/password combos, rather than just username. The username only method seemed a little too wide a net to cast.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyway, it's up and running, but I was hoping some others may be running it too so we could compare notes?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My initial findings..&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1) Obviously needs SSL inspection setup and working for all the URL categories you want to inspect for credentials&lt;/P&gt;&lt;P&gt;2) RODC's aren't that complex, but read the notes about groups allowed to sync to the RODC, if they dont sync, it wont work!&lt;/P&gt;&lt;P&gt;3) RODC's seem limited to 1500 sets of cached credentials? Interested in thoughts on how to scale out with domains with many 1000's of users&lt;/P&gt;&lt;P&gt;4) For my testing I used a domain account and typed those credentials into a variety of locations, facebook, linkedin, salesforce, google, outlook.com, several random websites.&lt;/P&gt;&lt;P&gt;5) Every single one was captured by the firewall&lt;/P&gt;&lt;P&gt;6) The continue page seems to use https://IPADDRESSOFWEBSITE:PORT/SOMEOTHERSTUFF, which causes an untrusted certificate error for the user&lt;/P&gt;&lt;P&gt;7) Block and Alert work fine&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":smiling_face_with_sunglasses:"&gt;😎&lt;/span&gt; in production (alert only) Had some false positives for google ads and some referal tracking links, checked with users who can be trusted and they are defintely NOT reusing corporate credetials.&lt;/P&gt;&lt;P&gt;9) Also had some false negatives in testing with the rest of the IT team, intentionally entering domain credentials into website and it doesnt catch them.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So in summary, looks VERY promising, but perhaps a few rough edges or some best practice guidance for reducing false positives would be very useful. I dont feel comfortable putting into full production with block pages just yet, but it is providing some useful information.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Over to you community!&lt;/P&gt;</description>
    <pubDate>Fri, 10 Feb 2017 10:57:03 GMT</pubDate>
    <dc:creator>Dpeters1</dc:creator>
    <dc:date>2017-02-10T10:57:03Z</dc:date>
    <item>
      <title>Corporate Credential Submission / Phishing protection in PANOS 8.0</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/corporate-credential-submission-phishing-protection-in-panos-8-0/m-p/142333#M48525</link>
      <description>&lt;P&gt;Good Morning,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm lucky enough to work with a few early adopters and have PANOS8.0 running in several production locations on VM and 3000 series appliances.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So far, business as usual with the "old" feature set....&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've now setup Credential Protection on two of these sites, using the RODC method to spot username/password combos, rather than just username. The username only method seemed a little too wide a net to cast.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyway, it's up and running, but I was hoping some others may be running it too so we could compare notes?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My initial findings..&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1) Obviously needs SSL inspection setup and working for all the URL categories you want to inspect for credentials&lt;/P&gt;&lt;P&gt;2) RODC's aren't that complex, but read the notes about groups allowed to sync to the RODC, if they dont sync, it wont work!&lt;/P&gt;&lt;P&gt;3) RODC's seem limited to 1500 sets of cached credentials? Interested in thoughts on how to scale out with domains with many 1000's of users&lt;/P&gt;&lt;P&gt;4) For my testing I used a domain account and typed those credentials into a variety of locations, facebook, linkedin, salesforce, google, outlook.com, several random websites.&lt;/P&gt;&lt;P&gt;5) Every single one was captured by the firewall&lt;/P&gt;&lt;P&gt;6) The continue page seems to use https://IPADDRESSOFWEBSITE:PORT/SOMEOTHERSTUFF, which causes an untrusted certificate error for the user&lt;/P&gt;&lt;P&gt;7) Block and Alert work fine&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":smiling_face_with_sunglasses:"&gt;😎&lt;/span&gt; in production (alert only) Had some false positives for google ads and some referal tracking links, checked with users who can be trusted and they are defintely NOT reusing corporate credetials.&lt;/P&gt;&lt;P&gt;9) Also had some false negatives in testing with the rest of the IT team, intentionally entering domain credentials into website and it doesnt catch them.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So in summary, looks VERY promising, but perhaps a few rough edges or some best practice guidance for reducing false positives would be very useful. I dont feel comfortable putting into full production with block pages just yet, but it is providing some useful information.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Over to you community!&lt;/P&gt;</description>
      <pubDate>Fri, 10 Feb 2017 10:57:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/corporate-credential-submission-phishing-protection-in-panos-8-0/m-p/142333#M48525</guid>
      <dc:creator>Dpeters1</dc:creator>
      <dc:date>2017-02-10T10:57:03Z</dc:date>
    </item>
    <item>
      <title>Re: Corporate Credential Submission / Phishing protection in PANOS 8.0</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/corporate-credential-submission-phishing-protection-in-panos-8-0/m-p/142413#M48539</link>
      <description>&lt;P&gt;Good rundown!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We've got a lab 200 that I hope to be standing up in the next week. &amp;nbsp;So I am probably 2 weeks out before I have anything constructive to add.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Feb 2017 17:05:34 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/corporate-credential-submission-phishing-protection-in-panos-8-0/m-p/142413#M48539</guid>
      <dc:creator>Brandon_Wertz</dc:creator>
      <dc:date>2017-02-10T17:05:34Z</dc:date>
    </item>
  </channel>
</rss>

