A new Request for Comments is now available in online RFC libraries.


	BCP 21:
	RFC 2350:

	Title:      Expectations for Computer Security Incident
	            Response
	Author(s):  N. Brownlee, E. Guttman
	Status:     Best Current Practice
	Date:       June 1998
	Mailbox:    n.brownlee@auckland.ac.nz, Erik.Guttman@sun.com
   	Pages:      38
        Characters: 86545
        Updates/Obsoletes: None

	pathname on venera.isi.edu: in-notes/rfc2350.txt

The purpose of this document is to express the general Internet
community's expectations of Computer Security Incident Response Teams
(CSIRTs).  It is not possible to define a set of requirements that
would be appropriate for all teams, but it is possible and helpful to
list and describe the general set of topics and issues which are of
concern and interest to constituent communities.  CSIRT constituents
have a legitimate need and right to fully understand the policies and
procedures of 'their' Computer Security Incident Response Team.  One
way to support this understanding is to supply detailed information
which users may consider, in the form of a formal template completed
by the CSIRT.  An outline of such a template and a filled in example
are provided.  This document is a product of the Guidelines and
Recommendations for Security Incident Processing Working Group of the
IETF.

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@ISI.EDU.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute