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.

Type and Title <strong>of</strong><br />

Publication<br />

Author(s)<br />

Step or Process<br />

Material Covered and/or<br />

O<strong>the</strong>r Comments<br />

that were available to assist <strong>the</strong> incident<br />

handling process.<br />

The Methodology<br />

<strong>of</strong> <strong>Incident</strong> Handling<br />

<strong>Security</strong> Architecture<br />

and <strong>Incident</strong><br />

Management for<br />

E-business<br />

<strong>Incident</strong> <strong>Response</strong><br />

and Reporting<br />

Procedure for<br />

<strong>State</strong> Government<br />

<strong>State</strong> <strong>of</strong> Vermont<br />

<strong>Incident</strong> Handling<br />

Procedure<br />

RFC 2196 Site<br />

<strong>Security</strong> Handbook<br />

Mat<strong>the</strong>w<br />

McGlashan, Australian<br />

<strong>Computer</strong><br />

Emergency <strong>Response</strong><br />

Team<br />

[McGlashan 01]<br />

Internet <strong>Security</strong><br />

Systems<br />

[Sokol 00]<br />

<strong>State</strong> <strong>of</strong><br />

Nebraska<br />

[Nebraska 02]<br />

<strong>State</strong> <strong>of</strong><br />

Vermont<br />

[Vermont 01]<br />

Barbara Fraser,<br />

Editor<br />

[Fraser 97]<br />

Identify scope and<br />

assess damage<br />

Communicate<br />

Collect and protect<br />

Apply short-term<br />

solutions<br />

Eliminate intruder<br />

access<br />

Return to normal<br />

operations<br />

Identify and implement<br />

lessons learned<br />

<strong>Incident</strong> preparedness<br />

Alerting<br />

Report and notification<br />

Preliminary investigation<br />

Decision and resource<br />

allocation<br />

<strong>Response</strong><br />

Recovery<br />

Lessons learned<br />

Detect <strong>the</strong> incident<br />

Analyze <strong>the</strong> incident<br />

Contain or eradicate <strong>the</strong><br />

problem<br />

Provide workarounds or<br />

fixes<br />

Prevent re-infection<br />

Log events<br />

Preserve evidence<br />

Conduct a postmortem/<br />

apply lessons learned<br />

Protect<br />

Identify<br />

Contain<br />

Eradicate<br />

Recover<br />

Follow-up<br />

Notification & exchange<br />

<strong>of</strong> information<br />

Protect evidence and<br />

activity logs<br />

Containment<br />

Eradication<br />

Recovery<br />

Follow-up<br />

High level; slide presentation<br />

Provides a high-level overview <strong>of</strong><br />

best practices for <strong>the</strong> development<br />

<strong>of</strong> an incident response process.<br />

A draft report summarizing <strong>the</strong><br />

guidelines for CIO Cyberthreat <strong>Response</strong><br />

and reporting (applicable to<br />

non-education state agencies,<br />

boards, and commissions receiving<br />

appropriation from <strong>the</strong> state Legislature,<br />

or state agencies that have direct<br />

connection to <strong>the</strong> state’s network.<br />

An interim guideline for incident<br />

response within <strong>the</strong> <strong>State</strong> <strong>of</strong> Vermont.<br />

Revised version <strong>of</strong> RFC 1244. Provides<br />

practical guidance for administrators<br />

on developing computer<br />

security policies and procedures.<br />

154 CMU/SEI-2003-TR-001

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

Saved successfully!

Ooh no, something went wrong!