Incident response on a hacked Linux server: logs to report
9 steps · about 4 h 50 min · Intermediate
- Practical Incident Response Guidance from NIST SP 800-61 (article, Armorpoint, 10 min)
It gives you the four-phase lifecycle that every later step hangs on.
- Computer Security Incident Handling Guide (SP 800-61 Rev. 2) (doc, NIST, 40 min)
This is the original standard behind the lifecycle. Read Section 3 on detection, analysis, containment and the handling checklist. NIST has since withdrawn Rev. 2 in favour of Rev. 3.
- Linux Incident Response: A Comprehensive Tutorial (tutorial, hackernoob.tips, 20 min)
It applies the lifecycle to Linux: baselines, which log files matter, and how to scope an attack.
- Linux Incident Response Playbook: Detection, Containment, and Recovery (guide, bariskode, 25 min)
Its triage steps for logins, processes and network connections show how to look without changing the system.
- Handling a Breach on a Linux Server - Essential Actions to Take (guide, LinuxSecurity, 15 min)
It covers collecting volatile evidence (processes, connections, logs) before you contain or rebuild.
- How to Detect and Respond to a Compromised Linux Server (guide, Infotechys, 30 min)
It collects indicators of compromise, journalctl queries and timeline-building commands in one place.
- Linux Log Analysis: Investigate Suspected Log Manipulation During Incident Response (article, LinuxSecurity, 15 min)
Attackers edit logs, so this teaches you to spot wiped or truncated logs and cross-check against external sources.
- Compromised_Server_Project: Linux Server Hardening & Incident Response (repo, GitHub (obinnambazi8-sys), 45 min)
You can run the grep commands yourself on a sample auth log from a brute-forced server, then draft the report.
- Incident Response with journald (interactive, Techlogia, 1 h 30 min)
This hands-on lab has you filter logs, build an attack timeline, isolate the service and write a report.