Performing Ioc Enrichment Automation
Overview
Cybersecurity skill for performing ioc enrichment automation. Follows industry best practices and security standards.
When to Use
Trigger phrases:
- "performing ioc enrichment automation"
- "SOC analysts need to quickly enrich IOCs from multiple sources during alert tria"
- "High alert volumes require automated enrichment to reduce manual lookup time"
- "Incident investigations need comprehensive IOC context for scope assessment"
Use this skill when:
- SOC analysts need to quickly enrich IOCs from multiple sources during alert triage
- High alert volumes require automated enrichment to reduce manual lookup time
- Incident investigations need comprehensive IOC context for scope assessment
- SOAR playbooks require enrichment actions as part of automated triage workflows
Do not use for bulk blocking decisions without analyst review — enrichment provides context, not definitive malicious/benign determination.
When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
Prerequisites
- API keys: VirusTotal (free or premium), AbuseIPDB, Shodan, URLScan.io, GreyNoise
- Python 3.8+ with
requests, vt-py, shodan libraries
- MISP instance or TIP for cross-referencing organizational intelligence
- SOAR platform (optional) for workflow integration
- Rate limit awareness: VT free (4 req/min), AbuseIPDB (1000/day), Shodan (1 req/sec)
Workflow
# Example: IOC detection
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs(text: str) -> dict:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
- Plan Operations — Define objectives, scope, and success criteria for ioc enrichment automation operations.
- Prepare Environment — Set up tools, access, and data sources required for ioc enrichment automation.
- Execute Core Workflow — Perform the ioc enrichment automation operations following established procedures.
- Validate Results — Verify that results meet quality standards and objectives.
- Report Findings — Document results, observations, and recommendations.
- Follow Up — Track remediation actions and verify fixes where applicable.
Tools
- Analysis Platform — Data processing and visualization
- Collaboration Tools — Team coordination and knowledge sharing
Process
- Design — Define interface, identify patterns, plan implementation
- Implement — Write code following existing conventions, add tests
- Verify — Run tests, check integration, validate behavior
Verification
Anti-Rationalization Table
| Rationalization |
Reality |
| "We are too small to be targeted" |
Automated attacks target everyone. Size does not matter. |
| "Security slows us down" |
A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" |
Vulnerabilities in production are exploited within hours. Fix before deploy. |
1---2name: performing-ioc-enrichment-automation3description: Use when automates Indicator of Compromise (IOC) enrichment by orchestrating lookups across VirusTotal, AbuseIPDB, Shodan, MISP, and other intelligence sources to provide contextual scoring and disposition recommendations. Use when SOC analysts need rapid multi-source enrichment of IPs, domains, URLs, and file hashes during alert triage or incident investigation.4license: Apache-2.05---67# Performing Ioc Enrichment Automation89## Overview1011Cybersecurity skill for performing ioc enrichment automation. Follows industry best practices and security standards.1213## When to Use1415**Trigger phrases:**16- "performing ioc enrichment automation"17- "SOC analysts need to quickly enrich IOCs from multiple sources during alert tria"18- "High alert volumes require automated enrichment to reduce manual lookup time"19- "Incident investigations need comprehensive IOC context for scope assessment"202122Use this skill when:23- SOC analysts need to quickly enrich IOCs from multiple sources during alert triage24- High alert volumes require automated enrichment to reduce manual lookup time25- Incident investigations need comprehensive IOC context for scope assessment26- SOAR playbooks require enrichment actions as part of automated triage workflows2728**Do not use** for bulk blocking decisions without analyst review — enrichment provides context, not definitive malicious/benign determination.293031## When NOT to Use3233- When you lack proper authorization for testing34- For production systems without change management35- When the task requires legal or compliance expertise beyond technical scope363738## Prerequisites3940- API keys: VirusTotal (free or premium), AbuseIPDB, Shodan, URLScan.io, GreyNoise41- Python 3.8+ with `requests`, `vt-py`, `shodan` libraries42- MISP instance or TIP for cross-referencing organizational intelligence43- SOAR platform (optional) for workflow integration44- Rate limit awareness: VT free (4 req/min), AbuseIPDB (1000/day), Shodan (1 req/sec)4546## Workflow4748```python49# Example: IOC detection50import re5152IOC_PATTERNS = {53 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",54 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",55 "hash_md5": r"\b[a-f0-9]{32}\b",56 "hash_sha256": r"\b[a-f0-9]{64}\b",57}5859def extract_iocs(text: str) -> dict:60 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}61```62631. **Plan Operations** — Define objectives, scope, and success criteria for ioc enrichment automation operations.642. **Prepare Environment** — Set up tools, access, and data sources required for ioc enrichment automation.653. **Execute Core Workflow** — Perform the ioc enrichment automation operations following established procedures.664. **Validate Results** — Verify that results meet quality standards and objectives.675. **Report Findings** — Document results, observations, and recommendations.686. **Follow Up** — Track remediation actions and verify fixes where applicable.6970## Tools7172- **Analysis Platform** — Data processing and visualization73- **Collaboration Tools** — Team coordination and knowledge sharing747576## Process77781. **Design** — Define interface, identify patterns, plan implementation791. **Implement** — Write code following existing conventions, add tests801. **Verify** — Run tests, check integration, validate behavior8182## Verification8384- [ ] All ioc enrichment automation procedures executed completely and documented85- [ ] Findings validated against multiple data sources86- [ ] False positives identified and filtered87- [ ] Results documented with evidence and timestamps88- [ ] Recommendations provided with risk-based prioritization8990## Anti-Rationalization Table9192| Rationalization | Reality |93|---|---|94| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |95| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |96| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |