<?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: Applying security policies with security profile groups in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/applying-security-policies-with-security-profile-groups/m-p/30136#M22022</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Rules are applied for the direction which the session is expected to start with.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have something like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rule:1&lt;/P&gt;&lt;P&gt;srczone: WIFI&lt;/P&gt;&lt;P&gt;dstzone: INTERNET&lt;/P&gt;&lt;P&gt;srcip: x.x.x.x/24&lt;/P&gt;&lt;P&gt;dstip: any&lt;/P&gt;&lt;P&gt;appid: web-browsing&lt;/P&gt;&lt;P&gt;service: TCP80&lt;/P&gt;&lt;P&gt;action: allow&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it means that WIFI-clients will be able to do web-browsing over TCP80 towards Internet (if they (the WIFI-clients) start the session).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However if someone from INTERNET tries to initiate a session towards one of your WIFI-clients it will fail unless you allow that traffic aswell like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rule:2&lt;/P&gt;&lt;P&gt;srczone: INTERNET&lt;/P&gt;&lt;P&gt;dstzone: WIFI&lt;/P&gt;&lt;P&gt;srcip: any&lt;/P&gt;&lt;P&gt;dstip: x.x.x.x/24&lt;/P&gt;&lt;P&gt;appid: web-browsing&lt;/P&gt;&lt;P&gt;service: TCP80&lt;/P&gt;&lt;P&gt;action: allow&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also note that PAN uses top-down first-match (similar to cisco acl) which means that you cannot "combine" security rules. The first security rule (from above in your rule list) which match the traffic will be used to determine if the flow should be allowed or denied.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example something like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rule:1&lt;/P&gt;&lt;P&gt;srczone: any&lt;/P&gt;&lt;P&gt;dstzone: any&lt;/P&gt;&lt;P&gt;srcip: any&lt;/P&gt;&lt;P&gt;dstip: any&lt;/P&gt;&lt;P&gt;appid: any&lt;/P&gt;&lt;P&gt;service: any&lt;/P&gt;&lt;P&gt;security: antivirus&lt;/P&gt;&lt;P&gt;action: allow&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rule:2&lt;/P&gt;&lt;P&gt;srczone: WIFI&lt;/P&gt;&lt;P&gt;dstzone: INTERNET&lt;/P&gt;&lt;P&gt;srcip: x.x.x.x/24&lt;/P&gt;&lt;P&gt;dstip: any&lt;/P&gt;&lt;P&gt;appid: web-browsing&lt;/P&gt;&lt;P&gt;service: TCP80&lt;/P&gt;&lt;P&gt;action: allow&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;just wont work as expected (if you expect the above to do antivirus for ALL traffic and then just allow web-browsing from WIFI to INTERNET) because your WIFI to INTERNET traffic will always match rule1 and rule1 allows any protocol (including unknown) in any direction (mostly a bad idea unless you setup PAN in a new environment and need to learn how the flows goes before you setup default block and only allow whats expected to flow through your PAN).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The correct setup of above would be:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rule:1&lt;/P&gt;&lt;P&gt;srczone: WIFI&lt;/P&gt;&lt;P&gt;dstzone: INTERNET&lt;/P&gt;&lt;P&gt;srcip: x.x.x.x/24&lt;/P&gt;&lt;P&gt;dstip: any&lt;/P&gt;&lt;P&gt;appid: web-browsing&lt;/P&gt;&lt;P&gt;service: TCP80&lt;/P&gt;&lt;P&gt;security: antivirus&lt;/P&gt;&lt;P&gt;action: allow&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also note that if you dont put any last rule there is an "invisible" rule that will drop/deny the traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In order to have such traffic logged you need to manually setup an any/any deny+log rule like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rule:&amp;lt;lastone&amp;gt;&lt;/P&gt;&lt;P&gt;srczone: any&lt;/P&gt;&lt;P&gt;dstzone: any&lt;/P&gt;&lt;P&gt;srcip: any&lt;/P&gt;&lt;P&gt;dstip: any&lt;/P&gt;&lt;P&gt;appid: any&lt;/P&gt;&lt;P&gt;service: any&lt;/P&gt;&lt;P&gt;action: deny&lt;/P&gt;&lt;P&gt;option: log (on session end)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Log on session end is prefered because PAN will then also know transmitted volume, start/end of session, and something else I always forgets (appid?). During debug log on both session start AND session end could be nice but in a large environment will result in shitloads of logs.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 22 Mar 2012 22:32:59 GMT</pubDate>
    <dc:creator>mikand</dc:creator>
    <dc:date>2012-03-22T22:32:59Z</dc:date>
    <item>
      <title>Applying security policies with security profile groups</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/applying-security-policies-with-security-profile-groups/m-p/30135#M22021</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Typically, are these applied on the inbound direction or outbound direction of an interface?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And if you wanted to protect an entire zone/interface would you just apply it to any source and any destination?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example if you wanted to apply Antivirus to a interface dedicated to your Wifi access devices?&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, 22 Mar 2012 21:42:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/applying-security-policies-with-security-profile-groups/m-p/30135#M22021</guid>
      <dc:creator>dkhoe</dc:creator>
      <dc:date>2012-03-22T21:42:47Z</dc:date>
    </item>
    <item>
      <title>Re: Applying security policies with security profile groups</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/applying-security-policies-with-security-profile-groups/m-p/30136#M22022</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Rules are applied for the direction which the session is expected to start with.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have something like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rule:1&lt;/P&gt;&lt;P&gt;srczone: WIFI&lt;/P&gt;&lt;P&gt;dstzone: INTERNET&lt;/P&gt;&lt;P&gt;srcip: x.x.x.x/24&lt;/P&gt;&lt;P&gt;dstip: any&lt;/P&gt;&lt;P&gt;appid: web-browsing&lt;/P&gt;&lt;P&gt;service: TCP80&lt;/P&gt;&lt;P&gt;action: allow&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it means that WIFI-clients will be able to do web-browsing over TCP80 towards Internet (if they (the WIFI-clients) start the session).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However if someone from INTERNET tries to initiate a session towards one of your WIFI-clients it will fail unless you allow that traffic aswell like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rule:2&lt;/P&gt;&lt;P&gt;srczone: INTERNET&lt;/P&gt;&lt;P&gt;dstzone: WIFI&lt;/P&gt;&lt;P&gt;srcip: any&lt;/P&gt;&lt;P&gt;dstip: x.x.x.x/24&lt;/P&gt;&lt;P&gt;appid: web-browsing&lt;/P&gt;&lt;P&gt;service: TCP80&lt;/P&gt;&lt;P&gt;action: allow&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also note that PAN uses top-down first-match (similar to cisco acl) which means that you cannot "combine" security rules. The first security rule (from above in your rule list) which match the traffic will be used to determine if the flow should be allowed or denied.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example something like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rule:1&lt;/P&gt;&lt;P&gt;srczone: any&lt;/P&gt;&lt;P&gt;dstzone: any&lt;/P&gt;&lt;P&gt;srcip: any&lt;/P&gt;&lt;P&gt;dstip: any&lt;/P&gt;&lt;P&gt;appid: any&lt;/P&gt;&lt;P&gt;service: any&lt;/P&gt;&lt;P&gt;security: antivirus&lt;/P&gt;&lt;P&gt;action: allow&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rule:2&lt;/P&gt;&lt;P&gt;srczone: WIFI&lt;/P&gt;&lt;P&gt;dstzone: INTERNET&lt;/P&gt;&lt;P&gt;srcip: x.x.x.x/24&lt;/P&gt;&lt;P&gt;dstip: any&lt;/P&gt;&lt;P&gt;appid: web-browsing&lt;/P&gt;&lt;P&gt;service: TCP80&lt;/P&gt;&lt;P&gt;action: allow&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;just wont work as expected (if you expect the above to do antivirus for ALL traffic and then just allow web-browsing from WIFI to INTERNET) because your WIFI to INTERNET traffic will always match rule1 and rule1 allows any protocol (including unknown) in any direction (mostly a bad idea unless you setup PAN in a new environment and need to learn how the flows goes before you setup default block and only allow whats expected to flow through your PAN).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The correct setup of above would be:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rule:1&lt;/P&gt;&lt;P&gt;srczone: WIFI&lt;/P&gt;&lt;P&gt;dstzone: INTERNET&lt;/P&gt;&lt;P&gt;srcip: x.x.x.x/24&lt;/P&gt;&lt;P&gt;dstip: any&lt;/P&gt;&lt;P&gt;appid: web-browsing&lt;/P&gt;&lt;P&gt;service: TCP80&lt;/P&gt;&lt;P&gt;security: antivirus&lt;/P&gt;&lt;P&gt;action: allow&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also note that if you dont put any last rule there is an "invisible" rule that will drop/deny the traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In order to have such traffic logged you need to manually setup an any/any deny+log rule like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rule:&amp;lt;lastone&amp;gt;&lt;/P&gt;&lt;P&gt;srczone: any&lt;/P&gt;&lt;P&gt;dstzone: any&lt;/P&gt;&lt;P&gt;srcip: any&lt;/P&gt;&lt;P&gt;dstip: any&lt;/P&gt;&lt;P&gt;appid: any&lt;/P&gt;&lt;P&gt;service: any&lt;/P&gt;&lt;P&gt;action: deny&lt;/P&gt;&lt;P&gt;option: log (on session end)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Log on session end is prefered because PAN will then also know transmitted volume, start/end of session, and something else I always forgets (appid?). During debug log on both session start AND session end could be nice but in a large environment will result in shitloads of logs.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Mar 2012 22:32:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/applying-security-policies-with-security-profile-groups/m-p/30136#M22022</guid>
      <dc:creator>mikand</dc:creator>
      <dc:date>2012-03-22T22:32:59Z</dc:date>
    </item>
  </channel>
</rss>

