idnits 2.17.1 draft-ietf-grip-prot-evidence-05.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 BCP 55 4 RFC 3227 6 Title: Guidelines for Evidence Collection and Archiving 7 Author(s): D. Brezinski, T. Killalea 8 Status: Best Current Practice 9 Date: February 2002 10 Mailbox: dbrezinski@In-Q-Tel.org, tomk@neart.org 11 Pages: 10 12 Characters: 18468 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-ietf-grip-prot-evidence-05.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3227.txt 19 A "security incident" as defined in the "Internet Security Glossary", 20 RFC 2828, is a security-relevant system event in which the system's 21 security policy is disobeyed or otherwise breached. The purpose of 22 this document is to provide System Administrators with guidelines on 23 the collection and archiving of evidence relevant to such a security 24 incident. 26 If evidence collection is done correctly, it is much more useful in 27 apprehending the attacker, and stands a much greater chance of being 28 admissible in the event of a prosecution. 30 This document specifies an Internet Best Current Practices for the 31 Internet Community, and requests discussion and suggestions for 32 improvements. Distribution of this memo is unlimited. 34 This announcement is sent to the IETF list and the RFC-DIST list. 35 Requests to be added to or deleted from the IETF distribution list 36 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 37 added to or deleted from the RFC-DIST distribution list should 38 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 40 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 41 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 42 help: ways_to_get_rfcs. For example: 44 To: rfc-info@RFC-EDITOR.ORG 45 Subject: getting rfcs 47 help: ways_to_get_rfcs 49 Requests for special distribution should be addressed to either the 50 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 51 specifically noted otherwise on the RFC itself, all RFCs are for 52 unlimited distribution.echo 53 Submissions for Requests for Comments should be sent to 54 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 55 Authors, for further information.