analyzing-docker-container-forensics SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
analyzing-docker-container-forensics from 26zl/cybersec-toolkit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add 26zl/cybersec-toolkit/analyzing-docker-container-forensics@v1.0Pins v1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- 26zl/cybersec-toolkit
- Path
.claude/skills/analyzing-docker-container-forensics/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0, committed Jun 2, 2026
- Size
- 12,897 bytes
- Repository stars
- 87
- License
- MIT
Investigate compromised Docker containers by analyzing images, layers,.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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 ## Prerequisites - Docker CLI access on the forensic workstation - Access to the Docker host file system (forensic image or live) - Understanding of Docker layered file system (overlay2, aufs) - dive, docker-explorer, or container-diff for image analysis - Knowledge of Docker daemon configuration and socket security - Trivy or Grype for vulnerability scanning of container images ## Workflow ### Step 1: Preserve Container State and Evidence ```bash # List all containers (including stopped) docker ps -a --no-trunc > /cases/case-2024-001/docker/container_list.txt # Inspect the compromised container CONTAINER_ID="abc123def456" docker inspect $CONTAINER_ID > /cases/case-2024-001/docker/container_inspect.json # Export container filesystem as tarball (preserves current state) …
Read the whole file at its exact version.
How to install
mdr add 26zl/cybersec-toolkit/analyzing-docker-container-forensics@sha256:bdbee7f68a5dcb5aThe line at the top of this page pins the label v1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_zvvl6p5zhdoly2qm)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jun 2, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (12897 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
26zl/cybersec-toolkit · 87 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zvvl6p5zhdoly2qm GET https://markdownregistry.com/api/v1/resolve?ref=26zl/cybersec-toolkit/analyzing-docker-container-forensics GET https://markdownregistry.com/api/v1/blob/bdbee7f68a5dcb5a2c47d49a3de4721c78ed3cf14546e824e7610baf93de66e5
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from 26zl/cybersec-toolkit
Every file in 26zl/cybersec-toolkit