<?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 PAC Retention and URL Category Priority Behavior in Prisma Access in Strata Cloud Manager</title>
    <link>https://live.paloaltonetworks.com/t5/strata-cloud-manager/pac-retention-and-url-category-priority-behavior-in-prisma/m-p/1247721#M110</link>
    <description>&lt;P&gt;Hello community.&lt;BR /&gt;This is a confirmation regarding Prisma Access (existing contract) for a specific project.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As background, &lt;BR /&gt;we are currently conducting a Proof of Concept (PoC) to verify whether Prisma Access (via Global Protect) can reliably implement the display of the “Information Security Pledge Screen” for external users of our customer.&lt;/P&gt;
&lt;P&gt;This functionality was previously handled by the authentication proxy.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The intended flow is as follows:&lt;BR /&gt;- When an unpledged external user attempts to access the web, the user is redirected to an Override page.&lt;BR /&gt;- From there, the user is redirected to the pledge page.&lt;BR /&gt;- The pledge page itself is configured as Allow.&lt;/P&gt;
&lt;P&gt;After the pledge is completed, subsequent user traffic should be routed through a proxy using a PAC file.&lt;BR /&gt;However, the pledge page cannot be accessed through the proxy, so unpledged user traffic must not use the PAC file.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Question 1: PAC configuration remains in the Global Protect app&lt;/P&gt;
&lt;P&gt;In Prisma Access (Mobile Users):&lt;/P&gt;
&lt;P&gt;1. GP App Configuration #1 (PAC enabled)&lt;BR /&gt;→ After connecting, the Global Protect app correctly retrieves PAC information.&lt;/P&gt;
&lt;P&gt;2. On the same endpoint, we then apply&lt;BR /&gt;GP App Configuration #2 (PAC disabled)&lt;BR /&gt;→ However, the PAC configuration obtained from Configuration #1 still remains on the device, even though the new configuration has PAC disabled.&lt;/P&gt;
&lt;P&gt;Is this the expected behavior?&lt;BR /&gt;If so, is there any method to prevent this, such as automatically clearing / removing the previously applied PAC configuration?&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Question 2: Priority behavior of Custom URL Categories in Prisma Access&lt;/P&gt;
&lt;P&gt;We configured the following Custom URL Categories in Prisma Access:&lt;/P&gt;
&lt;P&gt;- Category ①: * (Action: Override)&lt;BR /&gt;- Category ②: yahoo.co.jp (Action: Allow)&lt;/P&gt;
&lt;P&gt;With this configuration, all traffic matches Category ①, and traffic never matches Category ②.&lt;/P&gt;
&lt;P&gt;Is this the expected behavior?&lt;BR /&gt;If so, is there any recommended method to give precedence to a specific URL (such as yahoo.co.jp) over a wildcard category?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you very much for your support and clarification.&lt;/P&gt;</description>
    <pubDate>Mon, 09 Feb 2026 09:23:37 GMT</pubDate>
    <dc:creator>Y.Nyu149688</dc:creator>
    <dc:date>2026-02-09T09:23:37Z</dc:date>
    <item>
      <title>PAC Retention and URL Category Priority Behavior in Prisma Access</title>
      <link>https://live.paloaltonetworks.com/t5/strata-cloud-manager/pac-retention-and-url-category-priority-behavior-in-prisma/m-p/1247721#M110</link>
      <description>&lt;P&gt;Hello community.&lt;BR /&gt;This is a confirmation regarding Prisma Access (existing contract) for a specific project.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As background, &lt;BR /&gt;we are currently conducting a Proof of Concept (PoC) to verify whether Prisma Access (via Global Protect) can reliably implement the display of the “Information Security Pledge Screen” for external users of our customer.&lt;/P&gt;
&lt;P&gt;This functionality was previously handled by the authentication proxy.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The intended flow is as follows:&lt;BR /&gt;- When an unpledged external user attempts to access the web, the user is redirected to an Override page.&lt;BR /&gt;- From there, the user is redirected to the pledge page.&lt;BR /&gt;- The pledge page itself is configured as Allow.&lt;/P&gt;
&lt;P&gt;After the pledge is completed, subsequent user traffic should be routed through a proxy using a PAC file.&lt;BR /&gt;However, the pledge page cannot be accessed through the proxy, so unpledged user traffic must not use the PAC file.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Question 1: PAC configuration remains in the Global Protect app&lt;/P&gt;
&lt;P&gt;In Prisma Access (Mobile Users):&lt;/P&gt;
&lt;P&gt;1. GP App Configuration #1 (PAC enabled)&lt;BR /&gt;→ After connecting, the Global Protect app correctly retrieves PAC information.&lt;/P&gt;
&lt;P&gt;2. On the same endpoint, we then apply&lt;BR /&gt;GP App Configuration #2 (PAC disabled)&lt;BR /&gt;→ However, the PAC configuration obtained from Configuration #1 still remains on the device, even though the new configuration has PAC disabled.&lt;/P&gt;
&lt;P&gt;Is this the expected behavior?&lt;BR /&gt;If so, is there any method to prevent this, such as automatically clearing / removing the previously applied PAC configuration?&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Question 2: Priority behavior of Custom URL Categories in Prisma Access&lt;/P&gt;
&lt;P&gt;We configured the following Custom URL Categories in Prisma Access:&lt;/P&gt;
&lt;P&gt;- Category ①: * (Action: Override)&lt;BR /&gt;- Category ②: yahoo.co.jp (Action: Allow)&lt;/P&gt;
&lt;P&gt;With this configuration, all traffic matches Category ①, and traffic never matches Category ②.&lt;/P&gt;
&lt;P&gt;Is this the expected behavior?&lt;BR /&gt;If so, is there any recommended method to give precedence to a specific URL (such as yahoo.co.jp) over a wildcard category?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you very much for your support and clarification.&lt;/P&gt;</description>
      <pubDate>Mon, 09 Feb 2026 09:23:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/strata-cloud-manager/pac-retention-and-url-category-priority-behavior-in-prisma/m-p/1247721#M110</guid>
      <dc:creator>Y.Nyu149688</dc:creator>
      <dc:date>2026-02-09T09:23:37Z</dc:date>
    </item>
  </channel>
</rss>

