SynfraCore
Synfracore
Start Learning
Navigation

Academies

Platform

RoadmapsLabsCertificationsInterviewPYQsAI AssistantCareer
Start Learning Free🗺️ Learning Roadmaps

Incident ResponseCheatsheets

Quick reference — commands, syntax, and patterns

✍️
Written by senior engineers. Reviewed for technical accuracy.· Updated 2025 · SynfraCore Incident Response Team
Expert Content

Incident Response — Quick Reference

NIST IR phases

Preparation → Identification → Containment → Eradication → Recovery → Post-Incident
                                                                              ↓
                                                        (loops back to Preparation)

Severity classification

SeverityDefinitionSLA

|---|---|---|

P1 CriticalActive breach, exfiltration, ransomware15 min
P2 HighSuspicious activity, potential compromise1 hour
P3 MediumPolicy violation, failed attack attempt4 hours
P4 LowInformational, no active threat24 hours

Evidence collection order (critical)

1. Capture volatile evidence FIRST (memory, network connections)
2. THEN contain (isolate the host)
Reversing this order can destroy evidence — memory is lost on power-off,
and fileless malware may exist only in memory.

Chain of custody — required fields

[ ] Item description
[ ] Collected by (name), date/time with timezone
[ ] Collection method (tool + version)
[ ] Storage location + SHA-256 hash at collection time
[ ] Log of every subsequent access (who, when, why)

Forensic acquisition commands

bash
# Memory (before containment)
ftkimager --memory memory_dump.raw
volatility3 -f memory_dump.raw windows.pslist
volatility3 -f memory_dump.raw windows.netscan

# Disk (bit-for-bit copy, never analyze the original)
dd if=/dev/sda of=/evidence/disk_image.dd bs=4M status=progress
sha256sum /dev/sda /evidence/disk_image.dd   # confirm match

Containment commands

bash
# Isolate an EC2 instance
aws ec2 modify-instance-attribute --instance-id i-xxx --groups sg-isolated-only

# Block an IP at the firewall
iptables -A INPUT -s <attacker-ip> -j DROP

Playbook quick reference

Ransomware: Identify scope → isolate immediately (pull cable, don't reboot) → do NOT pay without legal/exec decision → assess backup integrity → notify legal/CISO/leadership/regulators as required

Phishing → credential theft: Identify affected accounts → force password reset → revoke sessions/tokens → check for mail-forwarding rules (persistence) → check for attacker-registered MFA devices → audit sent mail

Data breach: What data + how much + exfiltrated or just accessible → determine notification obligations (GDPR 72h, HIPAA 60d, DPDP Act) → preserve all logs under legal hold

Notification timelines by regulation

RegulationJurisdictionTimeline

|---|---|---|

GDPREU72 hours to supervisory authority
HIPAAUS healthcare60 days to affected individuals
DPDP ActIndiaEvolving — Data Protection Board oversight

Tools by category

CategoryTools

|---|---|

SIEMSplunk, Azure Sentinel, Elastic SIEM
EDRCrowdStrike, SentinelOne, Microsoft Defender
SOARSplunk SOAR, Palo Alto XSOAR
ForensicsVolatility (memory), Autopsy (disk), Wireshark (network)
Threat intelVirusTotal, Shodan, AlienVault OTX

IR metrics

MTTD — Mean Time to Detect (compromise → detection)
MTTR — Mean Time to Respond/Recover (detection → full recovery)
Dwell time — how long attacker had undetected access

Track per incident-type, not as one blended average — a blended
number can hide a severe gap in one specific attack pattern.
Share:
Join our Community
Daily tips, job alerts, interview help — join engineers learning together
Also Worth Exploring
← Back to all Incident Response modules
CertificationNotes