Defining Incident Management Processes for CSIRTs: A Work in Progress

This report presents a prototype best practice model for performing incident management processes and functions. It defines the model through five high-level incident management processes: Prepare/Sustain/Improve, Protect Infrastructure, Detect Events, Triage Events, and Respond. Workflow diagrams and descriptions are provided for each of these processes.

One advantage of the model is that it enables examination of incident management processes that cross organizational boundaries, both internally and externally. This can help computer security incident response teams (CSIRTs) improve their ability to collaborate with other business units and other organizations when responding to incidents.

Future reports will extend this work and provide additional guidance to enable both newly forming and existing incident management capabilities to use the model to determine where gaps exist in their current processes and to develop plans for creating, improving, or restructuring their incident management processes.

Although the processes defined in this document were originally developed for internal CSIRTs, the models and information presented here are applicable to other types of CSIRTs and other types of incident management and security management capabilities.

PDF [1533 KB]

Authors

Christopher J. Alberts (CERT)

Audrey J. Dorofee

Georgia Killcrece

Robin Ruefle

Mark Zajicek

This report is related to the following area(s) of work:

Security and Survivability

Technical Report
CMU/SEI-2004-TR-015
October 2004

Cite This Report

SEI:

Alberts, Christopher; Dorofee, Audrey; Killcrece, Georgia; Ruefle, Robin; & Zajicek, Mark. Defining Incident Management Processes for CSIRTs: A Work in Progress (CMU/SEI-2004-TR-015). Software Engineering Institute, Carnegie Mellon University, 2004. http://www.sei.cmu.edu/library/abstracts/reports/04tr015.cfm

IEEE:

C. Alberts, A. Dorofee, G. Killcrece, R. Ruefle, and M. Zajicek, "Defining Incident Management Processes for CSIRTs: A Work in Progress," Software Engineering Institute, Carnegie Mellon University, Pittsburgh, Pennsylvania, Technical Report CMU/SEI-2004-TR-015, 2004. http://www.sei.cmu.edu/library/abstracts/reports/04tr015.cfm

APA:

Alberts, C., Dorofee, A., Killcrece, G., Ruefle, R., & Zajicek, M. (2004). Defining Incident Management Processes for CSIRTs: A Work in Progress (CMU/SEI-2004-TR-015). Retrieved May 25, 2013, from the Software Engineering Institute, Carnegie Mellon University website: http://www.sei.cmu.edu/library/abstracts/reports/04tr015.cfm

CHI:

Alberts, Christopher, Audrey Dorofee, Georgia Killcrece, Robin Ruefle, and Mark Zajicek. Defining Incident Management Processes for CSIRTs: A Work in Progress (CMU/SEI-2004-TR-015). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2004. http://www.sei.cmu.edu/library/abstracts/reports/04tr015.cfm

MLA:

Alberts, C., Dorofee, A., Killcrece, G., Ruefle, R., & Zajicek, M. 2004. Defining Incident Management Processes for CSIRTs: A Work in Progress (Technical Report CMU/SEI-2004-TR-015). Pittsburgh: Software Engineering Institute, Carnegie Mellon University. http://www.sei.cmu.edu/library/abstracts/reports/04tr015.cfm

Find Us Here

Find us on Youtube  Find us on LinkedIn  Find us on twitter  Find us on Facebook

Share This Page

Share on Facebook  Send to your Twitter page  Save to del.ico.us  Save to LinkedIn  Digg this  Stumble this page.  Add to Technorati favorites  Save this page on your Google Home Page 

For more information

Contact Us

info@sei.cmu.edu

412-268-5800

Help us improve

Visitor feedback helps us continually improve our site.

Please tell us what you
think with this short
(< 5 minute) survey.