> For the complete documentation index, see [llms.txt](https://docs.devarmor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devarmor.com/getting-started/creating-your-first-threat-model.md).

# Creating Your First Threat Model

A step-by-step walkthrough of creating and reviewing your first threat model.

This page is a one-pager tour of the whole process, start to finish. Each section links out to the full page on that topic — read this first to see how everything fits together, then go deeper wherever you need to.

## 1. Create a project

Everything in DevArmor — threat models, design reviews, connected sources — lives inside a **project**. From your dashboard, create a new project and give it a name; this is usually a single application, service, or product area. See [Data Model Hierarchy](https://docs.devarmor.com/modules/threat-modeler/data-model-hierarchy.md) for how projects relate to teams and your organization if you're setting up more than one.

## 2. Start a threat model

Inside your project, start a new threat model. You can import an existing one from a JSON file, or start fresh and describe your application — see [Starting a Threat Model](https://docs.devarmor.com/modules/threat-modeler/starting-a-threat-model.md) for every supported way in.

From here, a threat model moves through four steps: **Describe → Decompose → Review → Implement**.

## 3. Describe

This is where you give DevArmor the raw material to work with. The two highest-leverage things to do here:

* **Connect a GitHub repository** for more accurate results — DevArmor generates architecture directly from your code instead of relying only on a description. See [Starting a Threat Model](https://docs.devarmor.com/modules/threat-modeler/starting-a-threat-model.md#connect-a-code-repository) and [GitHub Integration](https://docs.devarmor.com/getting-started/github-integration.md) for installing the GitHub App.
* **Upload or create an architecture diagram** — upload an existing diagram (including a PDF, photo, or whiteboard scan, which DevArmor digitizes automatically), or skip this if you don't have one and describe the application directly instead. See [Starting a Threat Model](https://docs.devarmor.com/modules/threat-modeler/starting-a-threat-model.md) for diagram uploads and the manual "Describe" flow.

You can also import supporting documents (PRDs, Confluence pages, Jira tickets, vulnerability/SAST reports) at this stage — none of this is required, but the more you connect, the less DevArmor has to infer.

## 4. Decompose

DevArmor distills what you've connected into the specific attributes a threat model needs, and generates architecture from it.

* **Verify Application Attributes** — review what DevArmor inferred (business criticality, data sensitivity, authentication methods, actors) and correct anything before analysis runs. See [Verify Application Attributes](https://docs.devarmor.com/modules/threat-modeler/verify-application-attributes.md).
* **Review the generated diagram** — inspect each component, data flow, and trust boundary DevArmor identified; the diagram is editable (zoom, pan, click a component to see its details) if anything needs adjusting. See [Architecture & Diagrams](https://docs.devarmor.com/modules/threat-modeler/architecture-and-diagrams.md).

## 5. Review

Once architecture is confirmed, DevArmor generates its findings: **Threats** (STRIDE-categorized, with MITRE ATT\&CK context), **Risks** (scored consistently via a defined formula), and **Controls** (the mitigations, mappable to compliance frameworks). Review and adjust any of these before moving on. See [Review Threat Model Output](https://docs.devarmor.com/modules/threat-modeler/review-threat-model-output.md).

## 6. Implement

The last step turns findings into action:

* **Triage tasks** — mitigation actions can be pushed straight to your issue tracker; automated tests become enforceable in [Code Reviewer](https://docs.devarmor.com/modules/code-reviewer.md) and [AI Guardrails](https://docs.devarmor.com/modules/code-reviewer/ai-guardrails.md); manual tests are tracked for your team to run directly.
* **Pen tests** — scopes generated per-component, ready to hand to a bug bounty program or pentest consultant.
* **Policies** — controls you mark for enforcement become the policies Code Reviewer applies to every pull request.
* **Reports** — generate the full Threat Model Analysis Report (with an executive summary and optional Privacy Impact Assessment) or an Attack Surface Analysis report, and export to PDF or Google Docs.

See [Implement Threat Model Results](https://docs.devarmor.com/modules/threat-modeler/implement-threat-model-results.md) and [Reports & Exports](https://docs.devarmor.com/modules/threat-modeler/reports-and-exports.md) for the full detail.

## Next steps

Once your first threat model is reviewed, later changes to the application don't mean starting over — see [Version Control](https://docs.devarmor.com/modules/threat-modeler/threat-model-versions.md) for creating new versions as the system evolves. And once a threat model exists, [Design Reviewer](https://docs.devarmor.com/modules/design-reviewer.md) can check every new ticket or doc against it automatically, before implementation begins.
