> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/ida-9.5/add-ons/malware/concepts/triage.md).

# Triage (coming soon)

Hex-Rays is developing a triage feature for the Malware Analysis add-on. It helps you decide where to start in a new sample.

Triage finds the interesting regions of code in the sample. It matches code signatures, identifies what the code can do, separates library code from first-party code, and finds the boundaries of the object files that the linker combined. When you open a sample, a dialog shows you where to begin. You do not spend time on common functions, and you can go directly to the key behaviors of the malware, such as config parsing and the code that creates host-based and network-based indicators (HBIs and NBIs).

The **Triage** group of the Malware Analysis menu contains the [Multi-service Checker](/ida-9.5/add-ons/malware/concepts/multi-service-checker.md), which finds out what external services already know about the sample.

{% hint style="info" %}

## Coming soon

If you want early access to triage, email <support@hex-rays.com>.

If you have a question, an idea, or a problem, email <support@hex-rays.com>. The Malware Analysis team reads every message and replies quickly.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hex-rays.com/ida-9.5/add-ons/malware/concepts/triage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.