Analyzing Threat Intelligence Feeds

Analyzing Threat Intelligence Feeds

Overview

Cybersecurity skill for analyzing threat intelligence feeds. Follows industry best practices and security standards.

When to Use

Trigger phrases:

• "analyzing threat intelligence feeds"
• "Ingesting new commercial or OSINT threat feeds and assessing their signal-to-noi"
• "Normalizing heterogeneous IOC formats (STIX 2"
• "Evaluating feed freshness, fidelity, and relevance to the organization's threat"

Use this skill when:

• Ingesting new commercial or OSINT threat feeds and assessing their signal-to-noise ratio
• Normalizing heterogeneous IOC formats (STIX 2.1, OpenIOC, YARA, Sigma) into a unified schema
• Evaluating feed freshness, fidelity, and relevance to the organization's threat profile
• Building automated enrichment pipelines that correlate IOCs against SIEM events

Do not use this skill for raw packet capture analysis or live incident triage without first establishing a CTI baseline.

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

• Access to a Threat Intelligence Platform (TIP) such as ThreatConnect, MISP, or OpenCTI
• API keys for at least one commercial feed (Recorded Future, Mandiant Advantage, or VirusTotal Enterprise)
• TAXII 2.1 client library (taxii2-client Python package or equivalent)
• Role with read/write permissions to the TIP's indicator database

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()}

1. Scope the Analysis — Define what threat intelligence feeds artifacts or data sources to examine and the investigation timeline.
2. Preserve Evidence — Create forensic copies of relevant data. Maintain chain of custody documentation.
3. Extract Key Indicators — Parse and extract relevant threat intelligence feeds data points from collected artifacts.
4. Correlate Findings — Cross-reference extracted data with other sources (threat intel, logs, timelines).
5. Build Timeline — Construct a chronological sequence of events related to threat intelligence feeds.
6. Document Analysis — Write findings report with evidence, conclusions, and recommendations.

Tools

• Forensic Toolkit — Evidence collection and analysis
• Timeline Tools — Chronological event reconstruction
• Log Analysis Platform — Centralized log parsing and search

Process

1. Scope — Define research questions, identify data sources, set time boundaries
2. Gather — Collect data from primary sources, APIs, and public records
3. Synthesize — Analyze findings, identify patterns, produce actionable report

Verification

• All threat intelligence feeds procedures executed completely and documented
• Findings validated against multiple data sources
• False positives identified and filtered
• Results documented with evidence and timestamps
• Recommendations provided with risk-based prioritization

Anti-Rationalization Table