Individual skill
analyzing-docker-container-forensics
Investigate compromised Docker containers by analyzing images, layers, volumes, logs, and runtime artifacts to identify malicious activity and evidence.
internal/tools/skills/data/digital-forensics/analyzing-docker-container-forensics/SKILL.md
Source commit d42f381ad34843e71a42658e5c57290c713e85af
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,309
- Repository last updated
- Nov 5, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- cybersecurity Repository topic
- security Repository topic
- bug-bounty Repository topic
- automation Repository topic
- autonomous-pentesting Repository topic
- ai-agent Repository topic
- ai-security Repository topic
- ethical-hacking Repository topic
- golang Repository topic
- penetration-testing Repository topic
- forensics Declared skill tag
- docker Declared skill tag
- container-forensics Declared skill tag
- container-security Declared skill tag
- image-analysis Declared skill tag
- runtime-investigation Declared skill tag
- devops Derived category
- security Derived category
- devops-containers Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Analyzing Docker Container Forensics
## When to Use
- When investigating a compromised Docker container or container host
- For analyzing malicious Docker images pulled from registries
- During incident response involving containerized application breaches
- When examining container escape attempts or privilege escalation
- For auditing container configurations and identifying misconfigurations
## Detection Gaps & Validation
- **Ephemeral evidence is lost first:** `docker stop`/`rm` destroys the writable layer and in-memory state. Before anything else, `docker pause` then `docker export`/`docker commit` the running container and dump host process memory (`/proc/<pid>/`), because a removed container's overlay2 `diff` dir under `/var/lib/docker/overlay2/<id>/diff` may already be reaped.
- **Most-missed artifacts:** the json-file logs at `/var/lib/docker/containers/<id>/<id>-json.log`, `config.v2.json`/`hostconfig.json` (mounts, caps, env secrets), and the image `history` (`RUN` lines that added a backdoor). `docker logs` returns nothing if the container used a `syslog`/`none`/`journald` logging driver - pivot to host journald.
- **Anti-forensics that defeats this analysis:** `docker diff` only reflects the writable layer, so files baked into a malicious image layer (or written to a `tmpfs`/anonymous volume) never appear as "changed." Compare layers with `container-diff`/`dive` against the pulled base image and inspect each `layer.tar` directly.