<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.sophos.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Does anyone have a list of possible authentication failures UTM can generate?</title><link>https://community.sophos.com/utm-firewall/f/general-discussion/105576/does-anyone-have-a-list-of-possible-authentication-failures-utm-can-generate</link><description>Hi. 
 
 I am trying to use Humio to collect logs from my Sophos UTM 9 firewall. This works well except I have a wrinkle when looking at authentication failures. I can easily see authentication failures, as they are logged, however the reason for the failure</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Does anyone have a list of possible authentication failures UTM can generate?</title><link>https://community.sophos.com/thread/385271?ContentTypeID=1</link><pubDate>Wed, 03 Oct 2018 15:26:12 GMT</pubDate><guid isPermaLink="false">4be5eb7d-caa4-4ff5-8e60-8f9463545a35:9f079c1b-04e1-4ecf-839e-b5ed5c222106</guid><dc:creator>DouglasFoster</dc:creator><description>&lt;p&gt;My actual logic works like this:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Every line has a standard header, so I separate the header section from the message body.&lt;/li&gt;
&lt;li&gt;If the message body does not begin with &amp;quot;id=&amp;quot;, then I append the message body to the previous line.&lt;/li&gt;
&lt;li&gt;I parse all expected keyword=&amp;quot;value&amp;quot; tokens into database fields where fieldname=keyword and field contents = value.&lt;/li&gt;
&lt;li&gt;Any unparsed text is thrown into a database field labelled &amp;quot;Comments&amp;quot;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;With this arrangement, I am able to pick up the occurrences of &amp;quot;[WARN-070] Too many failed logins&amp;quot;, which appear on a continuation line.&lt;/p&gt;
&lt;p&gt;But...&lt;/p&gt;
&lt;p&gt;you wanted to pick up the id=&amp;quot;3006&amp;quot;&amp;nbsp;name=&amp;quot;OTP verification did not succeed, failing authentication.&amp;quot; entries, and they don&amp;#39;t fit my model.&amp;nbsp; They contain an &amp;quot;id=&amp;quot; clause, so they get their own database record.&amp;nbsp; Also, they come before the 3005 entry which contains the username.&lt;/p&gt;
&lt;p&gt;Solution:&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Give each row in the file a sequential number, then you can match using sequence numbers.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;First, find the OTP errors based on text match.&amp;nbsp;&lt;/li&gt;
&lt;li&gt;Then the immediately preceding sequence number should be the &amp;quot;3006-Trying&amp;quot; message.&amp;nbsp; This identifies the server.&amp;nbsp;&lt;/li&gt;
&lt;li&gt;Then the immediately following sequence number should be the id=&amp;quot;3005&amp;quot; entry (to get the username and source IP).&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Even in the context with multiple servers, I think the 3005 entry will always be the next sequence number, because after an explicit fail, it does not try any additional servers.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Does anyone have a list of possible authentication failures UTM can generate?</title><link>https://community.sophos.com/thread/385210?ContentTypeID=1</link><pubDate>Wed, 03 Oct 2018 02:29:27 GMT</pubDate><guid isPermaLink="false">4be5eb7d-caa4-4ff5-8e60-8f9463545a35:369bd9b5-a4f0-4b08-993f-3bfe84c574f2</guid><dc:creator>Daniel James1</dc:creator><description>&lt;p&gt;Hi.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thank you, I&amp;#39;ll take another look.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Does anyone have a list of possible authentication failures UTM can generate?</title><link>https://community.sophos.com/thread/385201?ContentTypeID=1</link><pubDate>Tue, 02 Oct 2018 20:46:31 GMT</pubDate><guid isPermaLink="false">4be5eb7d-caa4-4ff5-8e60-8f9463545a35:02e64979-76ff-403f-ab95-53122b3876f8</guid><dc:creator>DouglasFoster</dc:creator><description>&lt;p&gt;There really are not many ways to do a login incorrectly:&amp;nbsp; wrong username/password or wrong OTP.&lt;/p&gt;
&lt;p&gt;I have parsed the log files, and concluded that the rows with id=&amp;quot;3004 name=&amp;quot;Authentication successful&amp;quot; or id=&amp;quot;3005&amp;quot; name=&amp;quot;Authentication failed&amp;quot; are all that matter.&amp;nbsp; They gives you the IP, username, and timestamp.&amp;nbsp; &amp;nbsp;For successes, it gives you the type of authentication service that issued the approval.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>