Evaluating Threat Intelligence Platforms
Overview
Cybersecurity skill for evaluating threat intelligence platforms. Follows industry best practices and security standards.
When to Use
Trigger phrases:
- "evaluating threat intelligence platforms"
- "Evaluates and selects Threat Intelligence Platform (TIP) products based on organ"
Use this skill when:
- Conducting a formal RFP or vendor evaluation for a TIP solution
- Assessing whether the current TIP (e.g., MISP) needs to be replaced or augmented as the CTI program scales
- Establishing evaluation criteria aligned to organizational maturity and budget
Do not use this skill for evaluating feed quality independently of the TIP — feed evaluation is a separate workflow focused on data quality rather than platform capabilities.
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
- Documented CTI program requirements: team size, feed sources, integration targets, use cases
- Budget range and procurement timeline
- Technical staff who will administer the platform (Python/API experience for open-source TIPs)
- List of current and planned integrations (SIEM, SOAR, EDR, firewalls)
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()}
- Define Objectives — Clarify the goals and scope for threat intelligence platforms.
- Gather Resources — Collect tools, data, and access needed for threat intelligence platforms.
- Execute Process — Carry out threat intelligence platforms operations methodically.
- Verify Quality — Check results against acceptance criteria.
- Document Outcomes — Record findings, decisions, and next steps.
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: evaluating-threat-intelligence-platforms3description: Use when evaluates and selects Threat Intelligence Platform (TIP) products based on organizational requirements including feed integration capability, STIX/TAXII support, workflow automation, analyst interface, and total cost of ownership. Use when conducting a TIP procurement, migrating between TIP solutions, or assessing whether the current TIP meets program maturity requirements. Activates for requests involving ThreatConnect, MISP, OpenCTI, Anomali, EclecticIQ, or TIP procurement decisions.4license: Apache-2.05---67# Evaluating Threat Intelligence Platforms89## Overview1011Cybersecurity skill for evaluating threat intelligence platforms. Follows industry best practices and security standards.1213## When to Use14**Trigger phrases:**15- "evaluating threat intelligence platforms"16- "Evaluates and selects Threat Intelligence Platform (TIP) products based on organ"171819Use this skill when:20- Conducting a formal RFP or vendor evaluation for a TIP solution21- Assessing whether the current TIP (e.g., MISP) needs to be replaced or augmented as the CTI program scales22- Establishing evaluation criteria aligned to organizational maturity and budget2324**Do not use** this skill for evaluating feed quality independently of the TIP — feed evaluation is a separate workflow focused on data quality rather than platform capabilities.252627## When NOT to Use2829- When you lack proper authorization for testing30- For production systems without change management31- When the task requires legal or compliance expertise beyond technical scope323334## Prerequisites3536- Documented CTI program requirements: team size, feed sources, integration targets, use cases37- Budget range and procurement timeline38- Technical staff who will administer the platform (Python/API experience for open-source TIPs)39- List of current and planned integrations (SIEM, SOAR, EDR, firewalls)4041## Workflow4243```python44# Example: IOC detection45import re4647IOC_PATTERNS = {48 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",49 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",50 "hash_md5": r"\b[a-f0-9]{32}\b",51 "hash_sha256": r"\b[a-f0-9]{64}\b",52}5354def extract_iocs(text: str) -> dict:55 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}56```57581. **Define Objectives** — Clarify the goals and scope for threat intelligence platforms.592. **Gather Resources** — Collect tools, data, and access needed for threat intelligence platforms.603. **Execute Process** — Carry out threat intelligence platforms operations methodically.614. **Verify Quality** — Check results against acceptance criteria.625. **Document Outcomes** — Record findings, decisions, and next steps.6364## Tools6566- **Analysis Platform** — Data processing and visualization67- **Collaboration Tools** — Team coordination and knowledge sharing686970## Process71721. **Design** — Define interface, identify patterns, plan implementation731. **Implement** — Write code following existing conventions, add tests741. **Verify** — Run tests, check integration, validate behavior7576## Verification7778- [ ] All threat intelligence platforms procedures executed completely and documented79- [ ] Findings validated against multiple data sources80- [ ] False positives identified and filtered81- [ ] Results documented with evidence and timestamps82- [ ] Recommendations provided with risk-based prioritization8384## Anti-Rationalization Table8586| Rationalization | Reality |87|---|---|88| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |89| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |90| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |