suspicious-login-triage

Triages suspicious login alerts by enriching user, IP, and hostname context from SIEM and SOAR.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Tier 1 SOC analysts face a high volume of suspicious login alerts (impossible travel, untrusted locations, repeated failed logins) and need a consistent, repeatable process to gather context and decide whether to close or escalate each case. ## Core Features & Use Cases - Entity Extraction & Enrichment: Pulls the user ID, source IP, and hostname from SOAR case events, then enriches them via Chronicle SIEM lookups and Google Threat Intelligence IP reports. - Login Pattern Analysis: Runs UDM queries over the last 24-72 hours of authentication events to detect anomalies such as impossible travel or success-after-failure patterns. - Documented Recommendations: Posts a synthesized triage comment with a clear recommendation (close as false positive, escalate to Tier 2, or consider account lockdown) directly into the SOAR case, with an optional Markdown report. - Use Case: An analyst receives an "Impossible Travel" alert for a user; the skill gathers user history, IP reputation, related open cases, and optional Okta account status, then documents an escalation recommendation in the case. ## Quick Start Triage the suspicious login alerts in SOAR case 4821 and document your findings and recommendation in the case.

Frequently Asked Questions about suspicious-login-triage

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

FAQPage Schema
How do I triage a suspicious login alert in a SOAR case?▼

Provide the SOAR case ID and alert identifiers, then extract the user ID, source IP, and hostname from case events. Enrich each entity with SIEM lookups and threat intelligence, analyze recent login patterns, and post a recommendation comment to the case.

How to investigate impossible travel alerts with Chronicle SIEM?▼

Use lookup_entity to retrieve the user's history and search_security_events with a UDM query filtering USER_LOGIN and AUTH_ATTEMPT events for the user over the last 24-72 hours. Compare source IPs and geolocations to identify impossible travel patterns.

What tools are needed for suspicious login triage?▼

The workflow uses secops-soar for case details and event listing, secops-mcp for SIEM entity lookups and UDM event searches, and gti-mcp for IP reputation reports. An identity provider integration such as okta-mcp is optional for account status checks.

Can this runbook check Okta account status during triage?▼

Yes, if an Okta MCP tool is available, the optional identity provider step calls lookup_okta_user with the extracted user ID to check account status, recent legitimate logins, and MFA methods. This step is skipped when no IdP tool is configured.

When should a suspicious login alert be escalated instead of closed?▼

Escalate when enrichment shows malicious IP reputation, anomalous login patterns inconsistent with user history, or related open cases indicating a broader campaign. Close as a false positive when evidence supports known legitimate activity, and document the reasoning in the case comment.