RFC 2350: Expectations for Computer Security Incident Response
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC2350
- Published
- June 1998
- Authors
- N. Brownlee; E. Guttman
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- ops
- Pages
- 38
- Also known as
- BCP21
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2548Microsoft Vendor-specific RADIUS AttributesCurrent
March 1999
- RFC 2619RADIUS Authentication Server MIBObsoleted
June 1999
- RFC 2620RADIUS Accounting Client MIBObsoleted
June 1999
- RFC 2621RADIUS Accounting Server MIBObsoleted
June 1999
- RFC 2059RADIUS AccountingObsoleted
January 1997
- RFC 2809Implementation of L2TP Compulsory Tunneling via RADIUSCurrent
April 2000
- RFC 2866RADIUS AccountingUpdated
June 2000
- RFC 8199YANG Module ClassificationCurrent
July 2017
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?