<?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: IPS and Malware Policy in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ips-and-malware-policy/m-p/3867873#M990510</link>
    <description>&lt;P&gt;Access Control Policy rules are first match (except for Monitor action rules) so I recommend specifying an IPS and Malware policy associated with each Allow rule. Exceptions would be things like a rule allowing encrypted traffic (ssl/tls, ssh etc.) where we won't be able to inspect files anyway.&lt;/P&gt;</description>
    <pubDate>Wed, 05 Jun 2019 05:10:26 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2019-06-05T05:10:26Z</dc:date>
    <item>
      <title>IPS and Malware Policy</title>
      <link>https://community.cisco.com/t5/network-security/ips-and-malware-policy/m-p/3867794#M990509</link>
      <description>&lt;P&gt;I'm new to Firepower. I'm migrating ASA FW Configuration to Firepower. We will be using FDM and not FMC.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My Question is: Should I enable IPS and Malware in every single (allowed) Access Rule OR create a single Rule for IPS and Malware for all the allowed traffic. What is the recommended implementation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jun 2019 23:58:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-and-malware-policy/m-p/3867794#M990509</guid>
      <dc:creator>sheikhrazib2766</dc:creator>
      <dc:date>2019-06-04T23:58:04Z</dc:date>
    </item>
    <item>
      <title>Re: IPS and Malware Policy</title>
      <link>https://community.cisco.com/t5/network-security/ips-and-malware-policy/m-p/3867873#M990510</link>
      <description>&lt;P&gt;Access Control Policy rules are first match (except for Monitor action rules) so I recommend specifying an IPS and Malware policy associated with each Allow rule. Exceptions would be things like a rule allowing encrypted traffic (ssl/tls, ssh etc.) where we won't be able to inspect files anyway.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jun 2019 05:10:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-and-malware-policy/m-p/3867873#M990510</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2019-06-05T05:10:26Z</dc:date>
    </item>
    <item>
      <title>Re: IPS and Malware Policy</title>
      <link>https://community.cisco.com/t5/network-security/ips-and-malware-policy/m-p/3867876#M990511</link>
      <description>&lt;P&gt;Thanks Marvin&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jun 2019 05:21:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-and-malware-policy/m-p/3867876#M990511</guid>
      <dc:creator>sheikhrazib2766</dc:creator>
      <dc:date>2019-06-05T05:21:13Z</dc:date>
    </item>
  </channel>
</rss>

