linux-internals

Translate Linux internals into actionable detection engineering knowledge.

4|1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/OpenTideHQ/AgentTide --skill linux-internals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linux-internals
Source: https://github.com/OpenTideHQ/AgentTide/tree/main/skills/linux-internals
Command: npx skills add https://github.com/OpenTideHQ/AgentTide --skill linux-internals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Linux knowledge is often hard to obtain and apply to detection engineering; this Skill consolidates Linux internals needed to write robust detections for Linux endpoints, servers, and containers.

Core Features & Use Cases

  • Understand process lifecycles, /proc, namespaces, and capabilities to write precise detections.
  • Map Linux operations to telemetry such as auditd, eBPF, systemd, PAM, and SSH for actionable signals.
  • Real-world use: create detectors that differentiate legitimate Linux admin tasks from abuse in containerized workloads.

Quick Start

Investigate a suspicious fork/exec sequence by tracing it through /proc, auditd records, and container namespaces to determine the correct detection signals.

Frequently Asked Questions about linux-internals

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

FAQPage Schema
How do I write precise Linux detections for suspicious process lifecycles?

To write precise Linux detections, trace suspicious fork/exec sequences through /proc, auditd records, and container namespaces to determine the correct telemetry signals. This approach differentiates legitimate admin tasks from abuse in containerized workloads.

What Linux telemetry sources can I map to detection signals?

Linux telemetry sources you can map to detection signals include auditd, eBPF tools, systemd, PAM, and SSH. Mapping these operations translates Linux internals into actionable knowledge for robust endpoint and server monitoring.

Does this approach work for detections inside containerized workloads?

Yes, this approach works for containerized workloads by examining container namespaces and boundaries. It helps create detectors that differentiate legitimate Linux admin tasks from abuse within isolated container environments.

How do I investigate a suspicious fork/exec sequence using /proc and auditd?

Investigate a suspicious fork/exec sequence by tracing it through /proc and auditd records alongside container namespaces. This determines the correct detection signals by mapping process lifecycles to actionable telemetry.

What Linux internals knowledge do I need to map capabilities and namespaces for detections?

You need knowledge of process lifecycles, procfs, namespaces, capabilities, audit records, and container isolation. Understanding these Linux internals ensures robust telemetry mappings for effective detection engineering.

When should I use eBPF tools over auditd for Linux detection engineering?

Use eBPF tools and auditd based on your telemetry requirements; both map Linux operations to actionable signals. eBPF offers dynamic kernel tracing while auditd provides systematic event logging for detection engineering.