<?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 Blocking Application Filters in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/blocking-application-filters/m-p/4031#M2978</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've browsed through these forums regarding the best way to block applications.&amp;nbsp; I've saw the posts of folks blocking applications by app filter. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have AD integrated AD groups.&amp;nbsp; These groups tie to individual Palo Alto security rules that allow any port any service as the destination, and then use group profiles to block specific categories.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am in the process of creating a rule above most of these AD LDAP group rules that contains all my blocked applications filters.&amp;nbsp;&amp;nbsp; Since I'm allowing any destination port, not just 80 and 443, I'm not sure what exactly I should block by app-ID.&amp;nbsp; I'm thinking of creating individual application filters based on the subcategories I want to block, such as voip-video, storage-backup, proxy, encrypted-tunnel, e-mail...&amp;nbsp;&amp;nbsp; And putting all these application filters in this block rule.&amp;nbsp;&amp;nbsp; I do understand that I run the risk of a new app-ID blocking things I did not want blocked.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm curious what others are doing.&amp;nbsp; There are over 1500 app-IDs.&amp;nbsp; Are you creating a application group and adding the 1000 you want blocked, or using filters?&amp;nbsp;&amp;nbsp; I'm interested in alternate approaches to this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 09 Aug 2012 22:44:59 GMT</pubDate>
    <dc:creator>EdwinD</dc:creator>
    <dc:date>2012-08-09T22:44:59Z</dc:date>
    <item>
      <title>Blocking Application Filters</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/blocking-application-filters/m-p/4031#M2978</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've browsed through these forums regarding the best way to block applications.&amp;nbsp; I've saw the posts of folks blocking applications by app filter. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have AD integrated AD groups.&amp;nbsp; These groups tie to individual Palo Alto security rules that allow any port any service as the destination, and then use group profiles to block specific categories.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am in the process of creating a rule above most of these AD LDAP group rules that contains all my blocked applications filters.&amp;nbsp;&amp;nbsp; Since I'm allowing any destination port, not just 80 and 443, I'm not sure what exactly I should block by app-ID.&amp;nbsp; I'm thinking of creating individual application filters based on the subcategories I want to block, such as voip-video, storage-backup, proxy, encrypted-tunnel, e-mail...&amp;nbsp;&amp;nbsp; And putting all these application filters in this block rule.&amp;nbsp;&amp;nbsp; I do understand that I run the risk of a new app-ID blocking things I did not want blocked.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm curious what others are doing.&amp;nbsp; There are over 1500 app-IDs.&amp;nbsp; Are you creating a application group and adding the 1000 you want blocked, or using filters?&amp;nbsp;&amp;nbsp; I'm interested in alternate approaches to this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Aug 2012 22:44:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/blocking-application-filters/m-p/4031#M2978</guid>
      <dc:creator>EdwinD</dc:creator>
      <dc:date>2012-08-09T22:44:59Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking Application Filters</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/blocking-application-filters/m-p/4032#M2979</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Appfilters is to create a custom "group" based on category, subcategory, risk or some other column.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you setup an application group you add each appid you want into this group.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also note that a flow can (today) only have a single appid.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Which gives that if you have security policies to allow traffic you will only need a "deny+log" as last rule to keep this tidy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You could however use appfilter in combination with appgroup.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Such as:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rule1) Deny appgroup(youtube)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rule2) Allow appfilter(category:video)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this would allow all flows identified as "video" except youtube (which is part of video).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Generally speaking when denying traffic the policy should be as broad as possible while allow traffic the policy should be as narrow as possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a sidenote I would recommend you to avoid using "service:any" but rather "service:default-application" to not open up more ports than necessary. Because appid detection might in some situations take a few packets before the flow is properly identified.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 20 Aug 2012 23:12:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/blocking-application-filters/m-p/4032#M2979</guid>
      <dc:creator>mikand</dc:creator>
      <dc:date>2012-08-20T23:12:39Z</dc:date>
    </item>
  </channel>
</rss>

