| | RFC 2350 - Expectations for Computer Security Incident Response (Site not responding. Last check: 2007-11-07) |
 | | While no recommendations are made as to what a CSIRT should adopt for its policy or procedures, different possibilities are outlined to give Brownlee and Guttman Best Current Practice [Page 7] RFC 2350 Expectations for Computer Security Incident Response June 1998 some examples. |
 | | Brownlee and Guttman Best Current Practice [Page 9] RFC 2350 Expectations for Computer Security Incident Response June 1998 3.3 Charter Every CSIRT must have a charter which specifies what it is to do, and the authority under which it will do it. |
 | | Depending on the objectives and services of a particular CSIRT, multiple forms may be used, for example a reporting form for a new vulnerability may be very different from the form used for reporting Brownlee and Guttman Best Current Practice [Page 16] RFC 2350 Expectations for Computer Security Incident Response June 1998 incidents. |
| www.packetizer.com /rfc/rfc.cgi?num=2350 (9774 words) |