<?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: Firepower -  file trajectory in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firepower-file-trajectory/m-p/3990918#M934909</link>
    <description>Yes you use AMP4E to get that information you require. You can also integrate with ISE in order to quarantine the device in infected.</description>
    <pubDate>Thu, 28 Nov 2019 21:00:00 GMT</pubDate>
    <dc:creator>Rob Ingram</dc:creator>
    <dc:date>2019-11-28T21:00:00Z</dc:date>
    <item>
      <title>Firepower -  file trajectory</title>
      <link>https://community.cisco.com/t5/network-security/firepower-file-trajectory/m-p/3990891#M934905</link>
      <description>&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Network file trajectory:&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;"Cisco maps how&amp;nbsp;&lt;STRONG&gt;hosts transfer files, including malware files, across your network&lt;/STRONG&gt;. It can see if a file transfer was blocked or the file was quarantined. This provides a means to scope, provide outbreak controls, and identify patient zero." -&amp;nbsp;&lt;A href="https://www.cisco.com/c/m/en_us/products/security/firewalls/competitive-comparison.html#~competitive=0" target="_blank" rel="nofollow noopener noreferrer"&gt;https://www.cisco.com/c/m/en_us/products/security/firewalls/competitive-comparison.html#~competitive=0&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What products do customers need to offer to implement the "&lt;STRONG&gt;Network file trajectory&lt;/STRONG&gt;" features?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;we don't put Firepower&amp;nbsp; into the east-west path of the traffic than we can not see&amp;nbsp;&lt;STRONG&gt;file trajectory&amp;nbsp;&lt;/STRONG&gt;&lt;STRONG&gt;across customer network without additional&amp;nbsp;products&amp;nbsp;such as, for example, AMP for Endpoint ?!&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So, in design (case 1 in attach)&amp;nbsp;&lt;SPAN&gt;&lt;STRONG&gt;without&amp;nbsp; AMP for Endpoint do I not see&amp;nbsp;file trajectory between host B and C ?&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Or do I need&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;additional Firepower between&amp;nbsp;host B and C&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;(case 2 in attach) or&amp;nbsp;&lt;STRONG&gt;AMP for Endpoint on both hosts ?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Could you correct me if I am wrong?&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 17:44:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-file-trajectory/m-p/3990891#M934905</guid>
      <dc:creator>cadet</dc:creator>
      <dc:date>2020-02-21T17:44:04Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower -  file trajectory</title>
      <link>https://community.cisco.com/t5/network-security/firepower-file-trajectory/m-p/3990906#M934907</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;It probably wouldn't be feasible or scalable to put a Firepower appliance in between host B and C in order to filter intra VLAN traffic. You should implement AMP for Endpoints.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;</description>
      <pubDate>Thu, 28 Nov 2019 20:09:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-file-trajectory/m-p/3990906#M934907</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2019-11-28T20:09:36Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower -  file trajectory</title>
      <link>https://community.cisco.com/t5/network-security/firepower-file-trajectory/m-p/3990914#M934908</link>
      <description>&lt;P&gt;Definitely &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;So, does AMP for Endpoint is mandatory element&amp;nbsp;in file trajectory functionality?&lt;/P&gt;</description>
      <pubDate>Thu, 28 Nov 2019 20:49:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-file-trajectory/m-p/3990914#M934908</guid>
      <dc:creator>cadet</dc:creator>
      <dc:date>2019-11-28T20:49:57Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower -  file trajectory</title>
      <link>https://community.cisco.com/t5/network-security/firepower-file-trajectory/m-p/3990918#M934909</link>
      <description>Yes you use AMP4E to get that information you require. You can also integrate with ISE in order to quarantine the device in infected.</description>
      <pubDate>Thu, 28 Nov 2019 21:00:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-file-trajectory/m-p/3990918#M934909</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2019-11-28T21:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower -  file trajectory</title>
      <link>https://community.cisco.com/t5/network-security/firepower-file-trajectory/m-p/3990927#M934910</link>
      <description>&lt;P&gt;does Firepower can&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;to quarantine the device if infected without ISE ?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 28 Nov 2019 21:18:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-file-trajectory/m-p/3990927#M934910</guid>
      <dc:creator>cadet</dc:creator>
      <dc:date>2019-11-28T21:18:13Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower -  file trajectory</title>
      <link>https://community.cisco.com/t5/network-security/firepower-file-trajectory/m-p/3990928#M934911</link>
      <description>You need ISE to quarantine. When quarantined ISE would send a DACL down to the switchport an infected device is connected to, which would restrict lateral movement within the VLAN for that device. Thus preventing the spread of malware/virus etc to other devices on the network.</description>
      <pubDate>Thu, 28 Nov 2019 21:27:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-file-trajectory/m-p/3990928#M934911</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2019-11-28T21:27:56Z</dc:date>
    </item>
  </channel>
</rss>

