<?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: PIX 515E question RE: https access in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-515e-question-re-https-access/m-p/390707#M609958</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What you have done is fine, you can remove your first rule (www) only if you want to prevent anyone from accessing your web site using HTTP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It doesn't matter whether you use "eq 443" or "eq https" on the PIX as it will interpret either correctly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;PD&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 16 Dec 2004 16:21:08 GMT</pubDate>
    <dc:creator>paddyxdoyle</dc:creator>
    <dc:date>2004-12-16T16:21:08Z</dc:date>
    <item>
      <title>PIX 515E question RE: https access</title>
      <link>https://community.cisco.com/t5/network-security/pix-515e-question-re-https-access/m-p/390706#M609957</link>
      <description>&lt;P&gt;We have a web server in our dmz allowing http access to an application.  We have installed SSL and now want to change our application access to https.  I'm having a little trouble with the config.  Here's the relevant config info:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inbound permit tcp any host x.x.x.110 eq www&lt;/P&gt;&lt;P&gt;static (dmz,outside) x.x.x.110 x.x.x.110 netmask 255.255.255.255 0 0&lt;/P&gt;&lt;P&gt;access-group inbound in interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have added:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inbound permit tcp any host x.x.x.110 eq https&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My questions are:  Is this sufficient to allow https access to my application?  Do I need to remove the access-list . . . www command?  Would I be better served by changing my new access-list command from eq https to eq 443?  Is there anything else I need to add to insure access?  Have I missed anything?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, Ben&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 07:48:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-515e-question-re-https-access/m-p/390706#M609957</guid>
      <dc:creator>bhhouston</dc:creator>
      <dc:date>2020-02-21T07:48:44Z</dc:date>
    </item>
    <item>
      <title>Re: PIX 515E question RE: https access</title>
      <link>https://community.cisco.com/t5/network-security/pix-515e-question-re-https-access/m-p/390707#M609958</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What you have done is fine, you can remove your first rule (www) only if you want to prevent anyone from accessing your web site using HTTP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It doesn't matter whether you use "eq 443" or "eq https" on the PIX as it will interpret either correctly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;PD&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Dec 2004 16:21:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-515e-question-re-https-access/m-p/390707#M609958</guid>
      <dc:creator>paddyxdoyle</dc:creator>
      <dc:date>2004-12-16T16:21:08Z</dc:date>
    </item>
    <item>
      <title>Re: PIX 515E question RE: https access</title>
      <link>https://community.cisco.com/t5/network-security/pix-515e-question-re-https-access/m-p/390708#M609959</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hello Ben,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You need configure the nat statement. The nat command will define for what networks firewall will  route.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The command is some thing like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (inside) 0 x.y.z.110 255.255.255.255 0 0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Kratz&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Dec 2004 16:23:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-515e-question-re-https-access/m-p/390708#M609959</guid>
      <dc:creator>d.kratz</dc:creator>
      <dc:date>2004-12-16T16:23:25Z</dc:date>
    </item>
    <item>
      <title>Re: PIX 515E question RE: https access</title>
      <link>https://community.cisco.com/t5/network-security/pix-515e-question-re-https-access/m-p/390709#M609960</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the replys.  It appears that my addition will take care of my access and I can take http access away by removing the www statement.  That's just the kind of information I was looking for.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Oh, and my NAT statement was already in place so I think I'm good there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again and if you think of anything else that would help me, feel free to add something.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Two thumbs up to the Cisco forums.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ben&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Dec 2004 18:39:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-515e-question-re-https-access/m-p/390709#M609960</guid>
      <dc:creator>bhhouston</dc:creator>
      <dc:date>2004-12-16T18:39:24Z</dc:date>
    </item>
  </channel>
</rss>

