I use to have a DMZ but we opened so mony holes it didn't make since. I am now in the process or going back to having a DMZ. I welcome comments on the need for a DMZ (pro or con)
The new DMZ will be built on a single physical Windows 2008 Server with multiple VMs running in Hyper-V.
It will have Exchange Edge Transport (which uses AD LDS (the new ADAM) to communicate with the Hub Transport on LAN - but I don't know if this AD LDS will handle other application authentications (I don't really have a good grip on ADAM or AD LDS). IIS 7, WSS v3, MOSS, and ColdFusion 8 - all of which will need authentication against current AD - my ColdFusion apps use a deprecated tag (cfntauthenication) that basically LDAPS the AD for user credentials over port 339 - I could open the port but wonder if AD FS or AD LDS was a more secure route) and a SQL 2005 server that supports the web applications.
So I am looking fo a good step-by-step deployment guide - or some detail (don't under estimate my ignorance) pointers on what to do - or possible a good argument for why a DMZ is not necessary.
DMZ is accessed off multi-port Astaro 220 firewall - no ISA server
Start Free Trial