<?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: Traffic History in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/traffic-history/m-p/5226877#M1117700</link>
    <description>&lt;P&gt;If you have logging enabled, FMC will store Connection Events. However it has a limited amount of storage. For instance, an FMCv can store 10 million events which can fill up in a day or less on a moderately sized deployment. For long term retention of data, we typically advise something like cloud-delivered FMC (can get 90 days or more of storage - at a price) or sending Netflow data to an external system.&lt;/P&gt;</description>
    <pubDate>Wed, 20 Nov 2024 16:58:45 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2024-11-20T16:58:45Z</dc:date>
    <item>
      <title>Traffic History</title>
      <link>https://community.cisco.com/t5/network-security/traffic-history/m-p/5226733#M1117683</link>
      <description>&lt;P&gt;Guys , please help me .&amp;nbsp;&lt;/P&gt;&lt;P&gt;is there anyway to get traffic history to specific destination from cisco FMC or FTD?&lt;/P&gt;</description>
      <pubDate>Wed, 20 Nov 2024 10:27:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/traffic-history/m-p/5226733#M1117683</guid>
      <dc:creator>ShareefKooliyodan0444</dc:creator>
      <dc:date>2024-11-20T10:27:44Z</dc:date>
    </item>
    <item>
      <title>Re: Traffic History</title>
      <link>https://community.cisco.com/t5/network-security/traffic-history/m-p/5226877#M1117700</link>
      <description>&lt;P&gt;If you have logging enabled, FMC will store Connection Events. However it has a limited amount of storage. For instance, an FMCv can store 10 million events which can fill up in a day or less on a moderately sized deployment. For long term retention of data, we typically advise something like cloud-delivered FMC (can get 90 days or more of storage - at a price) or sending Netflow data to an external system.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Nov 2024 16:58:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/traffic-history/m-p/5226877#M1117700</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2024-11-20T16:58:45Z</dc:date>
    </item>
    <item>
      <title>Re: Traffic History</title>
      <link>https://community.cisco.com/t5/network-security/traffic-history/m-p/5226894#M1117702</link>
      <description>&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/firepower/splunk/Cisco_Firepower_App_for_Splunk_User_Guide.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/firepower/splunk/Cisco_Firepower_App_for_Splunk_User_Guide.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Splunk can help you&lt;/P&gt;
&lt;P&gt;contact cisco for more info.&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Wed, 20 Nov 2024 17:12:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/traffic-history/m-p/5226894#M1117702</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-11-20T17:12:53Z</dc:date>
    </item>
    <item>
      <title>Re: Traffic History</title>
      <link>https://community.cisco.com/t5/network-security/traffic-history/m-p/5226897#M1117704</link>
      <description>&lt;P&gt;For Splunk be prepared to spend US$100k ++ annually if you send all your firewall connection logs. And hire a Splunk expert to turn the raw data into actionable information.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Nov 2024 17:14:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/traffic-history/m-p/5226897#M1117704</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2024-11-20T17:14:52Z</dc:date>
    </item>
  </channel>
</rss>

