hash-search-process-events-chronicle

Searches Chronicle SIEM for process execution events matching a file hash.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Analysts investigating a suspicious file hash need to know where and how that file was executed across the environment, but manually building UDM queries against Chronicle SIEM is slow and error-prone. This Skill provides a repeatable procedure for searching process launch and file-related events tied to a specific hash. ## Core Features & Use Cases - UDM Query Construction: Builds natural-language queries for the secops-mcp search_security_events tool using the correct hash-type UDM field (e.g., principal.process.file.sha256). - Structured Output Extraction: Returns affected hosts, executed command lines, event timestamps, and a translated UDM query for auditing. - Decision Logic: Defines next steps for success, no-results, and failure outcomes, including escalation guidance for widespread malicious execution. - Use Case: After an entity lookup confirms a malicious SHA256 was seen internally, run this Skill to enumerate every host that executed it and inspect the associated command lines for further IOCs. ## Quick Start Search Chronicle for all process launch events involving SHA256 hash abc123 over the last 72 hours and list the affected hosts and command lines.

Frequently Asked Questions about hash-search-process-events-chronicle

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

FAQPage Schema
How do I search Chronicle SIEM for events matching a file hash?▼

Use the secops-mcp search_security_events tool with a query like "Events where principal.process.file.sha256 = '{hash}' in the last 72 hours". The Skill maps the hash, time window, and optional filters into the tool's text parameter and returns matching UDM events.

Which UDM field should I use for a file hash search in Chronicle?▼

Use principal.process.file.sha256 for executed processes, target.file.sha256 for files written or modified, and about.file.sha256 for files scanned by security tools. MD5 and SHA1 equivalents follow the same field pattern.

Can I filter Chronicle hash searches to only process launch events?▼

Yes, pass additional_query_terms such as "AND metadata.event_type = 'PROCESS_LAUNCH'" to narrow results. Without this filter the search may return broad file observation events across many event types.

What happens when a Chronicle hash search returns no events?▼

The Skill returns output_status "NoEventsFound" and logs that no process or file events matched the hash and field within the specified time window. You can widen hours_back or try a different UDM hash field before concluding the file was not observed.

What are the limitations of hash-based event searches in Chronicle?▼

Results depend on Chronicle ingesting telemetry that records the hash in the chosen UDM field, and the default window is only 72 hours. Hashes observed only in network or email contexts may require different UDM fields than process execution fields.