full-disclosure - Automating patch deployment

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: <6130FAF67D15D411BF7100E01899071F5F99B1@stork.mightyoaks.local>
From: david.vincent at mightyoaks.com (David Vincent)
Subject: Automating patch deployment

> > The good thing about SUS is that you can set it up to not 
> > push out the packages until you approve them.  The SUS box 
> > downloads all the critical updates and then they sit in queue 
> > until you tell them it's ok to push them out.  I think that's 
> > the best way to handle the situation.  Sure it creates a 
> > little admin work, but I think the advantage is clear.  
> 
> The bad thing about SUS is that it uses Windows Update 
> technology which
> means it can be incorrect when determining if a box needs a 
> patch.  This
> means you can *look* like you're patched when you're not.
> 
> To me, that is unacceptable behavior.

c'mon folks.

if you rely on only one tool to make sure you're patched you deserve what
you get.  security is like an onion - layers upon layers!

-d