secops-triage

Triage security alerts and cases using the Alert Triage Protocol.

513|130|Updated Apr 2, 2025
One-click install
npx skills add https://github.com/google/mcp-security --skill secops-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secops-triage
Source: https://github.com/google/mcp-security/tree/main/extensions/google-secops/skills/triage
Command: npx skills add https://github.com/google/mcp-security --skill secops-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security operations teams need a repeatable, transparent process to triage alerts and cases, identify false positives, benign true positives, and true positives, and decide when to escalate or close.

Core Features & Use Cases

  • Standardized Alert Triage Protocol that guides context gathering, duplicate detection, related cases lookup, SIEM enrichment, and final actions.
  • Supports remote and local tooling workflows to determine escalation paths and next steps in incident response.
  • Use Case: A newly surfaced alert is quickly assessed for legitimacy, linked to existing cases, enriched with SIEM context, and either closed or escalated for investigation.

Quick Start

Provide an ALERT_ID or CASE_ID to begin triage of an alert or case. The skill will guide you through context gathering, duplication checks, SIEM enrichment, enrichment, and final actions.

Frequently Asked Questions about secops-triage

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

FAQPage Schema
How do I triage security alerts to identify false positives and true positives?

Security alert triage requires gathering context, detecting duplicates, searching related cases, and enriching SIEM data to classify alerts as false positives, benign true positives, true positives, or suspicious results.

What is the best way to standardize SOC case management and incident response workflows?

Standardized SOC case management applies a defined Alert Triage Protocol to guide context gathering, duplication checks, SIEM enrichment, and final actions, ensuring consistent and transparent escalation or closure decisions.

How do I check for duplicate alerts and related cases during incident response?

Checking for duplicate alerts involves using platform tooling like list_cases and udm_search to search existing cases, link newly surfaced alerts, and gather context before determining escalation paths.

Can I use SIEM enrichment to assess alert legitimacy and decide whether to escalate or close?

SIEM enrichment assesses alert legitimacy by applying remote and local tooling workflows to gather context, identify related cases, and determine whether to escalate for investigation or close as a false positive.

Do I need an ALERT_ID or CASE_ID to start security alert triage?

Starting security alert triage requires providing an ALERT_ID or CASE_ID, which initiates the workflow through context gathering, duplication checks, SIEM enrichment, and final standardized actions.