Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | RE: Major incident response procedure |
|---|---|
| Date: | Tue, 26 Jul 2005 12:45:17 +0530 |
Get on to Cert.org, probably on this link http://www.sei.cmu.edu/publications/documents/04.reports/04tr015.html Also NIST has something on this topic, I saw sometime back. Regards, Lalit Gupta "LG" Specialist-Information Security IT & IS Department -----Original Message----- From: Smith, Jacqui [mailto:Jacqui.Smith@atosorigin.com] Sent: Monday, July 25, 2005 9:34 PM To: security-management@securityfocus.com Subject: Major incident response procedure
Hi, I wonder if anyone has guidelines on the above subject,
specifically around communications to users and best practices.
Many thanks Jacqui
________________________________________________________________________ __ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. ________________________________________________________________________ __ ##################################################################### THIS EMAIL MESSAGE IS FOR THE SOLE USE OF THE INTENDED RECIPIENT(S) AND MAY CONTAIN CONFIDENTIAL AND PRIVILEGED INFORMATION. ANY UNAUTHORIZED REVIEW, USE, DISCLOSURE OR DISTRIBUTION IS PROHIBITED. BEFORE OPENING ANY ATTACHMENTS PLEASE CHECK FOR VIRUSES AND DEFECTS. IF YOU ARE NOT THE INTENDED RECIPIENT, PLEASE NOTIFY US IMMEDIATELY BY REPLY EMAIL AND DELETE THE ORIGINAL MESSAGE. #####################################################################
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Re: Identification of non Cisco AP's, mox11 |
|---|---|
| Next by Date: | Re: Major incident response procedure, Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP] |
| Previous by Thread: | Re: Major incident response procedure, Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP] |
| Next by Thread: | Identification of non Cisco AP's, Jonathan Gauntt |
| Indexes: | [Date] [Thread] [Top] [All Lists] |