full-disclosure - Verifying patches on MS servers

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>] [day] [month] [year] [list]

Message-ID: <84EA00803F398243AD22BF36134C87D5A33878@srvexch01.federatedinv.com>
From: FederatedInformationSecurity at federatedinv.com (Federated Information Security)
Subject: Verifying patches on MS servers

I've got a server that broke and had to be patched by uninstalling and
reinstalling a bunch of software, including various patches and maybe
even a service pack.  What's my best way to scan the server to make sure
no outdated .dlls were laid down or restored?  If I'm not mistaken, most
microsoft tools check the registry, which might not be accurate in this
case.  My options right now are ISS internet scanner, nessus, MBSA et
al, which is best?