<?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: Determining failed administrator interface logons from syslog in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/determining-failed-administrator-interface-logons-from-syslog/m-p/198173#M58844</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/82307"&gt;@Jimkoo&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;They should look&amp;nbsp;&lt;EM&gt;slightly&lt;/EM&gt; different depending on how you auth your admins. Part of the syslog message should show which auth profile was used in the 'auth-success' event, which you could utilize to filter out your GP logins from your admin logins. If you are using local auth for everything then I believe you're right and everything will look exactly the same.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Another thing to look at is not monitoring the auth events. A general event will actually get taked that reads similar to "User bpry logged in via CLI from 10.191.16.61" which would let you know how the admin logged in and who it was.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 01 Feb 2018 12:53:17 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2018-02-01T12:53:17Z</dc:date>
    <item>
      <title>Determining failed administrator interface logons from syslog</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/determining-failed-administrator-interface-logons-from-syslog/m-p/198161#M58842</link>
      <description>Hello!&lt;BR /&gt;&lt;BR /&gt;I'm running into an issue. I would like to record failed logons to the administrator interface via syslog but the log format and contents of the logs appear to be exactly the same as those when a user performs a failed login to GlobalProtect Client VPN. Therefore I am getting a bunch of false positives.&lt;BR /&gt;&lt;BR /&gt;Has anyone had any luck with this?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 01 Feb 2018 11:52:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/determining-failed-administrator-interface-logons-from-syslog/m-p/198161#M58842</guid>
      <dc:creator>Jimkoo</dc:creator>
      <dc:date>2018-02-01T11:52:16Z</dc:date>
    </item>
    <item>
      <title>Re: Determining failed administrator interface logons from syslog</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/determining-failed-administrator-interface-logons-from-syslog/m-p/198173#M58844</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/82307"&gt;@Jimkoo&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;They should look&amp;nbsp;&lt;EM&gt;slightly&lt;/EM&gt; different depending on how you auth your admins. Part of the syslog message should show which auth profile was used in the 'auth-success' event, which you could utilize to filter out your GP logins from your admin logins. If you are using local auth for everything then I believe you're right and everything will look exactly the same.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Another thing to look at is not monitoring the auth events. A general event will actually get taked that reads similar to "User bpry logged in via CLI from 10.191.16.61" which would let you know how the admin logged in and who it was.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Feb 2018 12:53:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/determining-failed-administrator-interface-logons-from-syslog/m-p/198173#M58844</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2018-02-01T12:53:17Z</dc:date>
    </item>
  </channel>
</rss>

