Awesome Reviewers checks + prompts

Attack surface inventory

Lists every entry point and trust boundary: API endpoints, webhooks, queues, schedulers, parsers, CLIs, third-party scripts, model calls.

V1059 technique
tactic Threat modeling
not detectable from CI configuration

Sub-techniques

5

IDNameDescription
V1059.001Network entry pointsHTTP, gRPC, WebSocket, raw socket and webhook receivers.
V1059.002Asynchronous entry pointsQueue consumers and scheduled jobs that act on external data.
V1059.003Data parsers and deserializationFile, archive and object parsers that take untrusted input.
V1059.004Infrastructure and configurationInfrastructure as code, secrets management, caching and edge routing.
V1059.005AI and model interactionsPrompts, tools and retrieved content that cross a trust boundary.

Craft it

  1. Enumerate entry points from route tables, consumers and schedulers in code.
  2. Describe the system as a model (pytm, Threagile) with data flows and trust boundaries.
  3. Regenerate the model when entry points change.

Reverse engineer it

Signs that a codebase already runs this technique, and where to read how it is configured.

  • threagile.yaml, pytm models or threat model documents in docs/.

Open-source packages

3