startthat.work home

AO-18 Threat modelling (STRIDE: spoofing, tampering, repudiation, information disclosure, denial of service, elevation of privilege)

Identifies security threats using six categories mapped to security properties, producing a list of threats by category.

Assess actors, options and risksEvidence: DocumentedPrimary technique, runs in step 5.3Strongest statement: describe

What it does

Identifies security threats by six categories mapped to security properties. Artefact: a list of threats by category.

When to use it

Use when a user asks what could go wrong with the security of a system and wants a structured checklist to find threats.

When it does not fit

Not established in the notes.

Result format

The result is a list of security threats grouped under the six STRIDE categories, with each threat tied to the security property it breaches. Every category appears in the list, including any with no threat found.

Requirements on the material

PropertyRequirement typeRequirement
Content typeAlways appliesrequires=text
Unit of analysisAlways appliesrequires=topic
Appraises source credibilityApplies in some casesno

Not restricted on: Structure, Variable types, Time structure, How the sample was chosen, Level of detail available, Number of sources, Whether sources can be joined, Amount of material, Known data problems, Producer interest, Source dependence, Origin, Document genre, Language, Personal information, Security classification, Licence.

Minimum materialA description of the system components and data flows. Data flow diagrams are the usual input, but this is unconfirmed.
Additional sources needednone
Not for (rules)none
Not for (text)The notes establish no fit test. Treat as the wrong choice when the system has no described components or data flows to attach threats to.

Choosing and ordering

Kind of techniquePrimary technique, runs in step 5.3
Phase taganalyse
Other phase tagsnone
Kind of findingrisk
Question answeredwhat
Strongest statement it supportsdescribe
Needs as input
Makes as output
Must exist firstNone
Loop targetreturn to gather

Library checks by stakes

Each stakes level includes the checks of the level below it. Checks that need a person apply at high stakes only, so the process leaves them out at lower stakes (decision 38). Repeatability: judgement dependent.

StakesCheckPerson involvedCounts as a different method
exploratoryspot checkoptionalno
decision-informingspot checkoptionalno
decision-informinghuman review sampleneeded; left out below high stakesno
decision-informingsource-span citationnoneno
high-stakesspot checkoptionalno
high-stakeshuman review sampleneededno
high-stakessource-span citationnoneno
high-stakesexpert reviewneededno
high-stakesindependent reviewneededno

Failure modes and limits

Model suitabilitymodel alone
Typical model failureLists generic threats for each of the six categories without tying them to a component or data flow of the system described.
Error sourcesinput data; language model; coder or rater judgement
Certainty limitsCertainty drops because the source gives no inputs, outputs or limits, and when the system description is incomplete (indirectness).

Evidence and tag basis

Documented. Developed at Microsoft by Garg and Kohnfelder; the page gives no inputs, outputs or limits. (Wikipedia, STRIDE model)

Tag basis: input profile inference; selection inference; sequencing inference; robustness inference. All tag values are inference unless a source is named.