I have a somewhat general question. I have a customer who will be implementing a web site for the registration of park district users. It will provide information but will also take credit card info so that the users can sign up for various programs that the park district offers.
Now normally I would get a Pix 515 or bigger, create a DMZ and put the web server in it. But this web server will need to interact with a transaction server on the inside network (for the above mentioned info and credit cards). The application calls for quite a few ports to be opened between the DMZ and the Inside network. Obviously, I will need to lockdown the web server, but I'm just not comfortable with the amount of open ports, etc.
Is there a better way? I had considered Microsoft's method which is to put an ISA server in the DMZ which would VPN through the DMZ to inside interface (I would open the appropriate ports)and connect to another ISA server there. But if the web server is attacked and penetrated I now have a clear shot to my inside network.
Sounds to me like your planning on using the DMZ like it's suppose to be used. A malicious user first would have to attack the DMZ server through what ever ports it's allowed to get to. They would have to stage a second attack from the DMZ to the inside network. If you add aditional layers of security like IPS to inspect that traffic and Host IPS to watch the behavior of your applications you shouldn't have any problems.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...