Intelligence Cycle
The iterative process turning requirements into finished, disseminated intelligence.
What it is
The repeating workflow by which raw information becomes usable intelligence: planning and direction, collection, processing, analysis and production, and dissemination, followed by feedback that resets requirements. It is a loop, not a one-way pipeline.
Why it matters
Following the cycle keeps a threat-intel program driven by stakeholder needs rather than by whatever data happens to be available, and the feedback step ensures products actually inform decisions instead of piling up unread.
In practice
Restarting the intelligence cycle after a stakeholder's feedback reveals the last report answered the wrong question.
What to look for
- Clear requirements before collection starts.
- Feedback from consumers on what helped.
- Collection that runs without a question behind it.
Common mistake
Skipping feedback. Without it, the team keeps producing what nobody uses.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
MISP Open source
An open source platform for storing, correlating and sharing threat indicators.
-
OpenCTI Open source
Organizes intelligence as linked STIX objects, from actors down to indicators.
-
VirusTotal Commercial
Pivots between files, domains and IPs to find related infrastructure.
-
ATT&CK Navigator Open source
Shows a group's known techniques on the ATT&CK matrix.
Read next
- Collection Requirements: The prioritized questions that direct what intelligence to gather.
- Strategic, Operational, and Tactical Intelligence: The three altitudes of threat intelligence, from boardroom trends to raw indicators.
- Tactics, Techniques, and Procedures: How an adversary operates: their goals, methods, and step-by-step execution.