mantis-threat-model

Automated threat modeling is achieved by synthesizing trust boundaries, attack surfaces, and attacker profiles from your architecture definitions. This skill generates structured threat models directly from existing knowledge base files to keep security assessments version-controlled.

Architecture-aware threat modeling analyzes system components by mapping trust boundaries and attack surfaces against defined attacker profiles. It works by reading pre-populated architectural knowledge bases to synthesize potential attack vectors specific to your system's design.

Yes, you need a pre-populated workspace containing architecture.md and entity definitions to generate a threat model. The tool requires these existing knowledge base files to correctly synthesize trust boundaries and attack surfaces.

Threat models are kept synchronized using snapshot-based provenance tracking. This ensures the generated security assessments are tied to a specific version-controlled state of your architectural knowledge base.

Identifying trust boundaries during a security review is best handled by automatically synthesizing them from your architecture documentation. This approach ensures consistent detection of potential attack vectors based on the latest system design.