There is a one-way or two-way trust relationship between Windows NT domains.

A Windows NT account policy has inappropriate, security-critical settings for lockout, e.g. lockout duration, lockout after bad logon attempts, etc.

The HKEY_CLASSES_ROOT key in a Windows NT system has inappropriate, system-critical permissions.

The HKEY_LOCAL_MACHINE key in a Windows NT system has inappropriate, system-critical permissions.

A Windows NT system's registry audit policy does not log an event success or failure for non-critical registry keys.

A Windows NT system's registry audit policy does not log an event success or failure for security-critical registry keys.

A Windows NT system's file audit policy does not log an event success or failure for non-critical files or directories.

A Windows NT system's file audit policy does not log an event success or failure for security-critical files or directories.

A Windows NT system's user audit policy does not log an event success or failure, e.g. for Logon and Logoff, File and Object Access, Use of User Rights, User and Group Management, Security Policy Changes, Restart, Shutdown, and System, and Process Tracking.

.reg files are associated with the Windows NT registry editor (regedit), making the registry susceptible to Trojan Horse attacks.

A router's configuration service or management interface (such as a web server or telnet) is configured to allow connections from arbitrary hosts.

Windows NT is not using a password filter utility, e.g. PASSFILT.DLL.

A URL for a WWW directory allows auto-indexing, which provides a list of all files in that directory if it does not contain an index.html file.

rpc.admind in Solaris is not running in a secure mode.

An attacker can write to syslog files from any location, causing a denial of service by filling up the logs, and hiding activities.

A Sendmail alias allows input to be piped to a program.

An attacker can force a printer to print arbitrary documents (e.g. if the printer doesn't require a password) or to become disabled.

The registry in Windows NT can be accessed remotely by users who are not administrators.

IIS has the #exec function enabled for Server Side Include (SSI) files.

A system-critical Windows NT file or directory has inappropriate permissions.