02.07.2014 Views

State of the Practice of Computer Security Incident Response Teams ...

State of the Practice of Computer Security Incident Response Teams ...

State of the Practice of Computer Security Incident Response Teams ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

-----BEGIN PGP SIGNED MESSAGE-----<br />

version 5.2, April 2000<br />

CERT(R) Coordination Center<br />

<strong>Incident</strong> Reporting Form<br />

CERT/CC has developed <strong>the</strong> following form in an effort to ga<strong>the</strong>r incident information.<br />

If you believe you are involved in an incident, we would appreciate your completing<br />

<strong>the</strong> form below. If you do not believe you are involved in an incident, but have a<br />

question, send email to:<br />

cert@cert.org<br />

Note that our policy is to keep any information specific to your site confidential<br />

unless we receive your permission to release that information.<br />

We would appreciate any feedback or comments you have on this <strong>Incident</strong> Reporting Form.<br />

Please send your comments to:<br />

cert@cert.org<br />

Submit this form to: cert@cert.org<br />

If you are unable to send email, fax this form to: +1 412 268 6989<br />

Your contact and organizational information<br />

1. name......................:<br />

2. organization name.........:<br />

3. sector type (such as banking, education, energy<br />

or public safety).........:<br />

4. email address.............:<br />

5. telephone number..........:<br />

6. o<strong>the</strong>r.....................:<br />

Affected Machine(s)<br />

(duplicate for each host)<br />

7. hostname and IP...........:<br />

8. timezone..................:<br />

9. purpose or function <strong>of</strong> <strong>the</strong> host (please be as specific<br />

as possible)..............:<br />

Source(s) <strong>of</strong> <strong>the</strong> Attack<br />

(duplicate for each host)<br />

10. hostname or IP...........:<br />

11. timezone.................:<br />

12. been in contact?.........:<br />

13. Estimated cost <strong>of</strong> handling incident<br />

(if known)...............:<br />

14. Description <strong>of</strong> <strong>the</strong> incident (include dates, methods <strong>of</strong> intrusion, intruder tools<br />

involved, s<strong>of</strong>tware versions and patch levels, intruder tool output, details <strong>of</strong><br />

vulnerabilities exploited, source <strong>of</strong> attack, or any o<strong>the</strong>r relevant information):<br />

Copyright 2003 Carnegie Mellon University<br />

-----BEGIN PGP SIGNATURE-----<br />

Version: GnuPG v1.0.6 (GNU/Linux)<br />

Comment: For info see http://www.gnupg.org<br />

iQCVAwUBP410w5Z2NNT/dVAVAQGlCgP/WZlEvbsNW04pRytLssVMEPd4RT7qshxssjtdp5IDFAA4RUnC2UxLGI<br />

HCyqihGawK45XUafD26fulh0yPISxg3Ev5b+4u7lM1GKjVcjtA0jtbW7UfQwBpkaPCJuVyhEOMMLRuWNCUF3Id<br />

FoJfuoFrcQ0tTJ26pUkA<br />

MXrIR2S011U=<br />

=xQHt<br />

-----END PGP SIGNATURE-----<br />

Reprinted with permission from <strong>the</strong> CERT® Coordination Center. Available at .

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!