Linux Endpoint Investigation
Master Linux Endpoint Investigation
Respond decisively when Linux systems are under attack. Learn a proven forensic methodology to investigate, contain, and eradicate threats in Linux, cloud, and container environments, turning complex incidents into structured, defensible investigations.
What you'll be able to do
Course Syllabus
Every module and every lesson. Open a module to see its lessons.
Download the full syllabus (PDF)
Phase 1: Foundations
What Linux Endpoint Investigation teaches: a proven forensic method to investigate, contain, and eradicate threats across Linux servers, cloud VMs, and containers.
11 lessonsHide lessons
- LX0.1 Why Linux IR Breaks Windows-Trained AnalystsPreview
- LX0.2 How a Linux Compromise Actually UnfoldsPreview
- LX0.3 The Linux Evidence Landscape and Order of VolatilityPreview
- LX0.4 Everything Is a File: The Forensic ConsequencePreview
- LX0.5 Reading the Authentication and System LogsPreview
- LX0.6 Where Attackers Hide: A First Look at PersistencePreview
- LX0.7 The Linux IR LifecyclePreview
- LX0.8 Measuring What Matters in Linux IRPreview
- LX0.9 The Environment This Course ReferencesPreview
- LX0.10 Course Toolkit and Lab SetupPreview
- LX0.11 Interactive: Triage a Compromised HostPreview
The architectural model a Linux investigator must hold before any applied technique makes sense: the filesystem and inode model, the four timestamps, the user and permission model, the process model, how the kernel...
11 lessonsHide lessons
- LX1.1 The Linux Filesystem Model
- LX1.2 Inodes and the Four Timestamps
- LX1.3 Users, Groups, and the Permission Model
- LX1.4 The Process Model
- LX1.5 How the Kernel Exposes the Running System
- LX1.6 Memory and the Running System
- LX1.7 Live Host versus Disk Image
- LX1.8 The Boot and Service Model
- LX1.9 Interactive: Mapping the Foundations to an Investigation
- Module Summary
- Check My Knowledge
Phase 2: Evidence and Analysis
Applied filesystem investigation on the two filesystems that dominate Linux estates: ext4 and xfs.
13 lessonsHide lessons
- LX2.1 The Filesystem on Disk: ext4 and xfs for Investigators
- LX2.2 Timestamp Forensics at Depth: Beneath stat and Into the Inode
- LX2.3 Deleted File Recovery: What Comes Back, What Does Not
- LX2.4 Timeline Generation: From Bodyfile to Super-Timeline
- LX2.5 Attacker Staging Areas: Where Intruders Work
- LX2.6 SUID, SGID, and Capability Indicators on Disk
- LX2.7 User Artifact Forensics: History, Keys, and the Home Directory
- LX2.8 Anti-Forensics Detection: Reading the Cleanup
- LX2.9 The Filesystem Investigation Workflow
- LX2.10 Acquiring the Disk Image
- LX2.11 Complex Disk Geometries
- Module Summary
- Check My Knowledge
The Linux logging architecture from an investigator's seat: syslog, journald, and auditd, what each captures and how to query it, authentication-log analysis for SSH and sudo, journald and auditd as forensic sources...
11 lessonsHide lessons
- LX3.1 The Linux Logging Architecture
- LX3.2 Authentication Log Analysis
- LX3.3 Journald Investigation
- LX3.4 Auditd Forensics
- LX3.5 Web Server Log Analysis
- LX3.6 System, Service, and Application Logs
- LX3.7 Cross-Log Correlation
- LX3.8 Log Integrity and Tampering Detection
- LX3.9 The Log Analysis Workflow
- Module Summary
- Check My Knowledge
Phase 3: Compromise Scenarios
How a Linux server gets breached, and how you prove which way it happened.
10 lessonsHide lessons
- LX4.1 The Two Entry Vectors
- LX4.2 Scoping the SSH Compromise
- LX4.3 Finding the SSH Breach Point
- LX4.4 The Web Application Vector
- LX4.5 Web Shells and Reverse Shells
- LX4.6 Application and Error Logs as Exploit Evidence
- LX4.7 Comparing the Two Vectors
- LX4.8 The Initial-Access Investigation Workflow
- Module Summary
- Check My Knowledge
What an attacker does after the foothold, and how you reconstruct all of it.
11 lessonsHide lessons
- LX5.1 The Post-Foothold Arc
- LX5.2 Escalation Vectors
- LX5.3 Reconstructing the Escalation Chain
- LX5.4 Persistence: Accounts, Keys, and Scheduled Jobs
- LX5.5 Persistence: Services and Shell Initialization
- LX5.6 Persistence: Library, PAM, and Kernel
- LX5.7 Lateral Movement: Trust, Pivots, and Config Management
- LX5.8 Lateral Movement: Credential Reuse and Internal Services
- LX5.9 The Multi-Host Campaign
- Module Summary
- Check My Knowledge
Incident response when the host is no longer the whole story.
14 lessonsHide lessons
- LX6.1 The Cloud and Container Investigation Surface
- LX6.2 Cloud-Native Evidence and Its Volatility
- LX6.3 The Instance Metadata Entry Vector
- LX6.4 IAM Credential Abuse and Cloud Enumeration
- LX6.5 Cloud Data Exfiltration
- LX6.6 Container Runtime and the Image Supply Chain
- LX6.7 Kubernetes Audit Logs and Service-Account/RBAC Abuse
- LX6.8 Container Escape to the Node
- LX6.9 Cloud Persistence and Cryptojacking
- LX6.10 The Cross-Environment Campaign
- LX6.11 ESXi Host Forensics
- LX6.12 vCenter and the Blast Radius
- Module Summary
- Check My Knowledge
Phase 4: Live Response and Deep Analysis
Investigating the evidence that exists only in RAM, and reverse-engineering what you recover.
12 lessonsHide lessons
- LX7.1 Why Memory Is Ground Truth
- LX7.2 Acquiring Memory Without Destroying It
- LX7.3 Building the Picture: Process and Profile Analysis
- LX7.4 Recovering What the Rootkit Hid
- LX7.5 Pulling Evidence From RAM
- LX7.6 Memory Timeline and the Disk Cross-Check
- LX7.7 Static Malware Triage for IR
- LX7.8 Dynamic Analysis in a Sandbox
- LX7.9 IOCs and YARA
- LX7.10 Memory and Malware Campaign
- LX7.11 Module Summary
- LX7.12 Check My Knowledge
The first hour on a running, compromised Linux host.
9 lessonsHide lessons
Phase 5: Readiness and Reporting
The two things that bracket every Linux investigation: being ready before one and reporting after it.
11 lessonsHide lessons
- LX9.1 Why Readiness and Reporting Decide the Outcome
- LX9.2 The Linux IR Playbook
- LX9.3 Readiness: Tooling and Collection Pre-Staged
- LX9.4 Tabletop Exercises
- LX9.5 IR Metrics and Maturity
- LX9.6 The Technical Findings Report
- LX9.7 The Executive Summary
- LX9.8 IOCs, Remediation, and Lessons Learned
- LX9.9 Legal, Regulatory, and Cross-Platform Reporting
- Module Summary
- Check My Knowledge
Phase 0: Course Resources
Ten sheets of Linux investigation commands, each entry showing what the output proves, what it does not, and where the course teaches the reasoning behind it.
10 lessonsHide lessons
- Orienting on an Unfamiliar Host
- Filesystem Structure and Timestamps
- Recovery and Anti-Forensics Detection
- Reading the Logs
- Establishing the Entry Point
- Escalation, Persistence, and Lateral Movement
- Containers, Cloud, and Virtualization
- Memory and Malware Triage
- Live Response and the Handoff
- Paths, Logs, and Distribution Deltas
Seven end-to-end Linux investigation procedures, each with the commands, the branch points, and what the procedure does not cover.
Building a Linux investigation lab on hardware you already own, with the logging Linux ships disabled turned on, and a written ground truth to check your analysis against.
Seven worked Linux investigations, each carried from the referral to a written finding, including the ones that end in a defensible no.
Seven Linux threats, each with the examination sequence that establishes what happened, the check that could end it early, and what the handoff must carry.
Where to practice Linux investigation and use it at work: guided scenarios against Linux evidence, the toolkit, the detection library, and your own lab.
Linux forensic tool documentation, distribution and kernel references, container and cloud provider resources, and incident response frameworks used throughout the Linux Endpoint Investigation course.
Course Completion
Linux Endpoint Investigation end-of-course exam: a simulation-based assessment testing your ability to triage, investigate, and report on a Linux server compromise you have not seen before, using the artifacts and...
1 lessonsHide lessons
Course overview
The Linux Endpoint Investigation course teaches a practical forensic methodology specifically for Security Engineers and IR Professionals working in Linux, cloud, and container environments. You'll gain hands-on expertise to:
By the end, you'll have the skills and structured approach to confidently lead Linux-focused incident response, reducing dwell time and strengthening defenses in modern cloud-native and hybrid environments.
How this course works
Linux investigation is done against a system that logs less than Windows and tells you more if you know where to look. This course runs the same loop for every compromise it works.
1. Establish what this distribution actually records. Log locations, retention and audit configuration vary by distribution and by whoever built the image. Assume nothing that has not been read.
2. Take the volatile evidence first. Processes, connections, open files and loaded modules. On a server nobody wants to reboot, this is the material with an expiry on it.
3. Read the filesystem for what the attacker had to touch. Timestamps, permissions, and the directories a technique cannot avoid. This is where the intrusion leaves marks it did not choose to leave.
4. Follow the account, not the process. Escalation and lateral movement are identity events on Linux as much as anywhere else, and the trail runs through sudo, SSH and the key files.
5. Say what the evidence supports and where it stops. A finding with a gap named is stronger than a finding with the gap hidden, and Linux estates have gaps.
What this course assumes
No minimum experience and no prerequisite course. The filesystem layout, the log stack and the process model are explained where they first matter, and the course does not assume you administer Linux.
What makes it go faster: a Linux machine you can run commands on, and comfort at a shell. Neither is required, and every command in the course is shown with its output.
What this course does not cover: Windows and macOS forensics, network investigation, and Linux system administration. Those are their own courses, and this one stays on the endpoint.
Who this course is for
You're a Security Engineer or Incident Response Professional who needs to investigate and respond to security incidents in Linux, cloud, and container environments. This course is built for you if you want to:
In short: if you're responsible for investigating incidents on Linux systems and want to do it effectively and professionally, this course is for you.
What you'll learn
By the end of this Linux Endpoint Investigation course you will be able to:
Key course takeaways
Things you need to know
What are the prerequisites for this course?
There are no prerequisites. The course teaches Linux forensic investigation from first principles. Basic Linux command-line familiarity will help you move faster, but is not required. Every artifact, tool, and technique is explained at first use.
What are the device requirements?
A device with a modern browser. For hands-on forensic work, a Linux VM (Ubuntu or RHEL) with standard forensic tools. The course walks you through setup and provides evidence datasets for all scenarios.
How will the course benefit your career?
Linux runs the majority of cloud workloads, containers, and production servers. Most IR cybersecurity professionals are stronger on Windows than Linux, this gap is a career differentiator. This course gives you the Linux forensic methodology, artifact knowledge, and container/cloud investigation skills that make you effective across the full infrastructure stack.
Cross-platform IR capability is increasingly a requirement for senior DFIR and security engineering roles.
Usage rights and disclaimer
Course materials: Licensed for individual professional development. You may deploy investigation scripts, collection tools, and analysis workflows in your production environment. You may not redistribute course content or share account credentials.
Fictional environment: All scenarios use Northgate Engineering. Any resemblance to real organizations is coincidental.
Version and changelog
Current version: 2.0 | Last updated: June 2026
June 2026, v2.0: Course rebuilt and renamed to Linux Endpoint Investigation. Ten modules from forensic foundations through compromise scenarios to readiness and reporting.
v1.0: Course launch. Filesystem forensics, log analysis, memory forensics, container and cloud investigation.
This course is actively maintained.
End of Course Exam
Complete the course, then prove your skills under time pressure. Pass mark: 70. Earn your certificate with CPE credits.
Requires 80% course completion. One random scenario per attempt. Certificate issued on pass.