secplus

Dashboard / 4.0 Security Operations

4.8 Explain appropriate incident response activities

Official exam objective outline (6 topics)
  • Process
    • Preparation
    • Detection
    • Analysis
    • Containment
    • Eradication
    • Recovery
    • Lessons learned
  • Training
  • Testing
    • Tabletop exercise
    • Simulation
  • Root cause analysis
  • Threat hunting
  • Digital forensics
    • Legal hold
    • Chain of custody
    • Acquisition
    • Reporting
    • Preservation
    • E-discovery

Breakdown 1 — Events vs. incidents (class)

An event is anything observable (a login, a blocked packet). An incident is an event (or set of events) that actually violates policy or harms C/I/A. Event evaluation sorts them — and can be wrong:

  • False positive — benign event mistaken for a problem (wastes time; too many → alert fatigue).
  • False negative — real problem mistaken for benign (the dangerous miss).
Alarm raisedNo alarm
Real problemTrue positive — problem detectedFalse negative — missed incident (BAD)
No problemFalse positive — wrong alarm (tolerable; tune it)True negative — correctly quiet

★ Starred in your notes (Day 5): dd tool → forensic image of a hard drive; use a write blocker (prevents writes, makes the source read-only).

Breakdown 2 — The IR process (memorize the order)

PhaseWhat happensKeywords
1 PreparationPolicies, IR plan, playbooks, tools, trained team, contacts, backups"before anything happens"
2 DetectionNotice the incident (SIEM alert, user report, threat hunt)"identify"
3 AnalysisScope it: what, how, which systems, is it real? Triage severity"determine impact"
4 ContainmentStop the bleeding — isolate hosts, disable accounts, block IPs; short-term vs. long-term"limit damage"
5 EradicationRemove the cause — delete malware, close the vulnerability, rebuild"remove"
6 RecoveryRestore systems/data to production, monitor closely for reinfection"return to normal"
7 Lessons learnedPost-incident review; update plan/controls; root cause analysis"improve"
1 Preparation 2 Detection 3 Analysis 4 Containment 5 Eradication 6 Recovery 7 Lessonslearned feeds back into preparation: update playbooks, controls, training "Stop the bleeding" (contain) before "remove the cause" (eradicate) before "return to normal" (recover).

From class — NIST's 4-phase version of the same cycle: Preparation → Detection & Analysis → Containment, Eradication & Recovery (loops back to detection as you learn more) → Post-incident activity. CompTIA splits the middle phases out into the 7 above; the order is the same. Root cause analysis → find the underlying cause, not just the symptom.

Training everyone on their role; testing with tabletop exercises (discussion) and simulations (hands-on drills). Threat hunting = proactively searching for compromise before an alert fires, using intel and hypotheses (class: threat-hunting tactics — AI can help sift the data).

Breakdown 3 — Attack models used in analysis (class: know them)

Cyber Kill Chain: Reconnaissance → Weaponization → Delivery → Exploitation → Installation → Command & Control → Actions on Objectives. Detecting early (recon/delivery) is cheaper than late (actions).

Diamond Model: Adversary · Infrastructure · Capability · Victim — link the four to pivot from one indicator to the others.

MITRE ATT&CK: catalog of tactics/techniques (initial access, persistence, privilege escalation, lateral movement, exfiltration…).

Breakdown 4 — Digital forensics

TermMeaning
Legal holdPreserve all relevant data (suspend deletion/retention) when litigation is anticipated
Chain of custodyDocumented who handled evidence, when, why — unbroken, or it's inadmissible; hash checking proves the copy matches the original (class)
AcquisitionCollect evidence in order of volatility: CPU/registers → RAM/cache → network state/processes → disk → backups/archives → printouts. Memory dumping first, then a bit-for-bit disk image with dd ★ through a write blocker; hash the image
PreservationWrite blockers, hashed copies, secure storage; work on copies
ReportingFindings, methods, timeline — in plain language, reproducible
E-discoveryProducing electronic records for legal proceedings — must be done in a way that is legal (class); if legal requires it, files must be retained longer (retention + legal hold)

Exam tip: "First step after confirming ransomware on a host" → containment (isolate). "Analyst reviewed the incident and updated the playbook" → lessons learned. "Which should be collected first?" → RAM (most volatile). "Evidence thrown out in court" → broken chain of custody. "Lawsuit is likely — don't delete emails" → legal hold. "Proactively look for attackers without an alert" → threat hunting.

Quick self-check

  • Order of the seven IR phases?
  • Containment vs. eradication? (Stop spread vs. remove cause.)
  • Most volatile evidence? (CPU registers/RAM.)

Sources: 20260917_173205.jpg, 20260917_173216.jpg, 20260918_175529.jpg, 20260918_175538.jpg