Verification · Threat modeling · Weakness discovery
Per-surface weakness search
Apply the weakness classes relevant to each surface category.
How to build it
- List each entry point by surface type, such as HTTP handler, queue consumer or CLI command.
- Map each surface type to the weakness classes that apply to it.
- Record each weakness with the entry point it can be reached from.
Signals in a repository
- A surface inventory file that lists handlers and their surface types.
- Security audit reports that cite an entry point for each finding.
- Issues labelled security that name a route or handler.
In practice
No scanned repository runs a tool for this check. The steps above are the only guidance.