<?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: New to Palo Alto from Juniper SSG in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/new-to-palo-alto-from-juniper-ssg/m-p/23923#M17431</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Gavin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, you will achieve this with both NAT and security policy. NAT policy will let you define the mapped ports and IP. That means if some-one comes for 1.1.1.1 on 443 translate it to 192.168.10.1 on 4443. Then on security policy you would say access to 1.1.1.1 is possible only with ssl application. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So if someone wants to access 1.1.1.1 anything other than ssl, it will be denied.&amp;nbsp; NAT on PA device is little different and unconventional. You can follow following documents for further information :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/videos/1550"&gt; Video Link : 1550&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/videos/1438"&gt; Video Link : 1438&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please note that destination NAT might be bit different as the zones are determined as per routing on pre-natted address. Hope this helps. Thank you&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 07 Oct 2014 14:13:12 GMT</pubDate>
    <dc:creator>ssharma</dc:creator>
    <dc:date>2014-10-07T14:13:12Z</dc:date>
    <item>
      <title>New to Palo Alto from Juniper SSG</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/new-to-palo-alto-from-juniper-ssg/m-p/23922#M17430</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;I was wondering if someone could enlighten me on how to replicate the Mapped IP functionality from Juniper SSG to Palo Alto.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;We have a number of services on our current Juniper SSG.&amp;nbsp; The way we firewall these services is using MIP's on the Untrust Zone then the traffic passing from Untrust to Trust using standard juniper policies.&amp;nbsp; I was playing around with the Palo Alto and it seems its as easy as setting up an address on the Untrust Zone and Trust Zone.&amp;nbsp; Then allowing the traffic based on the App-ID.&amp;nbsp; Can someone explain this to me please?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;Apologies for the noob question.&amp;nbsp; But gotta start somewhere eh?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;Cheers&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Oct 2014 13:29:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/new-to-palo-alto-from-juniper-ssg/m-p/23922#M17430</guid>
      <dc:creator>GavinPalmer</dc:creator>
      <dc:date>2014-10-07T13:29:10Z</dc:date>
    </item>
    <item>
      <title>Re: New to Palo Alto from Juniper SSG</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/new-to-palo-alto-from-juniper-ssg/m-p/23923#M17431</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Gavin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, you will achieve this with both NAT and security policy. NAT policy will let you define the mapped ports and IP. That means if some-one comes for 1.1.1.1 on 443 translate it to 192.168.10.1 on 4443. Then on security policy you would say access to 1.1.1.1 is possible only with ssl application. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So if someone wants to access 1.1.1.1 anything other than ssl, it will be denied.&amp;nbsp; NAT on PA device is little different and unconventional. You can follow following documents for further information :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/videos/1550"&gt; Video Link : 1550&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/videos/1438"&gt; Video Link : 1438&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please note that destination NAT might be bit different as the zones are determined as per routing on pre-natted address. Hope this helps. Thank you&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Oct 2014 14:13:12 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/new-to-palo-alto-from-juniper-ssg/m-p/23923#M17431</guid>
      <dc:creator>ssharma</dc:creator>
      <dc:date>2014-10-07T14:13:12Z</dc:date>
    </item>
    <item>
      <title>Re: New to Palo Alto from Juniper SSG</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/new-to-palo-alto-from-juniper-ssg/m-p/23924#M17432</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/u1/29978"&gt;GavinPalmer&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Welcome to forums.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I might be wrong but I think in screen OS you specified the NAT in the security policy itself which was from Untrust to Trust if your server is located in Trust.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But in PaloAlto, you will be creating two policies one for NAT and the other for security policy and the tricky part being NAT policy will be from Untrust to Untrust with destination as public IP of your server. Also the security policy will be from Untrust to Trust with destination as public IP of your server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let us know if you face any issues.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Oct 2014 16:00:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/new-to-palo-alto-from-juniper-ssg/m-p/23924#M17432</guid>
      <dc:creator>bat</dc:creator>
      <dc:date>2014-10-07T16:00:14Z</dc:date>
    </item>
    <item>
      <title>Re: New to Palo Alto from Juniper SSG</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/new-to-palo-alto-from-juniper-ssg/m-p/23925#M17433</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In ScreenOS on the SSG the MIP is a bidirectional static nat object mapping one ip address to another.&amp;nbsp; In PanOS you use the "Static nat" option to achieve the same result in your nat rule.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/docs/DOC-1553"&gt;What does the Bi-Directional NAT Feature Provide?&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When creating the static nat rule write the rule from the perspective of your internal server going out to the external zone.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/docs/DOC-1517"&gt;Understanding PAN-OS NAT&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 11 Oct 2014 11:07:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/new-to-palo-alto-from-juniper-ssg/m-p/23925#M17433</guid>
      <dc:creator>pulukas</dc:creator>
      <dc:date>2014-10-11T11:07:33Z</dc:date>
    </item>
    <item>
      <title>Re: New to Palo Alto from Juniper SSG</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/new-to-palo-alto-from-juniper-ssg/m-p/23926#M17434</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I believe Steven is correct.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, welcome to PANOS. &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://live.paloaltonetworks.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt; I used to have to manage a couple SSGs back in the day. I found it to be painful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Oct 2014 14:21:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/new-to-palo-alto-from-juniper-ssg/m-p/23926#M17434</guid>
      <dc:creator>SDorsey</dc:creator>
      <dc:date>2014-10-13T14:21:53Z</dc:date>
    </item>
    <item>
      <title>Re: New to Palo Alto from Juniper SSG</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/new-to-palo-alto-from-juniper-ssg/m-p/23927#M17435</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Steve,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ok thats great.&amp;nbsp; I have created the static NAT policy but now need to create a security policy for it.&amp;nbsp; will the direction of the sec policy be Untrust to Trust or Untrust to Untrust?&amp;nbsp; For example, to allow smtp to our exchange server, this comes in over a static public IP.&amp;nbsp; So should the security policy read, Untrust &amp;lt;ANY&amp;gt; -&amp;gt; Trust &amp;lt;exchange_internal&amp;gt; or Untrust &amp;lt;ANY&amp;gt; -&amp;gt; Untrust &amp;lt;exchange_public_ip&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Oct 2014 14:47:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/new-to-palo-alto-from-juniper-ssg/m-p/23927#M17435</guid>
      <dc:creator>GavinPalmer</dc:creator>
      <dc:date>2014-10-21T14:47:49Z</dc:date>
    </item>
    <item>
      <title>Re: New to Palo Alto from Juniper SSG</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/new-to-palo-alto-from-juniper-ssg/m-p/23928#M17436</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Gavin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Security policy should be Untrust to Trust.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And unidirectional NAT should be Untrust to Untrust.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If its bi-directional NAT than, it should be Trust to untrust.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Hardik Shah&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Oct 2014 14:50:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/new-to-palo-alto-from-juniper-ssg/m-p/23928#M17436</guid>
      <dc:creator>hshah</dc:creator>
      <dc:date>2014-10-21T14:50:31Z</dc:date>
    </item>
    <item>
      <title>Re: New to Palo Alto from Juniper SSG</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/new-to-palo-alto-from-juniper-ssg/m-p/23929#M17437</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I do have a bi-directional NAT setup for smtp.&amp;nbsp; but how can the traffic be trust to untrust when smtp mail flow comes in from the untrust zone?&amp;nbsp; I dont understand this.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Oct 2014 15:02:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/new-to-palo-alto-from-juniper-ssg/m-p/23929#M17437</guid>
      <dc:creator>GavinPalmer</dc:creator>
      <dc:date>2014-10-21T15:02:17Z</dc:date>
    </item>
    <item>
      <title>Re: New to Palo Alto from Juniper SSG</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/new-to-palo-alto-from-juniper-ssg/m-p/23930#M17438</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Gavin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you create one Bi-directional NAT, PAN breaks the NAT rule into two which looks like this(Bidirectional from Trust to Untrust):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"Trust-Untrust-Bidirectional NAT" {&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; from trust-L3;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; source 192.168.18.1;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; to untrust-L3;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; to-interface&amp;nbsp; ;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; destination any;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; service&amp;nbsp; any/any/any;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; translate-to "src: 10.10.10.10 (static-ip) (pool idx: 5)";&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; terminal no;&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"Trust-Untrust-Bidirectional NAT" {&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; from any;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; source any;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; to untrust-L3;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; to-interface&amp;nbsp; ;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; destination 10.10.10.10;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; service&amp;nbsp; any/any/any;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; translate-to "dst: 192.168.18.1";&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; terminal no;&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This can be seen in the CLI command "show running nat-policy".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Dileep&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Oct 2014 15:36:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/new-to-palo-alto-from-juniper-ssg/m-p/23930#M17438</guid>
      <dc:creator>dreputi</dc:creator>
      <dc:date>2014-10-21T15:36:55Z</dc:date>
    </item>
    <item>
      <title>Re: New to Palo Alto from Juniper SSG</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/new-to-palo-alto-from-juniper-ssg/m-p/254187#M72157</link>
      <description>&lt;P&gt;Can you give an example for DIP NAT policy &amp;amp; security&amp;nbsp; policy, MIP i undestand with your below comment. also DST with NAT &amp;amp; SEC policy&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Mar 2019 12:32:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/new-to-palo-alto-from-juniper-ssg/m-p/254187#M72157</guid>
      <dc:creator>Ismail_Mohammed</dc:creator>
      <dc:date>2019-03-19T12:32:01Z</dc:date>
    </item>
  </channel>
</rss>

