triage-alerts

Triage incoming security alerts using SOAR context, SIEM searches, and threat intelligence enrichment.

85|14|Updated May 17, 2025
One-click install
npx skills add https://github.com/dandye/adk_runbooks --skill triage-alerts-dandye
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage-alerts
Source: https://github.com/dandye/adk_runbooks/tree/main/skills/triage/triage-alerts
Command: npx skills add https://github.com/dandye/adk_runbooks --skill triage-alerts-dandye

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security operations teams face a constant stream of alerts that must be quickly assessed as false positives, benign activity, or genuine threats. This Skill provides a standardized runbook for the initial triage of security alerts, ensuring consistent assessment, duplicate detection, and proper escalation or closure decisions. ## Core Features & Use Cases - Duplicate Detection: Checks for similar or duplicate SOAR cases before investing analysis effort, closing confirmed duplicates with proper documentation. - Alert-Specific SIEM Search: Performs targeted SIEM queries based on alert type (suspicious logins, malware detections, network alerts) to gather immediate context. - Entity Enrichment: Enriches key entities (IPs, domains, hashes, users) using Google Threat Intelligence and Chronicle SIEM lookups. - Use Case: An analyst receives a suspicious login alert. The Skill gathers case details from the SOAR platform, checks for related open cases, searches SIEM for related login events, enriches the source IP with GTI, and either closes the alert as a false positive or escalates it with documented findings. ## Quick Start Triage the security alert with case ID 4821 by gathering context, checking for duplicates, enriching key entities, and recommending closure or escalation.

Frequently Asked Questions about triage-alerts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage security alerts in a SOAR platform?▼

Alert triage starts by gathering case details and events from the SOAR platform, then checking for duplicate cases, running a targeted SIEM search, and enriching key entities. Based on the findings, the alert is classified as false positive, benign true positive, or escalated for investigation.

How to check for duplicate security cases before investigation?▼

Use the SOAR platform's similar-case capability (siemplify_get_similar_cases) with the case ID to find potential duplicates. If duplication is confirmed, document the finding and close the case with a NOT_MALICIOUS reason referencing the existing case.

What tools are needed for automated alert triage?▼

This runbook uses Chronicle SOAR tools for case management, Chronicle SIEM for event searches and entity lookups, and Google Threat Intelligence for file, domain, IP, and URL reputation reports. These are accessed through MCP tool integrations.

Does alert triage include containment or eradication actions?▼

No, this runbook explicitly excludes containment, eradication, deep-dive investigation, and threat hunting. It covers only initial assessment, enrichment, and the decision to close or escalate the alert to further investigation runbooks.

When should an alert be closed as a false positive?▼

Close an alert as a false positive when enrichment and SIEM context show the activity matches known benign patterns or authorized behavior. Document the reasoning in the SOAR case and use an appropriate closure reason such as NOT_MALICIOUS with a valid root cause.