Forensicswiki.org has moved to this site, forensicswiki.xyz. For information, please join the Google Group forensicswiki-reborn
Incident Response is a set of procedures for an investigator to examine a computer security incident. This process involves figuring out what was happened and preserving information related to those events. Because of the fluid nature of computer investigations, incident response is more of an art than a science.
Incident response tools can be grouped into three categories. The first category is Individual Tools. These are programs designed to probe parts of the operating system and gather useful and/or volatile data. The tools are self-contained, useful, discrete, and do not create a large footprint on the victim system.
Standalone tools have been combined to create Script Based Tools. These tools combine a number of standalone tools that are run via a script or batch file. They require minimal interaction from the user and gather a fixed set of data. These tools are good in that they automate the incident response process and provide the examiner with a standard process to defend in court. They also do not require the first responder to necessarily be an expert with the individual tools. Their weakness, however, is that they can be inflexible. Once the order of the tools is set, it can be difficult to change. Some script based tools allow the user to pick and choose which standalone tools will be used in a given examination.
The final category of tools are Agent Based Tools. These tools require the examiner to install a program on the victim which can then report back to a central server. The upshot is that one examiner can install the program on multiple computers, gather data from all of them, and then view the results in the aggregate. Finding the victim or victims can be easier if they stand out from the crowd.
- Preservation of Fragile Digital Evidence by First Responders, by Jesse Kornblum, DFRWS 2002
- Journey to the Centre of the Breach, by Ben Downton, June 2, 2010
- Keeping Focus During an Incident, by jackcr, January 17, 2014
- Addressing emergency response provider fatigue in emergency response preparedness, management, policy making, and research, Clark J. Lee, JD, September 2011
- Intelligence-Driven Computer Network Defense Informed by Analysis of Adversary Campaigns and Intrusion Kill Chains, by Eric M. Hutchins, Michael J. Clopperty, Rohan M. Amin, March 2011
- Stalking the kill chain, by RSA
- APT Kill chain - Part 1 : Definition, by Cedric Pernet, April 28, 2014
- APT Kill chain - Part 2 : Global view, by Cedric Pernet, May 7, 2014
- APT Kill chain - Part 3: Reconnaissance, by Cedric Pernet, May 23, 2014
- APT Kill chain - Part 4 : Initial compromise, by Cedric Pernet, June 20, 2014
- APT Kill chain - Part 5 : Access Strenghtening and lateral movements, by Cedric Pernet, December 2, 2014
- Expanding the Expanded Incident Lifecycle, by Janet Kuhn, February 18, 2009
- Incident lifecycle, by ENISA
- The Diamond Model of Intrusion Analysis, by Sergio Caltagirone, Andrew Pendergast, Christopher Betz
- Palantir: A Framework for Collaborative Incident Response and Investigation, Himanshu Khurana, Jim Basney, Mehedi Bakht, Mike Freemon, Von Welch, Randy Butler, April 2009
Script Based Tools
Agent Based Tools
There are several books available that discuss incident response. For Windows, Windows Forensics and Incident Recovery by Harlan Carvey is an excellent introduction to possible scenarios and how to respond to them.