Threat Assessment, Vulnerability Assessment and Risk Analysis
Wednesday, March 4th, 2009I just received a lead on a neat tutorial on risk concepts for personal surveillance protection from my friend at Mercyhurst College, Kris Wheaton. Check it out at this link. I also posted this and what follows as a discussion topic on the SARMA group on LinkedIn.
Notice the manner in which this tutorial defines the term “threat” – a threat is defined as the undesired consequence of an attacker’s actions, not the nature of the actions themselves. Accordingly, risk is then the probability of the threat, which is consistent with accepted practice. Moreover, labeling an outcome a threat implicitly assigns a “value” to the outcome, which in this simple case is simply described as “undesirable.” But isn’t that the nature of security – to lessen the probably of undesirable events, or in this case, threats?
Now this is different from the DHS definition of threat, which puts it as the intent and capability of an attacker. DHS defines threat as the cause, the document linked to above defines it as the consequence all causes considered. Which do you prefer?
But of course, one can argue that intentions and capabilities when directed against a valued asset may result in undesired outcomes. So, does it really matter? That is, if bomb attack = damage, isn’t it equivalent to call both “damage” and “bomb attack” threats? Well, perhaps not if one seeks to define the term risk in terms of threat. In general, risk is defined as a probability distribution on outcomes with associated values. If we equate threat to cause, then threat is just one aspect of the problem. If we equate threat to undesired outcome, then risk is the probability of threat. So which should we use?
To answer this, I appeal to you. What does a threat assessment product typically answer? The ones I participated in sought to define the spectrum of harms (undesired event) of interest to the decision maker, and from these harms backout those potential causes of harm within my problem set. For a terrorist threat assessment considering the nuclear power industry, my threat assessment would identify what can go wrong and how it can happen. No valuation is attached to either outcome (what can go wrong) or cause, either in terms of probability or severity. That is, a threat assessment is purely descriptive.
From this, threat is both – cause and outcome – minus the valuation. I define the pairing of cause and outcome as a “scenario,” and if that scenario is undesirable either in cause or outcome, then it is a threat.
Vulnerability assessment, too, is descriptive in my mind. A vulnerability assessment seeks to identify the weakness that enable different causes to result in different undesired outcomes. Thus, a threat assessment provides a frame with which to do vulnerability assessment. However, vulnerability assessment also provides insights to help identify previously unknown undesired outcomes and causes. I would argue that neither precedes the other, but both should happen concurrently. But of course you got to start somewhere… which would you start with?
Now where does risk analysis fit in? In my view, risk analysis synthesizes the knowledge generated from the threat assessment and vulnerability assessment efforts to prioritize concerns for decision maker attention and providing guidance on what to do about it (i.e., actionable risk analysis). In so doing, risk analysis:
- Attempts to describe the likeliness of cause from our knowledge of adversary capabilities and historical record (among other things)
- Attempts to describe the likeliness of outcome given cause from our knowledge of system weaknesses, and
- Attempts to place value on the outcome beyond just undesirable or not undesirable.
Note how I use the word “describe” and not “quantify.” I did this deliberately – quantification is useful for structuring thought, but perhaps not so much as providing a basis for decision making (particularly in security settings).
