Educause Security Discussion mailing list archives
Re: Security Incident Handling Procedure
From: "Georgia T. Killcrece" <georgia () CERT ORG>
Date: Fri, 24 Mar 2006 09:04:19 -0500
In addition to the other pointers, Tim, you might look at <http://www.cert.org/security-improvement/modules/m06.html> georgia "--On Friday, March 24, 2006 9:16 AM +1100 Tim Lane <tlane () SCU EDU AU> wrote: "
Hi Folks, I am developing a written procedure "IT Security Incident Handling" to be followed in the event of an incident (mainly virus outbreak or hacking event). Just wondered if anyone has already been down this track and has some developed procedure that they might like to share??? Thanks, Tim Tim Lane Information Security Program Manager Information Technology and Telecommunication Services Southern Cross University PO Box 157 Lismore NSW 2480 (02 6620 3290 7 02 6620 3033 - tlane () scu edu au 8 http://www.scu.edu.au
"" -- Georgia Killcrece CERT(R)-Certified Computer Security Incident Handler CSIRT Development Team CERT(R) Program Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213-3890 U.S.A. Telephone: +1-412-268-5760 Fax: +1-412-268-6989 Key ID: 0xFA1A135E Fingerprint: 0089 77C6 5BEB 810A 1C35 96A5 47A8 F036 FA1A 135E http://www.cert.org/ http://www.cert.org/csirts/ http://www.cert.org/training/ The CERT Coordination Center is part of the Software Engineering Institute (SEI). The SEI is sponsored by the U.S. Department of Defense.
Current thread:
- Security Incident Handling Procedure Tim Lane (Mar 23)
- <Possible follow-ups>
- Re: Security Incident Handling Procedure Melissa Guenther (Mar 23)
- Re: Security Incident Handling Procedure Brad Miller (Mar 23)
- Re: Security Incident Handling Procedure Darlene Quackenbush (Mar 23)
- Re: Security Incident Handling Procedure lists educ (Mar 23)
- Re: Security Incident Handling Procedure Georgia T. Killcrece (Mar 24)
- Re: Security Incident Handling Procedure Brad Miller (Mar 24)
- Re: Security Incident Handling Procedure Glenn Forbes Fleming Larratt (Mar 24)
- Re: Security Incident Handling Procedure Geoffrey S. Nathan (Mar 24)
- Re: Security Incident Handling Procedure Glenn Forbes Fleming Larratt (Mar 24)