investigate-case-external-tools

Investigate SOAR cases by enriching entities with GTI, SIEM, and Okta intelligence.

85|14|Updated May 17, 2025
One-click install
npx skills add https://github.com/dandye/adk_runbooks --skill investigate-case-external-tools-dandye
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: investigate-case-external-tools
Source: https://github.com/dandye/adk_runbooks/tree/main/skills/investigation/investigate-case-external-tools
Command: npx skills add https://github.com/dandye/adk_runbooks --skill investigate-case-external-tools-dandye

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security analysts handling anomalous login cases must manually pivot across multiple platforms—SOAR, SIEM, threat intelligence, and identity providers—to gather context, decide on a disposition, and take containment action. This Skill orchestrates that entire investigation workflow so evidence is gathered consistently and decisions are documented. ## Core Features & Use Cases - Entity Extraction & Enrichment: Pulls alerts from a SOAR case, identifies entities (users, IPs, hosts), and enriches each with Chronicle SIEM lookups, Google Threat Intelligence reports, and UDM event searches. - Identity Verification & Response: Looks up the primary user in Okta, analyzes suspicious characteristics, and—after analyst confirmation—disables the compromised account. - Case Documentation: Posts a full investigation summary as a SOAR case comment, including related open cases found via entity-based case search. - Use Case: Given a case of anomalous login alerts, the agent enriches every involved entity with GTI and SIEM context, checks the user's Okta profile for suspicious signals, disables the user upon confirmation, and records findings for Tier 2 escalation or benign closure. ## Quick Start Investigate SOAR case 4821 for anomalous logins by enriching all entities with GTI and SIEM, checking the user's Okta profile, and disabling the account if suspicious.

Frequently Asked Questions about investigate-case-external-tools

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

FAQPage Schema
How do I investigate an anomalous login case with threat intelligence?ā–¼

Start by listing alerts in the SOAR case to extract entities like users, IPs, and hosts. Enrich each entity with SIEM lookups and GTI reports, search related UDM events, then check the user's Okta profile before deciding to escalate or close the case.

What tools does this investigation workflow use?ā–¼

The workflow uses secops-soar for case and alert management, secops-mcp for SIEM entity lookup and event search, gti-mcp for Google Threat Intelligence reports, and okta-mcp for user lookup and account disablement.

Can the agent disable an Okta user automatically?ā–¼

The agent analyzes Okta user details for suspicious characteristics but asks the analyst for confirmation before disabling the account. The disable action only executes after an explicit affirmative response.

How are investigation findings documented in the SOAR case?ā–¼

Findings are posted as a case comment summarizing the anomalous login, GTI and SIEM checks performed, related open cases, Okta review results, and any containment actions taken such as user disablement.

When should a case be escalated versus closed as benign?ā–¼

The external_tool_router node routes based on the enriched evidence: cases with confirmed suspicious indicators escalate to Tier 2, while cases where enrichment shows benign activity are closed. Both branches end with a documented report summary.