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.
88
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Perform exhaustive analysis of a single, potentially critical Indicator of Compromise escalated from Tier 1 or identified during an investigation.
IOC_VALUE - The IOC to analyze (IP, domain, hash, or URL)IOC_TYPE - The type: "IP Address", "Domain", "File Hash", or "URL"CASE_ID - case ID for documentation (optional)TIME_FRAME_HOURS - Lookback period (default: 168 = 7 days)secops-soar.get_case_full_details(case_id=CASE_ID)Get comprehensive threat intelligence:
| IOC Type | Tool |
|---|---|
| IP | gti-mcp.get_ip_address_report(ip_address=IOC_VALUE) |
| Domain | gti-mcp.get_domain_report(domain=IOC_VALUE) |
| Hash | gti-mcp.get_file_report(hash=IOC_VALUE) |
| URL | gti-mcp.get_url_report(url=IOC_VALUE) |
Record:
ASSOCIATED_THREAT_IDSUse /pivot-on-ioc or directly call GTI relationship tools:
Recommended relationships by type:
communicating_files, downloaded_files, resolutionsresolutions, communicating_files, subdomainscontacted_domains, contacted_ips, dropped_filescommunicating_files, downloaded_filesFor file hashes, also get behavior summary:
gti-mcp.get_file_behavior_summary(hash=IOC_VALUE)Search for activity involving the IOC and its related entities:
secops-mcp.search_security_events(
text="UDM query for IOC_VALUE",
hours_back=TIME_FRAME_HOURS
)Identify OBSERVED_RELATED_IOCS - IOCs from GTI pivoting that actually appear in SIEM results.
For the IOC and each OBSERVED_RELATED_IOC:
/enrich-ioc for enrichment/correlate-ioc for alert/case correlation/find-relevant-case for broader case searchIf ASSOCIATED_THREAT_IDS were found (malware families, actors):
gti-mcp.get_collection_report(id=THREAT_ID)Combine all findings:
Document in Case (if CASE_ID provided):
Use /document-in-case with comprehensive findings summaryOr generate standalone report:
Use /generate-report with REPORT_TYPE="deep_dive_ioc"After completing this skill, you MUST report these outputs:
| Output | Description |
|---|---|
GTI_DEEP_FINDINGS | Comprehensive GTI analysis (reputation, classification, behaviors) |
SIEM_DEEP_CONTEXT | Extended SIEM event context (hosts, users, timelines) |
RELATED_ENTITIES | Related IOCs from GTI pivoting (infrastructure connections) |
DISCOVERED_IOCS | All IOCs discovered during analysis |
THREAT_ATTRIBUTION | Threat actor/campaign attribution if found |
Additionally provide:
Use /enrich-ioc | Use /deep-dive-ioc |
|---|---|
| Initial triage | Escalated from Tier 1 |
| Quick context needed | Comprehensive investigation |
| Single IOC lookup | Full infrastructure mapping |
| Tier 1 workflow | Tier 2+ investigation |
67a00be
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.