<?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 ACL Syslog messages in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3316673#M926089</link>
    <description>Must admit, this wasnt as clear as I thought.&lt;BR /&gt;I need to dig into some more documentation if nobody else know exact steps to configure this? &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;br, Micke</description>
    <pubDate>Tue, 23 Jan 2018 12:16:48 GMT</pubDate>
    <dc:creator>mikael.lahtela</dc:creator>
    <dc:date>2018-01-23T12:16:48Z</dc:date>
    <item>
      <title>FTD ACL Syslog messages</title>
      <link>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3313782#M926078</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Versions FMC V6.2.2, FTD 2120 V8.2.2&lt;/P&gt;
&lt;P&gt;I have configured Logging to a syslog server on my ACP Default action. The aim is to Log acl deny messages.&lt;/P&gt;
&lt;P&gt;From the cli on the FTD 2120 device I can see hits on the acl.&lt;/P&gt;
&lt;P&gt;However my Syslog Server does not receive them. They are visible via FMC event Logs.&lt;/P&gt;
&lt;P&gt;Syslog has been defined in Policies - Actions - Alerts with Facility = Local4 and Severity = Warning.&lt;/P&gt;
&lt;P&gt;My Syslog Server has also been configured in my Device Platform settings Policy.&lt;/P&gt;
&lt;P&gt;I also enabled Syslog logging on another acl rule which has valid permit hit count. These do not appear in my Syslog server.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The syslog server is reachable via pings form my FTD device.&lt;/P&gt;
&lt;P&gt;Any suggestions to resolve this issue would be appreciated.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;thanks&lt;/P&gt;
&lt;P&gt;Ian&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 15:09:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3313782#M926078</guid>
      <dc:creator>iwearing</dc:creator>
      <dc:date>2020-02-21T15:09:50Z</dc:date>
    </item>
    <item>
      <title>Re: FTD ACL Syslog messages</title>
      <link>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3314669#M926079</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Just to verify, you have configured&amp;nbsp; "Alert" syslog server and activated it under the ACP rule?&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="syslog2.jpg" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/6536i7F783F7547041788/image-size/large?v=v2&amp;amp;px=999" role="button" title="syslog2.jpg" alt="syslog2.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="syslog.jpg" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/6535iDB79BD05DC7F5051/image-size/large?v=v2&amp;amp;px=999" role="button" title="syslog.jpg" alt="syslog.jpg" /&gt;&lt;/span&gt;Br, Micke&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jan 2018 17:28:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3314669#M926079</guid>
      <dc:creator>mikael.lahtela</dc:creator>
      <dc:date>2018-01-19T17:28:51Z</dc:date>
    </item>
    <item>
      <title>Re: FTD ACL Syslog messages</title>
      <link>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3314735#M926080</link>
      <description>Hi Micke,&lt;BR /&gt;&lt;BR /&gt;Thanks for the response.&lt;BR /&gt;&lt;BR /&gt;I have configured "alert" Syslog server and activated it in the ACP rule.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Ian&lt;BR /&gt;</description>
      <pubDate>Fri, 19 Jan 2018 19:02:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3314735#M926080</guid>
      <dc:creator>iwearing</dc:creator>
      <dc:date>2018-01-19T19:02:07Z</dc:date>
    </item>
    <item>
      <title>Re: FTD ACL Syslog messages</title>
      <link>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3314746#M926081</link>
      <description>Is the syslog port open from the FTD ip address to syslog server?&lt;BR /&gt;I checked in my home device that is a Firepower Services module and the syslog is sent from the device and not the FMC.&lt;BR /&gt;&lt;BR /&gt;br, Micke</description>
      <pubDate>Fri, 19 Jan 2018 19:20:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3314746#M926081</guid>
      <dc:creator>mikael.lahtela</dc:creator>
      <dc:date>2018-01-19T19:20:15Z</dc:date>
    </item>
    <item>
      <title>Re: FTD ACL Syslog messages</title>
      <link>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3316552#M926083</link>
      <description>&lt;P&gt;Hi Micke,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I agree that syslog messages are sourced from the FTD Interface connected to the syslog server.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The syslog server is reachable from the inside interface and there are no other devices in the path that could block syslog on UDP Port 514.&lt;/P&gt;
&lt;P&gt;regards&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Ian&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jan 2018 09:22:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3316552#M926083</guid>
      <dc:creator>iwearing</dc:creator>
      <dc:date>2018-01-23T09:22:26Z</dc:date>
    </item>
    <item>
      <title>Re: FTD ACL Syslog messages</title>
      <link>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3316554#M926086</link>
      <description>You could try and take packet capture on the traffic to see that you send and recieve packets between FTD and syslog.&lt;BR /&gt;Is the syslog server getting messages from other systems?&lt;BR /&gt;&lt;BR /&gt;br, Micke</description>
      <pubDate>Tue, 23 Jan 2018 09:29:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3316554#M926086</guid>
      <dc:creator>mikael.lahtela</dc:creator>
      <dc:date>2018-01-23T09:29:21Z</dc:date>
    </item>
    <item>
      <title>Re: FTD ACL Syslog messages</title>
      <link>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3316556#M926088</link>
      <description>&lt;P&gt;Hi Micke,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Syslog is receiving messages from other systems including 5585X ASA's with Firepower modules. They are managed by the same FMC at the FTD 2120 deices.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;regards&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Ian&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jan 2018 09:35:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3316556#M926088</guid>
      <dc:creator>iwearing</dc:creator>
      <dc:date>2018-01-23T09:35:30Z</dc:date>
    </item>
    <item>
      <title>Re: FTD ACL Syslog messages</title>
      <link>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3316673#M926089</link>
      <description>Must admit, this wasnt as clear as I thought.&lt;BR /&gt;I need to dig into some more documentation if nobody else know exact steps to configure this? &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;br, Micke</description>
      <pubDate>Tue, 23 Jan 2018 12:16:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3316673#M926089</guid>
      <dc:creator>mikael.lahtela</dc:creator>
      <dc:date>2018-01-23T12:16:48Z</dc:date>
    </item>
    <item>
      <title>Re: FTD ACL Syslog messages</title>
      <link>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3320699#M926091</link>
      <description>&lt;P&gt;Hey Mate,&lt;/P&gt;
&lt;P&gt;Did you get solution for this ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have the same issue , I have enabled syslog logging on one of the ACPs ( action as block) as&amp;nbsp; a part of prefilter policy. however cound't see logs coming to syslog server.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jan 2018 07:15:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3320699#M926091</guid>
      <dc:creator>prashant dwivedi</dc:creator>
      <dc:date>2018-01-29T07:15:33Z</dc:date>
    </item>
    <item>
      <title>Re: FTD ACL Syslog messages</title>
      <link>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3320965#M926093</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Looks like I managed to activate the logging following this guide:&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/security/firepower-ngfw/200479-Configure-Logging-on-FTD-via-FMC.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/security/firepower-ngfw/200479-Configure-Logging-on-FTD-via-FMC.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;But I need to do some more testing to see exactly what needs to be configured.&lt;BR /&gt;&lt;BR /&gt;Looks like the FTD is configured with regular "ASA" logging commands, you can see them with the troubleshooting commands in the end of the document.&lt;BR /&gt;&lt;BR /&gt;&amp;gt; system support diagnostic-cli &lt;BR /&gt;Attaching to ASA console ... Press 'Ctrl+a then d' to detach.&lt;BR /&gt;Type help or '?' for a list of available commands.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;lt;Press Enter&amp;gt;&lt;BR /&gt;firepower# sh run logging &lt;BR /&gt;logging enable&lt;BR /&gt;logging console emergencies&lt;BR /&gt;logging buffered debugging&lt;BR /&gt;logging host inside 192.0.0.192&lt;BR /&gt;logging flash-minimum-free 1024&lt;BR /&gt;logging flash-maximum-allocation 3076&lt;BR /&gt;logging permit-hostdown&lt;BR /&gt;&lt;BR /&gt;br, Micke</description>
      <pubDate>Mon, 29 Jan 2018 15:48:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3320965#M926093</guid>
      <dc:creator>mikael.lahtela</dc:creator>
      <dc:date>2018-01-29T15:48:02Z</dc:date>
    </item>
    <item>
      <title>Re: FTD ACL Syslog messages</title>
      <link>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3321008#M926096</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Unfortunately not resolved so far.&lt;/P&gt;
&lt;P&gt;br&lt;/P&gt;
&lt;P&gt;Ian&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jan 2018 16:41:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3321008#M926096</guid>
      <dc:creator>iwearing</dc:creator>
      <dc:date>2018-01-29T16:41:49Z</dc:date>
    </item>
    <item>
      <title>Re: FTD ACL Syslog messages</title>
      <link>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3321036#M926099</link>
      <description>&lt;P&gt;Now when I try to remove the configuration it's still logging.&lt;BR /&gt;At the moment I have disabled the logging from device profile and still getting logs to the syslog server.&lt;BR /&gt;Guess they are sent now by the configuration settings under alert.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Edit: Ok, so it looks like I get things working by configuring the syslog server under actions/alerts and then adding the server in the rule.&lt;/P&gt;
&lt;P&gt;The syslog message is sent from the FTD mgmt IP address.&lt;/P&gt;
&lt;P&gt;You can check the IP with following commands:&lt;BR /&gt;&amp;gt;expert&lt;/P&gt;
&lt;P&gt;~$ ip address&lt;/P&gt;
&lt;P&gt;9: management0: &amp;lt;BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP&amp;gt; mtu 1500 qdisc noqueue state UP&lt;BR /&gt; link/ether 38:90:a5:3a:c2:80 brd ff:ff:ff:ff:ff:ff&lt;BR /&gt; inet 10.215.240.219/24 brd 10.215.240.255 scope global management0&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;br, Micke&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jan 2018 17:59:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3321036#M926099</guid>
      <dc:creator>mikael.lahtela</dc:creator>
      <dc:date>2018-01-29T17:59:57Z</dc:date>
    </item>
    <item>
      <title>Re: FTD ACL Syslog messages</title>
      <link>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3321336#M926102</link>
      <description>&lt;P&gt;Thanks, did you configure SYSLOG Facility and Severity as "alert" and have applied this in a prefilter rule or at ACP ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I need to apply this to the rule which is the part of pre-filter policy.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can you please share the syslog output ( if this possible) i want to know if log messages contain rule name as well .&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jan 2018 01:46:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3321336#M926102</guid>
      <dc:creator>prashant dwivedi</dc:creator>
      <dc:date>2018-01-30T01:46:44Z</dc:date>
    </item>
    <item>
      <title>Re: FTD ACL Syslog messages</title>
      <link>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3321476#M926104</link>
      <description>The configuration on Alert is LOCAL4 and Severity INFO.&lt;BR /&gt;Not seeing anything from the prefilter logging just ACP.&lt;BR /&gt;&lt;BR /&gt;The ACP rule log includes this:&lt;BR /&gt;Jan 30 08:52:27 FPR2110-LAB-P SFIMS: Protocol: TCP&lt;BR /&gt; SrcIP: 172.16.0.101&lt;BR /&gt; OriginalClientIP: ::&lt;BR /&gt; DstIP: 136.243.5.166&lt;BR /&gt; SrcPort: 59143&lt;BR /&gt; DstPort: 443&lt;BR /&gt; TCPFlags: 0x0&lt;BR /&gt; IngressZone: LAN&lt;BR /&gt; EgressZone: INTERNET&lt;BR /&gt; DE: Primary Detection Engine (61cf9bfe-6c84-11e7-9bbc-b2da5b7afba6)&lt;BR /&gt; Policy: FPR2110-DEF-ACP&lt;BR /&gt; ConnectType: Start&lt;BR /&gt; AccessControlRuleName: internet-access&lt;BR /&gt; AccessControlRuleAction: Allow&lt;BR /&gt; Prefilter Policy: prefilter-test&lt;BR /&gt; UserName: No Authentication Required&lt;BR /&gt; Client: SSL client&lt;BR /&gt; ApplicationProtocol: HTTPS&lt;BR /&gt; InitiatorPackets: 3&lt;BR /&gt; ResponderPackets: 1&lt;BR /&gt; InitiatorBytes: 691&lt;BR /&gt; ResponderBytes: 66&lt;BR /&gt; NAPPolicy: Balanced Security and Connectivity&lt;BR /&gt; DNSResponseType: No Error&lt;BR /&gt; Sinkhole: Unknown&lt;BR /&gt; URLCategory: Web Advertisements&lt;BR /&gt; URLReputation: Well known&lt;BR /&gt; URL: &lt;A href="https://dc546.s372.meetrics.net" target="_blank"&gt;https://dc546.s372.meetrics.net&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;br, Micke&lt;BR /&gt;</description>
      <pubDate>Tue, 30 Jan 2018 08:58:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3321476#M926104</guid>
      <dc:creator>mikael.lahtela</dc:creator>
      <dc:date>2018-01-30T08:58:09Z</dc:date>
    </item>
    <item>
      <title>Re: FTD ACL Syslog messages</title>
      <link>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3322270#M926106</link>
      <description>&lt;P&gt;Thanks mate!&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jan 2018 08:30:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3322270#M926106</guid>
      <dc:creator>prashant dwivedi</dc:creator>
      <dc:date>2018-01-31T08:30:31Z</dc:date>
    </item>
    <item>
      <title>Re: FTD ACL Syslog messages</title>
      <link>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3739135#M926108</link>
      <description>&lt;P&gt;Did you find a solution ?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Nov 2018 14:31:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-acl-syslog-messages/m-p/3739135#M926108</guid>
      <dc:creator>Mykola Chekunov</dc:creator>
      <dc:date>2018-11-05T14:31:49Z</dc:date>
    </item>
  </channel>
</rss>

