# container-and-kubernetes-forensics

container-and-kubernetes-forensics is a Claude Code skill for investigating container and Kubernetes incidents. It examines container filesystems, image layers, audit logs, and node evidence.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 73 repo stars
- Author: W4L33Dx
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/W4L33Dx/Cyber-Monster/tree/HEAD/blue-team/digital-forensics/container-and-kubernetes-forensics/SKILL.md
- Updated: 2026-11-15
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/container-and-kubernetes-forensics

## What it does

The skill guides evidence gathering for incidents involving containers and Kubernetes. It focuses on node-level artifacts and API server audit records, rather than treating the container as the only source. Capture order matters for a running workload: deleting a container discards its writable layer.

Its guidance separates image layers from writable layers, volumes, and projected secrets, and covers searches for activity through `exec` and `attach` as well as changes to Kubernetes objects. When audit logging is off, the result should be marked `INCONCLUSIVE (Telemetry Gap)`, not treated as a clean cluster. Separate materials cover collection commands for `crictl`, `kubectl`, and `nerdctl`.

## Requirements
- Works with: Kubernetes

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add W4L33Dx/Cyber-Monster --skill container-and-kubernetes-forensics -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/container-and-kubernetes-forensics/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/container-and-kubernetes-forensics/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add W4L33Dx/Cyber-Monster --skill container-and-kubernetes-forensics -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/container-and-kubernetes-forensics/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add W4L33Dx/Cyber-Monster --skill container-and-kubernetes-forensics -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/container-and-kubernetes-forensics/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install W4L33Dx/Cyber-Monster blue-team/digital-forensics/container-and-kubernetes-forensics
```

2. **Manually: put the files in place**
- File: `.github/skills/container-and-kubernetes-forensics/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add W4L33Dx/Cyber-Monster --skill container-and-kubernetes-forensics -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/W4L33Dx/Cyber-Monster --path blue-team/digital-forensics/container-and-kubernetes-forensics
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/container-and-kubernetes-forensics/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/W4L33Dx/Cyber-Monster/tree/HEAD/blue-team/digital-forensics/container-and-kubernetes-forensics/SKILL.md

## When to use it
- capture node evidence before removing a running container
- inspect audit logs for access through `exec` or `attach`
- distinguish image layers from writable layers and mounted volumes
- identify which evidence remains after a pod is deleted

## Example prompts
- Investigate this Kubernetes incident and list the node evidence to capture before deleting the pod.
- Check the audit log for commands run through `exec` or `attach`.
- Determine whether this file came from an image layer, a writable layer, or a mounted volume.

## Similar
- [kubernetes-deployment](https://affpapa.org/en/nevibecode/skills/kubernetes-deployment.md) — skill · 768 installs
- [kubernetes-orchestration](https://affpapa.org/en/nevibecode/skills/kubernetes-orchestration.md) — skill · 474 installs
- [kubernetes-ops](https://affpapa.org/en/nevibecode/skills/kubernetes-ops.md) — skill · 454 installs
- [kubernetes-expert](https://affpapa.org/en/nevibecode/skills/kubernetes-expert.md) — skill · 215 installs
- [setup-kubernetes-deployment](https://affpapa.org/en/nevibecode/commands/setup-kubernetes-deployment.md) — command · 334 installs
- [kubernetes-pentesting](https://affpapa.org/en/nevibecode/skills/kubernetes-pentesting.md) — skill · 4100 installs

From the same set: [w4l33dx/cyber-monster](https://affpapa.org/en/nevibecode/by/w4l33dx/cyber-monster.md) — 61 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
