> For the complete documentation index, see [llms.txt](https://docs.threatdefence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.threatdefence.com/soc-analyst-guide/analyst-cheat-sheet.md).

# Analyst Cheat Sheet

A quick reference for common operations in the ThreatDefence Analyst Console.

***

| Goal                    | Action                                  | Hint                                              |
| ----------------------- | --------------------------------------- | ------------------------------------------------- |
| Find an alert           | Search: `td.alert.message:(*keyword*)`  | Combine `AND`, `OR`, and wildcards `*`            |
| Prioritise              | Use **Security Detections by Severity** | Work highest severity (e.g., **15**) first        |
| Take ownership          | Open alert → **Start Triage**           | Assign yourself to lock coordination              |
| Get advice/context      | Use **AI Assistant (Avesa)**            | Ask for likely root cause and next steps          |
| Investigate deeply      | Click **Hunt** from the alert           | Pivot by user, host, IP, file hash                |
| Document decisions      | Click **Update**                        | Always add notes; capture hypothesis & outcome    |
| Handle a false positive | **Interaction → Whitelist**             | Use **Lucene** syntax (see examples below)        |
| Escalate a real threat  | **Interaction → Escalate**              | Sends notification to default escalation contacts |
| Get human help          | Use **SecOps Chat**                     | Share alert link + short summary of findings      |

***


---

# 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.threatdefence.com/soc-analyst-guide/analyst-cheat-sheet.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.