The problem I have encountered currently and in
the past with the NIST definitions is that they blend terms together when you
read through their documents, which causes a bit of confusion, even among the
security professional, let along the end users or system/data owners. So, we
have had to break them down a bit so that others can understand and apply them.
I guess we’re trying to make it little simpler
or maybe clearer than NIST. So, I'm combining my thoughts in this tread
for both Risk and Threat, because the direction I was going with Threat is
based on how I define Risk.
Therefore, we decided to define risk as
basically: Risk = likelihood of a threat exploiting a vulnerability and its
impact.
Basically, what that equates to is you have risk
only when you have both the likelihood of an exploitation (“threat-source” as
defined by NIST) and a vulnerability. Also,
it allows you to address the likelihood a threat uses/triggers a exploitation
and/or the vulnerability and its impact as part of the risk mitigation process.
One of the underlying principals (or side
affects) in this approach is that threats are not truly addressable (i.e., human,
natural, and environmental threats always exist).
Basicly, after all this rambling, my point is
that we need to define risk with consideration on how it relates to Threat,
Vulnerability, and Impact, and then how it will be applied to the risk
management process.
mcurphey:Likelihood implies (to me) probability
On a side not, likelihood implies both quantitative and qualitative to me.