hash-lookup-entity-chronicle

Look up file hash entity activity and related alerts in Chronicle SIEM.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security analysts need a fast way to determine whether a suspicious file hash has been observed inside their environment. This Skill retrieves a Chronicle SIEM entity summary for a file hash, showing internal sightings, related alerts, and first/last seen times without manual console queries. ## Core Features & Use Cases - Entity Lookup: Calls the secops-mcp lookup_entity tool with a file hash (MD5, SHA1, or SHA256) and a configurable lookback window (default 72 hours). - Structured Outputs: Returns the Chronicle entity summary plus parsable fields such as related alert count and observed host count, with a clear status of Success, NoInfoFound, or Failure. - Decision Logic: Automatically flags hashes for further internal investigation when activity is observed and routes to process event search runbooks. - Use Case: After an external reputation check flags a SHA256 hash as suspicious, run this Skill to see whether any internal hosts executed or observed the file in the last three days. ## Quick Start Look up the file hash 44d88612fea8a8f36de82e1278abb02f in Chronicle for the last 72 hours and summarize any internal activity and related alerts.

Frequently Asked Questions about hash-lookup-entity-chronicle

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

FAQPage Schema
How do I look up a file hash in Chronicle SIEM?▼

Use the secops-mcp lookup_entity tool by mapping the file hash to the entity_value parameter and setting hours_back for the time window. The tool returns a textual summary of internal sightings, related alerts, and first/last seen times.

What hash formats does Chronicle entity lookup support?▼

The lookup accepts MD5, SHA1, and SHA256 file hashes as the entity_value input. The hash typically comes from alert data or the output of an external reputation check such as a Google Threat Intelligence report.

What is the default time window for Chronicle hash lookups?▼

The default hours_back value is 72 hours, covering three days of historical data. You can adjust this parameter to widen or narrow the search window depending on the investigation scope.

What happens when no activity is found for a file hash in Chronicle?▼

The runbook returns an output_status of NoInfoFound and logs that no activity was observed for the hash in the specified window. The hash is then flagged as having no internal activity observed via lookup.

What should I do after a Chronicle hash lookup shows internal sightings?▼

When related alerts or observed hosts are found, flag the hash for further internal investigation and proceed to the process event search runbook for detailed execution logs. This drills into which hosts executed the file and when.