Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
The intelligence lifecycle is the loop that turns a stakeholder question into collected data, analysis, a delivered product, and feedback that reshapes the next cycle.

What Is the Threat Intelligence Lifecycle?
The intelligence lifecycle is a loop borrowed from military and government practice, adapted for cybersecurity. Six stages—direction, collection, processing, analysis, dissemination, and feedback—describe how a question from someone who has to make a decision becomes an answer they can act on. The model is old, and the reason it survives is that teams who skip stages reliably produce intelligence nobody reads.
Everything starts with a requirement, not with a feed. Direction means agreeing with stakeholders what they need to decide and what they need to know to decide it. Those become Priority Intelligence Requirements, written specifically enough to be answerable: not “tell us about ransomware”, but “which groups have targeted UK logistics operators in the past six months, through which initial access routes, and are our edge devices among the products they exploit?”
Stakeholders differ. The board wants risk and investment context, the SOC wants detections, the vulnerability team wants exploitation status, and the fraud team wants pattern changes. One requirement list per audience prevents the common failure of producing a single report that half-serves everyone.
Collection is directed by those requirements, drawing on internal telemetry, commercial and open feeds, sector sharing through an ISAC, vendor reporting, criminal forum coverage, and the organisation’s own incident history. Internal data is persistently undervalued: your own past intrusions tell you more about who targets you than any external source.
Map sources to requirements explicitly. A source feeding no requirement is a subscription to cancel, and a requirement with no source is a collection gap to close.
Raw material is rarely usable as it arrives. Processing covers normalisation into a common schema—usually STIX—deduplication across overlapping sources, translation, extraction of indicators from narrative reports, enrichment with resolution and ownership data, and scoring for confidence. This stage is where feed quality work lives, and it is almost entirely automatable. Teams that leave it manual spend their analysts’ time on data preparation instead of analysis.
Analysis is the stage that distinguishes intelligence from data. It means judging what the processed material implies for your organisation specifically, and stating the judgement with a confidence level and the reasoning behind it. Structured techniques help here: analysis of competing hypotheses forces you to test alternatives rather than confirming the first explanation, and a key assumptions check catches the inherited beliefs nobody has revisited. Record what would change your mind, because an assessment with no disconfirming evidence attached is an opinion.
This is where most programmes fail. The product has to reach the decision maker in a form they can use within the time they have. A 40-page PDF does not serve a SOC analyst at 03:00, and a list of hashes does not serve a board considering investment. Match format to audience: machine-readable indicators pushed into tooling for detection, a one-page assessment with a recommendation for executives, a technique-level write-up with detection logic for engineers. Keep it short, lead with the judgement, and put the evidence underneath.
Ask what was used, what was wrong, and what question arrived too late. Feedback reshapes the requirements for the next cycle, and without it the programme drifts towards producing what is easy to collect rather than what is needed. Track something measurable—detections created from intelligence, decisions a product informed, the proportion of requirements answered—because a programme that cannot show its effect will eventually lose its budget.
Three habits separate working programmes from ceremonial ones. Run the cycle at more than one tempo: tactical indicators flow continuously, while strategic assessments align to planning cycles. Write requirements down and review them quarterly with the stakeholders who own them. And accept that a small programme answering four questions well is worth more than a large one producing weekly reports that nobody has asked for.
Our SOC maturation services cover the whole loop, from writing intelligence requirements with your stakeholders to turning the output into detections you can measure.
A specific question tied to a decision somebody has to make, written so it can be answered with evidence. Good examples name the actor, the sector, the technology, and the timeframe. Bad ones ask for general awareness of a topic. Requirements are what stop a programme collecting whatever is cheapest and calling the result intelligence.
Dissemination, followed closely by direction. Teams often collect and analyse competently, then deliver a format that does not fit the audience, so the work goes unread and unused. The second failure is starting with a feed purchase rather than a requirement, which produces a pipeline with no stated purpose and no way to judge whether it is working.
Yes, at a smaller scale. One analyst can run a cycle against three or four well-written requirements if processing is automated and dissemination is kept to short written products. What does not work is attempting broad coverage with limited capacity, which produces thin assessments on everything and useful answers on nothing.
Count outputs that changed something: detections built from intelligence and their true positive rate, patching decisions reprioritised because of exploitation reporting, controls funded or deferred after a strategic assessment, and the proportion of standing requirements answered each quarter. Report volume and feed counts measure activity, not value, and should not be used as the headline figure.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.