bctgroup
Posts: 30
Joined: 29.Nov.2005
From: Paul Welsh
Status: offline
|
Currently I have a setup that looks a bit like this. I have 2 ISA 2004 firewalls, each with 2 NICs, each connected to a separate Internet connection: Internet1 ---- ISA1 ----| |----- Internal Network, 2 x IIS Servers Internet2 ---- ISA2 ----| The 2 connections are for redundancy and to separate traffic. One connection, an 8 Mb ADSL, is used for web browsing and the other, a 2 Mb leased line, is for incoming traffic to our 2 x IIS servers, one of which is live and the other test/backup. As you'll notice, there's no DMZ. This is because I was persuaded by the "swiss cheese" argument that Microsoft use and that Tom quotes in his article: "you have to make cheese out of the firewall to allow intradomain communications, or use an IPSec tunnel through the firewall, so there’s no sense in having a firewall there at all”. Our IIS servers connect to (a) a SQL Server and (b) a file server so yes, I would have to make some "holes" in the DMZ to allow this traffic. The SQL Server connection will always be required. However, there are plans at some later date to change the code in the web app so as to use a web service rather than having to allow the CIFS protocol through. Internal clients also connect to the IIS servers. The application on the IIS servers authenticate internal users via Active Directory, so there's another hole in the firewall were a DMZ implemented. I'm thinking about implementing a DMZ for another IIS server that I'm rolling out shortly. This will also need access to a SQL db and to Active Directory. It will run SurfControl's Mobile Filter. In terms of access from the outside world, only port 80 will need to be open. In terms of the network topology, it would look like this, with each ISA server having a 3rd NIC and both of them connected to the DMZ. In the event of one Internet connection going down, the hosts on the DMZ would have their default gateways changed to go via the alternative Internet connection. Naturally we'd use DNS failover to point external users to the alternative ISA server if there was a problem with one of the connections. Internet1 ---- ISA1 -------| | | | | | --DMZ | ----- Internal Network | | | | | | Internet2 ---- ISA2 -------| My questions are as follows: 1. Is there any merit in the swiss cheese argument? I can clearly see the benefits of a DMZ for "standalone" web servers that don't communicate with the Internal network except in limited circumstances or, say, an SMTP server, but in my case there's a good deal of traffic between the internal network and the IIS servers - SQL, Active Directory, CIFS. 2. Tom's topology has an edge ISA server and a network services perimeter ISA firewall. In my situation, I don't think I can justify the expenditure of another server, 2003 Server licence and ISA 2004 licence in order to have a network services perimeter ISA firewall. Does this make a difference as to whether or not to go with a DMZ?
|