<?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 Clarification on how PA process Security profile with applied Service/URL Category in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/clarification-on-how-pa-process-security-profile-with-applied/m-p/561400#M113758</link>
    <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have a quick question and hopefully someone can help me understand how security profile is processed by PA.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I understand that security profile is processed from left to right, then top to bottom. My question is, does all criteria need to match so that the traffic will match the rule? Is the logic used by PA is AND or OR?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Source and destination address&lt;/LI&gt;
&lt;LI&gt;Source ports and destination ports&lt;/LI&gt;
&lt;LI&gt;Applications&lt;/LI&gt;
&lt;LI&gt;User-ID&lt;/LI&gt;
&lt;LI&gt;URL category&lt;/LI&gt;
&lt;LI&gt;Source and destination zones&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 12 Oct 2023 09:23:56 GMT</pubDate>
    <dc:creator>RadianLinog</dc:creator>
    <dc:date>2023-10-12T09:23:56Z</dc:date>
    <item>
      <title>Clarification on how PA process Security profile with applied Service/URL Category</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/clarification-on-how-pa-process-security-profile-with-applied/m-p/561400#M113758</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have a quick question and hopefully someone can help me understand how security profile is processed by PA.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I understand that security profile is processed from left to right, then top to bottom. My question is, does all criteria need to match so that the traffic will match the rule? Is the logic used by PA is AND or OR?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Source and destination address&lt;/LI&gt;
&lt;LI&gt;Source ports and destination ports&lt;/LI&gt;
&lt;LI&gt;Applications&lt;/LI&gt;
&lt;LI&gt;User-ID&lt;/LI&gt;
&lt;LI&gt;URL category&lt;/LI&gt;
&lt;LI&gt;Source and destination zones&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 12 Oct 2023 09:23:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/clarification-on-how-pa-process-security-profile-with-applied/m-p/561400#M113758</guid>
      <dc:creator>RadianLinog</dc:creator>
      <dc:date>2023-10-12T09:23:56Z</dc:date>
    </item>
    <item>
      <title>Re: Clarification on how PA process Security profile with applied Service/URL Category</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/clarification-on-how-pa-process-security-profile-with-applied/m-p/561403#M113761</link>
      <description>&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClVHCA0" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClVHCA0&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This explains how PAN device handles packet and each feature works.&lt;/P&gt;
&lt;P&gt;At beginning of section 3, it says...&lt;/P&gt;
&lt;DIV class="tb f108"&gt;&lt;EM&gt;A&amp;nbsp; firewall session consists of two unidirectional flows, each uniquely identified. In&amp;nbsp;PAN-OS ’s implementation, the firewall identifies the flow using a 6-tuple key:&lt;/EM&gt;&lt;/DIV&gt;
&lt;UL&gt;
&lt;LI class="tb f108"&gt;&lt;EM&gt;&lt;SPAN class="tx f120"&gt;Source and destination addresses: IP addresses from the IP packet.&amp;nbsp;&lt;/SPAN&gt;&lt;/EM&gt;&lt;/LI&gt;
&lt;LI class="tb f108"&gt;&lt;EM&gt;&lt;SPAN class="tx f120"&gt;Source and destination ports:&amp;nbsp; Port numbers from TCP/UDP protocol headers.&amp;nbsp; For non-TCP/UDP, different&amp;nbsp; protocol&amp;nbsp; fields are used (e.g. for ICMP the ICMP identifier and&amp;nbsp;&lt;SPAN class="tx f116"&gt;sequence numbers are used, for IPSec terminating on device the Security Parameter Index (SPI) is used, and for unknown, a constant reserved value is used to skip Layer-4 match).&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/EM&gt;&lt;/LI&gt;
&lt;LI class="tb f108"&gt;&lt;EM&gt;Protocol:&amp;nbsp;The IP protocol number from the IP header is used to derive the flow key . &amp;nbsp;&lt;/EM&gt;&lt;/LI&gt;
&lt;LI class="tb f108"&gt;&lt;EM&gt;Security zone:&amp;nbsp;This field is derived from the ingress interface at which a packet&amp;nbsp;arrives.&lt;/EM&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Other elements you are listing are used after few more packets are traversed.&lt;/P&gt;
&lt;P&gt;Hope this helps you.&lt;/P&gt;</description>
      <pubDate>Thu, 12 Oct 2023 09:44:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/clarification-on-how-pa-process-security-profile-with-applied/m-p/561403#M113761</guid>
      <dc:creator>emr_1</dc:creator>
      <dc:date>2023-10-12T09:44:56Z</dc:date>
    </item>
  </channel>
</rss>

