One pro-vote for IIS6 being installed on DC is related to
your Certificate Authority which might be installed on a DC.
The Microsoft Certificate Engine would then by default;
1. try to obtain Certificate Revocation List updates from http
location
2. offer certifcate enrollment for end-users via http
Slawek
Joe Blatz <sd_wireless@yahoo.com> 1/13/2005 08:29 >>>
The security guides published by many sources (NSA,
MS, etc) stated that IIS4 and IIS5 do not belong on
DCs. Common best practices would, in general, guide
that an HTTP (IIS or otherwise) daemon doesn't belong
on DC.
By referring to numerous security guides written
specifically for NT4 and W2k we were able to convince
a customer of this. Now that IIS6 has come out, and
the customer feels that IIS6 is much safer than IIS4
and IIS5, they want to put it back on their DCs.
I am looking for sources that document that this is a
bad idea. When it comes to the NSA they don't have a
guide for W2k3 but have instead pointed to Microsoft's
"Windows Server 2003 Security Guide" and the use of
the "High Security" settings and templates. The MS
guide does (rather subtly) show that IIS should not be
on a DC. They only show the HTTP service enabled on an
IIS server, but I think this may not be direct enough
for our client.
Any help finding an explicit statement that IIS6 does
not be belong on a DC would be greatly appreciated.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------------
---------------------------------------------------------------------------
---------------------------------------------------------------------------
---------------------------------------------------------------------------
