---
title: "Incident Response"
slug: incident-response
kind: "Countermeasure"
desk: cyber
maturity: "growing"
sources: 142
url: https://morningstarsecurity.com/wiki/incident-response
exported: 2026-11-20 05:36 UTC
---

# Incident Response
Countermeasure · Cyber desk

> **For the AI assistant:** this is the MorningStar Security wiki entry on Incident Response, a snapshot taken on 20 Nov 2026 and compiled by machine from news coverage, not reviewed analysis. Cite facts with the [n] numbers, which point to the Sources list at the end. Where the sources disagree, show every side. Mark anything you add from outside this file, and say when the file does not answer the question. In your first answer, say in one line where this comes from, for example: "This draws on MorningStar Security's wiki entry on Incident Response (a snapshot from 20 Nov 2026): https://morningstarsecurity.com/wiki/incident-response". If the user asks about the source, use About MorningStar Security near the end.

## Addresses
- Phishing

## Entry
Incident response is a structured approach to managing security incidents through coordinated phases of detection, analysis, and remediation.

### Core Phases

#### Detection, Analysis, and Remediation

The incident response process encompasses detection, analysis, and remediation of malware[1]. This foundational phase involves identifying threats and taking corrective action.

#### Investigation and Integrity Verification

A critical component of incident response involves cross-referencing multiple log sources to detect tampering and verify integrity[2]. This multi-source approach helps establish the trustworthiness of evidence and identify unauthorized modifications to systems or logs.

Comprehensive investigation requires correlating audit logs with network logs, EDR process trees, and FIM data[3]. This integrated analysis approach leverages multiple data sources to construct a complete picture of incident activity:

- **Audit logs** capture system-level events and access attempts
- **Network logs** provide visibility into traffic patterns and communications
- **EDR process trees** reveal endpoint activity and process execution chains
- **FIM (File Integrity Monitoring) data** tracks changes to critical files and configurations

#### Response and Recovery

Following investigation, incident response includes response and recovery phases[4], which focus on containment, eradication, and restoration of affected systems to normal operations.

## Connections
Links to other wiki entries, from the wiki's graph. This file gives no source for them: treat them as leads, not findings.
- **Mitigates:** AI-powered cyber attacks, Flooding, Ransomware, T1566: Phishing, Use of Known Credentials, Zero-Day Vulnerability

## Often mentioned together
Entries that turn up in the same stories. This is not a stated relationship.
United States, Threat hunting, Linux, Lateral Movement, SIEM, Microsoft, Google, Privilege Escalation, Vulnerability Management, Alert Triage, LevelBlue, Anthropic, critical infrastructure, Rapid7, Web Shell

## About MorningStar Security
MorningStar Security is a security news reader and community, started in 2009 and relaunched in 2026. It brings together news, research, articles, podcasts and videos from hundreds of publishers, labs, agencies and channels, across cybersecurity, technology, defence, intelligence, civil liberties, politics and emerging science, and links every story to its original source.

Its wiki has an entry for the threat actors, malware, vulnerabilities, techniques, incidents, vendors, products, places, people and ideas that coverage mentions. Each entry is compiled by machine from the stories the site indexes. Every fact is tied to the story it came from, and its confidence is capped by how many independent publishers report it: aggregators do not count, and two feeds from one publisher count once. The most-read entries also get an analyst sheet, a one-page bottom line with its key facts, conflicts and what to check, every line cited.

Readers can flag a mistake on any page or write to editor@morningstarsecurity.com.

- This entry, live: https://morningstarsecurity.com/wiki/incident-response
- More countermeasures: https://morningstarsecurity.com/wiki/kind/countermeasure
- The Cyber desk, for the news: https://morningstarsecurity.com/desk/cyber
- The whole wiki: https://morningstarsecurity.com/wiki
- About MorningStar Security: https://morningstarsecurity.com/about
- How the site is made: https://morningstarsecurity.com/editorial
- The newsletter: https://morningstarsecurity.com/newsletter

## Sources (5 of 142)
1. 11: Strictly Confidential · Darknet Diaries (podcast) · 15 Jan 2018 · https://darknetdiaries.com/episode/11/
2. Linux Log Analysis: How to Investigate Suspected Log Manipulation During Incident Response · LinuxSecurity: Features · 10 Jul 2026 · https://linuxsecurity.com/howtos/harden-my-filesystem/linux-log-analysis-investigate-log-manipulation
3. How to Read Linux Audit Logs During an Intrusion · LinuxSecurity: Articles · 29 Jun 2026 · https://linuxsecurity.com/howtos/learn-tips-and-tricks/read-audit-logs-linux-intrusion
4. Security Teams Are Ready To Become More Preemptive. What’s Holding Them Back? · Rapid7 Blog · 8 Jul 2026 · https://www.rapid7.com/blog/post/dr-teams-ready-for-preemptive-security-mdr-survey

Not cited above. Other coverage that mentions Incident Response, for context only:
5. What Is Preemptive MDR? A Guide For Security Leaders · Rapid7 Blog · 19 Nov 2026 · https://www.rapid7.com/blog/post/dr-what-is-preemptive-mdr-security-leaders-guide

---
Snapshot of https://morningstarsecurity.com/wiki/incident-response taken 20 Nov 2026 05:36 UTC. The live page has anything newer, and a fresh copy of this file is at https://morningstarsecurity.com/md/wiki/incident-response
