Managing Intelligence Lifecycle
When to Use
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.
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
Step 1: Planning and Direction
Define Priority Intelligence Requirements (PIRs) with stakeholders:
- Interview SOC leads, IR team, CISO, risk management, and product security
- Document PIRs in structured format: "What is the current capability and intent of [threat actor] to attack [critical asset] using [technique]?"
- Prioritize 5–10 PIRs for the quarter, reviewed monthly
Example PIR: "Is ransomware group Cl0p currently targeting organizations in our sector using MoveIT or GoAnywhere vulnerabilities?"
Step 2: Collection Planning
Map PIRs to required collection sources:
- Technical sources: commercial feeds, TAXII, ISAC data, honeypot telemetry, darkweb monitoring
- Human sources: vendor threat briefings, industry working groups, law enforcement partnerships
- Internal sources: SIEM logs, EDR telemetry, phishing submission mailbox
Document collection gaps and associated costs to fill them.
Step 3: Processing and Normalization
Implement automated processing pipeline:
- Ingest → normalize to STIX 2.1 → deduplicate → enrich → score confidence
- Reject unverifiable or duplicate indicators before analysis
- Tag all processed data with source, collection date, and expiration
Step 4: Analysis and Production
Produce intelligence at three levels:
- Strategic: Quarterly threat landscape report for executives; sector trends, geopolitical context
- Operational: Weekly campaign reports for security leadership; active campaigns, adversary activity
- Tactical: Daily IOC bulletins for SOC; actionable indicators with block/monitor recommendations
Apply structured analytic techniques: Analysis of Competing Hypotheses (ACH), Key Assumptions Check, Devil's Advocacy.
Step 5: Dissemination
Match product format to audience:
- Executives: 1-page PDF with risk ratings, business impact, recommended decisions
- SOC analysts: SIEM-ready IOC list, Sigma rules, MISP events
- Vulnerability management: CVE lists with EPSS scores and exploitation likelihood
- IT/Security leadership: Full intelligence report with technical appendix
Apply TLP classifications and distribution lists per product type.
Step 6: Feedback and Evaluation
Collect feedback within 5 business days of dissemination:
- Did the product address the PIR?
- Was actionability sufficient?
- What data was missing?
Track metrics quarterly: PIR coverage rate, IOC true positive rate, time-to-disseminate, stakeholder satisfaction score (NPS or structured survey).
Key Concepts
| Term |
Definition |
| PIR |
Priority Intelligence Requirement — specific, actionable question driving intelligence collection and analysis |
| Intelligence Lifecycle |
Six-phase iterative process: Planning → Collection → Processing → Analysis → Dissemination → Feedback |
| Strategic Intelligence |
Long-term threat trend analysis for executive decision-making; time horizon 6–24 months |
| Operational Intelligence |
Campaign-level analysis for security program decisions; time horizon 1–6 months |
| Tactical Intelligence |
Specific IOCs and TTPs for immediate detection and blocking; time horizon hours to days |
| FIRST CTI-SIG |
Forum of Incident Response and Security Teams — CTI Special Interest Group maturity model |
Tools & Systems
- ThreatConnect: TIP with built-in intelligence lifecycle workflows, PIR tracking, and stakeholder reporting dashboards
- MISP: Open-source TIP supporting intelligence lifecycle from collection through sharing
- OpenCTI: Graph-based CTI platform with workflow management for intelligence products
- Recorded Future: Commercial platform with structured intelligence reports aligned to the intelligence lifecycle
Common Pitfalls
- Collection without direction: Ingesting every available feed without PIRs produces data overload and no actionable intelligence.
- Missing feedback loops: Without structured feedback, CTI teams produce reports that don't meet stakeholder needs and lose organizational relevance.
- Tactical-only focus: Overemphasis on IOC sharing neglects strategic intelligence that informs security investment and risk decisions.
- No metrics program: Cannot demonstrate CTI program value without tracking detection contributions, true positive rates, and stakeholder satisfaction.
- Underfunded collection: PIRs cannot be answered without appropriate collection sources; document and escalate gaps rather than producing low-confidence estimates.
1---
2name: managing-intelligence-lifecycle
3description: 'Manages the end-to-end cyber threat intelligence lifecycle from planning
4 and direction through collection, processing, analysis, dissemination, and feedback
5 to ensure intelligence products meet stakeholder requirements and continuously improve.
6 Use when establishing or maturing a CTI program, defining intelligence requirements
7 with business stakeholders, or building feedback loops between intelligence consumers
8 and producers. Activates for requests involving CTI program maturity, intelligence
9 requirements, PIRs, or intelligence lifecycle management.
10
11 '
12domain: cybersecurity
13subdomain: threat-intelligence
14tags:
15- CTI
16- intelligence-lifecycle
17- PIR
18- NIST-SP-800-150
19- threat-intelligence-program
20- NIST-CSF
21version: 1.0.0
22author: team-cybersecurity
23license: Apache-2.0
24nist_csf:
25- ID.RA-01
26- ID.RA-05
27- DE.CM-01
28- DE.AE-02
29mitre_attack:
30- T1591
31- T1592
32- T1593
33- T1589
34source: https://github.com/mukul975/Anthropic-Cybersecurity-Skills
35source_commit: 04450304b12645cb2b974ab96d28c0664758a88d
36metadata:
37 source: https://skillmd.com/skills/yanacuti1121/managing-intelligence-lifecycle
38---
39
40# Managing Intelligence Lifecycle
41
42## When to Use
43
44Use this skill when:
45- Establishing a formal CTI program and defining its operational model
46- Conducting quarterly intelligence requirements reviews with business stakeholders
47- Evaluating CTI program maturity against established frameworks (FIRST CTI-SIG maturity model)
48
49**Do not use** this skill for day-to-day IOC triage or incident-specific intelligence tasks — those use operational intelligence workflows, not lifecycle management.
50
51## Prerequisites
52
53- Executive sponsorship and defined CTI team structure (1+ dedicated analysts)
54- Stakeholder map identifying intelligence consumers (SOC, IR, executive team, vulnerability management)
55- Existing feed subscriptions or ISAC memberships for collection baseline
56- CTI platform (MISP, ThreatConnect, OpenCTI) for lifecycle management
57
58## Workflow
59
60### Step 1: Planning and Direction
61
62Define Priority Intelligence Requirements (PIRs) with stakeholders:
63- Interview SOC leads, IR team, CISO, risk management, and product security
64- Document PIRs in structured format: "What is the current capability and intent of [threat actor] to attack [critical asset] using [technique]?"
65- Prioritize 5–10 PIRs for the quarter, reviewed monthly
66
67Example PIR: "Is ransomware group Cl0p currently targeting organizations in our sector using MoveIT or GoAnywhere vulnerabilities?"
68
69### Step 2: Collection Planning
70
71Map PIRs to required collection sources:
72- Technical sources: commercial feeds, TAXII, ISAC data, honeypot telemetry, darkweb monitoring
73- Human sources: vendor threat briefings, industry working groups, law enforcement partnerships
74- Internal sources: SIEM logs, EDR telemetry, phishing submission mailbox
75
76Document collection gaps and associated costs to fill them.
77
78### Step 3: Processing and Normalization
79
80Implement automated processing pipeline:
81- Ingest → normalize to STIX 2.1 → deduplicate → enrich → score confidence
82- Reject unverifiable or duplicate indicators before analysis
83- Tag all processed data with source, collection date, and expiration
84
85### Step 4: Analysis and Production
86
87Produce intelligence at three levels:
88- **Strategic**: Quarterly threat landscape report for executives; sector trends, geopolitical context
89- **Operational**: Weekly campaign reports for security leadership; active campaigns, adversary activity
90- **Tactical**: Daily IOC bulletins for SOC; actionable indicators with block/monitor recommendations
91
92Apply structured analytic techniques: Analysis of Competing Hypotheses (ACH), Key Assumptions Check, Devil's Advocacy.
93
94### Step 5: Dissemination
95
96Match product format to audience:
97- Executives: 1-page PDF with risk ratings, business impact, recommended decisions
98- SOC analysts: SIEM-ready IOC list, Sigma rules, MISP events
99- Vulnerability management: CVE lists with EPSS scores and exploitation likelihood
100- IT/Security leadership: Full intelligence report with technical appendix
101
102Apply TLP classifications and distribution lists per product type.
103
104### Step 6: Feedback and Evaluation
105
106Collect feedback within 5 business days of dissemination:
107- Did the product address the PIR?
108- Was actionability sufficient?
109- What data was missing?
110
111Track metrics quarterly: PIR coverage rate, IOC true positive rate, time-to-disseminate, stakeholder satisfaction score (NPS or structured survey).
112
113## Key Concepts
114
115| Term | Definition |
116|------|-----------|
117| **PIR** | Priority Intelligence Requirement — specific, actionable question driving intelligence collection and analysis |
118| **Intelligence Lifecycle** | Six-phase iterative process: Planning → Collection → Processing → Analysis → Dissemination → Feedback |
119| **Strategic Intelligence** | Long-term threat trend analysis for executive decision-making; time horizon 6–24 months |
120| **Operational Intelligence** | Campaign-level analysis for security program decisions; time horizon 1–6 months |
121| **Tactical Intelligence** | Specific IOCs and TTPs for immediate detection and blocking; time horizon hours to days |
122| **FIRST CTI-SIG** | Forum of Incident Response and Security Teams — CTI Special Interest Group maturity model |
123
124## Tools & Systems
125
126- **ThreatConnect**: TIP with built-in intelligence lifecycle workflows, PIR tracking, and stakeholder reporting dashboards
127- **MISP**: Open-source TIP supporting intelligence lifecycle from collection through sharing
128- **OpenCTI**: Graph-based CTI platform with workflow management for intelligence products
129- **Recorded Future**: Commercial platform with structured intelligence reports aligned to the intelligence lifecycle
130
131## Common Pitfalls
132
133- **Collection without direction**: Ingesting every available feed without PIRs produces data overload and no actionable intelligence.
134- **Missing feedback loops**: Without structured feedback, CTI teams produce reports that don't meet stakeholder needs and lose organizational relevance.
135- **Tactical-only focus**: Overemphasis on IOC sharing neglects strategic intelligence that informs security investment and risk decisions.
136- **No metrics program**: Cannot demonstrate CTI program value without tracking detection contributions, true positive rates, and stakeholder satisfaction.
137- **Underfunded collection**: PIRs cannot be answered without appropriate collection sources; document and escalate gaps rather than producing low-confidence estimates.