attack-surface-pentest

Map classical MITRE ATT&CK v19.1 and AI-class MITRE ATLAS TTPs across AI-era attack surfaces.

Updated May 11, 2026
One-click install
npx skills add https://github.com/blamejs/exceptd-skills --skill attack-surface-pentest
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: attack-surface-pentest
Source: https://github.com/blamejs/exceptd-skills/tree/main/skills/attack-surface-pentest
Command: npx skills add https://github.com/blamejs/exceptd-skills --skill attack-surface-pentest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Traditional penetration testing and attack surface management methodologies fail to cover AI-era attack surfaces including AI API egress channels, MCP server trust boundaries, RAG corpora, ephemeral cloud runtimes, and AI supply chain manifests, leaving organizations with false evidence of security posture and compliance with outdated frameworks.

Core Features & Use Cases

  • Extended 7-Layer Attack Surface Inventory: Enumerates classical perimeter, AI API egress channels, MCP servers, prompt-injection footprints, RAG corpora, ephemeral runtimes, and AI supply chain manifests, addressing the blind spots of traditional ASM tools that only scan internet-facing IPs and web apps.
  • Dual TTP Adversary Emulation: Maps both classical MITRE ATT&CK v19.1 and AI-class MITRE ATLAS v2026.06 tactics, techniques, and procedures to emulate mid-2026 adversary tradecraft including AI-API-as-C2 (SesameOp pattern) and prompt-injection-as-RCE.
  • Legacy Framework Gap Flagging: Explicitly identifies insufficiency in outdated security and compliance frameworks including NIST SP 800-115, OWASP WSTG, PTES, NIS2, TIBER-EU, CBEST, and ISO/IEC 27001:2022 to eliminate compliance theater.
  • Use Case: A financial institution preparing for DORA-mandated TIBER-EU threat-led penetration testing can use this skill to ensure its engagement covers AI-specific TTPs that are missing from official 2025–2026 scenario libraries.

Quick Start

Use the attack-surface-pentest skill to scope and execute a mid-2026 adversary emulation pen test that covers AI APIs, MCP servers, RAG corpora, and ephemeral runtimes alongside classical network and web application surfaces.

Frequently Asked Questions about attack-surface-pentest

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

FAQPage Schema
How do I include AI API egress channels and MCP server trust boundaries in a penetration testing scope?▼

To include AI API egress and MCP server trust boundaries in penetration testing, use an extended 7-layer attack surface inventory methodology that enumerates prompt-injection footprints, RAG corpora, and ephemeral runtimes alongside classical network assets.

What is MITRE ATLAS adversary emulation for AI-era attack surfaces?▼

MITRE ATLAS adversary emulation maps AI-class tactics, techniques, and procedures against AI-era attack surfaces, validating defense-in-depth controls by simulating mid-2026 tradecraft like AI-API-as-C2 and prompt-injection-as-RCE alongside classical MITRE ATT&CK v19.1 techniques.

Can I use traditional NIST SP 800-115 or OWASP WSTG frameworks for AI red teaming?▼

Traditional NIST SP 800-115 and OWASP WSTG frameworks are insufficient for AI red teaming, creating compliance theater by failing to cover AI supply chain manifests and RAG corpora; legacy framework gap flagging explicitly identifies these security blind spots.

How to prepare for TIBER-EU threat-led penetration testing with AI assistants deployed?▼

Preparing for TIBER-EU threat-led penetration testing with AI assistants deployed requires scoping adversary emulation engagements that map both classical MITRE ATT&CK and AI-class MITRE ATLAS TTPs to satisfy DORA-mandated scenario libraries missing AI-specific attacks.

Does attack surface management cover ephemeral cloud runtimes and AI supply chain manifests?▼

Yes, extended attack surface management covers ephemeral cloud runtimes and AI supply chain manifests by inventorying seven layers including AI API egress channels and RAG corpora, addressing blind spots left by traditional ASM tools scanning only internet-facing IPs.

Why does ISO/IEC 27001:2022 compliance fail to validate zero-trust postures for AI infrastructure?▼

ISO/IEC 27001:2022 compliance fails to validate zero-trust postures for AI infrastructure because legacy security frameworks lack controls for MCP server trust boundaries and prompt-injection footprints, creating false evidence of security posture without AI-specific TTP testing.