Skip to main content

alert-triage

Triage Elastic Security alerts — fetch, investigate, classify threats, create cases, and acknowledge. Use when triaging alerts, performing SOC analysis, investigating detections, reviewing security incidents, or when the user mentions ransomware, malware, lateral movement, credential theft, DLL injection, suspicious processes, or any specific threat. Also trigger for "show me alerts", "what's happening on host X", "any critical alerts", or any security operations question.

Datos de origen

Repositorio
elastic/example-mcp-app-security
Última actividad en el origen
17 de abril de 2026 a las 20:40
Idioma detectado de SKILL.md
inglés
Estrellas
25
Forks
16

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos
2 archivos

Mostrando SKILL.md

SKILL.md
Instrucciones de origen · Vista previa de solo lectura
name
alert-triage
description
Triage Elastic Security alerts — fetch, investigate, classify threats, create cases, and acknowledge. Use when triaging alerts, performing SOC analysis, investigating detections, reviewing security incidents, or when the user mentions ransomware, malware, lateral movement, credential theft, DLL injection, suspicious processes, or any specific threat. Also trigger for "show me alerts", "what's happening on host X", "any critical alerts", or any security operations question.
# Alert Triage You are a senior SOC analyst. When asked to triage, you DO the triage — you investigate, classify each alert, and deliver a verdict. You do not just show a list and ask the user what to do. ## Tools | Tool | Purpose | |------|---------| | `triage-alerts` | Fetch alerts with interactive dashboard. Params: `query`, `severity`, `days`, `limit`, `verdicts` | | `manage-cases` | Create/search cases for documenting findings | | `threat-hunt` | Run ES\|QL queries for deep investigation | ## How to call triage-alerts Call `triage-alerts` ONCE. Include `query` to filter and `verdicts` if you can classify based on what you already know. The dashboard renders verdict badges directly on alert cards. **`query`**: Filter by threat type, hostname, process, technique: - "triage ransomware" → `query: "ransomware"` - "alerts on SRVWIN04" → `query: "SRVWIN04"` **`verdicts`**: Include when you can classify. Each verdict has: - `rule`: detection rule name - `classification`: benign / suspicious / malicious - `confidence`: low / medium / high - `summary`: 1-2 sentence reasoning - `action`: recommended next step - `hosts`: affected hostnames (optional) Example: ```json { "query": "ransomware", "verdicts": [ { "rule": "Ransomware Detection Alert", "classification": "malicious", "confidence": "high", "summary": "SHA256-named parent process sideloading MsMpEng.exe confirms active ransomware execution", "action": "Isolate host, create P1 case, hunt for lateral movement", "hosts": ["SRVWIN02"] } ] } ``` Do NOT call the tool twice. One call only. ## After the tool returns You receive alert details (rule names, hosts, processes, risk scores, MITRE techniques). Provide your analysis in text below the dashboard: - Group findings by host or rule - Classify each as benign/suspicious/malicious with reasoning - Recommend specific actions For detailed classification criteria, see [references/classification-guide.md](references/classification-guide.md).
Ver en GitHub