Identifying Assets and Attack Surface
You'll learn how to systematically catalog the critical assets, entry points, and external interfaces that define your system's architectural attack surface.
What Is This?
After creating your data flow diagrams, the next step in architectural threat modeling is cataloging exactly what you're protecting and where attacks could enter. An asset is anything of value—customer data, intellectual property, authentication tokens, configuration secrets. The attack surface encompasses all entry points where untrusted data or actors can interact with your system.
Think of your architecture like a castle: assets are the treasures inside, and the attack surface is every door, window, drawbridge, and drainage pipe—any place an attacker might enter.
The Cataloging Process
Start by identifying critical assets:
- Data stores containing sensitive information
- Authentication/authorization mechanisms
- Business logic processing valuable transactions
- Cryptographic keys and credentials
Next, map your entry points:
- Public-facing APIs and web endpoints
- User input fields and upload mechanisms
- Third-party integrations and webhooks
- Admin interfaces and support tools
Finally, document external interfaces:
- Every boundary where your system trusts external data
- Inter-service communication channels
- Database connections
- File system access points
Why This Matters
You can't protect what you don't know exists. A complete asset inventory and attack surface map reveals where to apply controls from earlier principles (least privilege, complete mediation, fail-safe defaults). It also highlights forgotten or shadow components—that old API endpoint still running, or the debug interface someone left enabled.
Key Takeaway: A comprehensive catalog of assets and attack surface transforms vague security concerns into concrete protection targets, ensuring no critical component or entry point goes undefended during architectural design.