Verification · Threat modeling · Attack surface inventory
Infrastructure and configuration
Infrastructure as code, secrets management, caching and edge routing.
How to build it
- List the infrastructure as code files, secrets stores, caches and edge routing rules.
- Model each one as a component with its trust boundary and data flow.
- Update the model when a new service, bucket or route is added.
Signals in a repository
- Terraform, Helm or CloudFormation files whose components also appear in the threat model.
- A secrets manager reference or CDN routing configuration listed in the threat model file.
In practice
No scanned repository runs a tool for this check. The steps above are the only guidance.