full-disclosure - Getting the lead out of broken virus / worm email meta-reporting

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]

From: scroutinizer at beeb.net (The Central Scroutinizer)
Subject: Getting the lead out of  broken virus / worm email meta-reporting

> How fast is fast? The time it takes an av, spyware or firewall
> company to react to a real-time threat.   I think there is going
> to have to be a pooling of anti-virus, mail sweeping and firewall
> protection knowledge.   There should be a central policy that
> can be reported and distributed to the various vendors and
> clients that autoupdates the protecting software.  Simply a
> crisis-mail-alert with appropriate information for translation into a 
> protecting shield that updates all av, mail and firewall
> utilities.
>
> Has anyone written or read a spec. on standardizing worm, virus
> or other alerts with not just there's a'sploit, but a method of
> reporting the 'sploit or adware, malware in a way that the
> vendors and clients could instantly counter with a new filter or
> fix?

See :-

http://www.eeye.com/html/Research/Advisories/
http://www.cve.mitre.org/

I agree there should be an open standard and common public libraries of 
exploits and fixes.

Aaron