What is DFIR (digital forensics and incident response)?
DFIR combines digital forensics, which preserves and analyzes evidence, with incident response, which contains and recovers from an attack.
Definition
DFIR
Also called Digital forensics and incident response, Digital forensics, Computer forensics
DFIR (digital forensics and incident response) is the discipline of investigating security incidents by collecting and analyzing digital evidence to establish what happened, while containing the attack and restoring affected systems.
How it works
NIST's glossary, quoting SP 800-86, defines digital forensics as the process used to acquire, preserve, analyze, and report on evidence using scientific methods that are demonstrably reliable, accurate, and repeatable, such that it may be used in judicial proceedings. SP 800-86 itself presents forensics from an IT view rather than a law enforcement view, and covers data sources including files, operating systems, network traffic, and applications.
DFIR joins that discipline to incident response. Responders collect volatile data first (memory, running processes, network connections), then disk images, logs, and cloud audit trails, keeping a chain of custody. Analysts build a timeline from that evidence: initial access, what the attacker ran, which accounts and systems they touched, and what data left. The findings drive containment and eradication and become the incident report.
Example
After an EDR alert on a server, the responder captures memory before isolating it, then images the disk. Memory analysis reveals an injected process and the attacker's command-and-control address. Searching logs for that address finds two more hosts that contacted it, which are pulled into scope before the attacker can move again. The final report documents entry point, dwell time, and data accessed, which legal and compliance teams need.
Why it matters for a SOC
Forensics answers the questions containment alone can't: how the attacker got in, whether they're still present, and what they took. Those answers decide notification obligations and whether eradication actually worked. NIST SP 800-61r3 lists preserving the integrity of incident data, including its provenance, among response activities. For a SOC, DFIR readiness mostly means preparation: keeping logs long enough to reconstruct a timeline, being able to capture memory and disk remotely, and knowing in advance who handles evidence.
Related terms
- Incident responseIncident response is the set of processes an organization uses to detect, analyze, contain, eradicate, and recover from cybersecurity incidents, and to feed what it learns back into its defenses.
- Indicators of compromiseIndicators of compromise (IOCs) are technical artifacts, such as file hashes, IP addresses, domain names, and URLs, that suggest an attack is underway or that a system has already been compromised.
- YARA rulesYARA rules are pattern-matching descriptions of malware or other files, made of text, hexadecimal, or regular expression strings plus a Boolean condition, that the open-source YARA tool uses to identify and classify matching files.
- EDREDR (endpoint detection and response) is security software that records activity on laptops, servers, and other endpoints, detects suspicious behavior in that telemetry, and gives responders tools to investigate and contain affected hosts.
Go deeper
Sources
- SP 800-86, Guide to Integrating Forensic Techniques into Incident Response | CSRC · accessed November 16, 2026
- digital forensics - Glossary | CSRC · accessed November 16, 2026
- NIST SP 800-61 Rev. 3: Incident Response Recommendations and Considerations for Cybersecurity Risk Management · accessed November 16, 2026
