|
Posted by Steven L Umbach on September 26, 2005, 7:29 pm
Please log in for more thread options
I have not used it much myself but SCW so far seems impressive in that it is
tailored to server role and can implement ipsec filtering policy to also
mange outbound access of a computer. The general .inf security templates are
not tailored to a server role. I understand that the SCW can do a rollback
which you can also do with secedit for some security settings but it must be
done manually before you apply the security template locally. I would take
advantage of SCW and then you can use the Security Configuration and
Analysis Tool to check the security settings of the server against a
security template to see if the security setting are what you expect. The
Windows 2003 Server Security Guide [ free at link below] can also be very
helpful in determining how to secure your server by role along with running
MBSA on it. -- Steve
http://www.microsoft.com/technet/security/prodtech/windowsserver2003/W2003HG/SGCH00.mspx
> Writing up a new security policy for 2003 servers. 2003SP1 comes with
> SCW,
> but there's the SCE (since 2000SP4) out there too. I realize they both do
> some different things.
>
> SCE is a bit less user-friendly than SCW which comes with a nice wizard.
>
> These days, what are the risks of having run only SCW on a Windows 2003
> web
> server? Should I still run one of the 'high security' .inf templates from
> SCE on these systems for a 'best effort' against break-ins?
>
> I can't remember the last time we've had a Windows break in, since a
> trojan
> management to get onto a unsecured NT4 box a few years ago.
>
> Marco
>
>
| 
XML Sitemap