Skip to main content

dma-attack-techniques

Analyze PCIe DMA threats, FPGA device behavior, and IOMMU defenses. Use for DMA-specific threat modeling or detection; use windows-kernel-security for kernel mechanisms without a DMA boundary.

Datos de origen

Repositorio
NeverSight/NeverD
Última actividad en el origen
13 de septiembre de 2026 a las 11:12
Idioma detectado de SKILL.md
inglés
Estrellas
77
Forks
14

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos
6 archivos

Mostrando SKILL.md

SKILL.md
Instrucciones de origen · Vista previa de solo lectura
name
dma-attack-techniques
description
Analyze PCIe DMA threats, FPGA device behavior, and IOMMU defenses. Use for DMA-specific threat modeling or detection; use windows-kernel-security for kernel mechanisms without a DMA boundary.
# DMA attack techniques Use this skill for defensive research into hostile PCIe devices and DMA-capable hardware. Keep analysis within the user's authorized security scope. ## Topic routing Read only the reference that matches the task: - [PCIe and FPGA](references/pcie-and-fpga.md) for TLPs, configuration space, pcileech, FPGA constraints, and device emulation. - [IOMMU and virtualization](references/iommu-and-virtualization.md) for VT-d/AMD-Vi, ACS, ATS/PASID, domain assignment, hypervisors, and split address spaces. - [Detection and forensics](references/detection-and-forensics.md) for device fingerprinting, containment, telemetry, evidence capture, and defensive synthesis. - [Platforms and memory access](references/platforms-and-access.md) for Thunderbolt/USB4 and physical-memory access mechanics. - [Resource map](references/resources.md) when maintaining the source collection or locating upstream material. For general anti-cheat architecture, use `anti-cheat-systems`. For Windows driver, callback, PatchGuard, or kernel-memory internals without a PCIe focus, use `windows-kernel-security`. Prefer threat models, detection limits, and mitigations over operational bypass instructions. Clearly separate hardware capability, observed evidence, and inference.
Ver en GitHub