soc-investigator

Triage IOCs across Microsoft Defender, VirusTotal, and Sentinel without API access.

2|1|Updated Jun 23, 2026
One-click install
npx skills add https://github.com/Kaidanov/grekai-skills-4all --skill soc-investigator-kaidanov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: soc-investigator
Source: https://github.com/Kaidanov/grekai-skills-4all/tree/main/skills/soc-investigator
Command: npx skills add https://github.com/Kaidanov/grekai-skills-4all --skill soc-investigator-kaidanov

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Security teams in locked-down tenants cannot grant API, MCP, or Entra access to AI tools, which blocks automated SOC triage. This Skill coordinates an air-gapped workflow where the human runs portal queries in their own authenticated browser while local Python scripts handle KQL generation, CSV unification, and VirusTotal enrichment. ## Core Features & Use Cases - KQL Query Generation: Produces one Defender Advanced Hunting query per machine group from a single config.json containing your IOCs, device filters, and thresholds. - Local Enrichment Pipeline: Unifies exported Defender CSVs, looks up each indicator in VirusTotal v3 using your VT_API_KEY, applies verdict rules, and writes a report, a pre-filled Sentinel blast-radius query, and a soc_report.csv for Threat Sentinel. - Human-Confirmed Closure: Prepares the incident classification and comment package but never closes incidents automatically; the analyst approves and clicks Close in Sentinel. - Use Case: A CISO receives a list of suspicious domains and file hashes, runs the generated KQL in Defender, exports the CSVs, enriches them locally, and gets a ready-to-paste Sentinel query identifying every affected machine and user. ## Quick Start Ask Claude to run the SOC investigation on your list of suspicious domains and file hashes, then follow the guided Defender export and Sentinel pivot steps.

Frequently Asked Questions about soc-investigator

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

FAQPage Schema
How do I hunt IOCs in Microsoft Defender without API access?

Generate per-machine-group Advanced Hunting KQL from a config.json containing your domains, URLs, and hashes, then paste each query into Defender Advanced Hunting in your own browser and export the results as CSV. A local Python script then unifies and enriches those exports.

How do I enrich IOCs with VirusTotal from the command line?

Set your VT_API_KEY environment variable and run the enrichment script against your exported Defender CSVs. It looks up each domain, URL, IP, and hash via the VirusTotal v3 API, applies a detection-threshold verdict rule, and writes a report plus a Sentinel-ready query.

Does this require an Entra app registration or Sentinel API keys?

No. The default cowork mode makes zero API calls to Defender or Sentinel; you run queries in your own authenticated browser. An optional local-automated mode exists if you can register an Entra app with ThreatHunting.Read.All and Log Analytics Reader permissions.

Can it close Sentinel incidents automatically?

No. Closing incidents is always human-confirmed. The tooling prepares the incident list, classification, and justification comment, but the analyst clicks Close in the Sentinel UI, or explicitly approves with a typed yes plus a --close flag in local mode.

What Python dependencies does the enrichment script need?

None beyond the standard library. The scripts use only json, csv, urllib, and base64, so no pip install is required and they run in restricted environments.