<?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: https on PIX in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/https-on-pix/m-p/609677#M497282</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Lorenzo,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your question "..need to permit traffic to application layer https?" - are you referring to how to permit https traffic for application access from outside to inside?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If this is you're looking at, pls see example below:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What you need to do is to map your internal server IP (running application accessible via https) to a public IP and use access -list (ACL) to allow only HTTPS to pass through from outside to inside/internal (to your internal server). Once ready, bind the ACL to the outside interface. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list outside permit tcp any host xx.xx.xx.10 eq https  &amp;lt;--- access-list allowing incoming https traffic only&lt;/P&gt;&lt;P&gt;access-list outside deny ip any any  &amp;lt;-- deny other unwanted traffic. Make sure this parameter is the last one in your ACL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-group outside in interface outside    &amp;lt;-- bind ACL outside to your outside (eth0) interface&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) xx.xx.xx.10 aa.aa.aa.50 netmask 255.255.255.255  &amp;lt;--- map you aa.aa.aa.50 (internal server IP) to a public IP&lt;/P&gt;&lt;P&gt;route outside 0 0 xx.xx.xx.1  &amp;lt;---- default route for PIX pointing to your internet router&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Test connectivity using ICMP/ping from outside (ping from internet router or internet) to your server temporary opening the ICMP in the same outside ACL. Remove this if ping is successful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list outside permit icmp any host xx.xx.xx.10&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rgds,&lt;/P&gt;&lt;P&gt;AK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 27 Sep 2006 00:36:55 GMT</pubDate>
    <dc:creator>a.kiprawih</dc:creator>
    <dc:date>2006-09-27T00:36:55Z</dc:date>
    <item>
      <title>https on PIX</title>
      <link>https://community.cisco.com/t5/network-security/https-on-pix/m-p/609676#M497281</link>
      <description>&lt;P&gt;I have installed some PIX 501 with 6.3&lt;/P&gt;&lt;P&gt;software Cisco Secure.&lt;/P&gt;&lt;P&gt;I need to permit traffic to application layer https.&lt;/P&gt;&lt;P&gt;Does somebody advice me about configuration command or documents&lt;/P&gt;&lt;P&gt;about ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;best regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Lorenzo&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 09:11:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/https-on-pix/m-p/609676#M497281</guid>
      <dc:creator>lformelli</dc:creator>
      <dc:date>2020-02-21T09:11:42Z</dc:date>
    </item>
    <item>
      <title>Re: https on PIX</title>
      <link>https://community.cisco.com/t5/network-security/https-on-pix/m-p/609677#M497282</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Lorenzo,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your question "..need to permit traffic to application layer https?" - are you referring to how to permit https traffic for application access from outside to inside?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If this is you're looking at, pls see example below:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What you need to do is to map your internal server IP (running application accessible via https) to a public IP and use access -list (ACL) to allow only HTTPS to pass through from outside to inside/internal (to your internal server). Once ready, bind the ACL to the outside interface. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list outside permit tcp any host xx.xx.xx.10 eq https  &amp;lt;--- access-list allowing incoming https traffic only&lt;/P&gt;&lt;P&gt;access-list outside deny ip any any  &amp;lt;-- deny other unwanted traffic. Make sure this parameter is the last one in your ACL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-group outside in interface outside    &amp;lt;-- bind ACL outside to your outside (eth0) interface&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) xx.xx.xx.10 aa.aa.aa.50 netmask 255.255.255.255  &amp;lt;--- map you aa.aa.aa.50 (internal server IP) to a public IP&lt;/P&gt;&lt;P&gt;route outside 0 0 xx.xx.xx.1  &amp;lt;---- default route for PIX pointing to your internet router&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Test connectivity using ICMP/ping from outside (ping from internet router or internet) to your server temporary opening the ICMP in the same outside ACL. Remove this if ping is successful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list outside permit icmp any host xx.xx.xx.10&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rgds,&lt;/P&gt;&lt;P&gt;AK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Sep 2006 00:36:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/https-on-pix/m-p/609677#M497282</guid>
      <dc:creator>a.kiprawih</dc:creator>
      <dc:date>2006-09-27T00:36:55Z</dc:date>
    </item>
  </channel>
</rss>

