> 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/modules/threat-modeler/implement-threat-model-results.md).

# Implement Threat Model Results

At the last step, you can operationalize the threat model outputs. At this step, you can review security requirements, actions, tests, and other tasks that were deemed relevant as a result of the threat modeling.

We group these downstream activities into four groups:

* Mitigation Actions: These are tasks that need to be performed by security or engineering teams. You can directly push these tasks to your issue tracking platform.
* Automated Tests: These are tests that DevArmor can automatically run in GitHub. They act as policies that apply to code review performed by DevArmor.
* Maual Tests: These items are tests that cannot be run automatically and need to be run manually by users.
* Penetration Tests: These are penetration test scopes that can be pushed to bug bounty programs or penetration testing consultants.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.devarmor.com/modules/threat-modeler/implement-threat-model-results.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.