Terminology Index
Glossary
2953 terms
Requirements Evolution
Updating intelligence requirements over time as the threat landscape, business, and stakeholder needs change, so the program continues to answer the right questions rather than the questions it started with.
Intelligence requirements are not set once and frozen. As threats shift, the business changes, and consumers' needs mature, requirements must evolve, retire stale ones, add new ones, re-prioritize. Without evolution, a program drifts: collecting on outdated questions while real needs go unmet. Treating requirements as living artifacts, reviewed regularly, is a hallmark of mature threat-intelligence operations and ties the program to ongoing relevance rather than initial setup.
Introduced in: Threat Intelligence for SOC Analysts
Examples
- Retiring a requirement that no longer reflects the threat landscape.
- Adding new requirements after a business expansion changes risk.
- Reviewing requirements regularly so the program stays relevant.
Related
