Ask most CTI teams what their intelligence requirements are and you will get blank stares. They can tell you what feeds they subscribe to, what platforms they use, and what indicators they track. What they cannot tell you is what questions they are actually trying to answer.

This gap, between data collection and decision support, is the defining problem of enterprise CTI. Intelligence requirements management is the discipline that closes it.

What Are Intelligence Requirements?

Intelligence requirements are formal statements of what decision-makers need to know in order to make better decisions. They are not threat feeds. They are not alerts. They are structured questions that direct every collection, analysis, and production activity in the program.

Enlighten uses the Series method to organize intelligence requirements. Rather than a rigid two-tier hierarchy, requirements are grouped into four series based on their decision support function, and assigned priority levels within each series.

The Four Requirement Series

Threat Warning

Threat Warning requirements focus on near-term, actionable intelligence about specific threats. They are the most time-sensitive series and drive the most direct operational response. Examples include active campaigns targeting your sector, imminent threat actor activity, and emerging vulnerabilities with high exploitation likelihood.

Decision Support

Decision Support requirements feed specific leadership decisions: M&A risk analysis, product launch security posture, regional expansion threat landscape, and supply chain risk evaluation. These requirements are tied to concrete business decisions and have defined timelines aligned to those decisions.

Analysis

Analysis requirements establish and maintain foundational knowledge about the threat environment. They provide the contextual layer that makes Threat Warning and Decision Support intelligence interpretable. Understanding who the relevant threat actors are, what their capabilities look like, and how they operate is baseline work that never stops.

Environment

Environment requirements track the broader conditions in which threats operate: geopolitical developments, regulatory changes, infrastructure shifts, and sector-level trends. These requirements are longer-horizon and support strategic planning rather than immediate operational response.

Why the Series Method Works

The Series method reflects how intelligence consumers actually use intelligence. Different stakeholders need different types of intelligence on different timescales. A SOC analyst and a CFO evaluating an acquisition have entirely different decision contexts. Organizing requirements by series allows the program to serve both without conflating their needs.

  • Collection gaps become visible: if no source is answering an active requirement, you know where to invest
  • Intelligence products are immediately actionable because they trace to specific decisions
  • ROI is measurable: what percentage of active requirements were answered this quarter?
  • Stakeholder confidence increases because intelligence is relevant, not just voluminous

Building an Intelligence Requirements Program

The requirements process is continuous, not a one-time exercise. It starts with stakeholder elicitation, structured interviews with decision-makers across security, executive, legal, and business units. Requirements are then documented, assigned to the appropriate series and level, prioritized, assigned to collection teams, and reviewed on a regular cycle.

The eIMF (Enlighten Intelligence Management Framework) provides a structured approach to this process. Platforms like Theia make it operationally practical: requirements can be created, assigned, tracked, and closed in the same workflow where collection and analysis happen.

Key Insight

The most mature CTI programs treat intelligence requirements as living documents that evolve with the business. Requirements reviews should happen quarterly at minimum, and after any major business event like a merger, product launch, or geopolitical shift.