linux-forensics

Collect Linux forensic evidence across Debian, RHEL, and SUSE families.

175|26|Updated Aug 14, 2025
One-click install
npx skills add https://github.com/jmagly/aiwg --skill linux-forensics-jmagly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linux-forensics
Source: https://github.com/jmagly/aiwg/tree/main/agentic/code/frameworks/forensics-complete/skills/linux-forensics
Command: npx skills add https://github.com/jmagly/aiwg --skill linux-forensics-jmagly

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of gathering forensic evidence from Linux systems, ensuring comprehensive and consistent data collection across different distribution families.

Core Features & Use Cases

  • Distribution-Aware Collection: Automatically detects and adapts to Debian/Ubuntu, RHEL/CentOS/Rocky, and SUSE families.
  • System Integrity Verification: Checks for modified system binaries and configuration files.
  • Evidence Gathering: Collects logs, scheduled tasks, persistence mechanisms, network state, and kernel information.
  • Use Case: When a Linux server shows signs of compromise, this skill can be triggered to perform a rapid, structured forensic analysis, producing a findings report aligned with NIST guidelines.

Quick Start

Run the linux forensics skill to investigate the remote host api-prod-01.example.com.

Frequently Asked Questions about linux-forensics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform Linux incident response and forensic analysis across different distributions?

Linux incident response is automated by detecting the distribution family and adapting collection accordingly. The process gathers package integrity, authentication logs, scheduled tasks, persistence mechanisms, network state, and kernel information into a NIST SP 800-86 aligned findings report.

What does a Linux forensic investigation collect for evidence gathering?

Linux forensic evidence gathering collects modified system binaries, configuration files, authentication logs, scheduled tasks, persistence mechanisms, network state, and kernel information. This comprehensive collection ensures consistent data extraction for analyzing security incidents.

Can I use automated forensic analysis on Debian, RHEL, and SUSE Linux systems?

Automated forensic analysis supports Debian/Ubuntu, RHEL/CentOS/Rocky, and SUSE Linux families. It automatically detects the running distribution and adapts its collection mechanisms to ensure accurate evidence gathering across these platforms.

How do I check for system integrity and modified binaries during a security incident?

Checking system integrity involves verifying modified system binaries and configuration files. The forensic analysis automates this verification process alongside collecting authentication logs and persistence mechanisms to identify potential system compromise.

What is the best way to structure forensic evidence collection following NIST guidelines?

Structuring forensic evidence collection following NIST guidelines involves ordering the process according to NIST SP 800-86. This ensures that evidence gathering for package integrity, logs, and network state produces a standardized findings document for incident response.

How do I investigate Linux persistence mechanisms and scheduled tasks after a compromise?

Investigating Linux persistence mechanisms involves collecting scheduled tasks and analyzing system configurations for unauthorized modifications. The forensic analysis automates this collection alongside network state and kernel information to identify how an attacker maintains access.