If You Want to Build Good Intelligence Requirements, You Do Not Start with Intelligence Requirements
summary
Argues that useful intelligence starts by mapping stakeholder intended actions and their measures of success, not by making a generic list of requirements. Recommends using the intel cycle and lightweight workflows (mentions ReqFast as a requirements-to-workflow SaaS) to tie collections to decisions, with the CISO/DDoS example showing what to collect and when to recommend buy/replace/keep. Notes vendor adoption is growing but failures come from overcomplication and lack of built-in feedback loops.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 0:51State of Intelligence Requirements
- 1:25Adoption Acceptance
- 2:21Intelligence Requirements
- 3:30Scenario
- 3:51Conversation Top
- 6:09Intel 471
- 7:49Youre not special
- 8:38We are professionals
- 8:56Everyone does Intel
- 9:49Key takeaways
- 10:18Your role as an intelligence professional
- 13:00The Intelligence Cycle
- 13:28Other Intelligence Cycles
- 14:16How to Tie the Cycle to Your Everyday
- 14:44Flowchart
- 15:34Actions
- 15:45Priorities
- 16:36Tasking
- 17:06What does the CEO want to know
- 17:36What else do we need
- 18:28How do we help
- 21:53Measures of success
- 23:36You are special
- 24:45Conclusion
- 26:00QA
- 26:55Seed the Conversation
- 28:48Actionable Intelligence
related talks
37mThreats versus Capabilities Building Better Detect and Respond Capabilities
18mIntelligence Driven Security
23mBuilding a Higher Order of Security Intelligence
21mGet Real Operationalizing an Intelligence Driven Security Program
51mExpect More: Realizing the True Impact of Your Intelligence Program
25mYour Software Supply Chain is Only as Secure as its Weakest Link
18mDesigning for Security Outcomes
26mEvaluating Threat Intelligence Through Velocity