CFP: Attacking systems

["Gary McGraw" <gem () cigital com>]

More need for help!

Please contact Ivan and/or me if you're interested in this.

gem

Special issue of IEEE S&P magazine: Attacking Systems
July/August 2004
Deadline: April 4, 2004
For more information see: http://www.computer.org/mc/security/author.htm

Guest editors: Ivan Arce and Gary McGraw
ivan.arce-AT-coresecurity.com  gem-AT-cigital.com

Some security practitioners believe that the only way to know how to
protect a system against attack is to know how attacks really work.
Such people advocate teaching about attacks when building security
expertise, carrying out attacks as part of testing, and thinking and
writing creatively about attacks.  Others feel that discussing,
publishing, and teaching attacks is irresponsible.  Where do you stand?

This special issue is devoted to the idea of attacking systems in order
to better understand how to defend them.  We're looking for a set of
papers exploring the following ideas:
* exploiting software
* attack categories: bugs and flaws
* worms, viruses, and malicious code as an attack vector
* attacking modern extensible systems: Java and .NET
* rootkits, injection vectors, and networked machines
* the politics of breaking systems
* teaching students to break systems (pros and cons)
* ethical hacking, red teaming, and penetration testing
* attack modeling


----------------------------------------------------------------------------
This electronic message transmission contains information that may be
confidential or privileged.  The information contained herein is intended
solely for the recipient and use by any other party is not authorized.  If
you are not the intended recipient (or otherwise authorized to receive this
message by the intended recipient), any disclosure, copying, distribution or
use of the contents of the information is prohibited.  If you have received
this electronic message transmission in error, please contact the sender by
reply email and delete all copies of this message.  Cigital, Inc. accepts no
responsibility for any loss or damage resulting directly or indirectly from
the use of this email or its contents.
Thank You.
----------------------------------------------------------------------------