菜单
Explore GTI relationships for an IOC to discover related entities. Use to expand investigation by finding connected domains, IPs, files, or threat actors. Takes an IOC and relationship types to query.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Perform exhaustive analysis of a critical IOC. Use when an IOC needs Tier 2+ investigation beyond basic enrichment - includes GTI pivoting, deep SIEM searches, correlation with related entities, and threat attribution. For escalated IOCs requiring comprehensive investigation.
Complete Tier 1 triage workflow. Orchestrates the full alert triage process: check-duplicates, triage-alert, enrich-ioc for each entity, and either close (FP/BTP) or escalate (TP/Suspicious). Use for end-to-end alert processing.
Complete Tier 2 investigation workflow. Orchestrates deep investigation of escalated cases: deep-dive-ioc, correlate-ioc, specialized triage (malware/login), pivot-on-ioc, and generate comprehensive report. Use for escalated cases requiring thorough analysis.
Check for duplicate or similar cases. Use before deep analysis to avoid investigating the same incident twice. Takes a CASE_ID and returns list of similar cases.
Close a case or alert with proper reason and documentation. Use when triage determines an alert is FP/BTP or investigation is complete. Requires artifact ID, type, closure reason, and root cause.
Check for existing SIEM alerts and case management entries related to IOCs. Use to understand if an indicator has triggered previous alerts or is part of ongoing investigations. Takes IOC list and returns related alerts and cases.
| name | pivot-on-ioc |
| description | Explore GTI relationships for an IOC to discover related entities. Use to expand investigation by finding connected domains, IPs, files, or threat actors. Takes an IOC and relationship types to query. |
| required_roles | {"gti":"GTI Enterprise+"} |
| personas | ["tier2-analyst","tier3-analyst","threat-hunter"] |
Explore relationships connected to an IOC within Google Threat Intelligence (GTI) to discover related entities for investigation expansion.
IOC_VALUE - The indicator value to pivot fromIOC_TYPE - The type: "IP Address", "Domain", "File Hash", "URL", or "Collection"RELATIONSHIP_NAMES - List of relationships to query (see table below)| IOC Type | Common Relationships |
|---|---|
| IP Address | communicating_files, downloaded_files, referrer_files, resolutions |
| Domain | resolutions, communicating_files, downloaded_files, subdomains, siblings |
| File Hash | contacted_domains, contacted_ips, contacted_urls, dropped_files, embedded_domains |
| URL | communicating_files, downloaded_files, last_serving_ip_address |
| Collection | malware_families, attack_techniques, threat_actors, indicators |
Based on IOC_TYPE:
| IOC Type | Tool |
|---|---|
| IP Address | gti-mcp.get_entities_related_to_an_ip_address |
| Domain | gti-mcp.get_entities_related_to_a_domain |
| File Hash | gti-mcp.get_entities_related_to_a_file |
| URL | gti-mcp.get_entities_related_to_an_url |
| Collection | gti-mcp.get_entities_related_to_a_collection |
For each relationship in RELATIONSHIP_NAMES:
[selected_tool](
identifier=IOC_VALUE,
relationship_name=relationship
)
Store results keyed by relationship name.
After completing this skill, you MUST report these outputs:
| Output | Description |
|---|---|
RELATED_ENTITIES | Dictionary of entities found per relationship |
EXPANDED_IOCS | Flattened list of all discovered IOCs (IPs, domains, hashes) |
THREAT_CONTEXT | Threat actor/campaign context if found during pivoting |
PIVOT_STATUS | Success/failure status of the pivoting |
File Hash Investigation:
IOC_VALUE: "abcdef123456..."
IOC_TYPE: "File Hash"
RELATIONSHIP_NAMES: ["contacted_domains", "contacted_ips", "dropped_files"]
Domain Investigation:
IOC_VALUE: "suspicious-domain.com"
IOC_TYPE: "Domain"
RELATIONSHIP_NAMES: ["resolutions", "communicating_files", "subdomains"]