________________________________________________________________________
Dear workshop attendees:
I hope that you find the following recommendations to be helpful. Wish I could be there!
Russ
________________________________________________________________________
Recommendations:
- In my judgement, the five "Cyber Security Functions" described in the July 1 draft are inadequate to support agile and continuously innovative cyber security. As detailed in this analysis, the five functional categories have serious deficiencies:
- "Know" is too broad and too vague
- "Respond" and "Recover" are too narrow and could be combined
- "Detect" does not adequately cover of Threat Intelligence
- Missing:
- Design & Development
- Resilience
- Execution & Operations
- External Engagement
- Agility & Learning
- Total Cost of Risk
- Responsibility & Accountability
- Rather than using functional categories which are nothing more than "buckets of content", it would be better to organize the framework around performance dimensions. This will help make the framework more coherent and better justified.
- I recommend organizing the framework according to Ten Dimensions of Cyber Security Performance, (slides), which are explained individually the linked posts:
- Optimize Exposure
- Effective Threat Intelligence
- Effective Design & Development
- Quality of Protection & Controls
- Effective/Efficient Execution & Operations
- Effective Response, Recovery, & Resilience
- Effective External Engagement
- Effective Learning & Agility
- Optimize Total Cost of Risk
- Responsibility & Accountability
- I recommend that the framework should explicitly support Double Loop Learning, which is described in these two posts:
- I recommend that pilot projects be started right away to design and test inference methods for estimating cyber security performance, as sketched in this post.
No comments:
Post a Comment