<?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: Splunk Add-on for Cisco ASA - Warning: Need to modify the &amp;quot;transforms.conf&amp;quot; file if you have someone with &amp;quot;Deny&amp;quot; in their name or e-mail. in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Cisco-ASA-Warning-Need-to-modify-the-quot/m-p/500866#M61653</link>
    <description>&lt;P&gt;To resolve this I have found that throwing a &lt;CODE&gt;\s&lt;/CODE&gt; after the &lt;CODE&gt;Deny&lt;/CODE&gt; in the two stanzas listed above, will process the fields correctly for those people that have the string as part of their name or email. So &lt;CODE&gt;|Deny\s|&lt;/CODE&gt; will fix it. The corrected regex is below. Be sure not to make the change under the default folder &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;REGEX=([Aa]uthentication [Ss]ucceeded|[Aa]uthorization [Pp]ermitted|authentication Successful|passed authentication|Login permitted|Authentication failed|Authorization denied|Can't find authorization|Authentication Failed|authentication Rejected|credentials rejected|Authentication:Dropping|login warning|login failed|failed authentication|[Cc]onnection denied|Deny inbound|Deny\s|Terminating|action locally|Unable to Pre-allocate|denied\s[tcp|udp|icmp]+|access denied|access requested|access permitted|limit exceeded|Dropped|Dropping|[B|b]uilt|[pP]ermitted|whitelisted|Pre-allocated|Rebuilt|redirected|discarded)
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Tue, 04 Feb 2020 17:31:58 GMT</pubDate>
    <dc:creator>cchimento</dc:creator>
    <dc:date>2020-02-04T17:31:58Z</dc:date>
    <item>
      <title>Splunk Add-on for Cisco ASA - Warning: Need to modify the "transforms.conf" file if you have someone with "Deny" in their name or e-mail.</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Cisco-ASA-Warning-Need-to-modify-the-quot/m-p/500865#M61652</link>
      <description>&lt;P&gt;Hello - I come with a warning from an issue I just had recently and resolved. Hopefully this will get some visibility and possibly fixed in a later release of the add-on. This was tested with the latest version of this add-on (ver 3.4.0) and in reference to the log entry:  &lt;CODE&gt;%ASA-5-746012: user-identity: Add IP-User mapping IP Address - domain_name \user_name result - reason&lt;/CODE&gt; &lt;/P&gt;

&lt;P&gt;If you are using this Add-On - please make a note to check if you have anyone in your org with the string "Deny" (Capital D) as part of their name or e-mail address. This would likely be someone named Denys or similar. As well as part of a last name, likely the leading characters. &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;ex:  
Cisco_ASA_user = LOCAL\Denys.Somelastname@yourdomain.com
Cisco_ASA_user = LOCAL\Bob.Denyan@yourdomain.com 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I have found that due to two weak regex entries in the  &lt;STRONG&gt;transforms.conf&lt;/STRONG&gt; file for the add-on, it will look for a "Deny" string (capital D) in the log entry from your ASAs to populate the &lt;CODE&gt;[cisco_asa_vendor_action]&lt;/CODE&gt; and &lt;CODE&gt;[vendor_action]&lt;/CODE&gt; fields. This results in a deny vendor action even when the actual result reason shows succeeded; per the logs.  &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[cisco_asa_vendor_action]
REGEX=([Aa]uthentication [Ss]ucceeded|[Aa]uthorization [Pp]ermitted|authentication Successful|passed authentication|Login permitted|Authentication failed|Authorization denied|Can't find authorization|Authentication Failed|authentication Rejected|credentials rejected|Authentication:Dropping|login warning|login failed|failed authentication|[Cc]onnection denied|Deny inbound|Deny|Terminating|action locally|Unable to Pre-allocate|denied\s[tcp|udp|icmp]+|access denied|access requested|access permitted|limit exceeded|Dropped|Dropping|[B|b]uilt|[pP]ermitted|whitelisted|Pre-allocated|Rebuilt|redirected|discarded)
FORMAT=vendor_action::$1

[cisco_asa_vendor_action_for_performance]
REGEX=([Aa]uthentication [Ss]ucceeded|[Aa]uthorization [Pp]ermitted|authentication Successful|passed authentication|Login permitted|Authentication failed|Authorization denied|Can't find authorization|Authentication Failed|authentication Rejected|credentials rejected|Authentication:Dropping|login warning|login failed|failed authentication|[Cc]onnection denied|Deny inbound|Deny|Terminating|action locally|Unable to Pre-allocate|denied\s[tcp|udp|icmp]+|access denied|access requested|access permitted|limit exceeded|Dropped|Dropping|[B|b]uilt|[pP]ermitted|whitelisted|Pre-allocated|Rebuilt|redirected|discarded)
FORMAT=Cisco_ASA_vendor_action::$1
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;You can see in the regex that it is looking through OR &lt;CODE&gt;|&lt;/CODE&gt; statements to find &lt;CODE&gt;Deny&lt;/CODE&gt;.  &lt;/P&gt;

&lt;P&gt;To resolve this I have found that throwing a &lt;CODE&gt;\s&lt;/CODE&gt; after the &lt;CODE&gt;Deny&lt;/CODE&gt; in the two stanzas listed above, will process the fields correctly for those people that have the string as part of their name or email.  So &lt;CODE&gt;|Deny\s|&lt;/CODE&gt; will fix it. The corrected regex is below. Be sure not to make the change under the default folder &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;REGEX=([Aa]uthentication [Ss]ucceeded|[Aa]uthorization [Pp]ermitted|authentication Successful|passed authentication|Login permitted|Authentication failed|Authorization denied|Can't find authorization|Authentication Failed|authentication Rejected|credentials rejected|Authentication:Dropping|login warning|login failed|failed authentication|[Cc]onnection denied|Deny inbound|Deny\s|Terminating|action locally|Unable to Pre-allocate|denied\s[tcp|udp|icmp]+|access denied|access requested|access permitted|limit exceeded|Dropped|Dropping|[B|b]uilt|[pP]ermitted|whitelisted|Pre-allocated|Rebuilt|redirected|discarded)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Hope this helps!&lt;BR /&gt;
-Chris&lt;/P&gt;</description>
      <pubDate>Tue, 04 Feb 2020 17:30:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Cisco-ASA-Warning-Need-to-modify-the-quot/m-p/500865#M61652</guid>
      <dc:creator>cchimento</dc:creator>
      <dc:date>2020-02-04T17:30:08Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for Cisco ASA - Warning: Need to modify the "transforms.conf" file if you have someone with "Deny" in their name or e-mail.</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Cisco-ASA-Warning-Need-to-modify-the-quot/m-p/500866#M61653</link>
      <description>&lt;P&gt;To resolve this I have found that throwing a &lt;CODE&gt;\s&lt;/CODE&gt; after the &lt;CODE&gt;Deny&lt;/CODE&gt; in the two stanzas listed above, will process the fields correctly for those people that have the string as part of their name or email. So &lt;CODE&gt;|Deny\s|&lt;/CODE&gt; will fix it. The corrected regex is below. Be sure not to make the change under the default folder &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;REGEX=([Aa]uthentication [Ss]ucceeded|[Aa]uthorization [Pp]ermitted|authentication Successful|passed authentication|Login permitted|Authentication failed|Authorization denied|Can't find authorization|Authentication Failed|authentication Rejected|credentials rejected|Authentication:Dropping|login warning|login failed|failed authentication|[Cc]onnection denied|Deny inbound|Deny\s|Terminating|action locally|Unable to Pre-allocate|denied\s[tcp|udp|icmp]+|access denied|access requested|access permitted|limit exceeded|Dropped|Dropping|[B|b]uilt|[pP]ermitted|whitelisted|Pre-allocated|Rebuilt|redirected|discarded)
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 04 Feb 2020 17:31:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Cisco-ASA-Warning-Need-to-modify-the-quot/m-p/500866#M61653</guid>
      <dc:creator>cchimento</dc:creator>
      <dc:date>2020-02-04T17:31:58Z</dc:date>
    </item>
  </channel>
</rss>

