Risk Management & Risk Driven Test Planning

Question 1

Risk(incident) =

Answer 1

p(occurrence) * impact

Question 2

p(occurrence) vs. p(vulnerability) ratio

Answer 2

We assume they are proportional

Question 3

Naïve Security Risk Assessment

Answer 3

Write down your worst fears for the system
Try to avoid those things

Question 4

Naïve Security Risk Assessment Cons

Answer 4

Requires a big “bag of tricks”
Easily overwhelming for security

Question 5

Protection Poker

Answer 5

Uses story points
Assets have value
Security risk = Ease of attack (1 - 100) * asset value

Question 6

Risk-Driven Test Planning Goals

Answer 6

Mitigate negative impact on the customer
Create the mitigation strategies early
Allow a “disruption-free” usage of the product

Question 7

Top-Down Test Planning

Answer 7

Start with the broad analysis of the domain
Goals → Risks → Indicators → Tests

Benefit: tied to specific goals
Drawback: incomplete within the categories

Question 8

Bottom-Up Security Test Planning

Answer 8

Step 1: Write down a lot of tests
Step 2: Group those tests into various categories
Step 3: Revise the categories as a group
Step 4: Add more tests to each category

Benefit: gives you freedom to write your best tests immediately
Drawbacks: easy to miss stuff