tm-init

To generate an asset inventory from architecture documentation, run an initialization command pointing to your docs path. The tool discovers assets, maps data flows, identifies trust boundaries, and catalogs the attack surface into a structured threat model scaffold.

A trust boundary in a threat model identifies where privilege levels or data transit security changes. It is identified by mapping data flows across systems like web apps, services, and databases to clarify where data crosses security perimeters.

Yes, threat modeling initialization supports existing services and database integrations. It performs documentation discovery across systems to classify assets, map data flows, and catalogue attack surface entries for new projects or security assessments.

Map data flows and attack surfaces by analyzing architecture documentation to trace data transit between clients, services, and data stores. This process catalogs attack surface entries and generates stakeholder-ready diagrams automatically.

The best way to start threat modeling with scattered architecture docs is to consolidate them into a docs path and run an initialization command. This discovers assets, maps data flows, and outputs a structured scaffold with state files and diagrams.

No specific architecture format is required to map data flows and trust boundaries. The tool performs documentation discovery on standard text-based architecture docs to inventory assets and generate threat model state files and diagrams.