1. Risk Assessment
What is good about the Microsoft approach to threat modeling?
What is bad about it?
OCTAVE…
 Advantage: ___________
 Disadvantage: ___________

2. OCTAVE– a brief history
1999
OCTAVE developed by Software Engineering Institute
2003
OCTAVE-S a streamlined version
2007
OCTAVE Allegro

3. OCTAVE Phases Phase 1 Organizational View  assets  threats
 current practices
 organizational vulnerabilities
Phase 3
Strategy & Plan
 security requirements
 risks
Phase 2
Technological View
 protection strategy
 mitigation plan
 key components
 technical vulnerabilities

4. OCTAVE Allegro Roadmap
(see reference on previous slide)

5. Step 1: Establish Risk Mgmt Criteria
This is concerned with things like …
“organizational drivers”,
“mission”,
“business objectives”
The purpose is to think about later threat ranking

6. Step 2: Develop an Info Asset Profile
For a software project we need to
 __________________
 ___________________
Step 3: Identify Asset Containers
Where are the assets
 ..stored?
 ..transported?
 ..processed?

7. Step 4: Identify Areas of Concern
Brainstorm possible threats
Step 5: Identify Threat Scenarios
Build threat trees
A scenario is ___________________________

9. Step 8: Select Mitigation Approach
Step 6: Identify Risks
Step 7: Analyze Risks
Use formula of probability * impact
Step 8: Select Mitigation Approach
An interesting omission from the Microsoft approach

10. Ranking Example For a single threat/risk:
There are worksheets to help discover ranges for ranking