Linux Incident Response and Digital Forensics
Investigate your own compromised Linux servers without destroying evidence: triage, logs, persistence, suspicious files, disk and memory imaging, timeline, then communication and obligations in Morocco (DGSSI, CNDP).
A MasterLinux course · Original text
What you will learn
- Run the incident response cycle, from preparation to the lessons-learned review
- Collect evidence in order of volatility and keep a chain of custody
- Triage a suspect Linux server (processes, connections, accounts, SSH keys, scheduled tasks, services)
- Read auth.log, journald, wtmp and auditd to find who logged in and what ran
- Hunt persistence (systemd, cron, ld.so.preload, shell profiles, authorized_keys)
- Analyze a suspicious file without running it (hashes, strings, permissions, timestamps)
- Understand disk and memory acquisition and verify image integrity
- Rebuild an attack timeline in UTC from disk and logs
- Communicate during a crisis and meet Moroccan obligations (law 05-20, DGSSI, law 09-08, CNDP)
- Investigate three rewritten real incidents end to end (mining, web shell, added SSH key)
Course content
12 lessons · 11 h 15 minSection 1 — Fundamentals
Section 2 — Triage and logs
Section 3 — Investigation
Section 4 — Obligations and real cases
Section 5 — Final project
Requirements
- Solid hands-on experience with the Linux command line (at least the "Fundamentals" course)
- Able to administer a Debian or Rocky server (services, users, logs)
- Ideally the "Linux Server Hardening" or "SOC Analyst with Wazuh" course
Who is this course for?
- System administrators who must react when one of their servers is compromised
- SOC analysts who want to move from an alert to an on-host investigation
- Students and technicians aiming for an incident response role (CSIRT, CERT, security team)