# Analyst Cheat Sheet A quick reference for common operations in the CybrHawk 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: 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: ``` GET https://cybrhawksoc.gitbook.io/cybrhawk-docs/soc-analyst-guide/analyst-cheat-sheet.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.