Managing Intelligence Lifecycle
Overview
Cybersecurity skill for managing intelligence lifecycle. Follows industry best practices and security standards.
When to Use
Trigger phrases:
- "managing intelligence lifecycle"
- "Establishing a formal CTI program and defining its operational model"
- "Conducting quarterly intelligence requirements reviews with business stakeholder"
- "Evaluating CTI program maturity against established frameworks (FIRST CTI-SIG ma"
Use this skill when:
- Establishing a formal CTI program and defining its operational model
- Conducting quarterly intelligence requirements reviews with business stakeholders
- Evaluating CTI program maturity against established frameworks (FIRST CTI-SIG maturity model)
Do not use this skill for day-to-day IOC triage or incident-specific intelligence tasks — those use operational intelligence workflows, not lifecycle management.
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
- Executive sponsorship and defined CTI team structure (1+ dedicated analysts)
- Stakeholder map identifying intelligence consumers (SOC, IR, executive team, vulnerability management)
- Existing feed subscriptions or ISAC memberships for collection baseline
- CTI platform (MISP, ThreatConnect, OpenCTI) for lifecycle management
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 intelligence lifecycle.
- Gather Resources — Collect tools, data, and access needed for intelligence lifecycle.
- Execute Process — Carry out intelligence lifecycle 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
- Scope — Define research questions, identify data sources, set time boundaries
- Gather — Collect data from primary sources, APIs, and public records
- Synthesize — Analyze findings, identify patterns, produce actionable report
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: managing-intelligence-lifecycle3description: Use when manages the end-to-end cyber threat intelligence lifecycle from4 planning and direction through collection, processing, analysis, dissemination,5 and feedback to ensure intelligence products meet stakeholder requirements and continuously6 improve. Use when establishing or maturing a CTI program, defining intelligence7 requirements with business stakeholders, or building feedback loops between intelligence8 consumers and producers.9domain: cybersecurity10tags:11- CTI12- intelligence-lifecycle13- PIR14- NIST-SP-800-15015- threat-intelligence-program16- NIST-CSF17subdomain: threat-intelligence18version: 1.0.019author: oyi7720license: Apache-2.021nist_csf:22- ID.RA-0123- ID.RA-0524- DE.CM-0125- DE.AE-0226category: cybersecurity27metadata:28 source: https://skillmd.com/skills/oyi77/managing-intelligence-lifecycle29---3031# Managing Intelligence Lifecycle3233## Overview3435Cybersecurity skill for managing intelligence lifecycle. Follows industry best practices and security standards.3637## When to Use3839**Trigger phrases:**40- "managing intelligence lifecycle"41- "Establishing a formal CTI program and defining its operational model"42- "Conducting quarterly intelligence requirements reviews with business stakeholder"43- "Evaluating CTI program maturity against established frameworks (FIRST CTI-SIG ma"444546Use this skill when:47- Establishing a formal CTI program and defining its operational model48- Conducting quarterly intelligence requirements reviews with business stakeholders49- Evaluating CTI program maturity against established frameworks (FIRST CTI-SIG maturity model)5051**Do not use** this skill for day-to-day IOC triage or incident-specific intelligence tasks — those use operational intelligence workflows, not lifecycle management.525354## When NOT to Use5556- When you lack proper authorization for testing57- For production systems without change management58- When the task requires legal or compliance expertise beyond technical scope596061## Prerequisites6263- Executive sponsorship and defined CTI team structure (1+ dedicated analysts)64- Stakeholder map identifying intelligence consumers (SOC, IR, executive team, vulnerability management)65- Existing feed subscriptions or ISAC memberships for collection baseline66- CTI platform (MISP, ThreatConnect, OpenCTI) for lifecycle management6768## Workflow6970```python71# Example: IOC detection72import re7374IOC_PATTERNS = {75 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",76 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",77 "hash_md5": r"\b[a-f0-9]{32}\b",78 "hash_sha256": r"\b[a-f0-9]{64}\b",79}8081def extract_iocs(text: str) -> dict:82 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}83```84851. **Define Objectives** — Clarify the goals and scope for intelligence lifecycle.862. **Gather Resources** — Collect tools, data, and access needed for intelligence lifecycle.873. **Execute Process** — Carry out intelligence lifecycle operations methodically.884. **Verify Quality** — Check results against acceptance criteria.895. **Document Outcomes** — Record findings, decisions, and next steps.9091## Tools9293- **Analysis Platform** — Data processing and visualization94- **Collaboration Tools** — Team coordination and knowledge sharing959697## Process98991. **Scope** — Define research questions, identify data sources, set time boundaries1001. **Gather** — Collect data from primary sources, APIs, and public records1011. **Synthesize** — Analyze findings, identify patterns, produce actionable report102103## Verification104105- [ ] All intelligence lifecycle procedures executed completely and documented106- [ ] Findings validated against multiple data sources107- [ ] False positives identified and filtered108- [ ] Results documented with evidence and timestamps109- [ ] Recommendations provided with risk-based prioritization110111## Anti-Rationalization Table112113| Rationalization | Reality |114|---|---|115| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |116| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |117| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |