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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

For more information see:<br />

http://cert.uni-stuttgart.de/projects/caif/<br />

3.10.2.4 Guidelines for Evidence Collection and Archiving (RFC 3227,<br />

Best <strong>Practice</strong>)<br />

This RFC provides high-level guidelines for collecting and archiving data related to an intrusion.<br />

It presents best practice recommendations for determining volatility <strong>of</strong> data, deciding<br />

what to collect, performing <strong>the</strong> collection, and determining how to store and document <strong>the</strong><br />

data. It also brings up topics to consider concerning privacy and legal issues when collecting<br />

intrusion data.<br />

For more information see:<br />

http://www.ietf.org/rfc/rfc3227.txt<br />

3.10.2.5 Australian Standard for Managing IT Evidence (HB-171-2003)<br />

This standard “provides guidance on <strong>the</strong> management <strong>of</strong> electronic records that may be used<br />

as evidence in judicial or administrative proceedings, whe<strong>the</strong>r as a plaintiff, defendant, or<br />

witness.” It specifically deals with litigation in Australia, but is based on general best practices<br />

in forensic evidence collection and IT security [HB171].<br />

For more information see:<br />

http://www.standards.com.au/catalogue/script/Details.asp?DocN=AS342335504743<br />

3.10.2.6 Expectations for <strong>Computer</strong> <strong>Security</strong> <strong>Incident</strong> <strong>Response</strong> (RFC<br />

2350, Best <strong>Practice</strong>)<br />

One <strong>of</strong> <strong>the</strong> older best practice documents that involved CSIRTs was <strong>the</strong> “Expectations for<br />

<strong>Computer</strong> <strong>Security</strong> <strong>Incident</strong> <strong>Response</strong>” RFC. This document provides guidance on <strong>the</strong> type <strong>of</strong><br />

information that should be published to a CSIRT’s constituency and to o<strong>the</strong>r CSIRTs. It discusses<br />

defining <strong>the</strong> CSIRT’s mission, charter, constituency, services, policies, and procedures.<br />

For more information see:<br />

http://www.ietf.org/rfc/rfc2350.txt<br />

3.10.3 <strong>Incident</strong> Data Collection<br />

New teams are always looking for tools to not only help <strong>the</strong>m collect incident data but also to<br />

compare how <strong>the</strong>ir incident activity compares with o<strong>the</strong>r sites and organizations. During an<br />

incident, a team will <strong>of</strong>ten need to determine if what <strong>the</strong>y are seeing is limited to <strong>the</strong>ir systems<br />

or is more widespread. Various organizations have been developing tools or mecha-<br />

124 CMU/SEI-2003-TR-001

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

Saved successfully!

Ooh no, something went wrong!