Subscribe to Windows IT Pro
July 01, 1998 12:00 AM

NT Server Security Checklist

Windows IT Pro
InstantDoc ID #3571
Rating: (6)
Steps to address NT's security weaknesses

Windows NT systems have been the subject of much attention lately. I'm not talking about the latest Microsoft public relations campaign extolling NT's virtues, I'm talking about the full-scale security war that hackers are waging against the NT operating system (OS). Several denial-of-service and NT password gathering and hacking utilities such as GetAdmin, RedButton, and TearDrop2-based programs have appeared during the past year. These utilities expose holes in NT's architecture and maliciously attack NT systems in various ways. The hackers and NT security experts who develop these programs are causing some real headaches for Microsoft, as well as enterprises and NT administrators. What was intended as a useful and necessary campaign to expose holes in NT's security architecture has rapidly escalated into a security hole witch hunt.

All the negative publicity about NT's security holes is frightening. After all, who wants to run an OS that's easy to hack? However, NT is very securable. Notice I didn't say secure, I said securable. NT gives you several tools to secure your servers and workstations against many types of attacks. However, Microsoft doesn't enable most NT security features by default, even when you install Service Pack 3 (SP3--for information about SP3 and NT security, see Mark Joseph Edwards, "Service Pack 3 Is Really Security Pack 3," August 1997). Contrary to popular belief, you can't just install the latest Microsoft service pack and walk away. Although installing the latest patches is a good start, you need to implement a comprehensive set of policies and procedures to address various weaknesses in NT and networked PCs as a whole.

Every new denial-of-service attack and security-cracking utility (and the subsequent fixes Microsoft has issued to thwart them) has made NT more secure. Although NT users have to suffer through interim periods in which the OS is defenseless against a particular type of attack, Microsoft has been quick to respond with updates (i.e., service packs and hotfixes) that patch the affected system components.

To effectively address the latest security concerns, you need to develop a comprehensive NT systems security checklist that covers the most important aspects of maintaining a secure NT network environment. In this article, I'll give you security tips to help you audit your system configurations and take the necessary steps to improve the security of your environment.

Contact Info
Enterprise Administrator
Mission Critical Software * 713-548-1700 or 800-814-9130
Web: http://www.missioncritical.com
Kane Security Analyst for Windows NT and Kane Security Monitor for Windows NT
Intrusion Detection Systems * 212-348-8900 or 800-408-6104
Web: http://www.intrusion.com
L0phtCrack 2.0
L0pht Heavy Industries
Web: http://www.L0pht.com
RealSecure, Internet Scanner, and System Security Scanner
Internet Security Systems * 678-443-6000
Web: http://www.iss.net

Related Content:

ARTICLE TOOLS

Comments
  • Anonymous User
    7 years ago
    Jan 27, 2005

    fh

  • John Hall
    13 years ago
    Aug 11, 1999

    I liked Sean Daily’s informative “NT Server Security Checklist” (July). I’m unclear about one point. Can I remove lm-fix (which Microsoft has removed from its Web site) and still have the Windows 95 clients log on successfully to the Windows NT servers?

    --John Hall



    Even with lm-fix installed, Windows 95 and Win3.x clients can log on successfully. Unless you’ve set LMCompatibilityLevel (in the HKEY_LOCAL_MACHINE\\SYSTEMCurrentControlSet\\Control\\Lsa Registry key) to 2, these clients will still be able to successfully log on to the NT server. If you’ve set the value to 2, you can either reset it to 1 (send LM authentication only if the server requests it) or 0 (send LM authentication always), or simply remove the hotfix from the server.
    Glad to hear you liked the article. For more information about lm-fix, see “Lm-fix: Now You See It, Now You Don’t,” page 132.

    --Sean Daily

You must log on before posting a comment.

Are you a new visitor? Register Here

advertisement

advertisement

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.