ip-lookup-entity-chronicle

Retrieves IP address activity summaries from Chronicle SIEM using the lookup_entity tool.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security analysts need a fast way to check whether an IP address has been active inside their environment before deciding how deep to investigate. This Skill queries Chronicle SIEM's entity graph to return a summary of an IP's internal interactions, related alerts, and first/last seen timestamps within a configurable time window. ## Core Features & Use Cases - Entity Activity Lookup: Calls the secops-mcp lookup_entity tool with an IP address and optional hours_back window (default 24 hours). - Structured Outcomes: Returns a Chronicle entity summary plus a status of Success, NoInfoFound, or Failure, with optional parsing of related alert counts and seen timestamps. - Guided Triage Decisions: Includes decision logic that flags high-activity IPs for deeper network traffic analysis and escalates failures to human analysts. - Use Case: After an external threat intelligence check flags an IP as suspicious, run this Skill to see whether that IP touched any internal assets in the last 24 hours and whether it triggered related alerts. ## Quick Start Look up the IP address 203.0.113.10 in Chronicle for the last 24 hours and summarize its internal activity and related alerts.

Frequently Asked Questions about ip-lookup-entity-chronicle

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

FAQPage Schema
How do I look up an IP address in Chronicle SIEM?▼

Use the lookup_entity tool from the secops-mcp server, passing the IP address as the entity_value parameter. The tool returns a textual summary of the entity's activity, related alerts, and first/last seen times within the specified window.

How do I change the time window for a Chronicle entity lookup?▼

Set the hours_back parameter on the lookup_entity call to control how much historical data is considered. The default is 24 hours, but you can raise it to a larger value such as 168 for a 7-day view of older incidents.

What does it mean when a Chronicle IP lookup returns no information?▼

A NoInfoFound status means the tool ran successfully but found no activity for that IP in the time window. If external reputation is high risk, absence of internal logs may indicate a new command-and-control host or a logging gap worth investigating.

When should I run an internal IP lookup versus an external reputation check?▼

Internal Chronicle lookups typically run after external reputation checks, such as a Google Threat Intelligence report. The internal lookup confirms whether the IP actually interacted with your environment, which drives escalation decisions.

What should I do if the Chronicle lookup_entity call fails?▼

A Failure status includes an output message describing the issue. Log the error details to the case and escalate to a human analyst, since automated triage cannot proceed without the entity summary.