<?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 Field extractor for Firepower syslogs in Splunk Enterprise Security</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Field-extractor-for-Firepower-syslogs/m-p/509558#M9018</link>
    <description>&lt;P&gt;Hi All, I am working on Cisco Firepower field extraction.&lt;/P&gt;&lt;P&gt;I got 2 different patterns mentioned below:&lt;/P&gt;&lt;P&gt;1. For the below one, I am getting action field either "Allow" or "Block" and I am able to extract that.&lt;/P&gt;&lt;P&gt;Jul 16 2020 17:47:00 %FTD-1-430002: AccessControlRuleAction: Allow, SrcIP: 10.216.6.64, DstIP: 40.126.2.50, SrcPort: 57033, DstPort: 443, Protocol: tcp, IngressZone: in, EgressZone: out, ACPolicy: Azure-Policy-old, AccessControlRuleName: ASADmz_Internal_Access, Prefilter Policy: Allow_new, User: No Authentication Required, InitiatorPackets: 2, ResponderPackets: 1, InitiatorBytes: 120, ResponderBytes: 66, NAPPolicy: Unknown&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. How can I write single extractor for action field to cover below type of logs? Field action would be unknown for below pattern I believe.&lt;/P&gt;&lt;P&gt;Jul 16 17:47:00 UTC: %FTD-session-6-305011: Built dynamic TCP translation from Inside:10.216.6.64/57035 to Outside:10.216.3.10/57035&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The same issue I am facing with ASA firewall logs also.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any direction would be highly appreciated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Tejas&lt;/P&gt;</description>
    <pubDate>Thu, 16 Jul 2020 17:59:46 GMT</pubDate>
    <dc:creator>tbavarva</dc:creator>
    <dc:date>2020-07-16T17:59:46Z</dc:date>
    <item>
      <title>Field extractor for Firepower syslogs</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Field-extractor-for-Firepower-syslogs/m-p/509558#M9018</link>
      <description>&lt;P&gt;Hi All, I am working on Cisco Firepower field extraction.&lt;/P&gt;&lt;P&gt;I got 2 different patterns mentioned below:&lt;/P&gt;&lt;P&gt;1. For the below one, I am getting action field either "Allow" or "Block" and I am able to extract that.&lt;/P&gt;&lt;P&gt;Jul 16 2020 17:47:00 %FTD-1-430002: AccessControlRuleAction: Allow, SrcIP: 10.216.6.64, DstIP: 40.126.2.50, SrcPort: 57033, DstPort: 443, Protocol: tcp, IngressZone: in, EgressZone: out, ACPolicy: Azure-Policy-old, AccessControlRuleName: ASADmz_Internal_Access, Prefilter Policy: Allow_new, User: No Authentication Required, InitiatorPackets: 2, ResponderPackets: 1, InitiatorBytes: 120, ResponderBytes: 66, NAPPolicy: Unknown&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. How can I write single extractor for action field to cover below type of logs? Field action would be unknown for below pattern I believe.&lt;/P&gt;&lt;P&gt;Jul 16 17:47:00 UTC: %FTD-session-6-305011: Built dynamic TCP translation from Inside:10.216.6.64/57035 to Outside:10.216.3.10/57035&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The same issue I am facing with ASA firewall logs also.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any direction would be highly appreciated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Tejas&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jul 2020 17:59:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Field-extractor-for-Firepower-syslogs/m-p/509558#M9018</guid>
      <dc:creator>tbavarva</dc:creator>
      <dc:date>2020-07-16T17:59:46Z</dc:date>
    </item>
    <item>
      <title>Re: Field extractor for Firepower syslogs</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Field-extractor-for-Firepower-syslogs/m-p/509598#M9022</link>
      <description>Have you looked the available apps in splunkbase? They may save you a lot of effort. See &lt;A href="https://splunkbase.splunk.com/apps/#/search/firepower/" target="_blank"&gt;https://splunkbase.splunk.com/apps/#/search/firepower/&lt;/A&gt;</description>
      <pubDate>Thu, 16 Jul 2020 20:34:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Field-extractor-for-Firepower-syslogs/m-p/509598#M9022</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2020-07-16T20:34:28Z</dc:date>
    </item>
    <item>
      <title>Re: Field extractor for Firepower syslogs</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Field-extractor-for-Firepower-syslogs/m-p/509645#M9024</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/213957"&gt;@richgalloway&lt;/a&gt;&amp;nbsp; Thanks for your prompt response.&lt;/P&gt;&lt;P&gt;Sorry I missed to mention that we have latest version of Splunk i.e. 8.0 both SH and HF.&lt;/P&gt;&lt;P&gt;So none of these apps or add-on are compatible and cisco estreamer for Splunk app is tested on unix platform. We have installed HF on Windows server.&lt;/P&gt;&lt;P&gt;Can you please suggest some other solution?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Tejas&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 17 Jul 2020 05:48:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Field-extractor-for-Firepower-syslogs/m-p/509645#M9024</guid>
      <dc:creator>tbavarva</dc:creator>
      <dc:date>2020-07-17T05:48:53Z</dc:date>
    </item>
    <item>
      <title>Re: Field extractor for Firepower syslogs</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Field-extractor-for-Firepower-syslogs/m-p/509687#M9025</link>
      <description>That splunkbase doesn't say an app is compatible with a certain version does not mean that app is not compatible with that version. It's possible the app simply has not been tested. Compatibility with Splunk 8 usually hinges on which Python version the app uses. If the app does not use any Python then compatibility should not be a problem.&lt;BR /&gt;You can use one of the apps as a guide for building your own app.</description>
      <pubDate>Fri, 17 Jul 2020 12:44:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Field-extractor-for-Firepower-syslogs/m-p/509687#M9025</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2020-07-17T12:44:06Z</dc:date>
    </item>
  </channel>
</rss>

