<?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: FTD logging to Algosec in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ftd-logging-to-algosec/m-p/4864689#M1102146</link>
    <description>&lt;P&gt;FTD doesn't use 106100, it uses the following:&lt;/P&gt;
&lt;P&gt;430002 - log at beginning&lt;/P&gt;
&lt;P&gt;430003 - log at end&lt;/P&gt;</description>
    <pubDate>Thu, 29 Jun 2023 13:53:41 GMT</pubDate>
    <dc:creator>Marius Gunnerud</dc:creator>
    <dc:date>2023-06-29T13:53:41Z</dc:date>
    <item>
      <title>FTD logging to Algosec</title>
      <link>https://community.cisco.com/t5/network-security/ftd-logging-to-algosec/m-p/4401920#M1080721</link>
      <description>&lt;P&gt;Has anyone here set up logging from FTD to Algosec?&amp;nbsp; The only documentation I have found on the Algosec site with regards to logging was for ASA and there it stated that syslog message ID 106100 is needed.&amp;nbsp; This syslog ID is not available in FTD after 6.2. So I am wondering if anyone has successfully set up logging towards Algosec and which syslog message IDs were used?&lt;/P&gt;</description>
      <pubDate>Wed, 12 May 2021 12:57:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-logging-to-algosec/m-p/4401920#M1080721</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2021-05-12T12:57:06Z</dc:date>
    </item>
    <item>
      <title>Re: FTD logging to Algosec</title>
      <link>https://community.cisco.com/t5/network-security/ftd-logging-to-algosec/m-p/4864674#M1102142</link>
      <description>&lt;P&gt;Not using Algosec, running into a similar problem though. Have you ever managed to fix/solve it?&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jun 2023 13:31:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-logging-to-algosec/m-p/4864674#M1102142</guid>
      <dc:creator>1_am_r00t</dc:creator>
      <dc:date>2023-06-29T13:31:17Z</dc:date>
    </item>
    <item>
      <title>Re: FTD logging to Algosec</title>
      <link>https://community.cisco.com/t5/network-security/ftd-logging-to-algosec/m-p/4864682#M1102143</link>
      <description>&lt;P&gt;Yes, solved this by enabling logging to syslog server under each ACP rule.&amp;nbsp; Once I did this syslog was sent.&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jun 2023 13:37:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-logging-to-algosec/m-p/4864682#M1102143</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2023-06-29T13:37:38Z</dc:date>
    </item>
    <item>
      <title>Re: FTD logging to Algosec</title>
      <link>https://community.cisco.com/t5/network-security/ftd-logging-to-algosec/m-p/4864683#M1102144</link>
      <description>&lt;P&gt;Interesting. I have enabled logging for the majority of ACP rules (see screenshot attached), however, 106100 is not being sent. Maybe it is version specific - we're using 6.6.5.2 in this deployment.&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jun 2023 13:41:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-logging-to-algosec/m-p/4864683#M1102144</guid>
      <dc:creator>1_am_r00t</dc:creator>
      <dc:date>2023-06-29T13:41:16Z</dc:date>
    </item>
    <item>
      <title>Re: FTD logging to Algosec</title>
      <link>https://community.cisco.com/t5/network-security/ftd-logging-to-algosec/m-p/4864689#M1102146</link>
      <description>&lt;P&gt;FTD doesn't use 106100, it uses the following:&lt;/P&gt;
&lt;P&gt;430002 - log at beginning&lt;/P&gt;
&lt;P&gt;430003 - log at end&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jun 2023 13:53:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-logging-to-algosec/m-p/4864689#M1102146</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2023-06-29T13:53:41Z</dc:date>
    </item>
  </channel>
</rss>

