| Javascript Feeds RSS Feed Security Dashboard | SearchSecurity.com |
|
Hardening Windows 2000 in the Enterprise: Seeing the Forest in Spite of the Trees Part Three Well, we are finally here. Over the first two installments of this series, we've been building up to this part, and I must say, I'm excited. Though we've covered quite a bit in the way of security settings on Win2k, we have really only scratched the surface of a deeply powerful policy management system. The Local Security Policy can take us part of the way, but it can't deliver us safely to where we really want to go: a place called "security". Of course, security is a relative term: it doesn't really mean anything by itself - we have to compare it to something. For these discussions, it will be a "before and after" comparison of our systems of when they come out of the box and how they are after an effective Group Policy is applied.
03/20/2004
|
|
Hardening Windows 2000 in the Enterprise Part Two: This is the second article in a three-part series devoted to hardening Windows 2000 across the enterprise, as opposed to focusing on individual servers or workstations. In the first installment, I discussed some of the security-enhancing tools that Windows 2000 offers, such as: Active Directory, Organizational Units, Security and Group Policies, and Security Configuration and Analysis. This article takes us right to the security policy options that can be used to strengthen our Win2k installations.
03/20/2004
|
|
Hardening Windows 2000 in the Enterprise Part One: In Windows 2000, this has all changed. At the risk of receiving some "what are you smoking?" emails, I will go so far as to say that not only is administering a Win2k enterprise easy, but it is fun too! And that is what this series of articles is all about: securing your Win2k enterprise. Note the word 'enterprise'; that means not just servers, but workstations too! I have seen many documents telling me what settings to use on a server to "harden" it in Win2k, but that is only part of the battle. Properly controlling what the workstations can do and, more importantly, what they can't do is crucial to the concept of a secure environment. This series won't just talk about WHAT to configure, but HOW to configure it.
03/20/2004
|
|
Using Scripts to Exploit and Mitigate Risks It’s fairly common knowledge that batch files, or scripts, can be used to automate many mundane and tedious tasks. It is not said enough, however, that scripts can create risks. On the lighter side, you can also use scripts to help mitigate risks. If you are an administrator utilizing multiple Microsoft® platforms, perhaps you should consider how well your network is protected. We’ll cover how scripts can best help you and your unique situations by covering some of the commands that really make a script what it is; powerful. Rather than talking solely about how to automate tasks, we’ll take a deeper look at script-automation and see how we can use it for the forces of good - and how it can be turned to evil.
03/16/2004
|
|
NSA Windows NT Configuration Guide National Security Agency (NSA) guide for configuring Cisco routers in a secure manner.
03/08/2004
|
|
NSA Windows 2000 Configuration Guide National Security Agency (NSA) document for installing Microsoft Windows 2000 in a secure manner.
03/08/2004
|
|
Page: 123 4 |
