<?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: File policy rule targeting application protocol &amp;quot;Any&amp;quot; may never be triggered due to Application selection in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/file-policy-rule-targeting-application-protocol-quot-any-quot/m-p/3767868#M1026790</link>
    <description>I found out that file inspection can not be done on applications so simply removing file inspection from the rule solved my problem.</description>
    <pubDate>Fri, 21 Dec 2018 13:47:13 GMT</pubDate>
    <dc:creator>Emrecan Ural</dc:creator>
    <dc:date>2018-12-21T13:47:13Z</dc:date>
    <item>
      <title>File policy rule targeting application protocol "Any" may never be triggered due to Application selection</title>
      <link>https://community.cisco.com/t5/network-security/file-policy-rule-targeting-application-protocol-quot-any-quot/m-p/2682077#M1026789</link>
      <description>&lt;P&gt;I have a few Access Rules where I want to apply a file policy for hits on specific applications.&lt;/P&gt;&lt;P&gt;When I try that, I get the following Rule&amp;nbsp;Warning:&lt;/P&gt;&lt;P style="margin-left: 40px;"&gt;"File policy rule targeting application protocol "Any" may never be triggered due to Application selection."&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My application selection is ie. "Microsoft download", "Microsoft Update", "cURL", "Wget" etc...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My goal is to apply a less restrictive file policy for those applications.&lt;/P&gt;&lt;P&gt;Do you know how to achieve this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Or where to find more guidance on Rule Warnings and Info. A bit deeper than FireSIGHT System User Guide, please.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;rgds&lt;/P&gt;&lt;P&gt;Thomas Winther&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 12:43:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/file-policy-rule-targeting-application-protocol-quot-any-quot/m-p/2682077#M1026789</guid>
      <dc:creator>Thomas Winther</dc:creator>
      <dc:date>2019-03-12T12:43:07Z</dc:date>
    </item>
    <item>
      <title>Re: File policy rule targeting application protocol "Any" may never be triggered due to Application selection</title>
      <link>https://community.cisco.com/t5/network-security/file-policy-rule-targeting-application-protocol-quot-any-quot/m-p/3767868#M1026790</link>
      <description>I found out that file inspection can not be done on applications so simply removing file inspection from the rule solved my problem.</description>
      <pubDate>Fri, 21 Dec 2018 13:47:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/file-policy-rule-targeting-application-protocol-quot-any-quot/m-p/3767868#M1026790</guid>
      <dc:creator>Emrecan Ural</dc:creator>
      <dc:date>2018-12-21T13:47:13Z</dc:date>
    </item>
    <item>
      <title>Re: File policy rule targeting application protocol "Any" may never be triggered due to Application selection</title>
      <link>https://community.cisco.com/t5/network-security/file-policy-rule-targeting-application-protocol-quot-any-quot/m-p/3768772#M1026791</link>
      <description>&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/firepower/60/configuration/guide/fpmc-config-guide-v60/Reference_a_wrapper_Chapter_topic_here.pdf" target="_self"&gt;File Policies and Advanced Malware Protection&lt;/A&gt; Guide&lt;/P&gt;</description>
      <pubDate>Tue, 25 Dec 2018 07:34:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/file-policy-rule-targeting-application-protocol-quot-any-quot/m-p/3768772#M1026791</guid>
      <dc:creator>Abheesh Kumar</dc:creator>
      <dc:date>2018-12-25T07:34:17Z</dc:date>
    </item>
  </channel>
</rss>

