full-disclosure - Re: Security Incident Response Testing To Meet Audit

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]

Date: Fri, 10 Dec 2010 20:52:22 -0800
From: Charles Polisher <cpolish@...il.com>
To: Adam Behnke <adam@...osecinstitute.com>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: Security Incident Response Testing To Meet
	Audit

Adam Behnke wrote:
> Hi everyone, InfoSec Institute author Russ McRee has written up an overview
> on tools to ensure maximum readiness for incident response teams, including
> drill tactics. PCI-DSS audits often require IR testing validation; drill
> quarterly and be ready next audit cycle.
>
> http://resources.infosecinstitute.com/incident-response-and-audit-requirements/
>
> Please let me know your thoughts.

  "Remember that you're playing with binaries that will likely cause
   antivirus to fire."

I take issue with this statement. Tonight I tested $VENDOR's
up-to-date anti-virus against 10 day-old malware samples captured
from the wild - the detection rate was abysmal (225/539).
Maybe your AV is better than mine.

--
Charles Polisher

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/