<?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: Can PAN support inbould traffic filtering based on URI? in Automation/API Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/can-pan-support-inbould-traffic-filtering-based-on-uri/m-p/22348#M597</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello John,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can create Custom-Application based on the URI path.&lt;/P&gt;&lt;P&gt;Here is a documentation explaining things.&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" class="active_link" href="https://live.paloaltonetworks.com/docs/DOC-2015"&gt;https://live.paloaltonetworks.com/docs/DOC-2015&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Ameya&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 01 Sep 2012 19:23:41 GMT</pubDate>
    <dc:creator>UhMayYeah</dc:creator>
    <dc:date>2012-09-01T19:23:41Z</dc:date>
    <item>
      <title>Can PAN support inbould traffic filtering based on URI?</title>
      <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/can-pan-support-inbould-traffic-filtering-based-on-uri/m-p/22347#M596</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Environment:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- There is a web server resides on DMZA. Two application URIs: www.url.com/service_1 and www.url.com/service_2, have configured on this web server.&lt;/P&gt;&lt;P&gt;- The DMZA is protected by PAN in vwire mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can PAN fulfill following requirement? If yes, could you please let me know the configuration?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- www.url.com/service_1 can be accessed from the Internet without limitation.&lt;/P&gt;&lt;P&gt;- www.url.com/service_2 can only be accessed from the Internet if the source IP is x.x.x.x&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks a lot.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 01 Sep 2012 14:05:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/automation-api-discussions/can-pan-support-inbould-traffic-filtering-based-on-uri/m-p/22347#M596</guid>
      <dc:creator>John.ZHANG</dc:creator>
      <dc:date>2012-09-01T14:05:08Z</dc:date>
    </item>
    <item>
      <title>Re: Can PAN support inbould traffic filtering based on URI?</title>
      <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/can-pan-support-inbould-traffic-filtering-based-on-uri/m-p/22348#M597</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello John,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can create Custom-Application based on the URI path.&lt;/P&gt;&lt;P&gt;Here is a documentation explaining things.&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" class="active_link" href="https://live.paloaltonetworks.com/docs/DOC-2015"&gt;https://live.paloaltonetworks.com/docs/DOC-2015&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Ameya&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 01 Sep 2012 19:23:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/automation-api-discussions/can-pan-support-inbould-traffic-filtering-based-on-uri/m-p/22348#M597</guid>
      <dc:creator>UhMayYeah</dc:creator>
      <dc:date>2012-09-01T19:23:41Z</dc:date>
    </item>
    <item>
      <title>Re: Can PAN support inbould traffic filtering based on URI?</title>
      <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/can-pan-support-inbould-traffic-filtering-based-on-uri/m-p/22349#M598</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If im not mistaken you can do this in 3 different ways in a PA device:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) Setup a custom URL-category which you attach to each rule (rule1 will allow srcip:any to access service1 and rule2 will only allow srcip:x.x.x.x to access service2).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) Setup a custom APP-ID that will be identified when each service url is being used.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3) Setup a custom IPS signature to trigger if the request doesnt match, and use this custom IPS signature only for the two rules above.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You could of course also combine the methods mentioned above.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The good part with using method 2 above (as example) is that your reports will have these requests as their own line (appid:service1 and appid:service2) - the bad part is that you probably have other files on your webserver which each service will use (lets say background pictures or such using /pics as uri or so) and in those cases you will need to look at several appids to find out for example how much traffic each service uses.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 02 Sep 2012 17:28:11 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/automation-api-discussions/can-pan-support-inbould-traffic-filtering-based-on-uri/m-p/22349#M598</guid>
      <dc:creator>mikand</dc:creator>
      <dc:date>2012-09-02T17:28:11Z</dc:date>
    </item>
  </channel>
</rss>

