ip-search-network-traffic-chronicle

Searches Chronicle SIEM for UDM network connection events involving a target IP address.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security analysts often need deeper visibility than a high-level entity summary provides when investigating a suspicious IP address. This Skill performs a detailed search of UDM network connection events in Chronicle SIEM, returning the raw event records needed to identify suspicious patterns like beaconing, unusual ports, or large data transfers. ## Core Features & Use Cases - Targeted UDM Event Search: Queries Chronicle via the secops-mcp search_security_events tool for network traffic where the IP appears as principal or target. - Configurable Query Parameters: Supports adjustable lookback windows (hours_back), result limits (max_events), and additional UDM filter terms such as protocol or port conditions. - Structured Output & Decision Logic: Returns UDM events, the translated query, total match counts, and a status field, with explicit next-step guidance for success, no-results, and failure cases. - Use Case: After an entity lookup flags IP 192.168.1.100 as suspicious, run this Skill to retrieve all network connections involving that IP over the last 48 hours, then analyze destination ports and protocols for signs of lateral movement. ## Quick Start Search Chronicle for all network traffic involving IP address 203.0.113.50 over the last 24 hours and summarize the destination ports and protocols.

Frequently Asked Questions about ip-search-network-traffic-chronicle

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

FAQPage Schema
How do I search network traffic for an IP address in Chronicle SIEM?▼

Use the search_security_events tool from the secops-mcp server with a query matching the IP as principal or target. Provide the IP address, a lookback window in hours, and optionally a maximum event count and extra UDM filter terms.

How to filter Chronicle UDM queries by protocol or port?▼

Append additional UDM filter conditions through the additional_query_terms parameter, such as "AND network.application_protocol = 'DNS'" or "AND target.port = 445". These terms are appended to the base IP query before execution.

What does the search_security_events tool return in Chronicle?▼

It returns a list of UDM event records, the translated UDM query that Chronicle executed, and the total number of matching events. The total may exceed the max_events limit, meaning only a subset of results was returned.

Why does a Chronicle IP traffic search return no events?▼

A NoEventsFound status means the query ran successfully but no matching network events existed in the specified time window. Consider extending hours_back, loosening filter terms, or evaluating whether the absence of traffic is itself suspicious.

When should I use detailed event search instead of an entity lookup?▼

Use detailed event search when an entity lookup summary is insufficient or indicates suspicious activity requiring deeper analysis. Entity lookups provide broad context, while event searches return the raw UDM records needed for pattern analysis.