Skip to content
Security
Skill

/alert-triage

Triage a SIEM/EDR alert end-to-end — validate it's real, enrich and scope it, reach a consistent verdict, and decide escalate vs. close with documented rationale. Use when working a SOC alert queue and you need a repeatable, defensible triage.

From plugin
awesome-claude-security
11111 skills17 agents13 commands1 MCP

Claude Code

$ npx -y skills add jassics/awesome-claude-security --skill alert-triage --agent claude-code

SKILL.md

alert-triage.SKILL.md
name: alert-triage
description: >-
  Triage a SIEM/EDR alert end-to-end — validate it's real, enrich and scope it,
  reach a consistent verdict, and decide escalate vs. close with documented rationale.
  Use when working a SOC alert queue and you need a repeatable, defensible triage.

Goal

A consistent, evidence-backed verdict on an alert — true positive / false positive / benign-true-positive — with the right next action (escalate, close, tune) and a record that the next analyst can follow.

Steps

1. **Understand the alert** — what detection fired, the underlying logic, the ATT&CK technique, and why it triggered. Read the rule, don't guess. 2. **Validate** — is this real activity or a known false-positive pattern? Confirm against the source telemetry, not just the alert summary. 3. **Enrich** — add context: user/asset criticality, the involved IOCs (`threat-intelligence:ioc-enrichment`), process lineage, recent related alerts, and whether it matches known-good behavior. 4. **Scope** — pivot to see if it's isolated or part of a broader pattern (same host/ user/campaign, lateral movement). Check for related alerts you should correlate. 5. **Decide & act:**

  • **Escalate** → `dfir:incident-response` for confirmed/likely incidents, with the

evidence package and scope assembled.

  • **Close** → document why (benign/expected), preserving the rationale.
  • **Tune** → recurring false positive → feed back to

`detection-engineering:detection-rule-development` (don't just mute). 6. **Record** — verdict, evidence, actions, and timestamps.

Output

A triage record: alert · ATT&CK technique · verdict · evidence · scope · action (escalate/close/tune) · rationale. Confirmed incidents → `dfir`; recurring FPs → `detection-engineering`.

Notes

Consistency is the goal — the same alert should get the same verdict regardless of analyst. Always validate against source telemetry before deciding, and feed recurring false positives back into detection tuning rather than muting them (muting hides the problem and erodes coverage). Preserve evidence and rationale for every verdict.

Read more
@jassics
Ships withawesome-claude-security

A Claude Code plugin marketplace for the full cybersecurity & GenAI-security lifecycle — from recon and threat modeling to detection engineering, GRC, and CISO-level strategy. A pentester knows which OWASP test bends a broken-access-control endpoint.

11111 skills17 agents1 MCP
Get the whole plugin

Stars on GitHub

Momentum

stars in total
11
Star history of jassics/awesome-claude-security on GitHub, a chart by star-history.com

Other skills on awesome-claude-security.

More skills from other plugins.

api-security

api-security

Use for authorized security assessment of REST, GraphQL, WebSocket, or SOAP APIs, including discovery, authentication,…

@zhaoxuya520@zhaoxuya520Install Skill
nemoclaw-user-guide

nemoclaw-user-guide

Find official NemoClaw documentation for installation, configuration, operation, or troubleshooting. Also handles requested docs…

nemoclaw12d23k
@nvidia@nvidiaInstall Skill

Questions about alert-triage.

Which coding agents can use alert-triage?
alert-triage installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.