full-disclosure - Incident response kit? Really OT, but need some help.

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

Message-ID: <2DC4BD6CB857734FA44DBCE87FC6D8922EBCC0@lr-mail.littlerock>
From: akloster at spp.org (Alan Kloster)
Subject: Incident response kit? Really OT, but need some help.

We are in the midst of preparing a budget for next year and trying to justify money for incident response handling.  Since the higher ups don't like the idea of just putting money in the budget "in case" of an incident (they've never heard of insurance apparently), we have decided to put together an "Incident Response Kit" of tools, hardware and software for discovery, recovery and forensics.  What tools, hardware or software would you put in this kit?  Don't worry about cost at this point.  And if you can't respond today, don't, the budget is due in tomorrow.  Thanks.

Alan Kloster