<?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 and Cisco Firepower Audit Logs in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-and-Cisco-Firepower-Audit-Logs/m-p/743731#M118149</link>
    <description>&lt;P&gt;Also remember that while Splunk can listen for syslogs this is not a recommended setup. It's relatively ok for a small lab deployment but in production you'd rather want to go for a separate syslog daemon either writing to local files for pick up by UF or sending to HEC input.&lt;/P&gt;</description>
    <pubDate>Mon, 07 Apr 2025 22:27:26 GMT</pubDate>
    <dc:creator>PickleRick</dc:creator>
    <dc:date>2025-04-07T22:27:26Z</dc:date>
    <item>
      <title>Splunk and Cisco Firepower Audit Logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-and-Cisco-Firepower-Audit-Logs/m-p/743693#M118130</link>
      <description>&lt;P&gt;Hello folks,&lt;/P&gt;&lt;P&gt;My organization is struggling with ingesting the Cisco Firepower audit (sys)logs into Splunk, we've been able to successfully ingest all the other sources. With the Firepowers only offering up 514udp which is unavailable according to Splunk, or a HEC configuration without tokens so Splunk is (would?) drop the events our option appear limited. Has anyone else come across this issue and solved it?&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2025-04-07 114755.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/38484iA026F45779F014B9/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Screenshot 2025-04-07 114755.png" alt="Screenshot 2025-04-07 114755.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2025-04-07 114809.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/38485iEBF7A04E929A634E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Screenshot 2025-04-07 114809.png" alt="Screenshot 2025-04-07 114809.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;  &lt;/P&gt;</description>
      <pubDate>Mon, 07 Apr 2025 15:53:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-and-Cisco-Firepower-Audit-Logs/m-p/743693#M118130</guid>
      <dc:creator>b17gunnr</dc:creator>
      <dc:date>2025-04-07T15:53:16Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk and Cisco Firepower Audit Logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-and-Cisco-Firepower-Audit-Logs/m-p/743694#M118131</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/308735"&gt;@b17gunnr&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The error "UDP port 514 is not available" typically means that Splunk is not able to listen to the port, which is typically for 1 of 2 reasons:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Another process is already listening to the port&lt;BR /&gt;Confirm that nothing is already using this port, this process will vary between different OS.&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;&lt;LI&gt;Splunk does not have permissions to listen to port 514.&lt;BR /&gt;To listen to ports &amp;lt;1024 the Splunk process may require additional permissions (&lt;EM&gt;CAP_NET_BIND_SERVICE)&amp;nbsp;&lt;/EM&gt;and/or could be affected by AppArmor / SELinux. This will also vary depending on OS.&amp;nbsp;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;For more information check out&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Data/Monitornetworkports" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Data/Monitornetworkports&amp;nbsp;&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, theres a previous Splunk answer which might help at&amp;nbsp;&lt;A href="https://community.splunk.com/t5/Getting-Data-In/how-to-listen-to-port-UDP-514-when-splunk-is-not-root/m-p/108169" target="_blank"&gt;https://community.splunk.com/t5/Getting-Data-In/how-to-listen-to-port-UDP-514-when-splunk-is-not-root/m-p/108169&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":glowing_star:"&gt;🌟&lt;/span&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Did this answer help you?&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;If so, please consider:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Adding karma to show it was useful&lt;/LI&gt;&lt;LI&gt;Marking it as the solution if it resolved your issue&lt;/LI&gt;&lt;LI&gt;Commenting if you need any clarification&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Your feedback encourages the volunteers in this community to continue contributing&lt;/P&gt;</description>
      <pubDate>Mon, 07 Apr 2025 16:02:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-and-Cisco-Firepower-Audit-Logs/m-p/743694#M118131</guid>
      <dc:creator>livehybrid</dc:creator>
      <dc:date>2025-04-07T16:02:09Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk and Cisco Firepower Audit Logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-and-Cisco-Firepower-Audit-Logs/m-p/743731#M118149</link>
      <description>&lt;P&gt;Also remember that while Splunk can listen for syslogs this is not a recommended setup. It's relatively ok for a small lab deployment but in production you'd rather want to go for a separate syslog daemon either writing to local files for pick up by UF or sending to HEC input.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Apr 2025 22:27:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-and-Cisco-Firepower-Audit-Logs/m-p/743731#M118149</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2025-04-07T22:27:26Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk and Cisco Firepower Audit Logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-and-Cisco-Firepower-Audit-Logs/m-p/744010#M118193</link>
      <description>&lt;P&gt;Unfortunately neither of these were the cause. In the end I believe we're going to set up an intermediate VM with a UF to catch the logs from the Firepowers on udp514. Clunky but it appears to be the only option. I appreciate the help.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Apr 2025 11:21:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-and-Cisco-Firepower-Audit-Logs/m-p/744010#M118193</guid>
      <dc:creator>b17gunnr</dc:creator>
      <dc:date>2025-04-11T11:21:03Z</dc:date>
    </item>
  </channel>
</rss>

