CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dma-attack-techniques

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.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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 for acquisition-path distinctions and attacker prerequisites.
  • PCIe devices for TLPs, configuration space, programmable endpoints, and emulation limits.
  • IOMMU and defense for VT-d/AMD-Vi, ACS, ATS/PASID, domain assignment, hypervisors, and trust anchors.
  • IOMMU state verification for separating ACPI advertisement, Windows policy, live unit state, and per-requester coverage.
  • Detection and forensics for defensive PCIe inventory, signal correlation, evidence capture, Thunderbolt/USB4, and memory access.
  • Acquisition and transport, assurance boundaries, and repository resources for focused evidence and source selection.
  • Repository map 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.

Repository

gmh5225/awesome-game-security

Path

.claude/skills/dma-attack/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.