Skip to content
Back to skills

Enrich Ioc

ASecurity

Enrich an IOC (IP, domain, hash, URL) with threat intelligence. Use when you need to look up reputation and context for an indicator using GTI and SIEM. Returns threat intel findings, SIEM entity summary, and IOC match status.

  • 124 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added June 5, 2026
toolsgo

Works with

  • mcp

Security analysis

A100/100

Scanned June 5, 2026

npx -y skills add dandye/ai-runbooks --skill enrich-ioc --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Enrich Ioc?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Enrich Ioc
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/dandye-enrich-ioc/badge)](https://www.skillsdirectory.com/skills/dandye-enrich-ioc)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: enrich-ioc
description: "Enrich an IOC (IP, domain, hash, URL) with threat intelligence. Use when you need to look up reputation and context for an indicator using GTI and SIEM. Returns threat intel findings, SIEM entity summary, and IOC match status."
required_roles:
  chronicle: roles/chronicle.viewer
  gti: GTI Standard
personas: [tier1-analyst, tier2-analyst, tier3-analyst, threat-hunter, incident-responder]
---

# Enrich IOC Skill

Perform standardized enrichment for a single Indicator of Compromise (IOC) using Google Threat Intelligence (GTI) and Chronicle SIEM.

## Inputs

- `IOC_VALUE` - The indicator value (e.g., "198.51.100.10", "evil-domain.com", "abcdef123456...", "http://bad.url/path")
- `IOC_TYPE` - The type: "IP Address", "Domain", "File Hash", or "URL"

## Workflow

### Step 1: GTI Enrichment

Based on IOC_TYPE, call the appropriate GTI tool:

| IOC Type | Tool | Example |
|----------|------|---------|
| IP Address | `gti-mcp.get_ip_address_report` | `get_ip_address_report(ip_address="198.51.100.10")` |
| Domain | `gti-mcp.get_domain_report` | `get_domain_report(domain="evil-domain.com")` |
| File Hash | `gti-mcp.get_file_report` | `get_file_report(hash="abcdef123...")` |
| URL | `gti-mcp.get_url_report` | `get_url_report(url="http://bad.url/path")` |

Store key findings in `GTI_FINDINGS`:
- Reputation score
- Classification (malicious, suspicious, clean)
- Key relationships (contacted domains, IPs, etc.)
- Associated malware families or campaigns

**Error Handling:** If GTI fails (quota exceeded, IOC not found), note the limitation and proceed with SIEM enrichment.

### Step 2: SIEM Entity Lookup

```
secops-mcp.lookup_entity(entity_value=IOC_VALUE)
```

Store in `SIEM_ENTITY_SUMMARY`:
- First/last seen timestamps
- Related alerts
- Associated assets/users

### Step 3: SIEM IOC Match Check

```
secops-mcp.get_ioc_matches()
```

Check if IOC_VALUE appears in results. Store Yes/No in `SIEM_IOC_MATCH_STATUS`.

## Required Outputs

**After completing this skill, you MUST report these outputs:**

| Output | Description |
|--------|-------------|
| `GTI_FINDINGS` | Summary of GTI report (reputation, classification, relationships) |
| `SIEM_SUMMARY` | SIEM entity context (first/last seen, related alerts) |
| `IOC_MATCH_STATUS` | Yes/No - whether IOC appears in recent threat feed matches |
| `THREAT_SCORE` | Numerical threat score (0-100) based on GTI reputation |
| `MALICIOUS_CONFIDENCE` | Confidence level: `high`, `medium`, `low`, or `none` |

## Quick Reference

**GTI Tools:**
- `get_ip_address_report(ip_address)`
- `get_domain_report(domain)`
- `get_file_report(hash)`
- `get_url_report(url)`

**SIEM Tools:**
- `lookup_entity(entity_value)`
- `get_ioc_matches()`

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.