Attack Surface Map

Enumerate API endpoints and document authentication, validation, rate limits, and data sensitivity.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/cdalsoniii/brightpath-coder --skill attack-surface-map
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Attack Surface Map
Source: https://github.com/cdalsoniii/brightpath-coder/tree/main/.cursor/skills/attack-surface-map
Command: npx skills add https://github.com/cdalsoniii/brightpath-coder --skill attack-surface-map

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of identifying and documenting an API's potential vulnerabilities by mapping its entire attack surface, ensuring comprehensive security reviews.

Core Features & Use Cases

  • Endpoint Enumeration: Automatically discovers all API endpoints, including HTTP methods and paths.
  • Security Profile Generation: Details authentication requirements, rate limits, and data sensitivity for each endpoint.
  • Use Case: When a new set of API endpoints is deployed, this Skill can be invoked to generate an immediate report of their security posture, flagging high-risk areas for immediate attention.

Quick Start

Use the attack surface map skill to enumerate all endpoints and their security controls for the current API project.

Frequently Asked Questions about Attack Surface Map

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

FAQPage Schema
How do I map my API attack surface for a security review?

Mapping an API attack surface involves enumerating all endpoints, authentication requirements, input validation, and rate limits to generate a detailed security profile for each route.

What is API endpoint enumeration and how does it classify data sensitivity?

API endpoint enumeration is the process of discovering all API paths and HTTP methods to document their security controls. It classifies data sensitivity to flag high-risk areas requiring immediate attention during threat modeling.

Do I need OpenAPI specifications to generate an API threat model?

You need read access to route configurations, handlers, middleware, and OpenAPI specifications to accurately map the attack surface. These inputs allow the process to automatically discover endpoints and detail authentication requirements.

Can I use this approach to check rate limits and input validation on new endpoints?

Yes, you can check rate limits and input validation on new endpoints by analyzing route configurations and middleware. This generates an immediate report of the security posture for newly deployed API paths.

What is the best way to automate vulnerability assessment for API routes?

The best way to automate vulnerability assessment for API routes is to systematically enumerate endpoints and document their security controls. This flags high-risk areas and automates identifying potential vulnerabilities across the entire API.