<?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 NAT Logging in Firepower 4110 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/nat-logging-in-firepower-4110/m-p/3804232#M982024</link>
    <description>&lt;P&gt;Is there a way to configure FTD to write syslog messages for changes to the NAT table? We'd like to be able to find which device on our network did a thing based on reports sent from external sources, but we can't without having a record of which device was using which port at a specific time.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 14:17:59 GMT</pubDate>
    <dc:creator>jbarrere@lccc.wy.edu</dc:creator>
    <dc:date>2019-03-12T14:17:59Z</dc:date>
    <item>
      <title>NAT Logging in Firepower 4110</title>
      <link>https://community.cisco.com/t5/network-security/nat-logging-in-firepower-4110/m-p/3804232#M982024</link>
      <description>&lt;P&gt;Is there a way to configure FTD to write syslog messages for changes to the NAT table? We'd like to be able to find which device on our network did a thing based on reports sent from external sources, but we can't without having a record of which device was using which port at a specific time.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 14:17:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-logging-in-firepower-4110/m-p/3804232#M982024</guid>
      <dc:creator>jbarrere@lccc.wy.edu</dc:creator>
      <dc:date>2019-03-12T14:17:59Z</dc:date>
    </item>
    <item>
      <title>Re: NAT Logging in Firepower 4110</title>
      <link>https://community.cisco.com/t5/network-security/nat-logging-in-firepower-4110/m-p/3804766#M982025</link>
      <description>I don't think so there is an option to configure logging for NAT table, You can configure Syslog instead.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 19 Feb 2019 10:41:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-logging-in-firepower-4110/m-p/3804766#M982025</guid>
      <dc:creator>Abheesh Kumar</dc:creator>
      <dc:date>2019-02-19T10:41:27Z</dc:date>
    </item>
    <item>
      <title>Re: NAT Logging in Firepower 4110</title>
      <link>https://community.cisco.com/t5/network-security/nat-logging-in-firepower-4110/m-p/3805173#M982026</link>
      <description>&lt;P&gt;I considered that, but don't see any meaningful Syslog messages relating to NAT. The only NAT related messages I see are like this:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Feb 19 2019 10:22:06 firepower syslog-ng[2115]: Log statistics; processed='source(msgs)=2296389', processed='global(payload_reallocs)=2369603', processed='src.none()=0', stamp='src.none()=0', processed='global(internal_queue_length)=0', processed='global(msg_clones)=0', processed='destination(cron_destination)=2907', processed='src.internal(msgs#2)=15233', stamp='src.internal(msgs#2)=1550596326', processed='global(sdata_updates)=0', processed='destination(messages_destination)=1540934', processed='center(received)=2296389', processed='center(queued)=1543841'&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;That isn't particularly helpful, since it doesn't say what IP addresses are involved or anything. Do I need to change something to get the information I care about logged?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Feb 2019 18:45:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nat-logging-in-firepower-4110/m-p/3805173#M982026</guid>
      <dc:creator>jbarrere@lccc.wy.edu</dc:creator>
      <dc:date>2019-02-19T18:45:40Z</dc:date>
    </item>
  </channel>
</rss>

