<?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 as IPS in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ftd-as-ips/m-p/3730351#M985477</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/120128"&gt;@gbekmezi-DD&lt;/a&gt;, but we want to pinpoint the actual traffic causing the issue and as per TAC we can only determine that when we do flow profiling but it is not an option in our environment that is why if we can put our spare IPS into passive mode then do flow profiling there if it is possible?&lt;/P&gt;
&lt;P&gt;You said netflow, we have a netflow collector deployed in the network. is it possible to use that? What parameters should we look in the netflow data for us to find the elephant flow?&lt;/P&gt;
&lt;P&gt;thanks&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>Tue, 23 Oct 2018 03:43:41 GMT</pubDate>
    <dc:creator>fatalXerror</dc:creator>
    <dc:date>2018-10-23T03:43:41Z</dc:date>
    <item>
      <title>FTD as IPS</title>
      <link>https://community.cisco.com/t5/network-security/ftd-as-ips/m-p/3730064#M985475</link>
      <description>&lt;P&gt;Hi, I am having an issue about Elephant flow in my FTD and as per the TAC we need to do flow profiling to pinpoint which traffic is causing it however, it is not an option in my environment because this will have an interruption.&lt;/P&gt;
&lt;P&gt;We think of an option to connect another IPS (same model) that will act like a tap. The prod IPS will send a copy of the packet to the other IPS acting as tap then we do the flow profiling there in the tapped IPS?&lt;/P&gt;
&lt;P&gt;I would like to know if that is feasible and what configuration should we do for the tapped IPS?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 16:22:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-as-ips/m-p/3730064#M985475</guid>
      <dc:creator>fatalXerror</dc:creator>
      <dc:date>2020-02-21T16:22:54Z</dc:date>
    </item>
    <item>
      <title>Re: FTD as IPS</title>
      <link>https://community.cisco.com/t5/network-security/ftd-as-ips/m-p/3730153#M985476</link>
      <description>Do you think adding another appliance in line would be less intrusive than one of these options?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;  *   use netflow do try to identify large flows: &lt;A href="https://community.cisco.com/t5/security-documents/configuring-nsel-netflow-on-cisco-firepower-threat-defense-ftd/ta-p/3646300" target="_blank"&gt;https://community.cisco.com/t5/security-documents/configuring-nsel-netflow-on-cisco-firepower-threat-defense-ftd/ta-p/3646300&lt;/A&gt;&lt;BR /&gt;  *   use packet captures on the FTD appliance itself: &lt;A href="https://www.cisco.com/c/en/us/support/docs/security/firepower-ngfw/212474-working-with-firepower-threat-defense-f.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/security/firepower-ngfw/212474-working-with-firepower-threat-defense-f.html&lt;/A&gt;&lt;BR /&gt;  *   SPAN/Mirror/Monitor traffic from the switch the FTD appliance is connected to&lt;BR /&gt;</description>
      <pubDate>Mon, 22 Oct 2018 20:07:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-as-ips/m-p/3730153#M985476</guid>
      <dc:creator>gbekmezi-DD</dc:creator>
      <dc:date>2018-10-22T20:07:00Z</dc:date>
    </item>
    <item>
      <title>Re: FTD as IPS</title>
      <link>https://community.cisco.com/t5/network-security/ftd-as-ips/m-p/3730351#M985477</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/120128"&gt;@gbekmezi-DD&lt;/a&gt;, but we want to pinpoint the actual traffic causing the issue and as per TAC we can only determine that when we do flow profiling but it is not an option in our environment that is why if we can put our spare IPS into passive mode then do flow profiling there if it is possible?&lt;/P&gt;
&lt;P&gt;You said netflow, we have a netflow collector deployed in the network. is it possible to use that? What parameters should we look in the netflow data for us to find the elephant flow?&lt;/P&gt;
&lt;P&gt;thanks&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>Tue, 23 Oct 2018 03:43:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-as-ips/m-p/3730351#M985477</guid>
      <dc:creator>fatalXerror</dc:creator>
      <dc:date>2018-10-23T03:43:41Z</dc:date>
    </item>
  </channel>
</rss>

