bugtraq - Re: First vulnerabilities in the SP2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Wed, 18 Aug 2004 23:57:53 -0400
From: Robert Decker <rdecker@...systems.com>
Cc: bugtraq@...urityfocus.com
Subject: Re: First vulnerabilities in the SP2 - XP ?...

As a work around to the issue - although not to easy to configure for 
the home user,

I would think if you have users who are ignorant, gullable, or just 
plain stupid - a windows sysadmin might consider a GPO in AD with one or 
more of the following policies:

User Configuration --> Administrative Templates --> System -->  Prevent 
Access to Command Prompt

User Configuration --> Administrative Templates --> System -->  Run Only 
Allowed Windows Applications

User Configuration --> Administrative Templates --> System -->  Don't 
Run Specified  Windows Applications

Another huge advantage would be the proper implementation of the 
following in an AD GPO:

Configure some Software Restriction Policies in   User Configuration --> 
Windows Settings --> Security Settings --> Software Restrictions

and  if possible, couple it with certificates.  (although, i'm not too 
familiar with this one)

Computer Configuration --> Windows Settings --> Security Settings --> 
Local Policies --> Security Options -->  System settings: Use 
Certificate Rules on Windows Executables for Software Restriction  Policies