<?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: Security Policy using URLs? in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/security-policy-using-urls/m-p/202696#M59774</link>
    <description>&lt;P&gt;Will try that out, thanks!&lt;BR /&gt;Just&amp;nbsp;waiting on&amp;nbsp;a response on the change order first &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 28 Feb 2018 10:21:34 GMT</pubDate>
    <dc:creator>pasmartin</dc:creator>
    <dc:date>2018-02-28T10:21:34Z</dc:date>
    <item>
      <title>Security Policy using URLs?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/security-policy-using-urls/m-p/201525#M59562</link>
      <description>&lt;P&gt;Hello community.&lt;BR /&gt;&lt;BR /&gt;Let's say I have an Atlassian Confluence site that needs to be accessed by a user (or multiple) - is it possible to specify down to the URL to only give the user access to a given set of&amp;nbsp;pages?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Confluence permissions only allow me to give access to entire spaces.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Could be advantageous to allow a general user not tied to a specific person to get access only to a list of URLs in many different spaces, for instance where you would have&amp;nbsp;a consultant or something like that&amp;nbsp;that&amp;nbsp;needs to access some pages spread across the entire space directory.&lt;BR /&gt;&lt;BR /&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 21 Feb 2018 07:38:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/security-policy-using-urls/m-p/201525#M59562</guid>
      <dc:creator>pasmartin</dc:creator>
      <dc:date>2018-02-21T07:38:01Z</dc:date>
    </item>
    <item>
      <title>Re: Security Policy using URLs?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/security-policy-using-urls/m-p/201555#M59566</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/34042"&gt;@pasmartin&lt;/a&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You could create a custom URL category where you configure the URLs you want and then attach this custom URL category directly into the securitypolicy (not in an URL filtering profile). This way the rule allows specific access to the configured URLs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regarding the general user. It's a possibility with advantages and disadvantges, but in general it matters how the firewall gets the User-ID information. If you have a captive portal then is easily possible to have a generic user. But obviously you then have to give this one account to multiple users.&lt;/P&gt;</description>
      <pubDate>Wed, 21 Feb 2018 09:44:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/security-policy-using-urls/m-p/201555#M59566</guid>
      <dc:creator>Remo</dc:creator>
      <dc:date>2018-02-21T09:44:55Z</dc:date>
    </item>
    <item>
      <title>Re: Security Policy using URLs?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/security-policy-using-urls/m-p/202696#M59774</link>
      <description>&lt;P&gt;Will try that out, thanks!&lt;BR /&gt;Just&amp;nbsp;waiting on&amp;nbsp;a response on the change order first &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Feb 2018 10:21:34 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/security-policy-using-urls/m-p/202696#M59774</guid>
      <dc:creator>pasmartin</dc:creator>
      <dc:date>2018-02-28T10:21:34Z</dc:date>
    </item>
  </channel>
</rss>

