dma-attack-techniques — Claude Code skill: PCIe DMA analysis
dma-attack-techniques — a skill for analyzing PCIe DMA threats, host-mediated memory acquisition, and IOMMU defenses. Helps classify memory initiators, transport paths, and security boundaries in hardware architecture.
MIT 169 installs ★ 3,784 updated 2026-10-25
npx skills add gmh5225/awesome-game-security --skill dma-attack-techniques -a claude-codeWhat dma-attack-techniques does
This skill classifies DMA attacks by identifying who initiates memory access and how data flows across the system boundary. It includes reference materials on PCIe devices, TLP packets, configuration space, VT-d and AMD-Vi technologies, and detection methods.
The skill covers five core elements: memory initiator, transport mechanism, required privilege level, isolation boundary, and observable artifacts. This framework distinguishes actual DMA vectors from other host-kernel attack paths. Apply it when the device-host boundary shapes the threat model; for pure kernel security, refer to windows-kernel-security.
What it helps with
- Identify the memory initiator in PCIe topology and privileges required for an attack
- Analyze PCIe device configuration space and state transitions
- Evaluate IOMMU and ACS effectiveness on a host platform
- Gather forensic evidence from memory acquisition and PCIe transport
- Distinguish DMA vectors from host-kernel attack patterns
Example prompts for the agent
- What privilege level do I need for a DMA attack via Thunderbolt on Windows?
- How do I verify whether IOMMU is enabled in ACPI and in device runtime state?
- What artifacts remain in memory after a PCIe TLP acquisition?
How to install dma-attack-techniques
1Skills CLI (Vercel)
npx skills add gmh5225/awesome-game-security --skill dma-attack-techniques -a claude-code2Manually: put the files in place
~/.claude/skills/dma-attack/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/dma-attack/
1Skills CLI (Vercel)
npx skills add gmh5225/awesome-game-security --skill dma-attack-techniques -a codex2Manually: put the files in place
.agents/skills/dma-attack/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add gmh5225/awesome-game-security --skill dma-attack-techniques -a cursor2Manually: put the files in place
.cursor/skills/dma-attack/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install gmh5225/awesome-game-security .claude/skills/dma-attack2Manually: put the files in place
.github/skills/dma-attack/SKILL.md1Skills CLI (Vercel)
npx skills add gmh5225/awesome-game-security --skill dma-attack-techniques -a gemini-cli2Platform CLI
gemini skills install https://github.com/gmh5225/awesome-game-security --path .claude/skills/dma-attackManually: put the files in place
.devin/skills/dma-attack/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add gmh5225/awesome-game-security --skill dma-attack-techniques -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about dma-attack-techniques
How do I install dma-attack-techniques for Claude Code?
Run npx skills add gmh5225/awesome-game-security --skill dma-attack-techniques -a claude-code, then open ~/.claude/skills/dma-attack/SKILL.md.
What does the dma-attack-techniques skill do?
It helps you analyze PCIe DMA threats: who initiates memory access, how data is transported, what privilege level is needed, where isolation boundaries exist, and what traces remain. Includes references on IOMMU, detection, and attack classification.
When should I use dma-attack-techniques instead of windows-kernel-security?
Use dma-attack-techniques when the device-host boundary matters, memory acquisition flows through PCIe, or FPGA behavior is relevant. Choose windows-kernel-security for host driver protection and kernel internals.
Source text
SKILL.md · MIT
--- name: dma-attack-techniques description: Analyze PCIe DMA threats, host-mediated memory acquisition, FPGA behavior, and IOMMU defenses. Use when the memory initiator or device boundary matters; use kernel security for host-only mechanisms. --- # DMA attack techniques Identify the memory initiator, transport, required privilege, isolation boundary, and observable artifacts before classifying a technique as DMA. ## Topic routing - [Classification and threat model](references/classification-and-threat-model.md) for acquisition-path distinctions and attacker prerequisites. - [PCIe devices](references/pcie-devices.md) for TLPs, configuration space, programmable endpoints, and emulation limits. - [IOMMU and defense](references/iommu-and-defense.md) for VT-d/AMD-Vi, ACS, ATS/PASID, domain assignment, hypervisors, and trust anchors. - [IOMMU state verification](references/iommu-state-verification.md) for separating ACPI advertisement, Windows policy, live unit state, and per-requester coverage. - [Detection and forensics](references/detection-and-forensics.md) for defensive PCIe inventory, signal correlation, evidence capture, Thunderbolt/USB4, and memory access. - [Acquisition and transport](references/acquisition-and-transport.md), [assurance boundaries](references/assurance-boundaries.md), and [repository resources](references/repository-resources.md) for focused evidence and source selection. - [Repository map](references/repository-map.md) when maintaining the collection. Use `windows-kernel-security` for host driver and kernel internals. Apply `game-security-research-rigor` before turning architecture claims into findings.
© gmh5225 · MIT · gmh5225/awesome-game-security