STRIDE 6150 Security Evaluation Methodologies

Jeremy Clark

Course Goal given x asked is it secure

what do you do

applicationsdatabases OS

softwfirm

hu yw

Aetw computerserver smart

edo

lotlocks safes s

physida hydro plant saa

cars

big data privacy

PeoplePrutc

cryptographicrat engineer j usability procedurespolicies argo

Evaluat on is hardno single meth duty that works for

everything

you have to understand the functionalof something before think y about

its security

security is necessary but not

sufficient

after evaluation you cannotconclude it is secure onlythat it isn't insecure withregards to a set of known

vulnerabilities

High Level Methodologies

Useful for organizing securityand brainstorming attacks

Three Examples

STRIDE 7 evaluate ya solution

Evaluation Framework 3 evaluating aset of solutions

Attack Tree eualtat y a singlethreat on a solution

STRIDENClass f cation for threatsExtension of a basic classification

CIA

Confident.nl lyintegrityAvailability

C

A

ETalat on

N

Spoofery TocutUTime of check us time

of use

Denial of Service DosO

DistributedO O Dos

THA

µ websiteO OB YID

0

website

riffne

ppospjq.int'MEg

EvaluatrunFraneworkycomparison between alternativesthere are no solutions only 1 rude offs

deliverable is a simple chart coming

up with cr.it area is harder than

it seems

there is more to security than security

holisticsecurity usability deployability

Fmmewk oeeijIeetiIs.e.tt phrased positivelydesirable properties

O

a'it.is I nexem oi e strue alternatives

Goal Neutral presentation of information

Dots achieves propertyachieves property w caveats

doesn't ache.ve property

Example Passwords

AlternativesPasswordsBiometrics

Hardware Token e.g RSA

Google 2 FA e g SMS one time password

Password Managers

Cl.ent certificate certificates

Single Sign On Facebook connect

Graph nl Passwords e g Android