hw-sw-boundary

Analyze hardware-software security interfaces for feature enablement and DMA protection.

1|1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/dtsong/claude-code-windows-setup --skill hw-sw-boundary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hw-sw-boundary
Source: https://github.com/dtsong/claude-code-windows-setup/tree/main/skills/council/warden/hw-sw-boundary
Command: npx skills add https://github.com/dtsong/claude-code-windows-setup --skill hw-sw-boundary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that hardware security features are correctly enabled and configured by software, preventing vulnerabilities at the hardware-software interface.

Core Features & Use Cases

  • Hardware Feature Verification: Checks if security features like IOMMU/SMMU, MTE, and PAC are enabled in the kernel and firmware.
  • DMA Protection Audit: Assesses the configuration of IOMMU/SMMU to prevent unauthorized Direct Memory Access.
  • Trust Model Coherence: Verifies that the software's assumptions about hardware security align with actual hardware capabilities.
  • Use Case: A security auditor can use this Skill to systematically review a system's boot chain and device configurations to ensure robust hardware-level security is in place.

Quick Start

Review the hardware security features and DMA protection configuration for the current system.

Frequently Asked Questions about hw-sw-boundary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify IOMMU and SMMU DMA protection configuration in my system?

Verifying IOMMU and SMMU DMA protection requires reading kernel configuration, firmware settings, and device trees. This Skill analyzes hardware-software interfaces to confirm these features are enabled, preventing unauthorized Direct Memory Access across your system's components.

What is hardware-software trust model coherence and why does it matter?

Hardware-software trust model coherence ensures software security assumptions align with actual hardware capabilities. Analyzing kernel configuration, firmware settings, and device trees verifies that hardware security features like MTE and PAC are properly enabled and trusted by the operating system.

How do I audit boot chain security and memory protection features?

Auditing boot chain security and memory protection involves systematically reviewing firmware settings, kernel configurations, and hardware documentation. This Skill checks control flow integrity features and verifies the boot chain to ensure robust hardware-level security is correctly configured.

Can I check if kernel security features like MTE and PAC are enabled in firmware?

Yes, checking kernel security features like MTE and PAC requires analyzing both kernel configurations and firmware settings. This Skill verifies hardware feature enablement by reading these sources to ensure security mechanisms are correctly activated across the hardware-software interface.

What's the best way to review hardware security feature enablement for an audit?

Reviewing hardware security feature enablement is best done by analyzing kernel configurations, firmware settings, device trees, and hardware documentation. This Skill systematically verifies IOMMU/SMMU configurations and boot chain integrity to provide a comprehensive security audit.

Why does my software assume hardware security features are active when they aren't?

Software may assume hardware security features are active when firmware or kernel configurations disable them. This Skill identifies trust model incoherence by cross-referencing software assumptions with actual hardware capabilities found in device trees and firmware settings.