Risk likelihood is the estimated chance that a threat will take advantage of a vulnerability. It is one of the main inputs in PCI risk analysis and is used alongside potential impact to assign priority. Likelihood should be reassessed as threats, systems, and business conditions change.
What Risk Likelihood Means in Practice
Risk likelihood is not a precise forecast, but a structured estimate of how plausible a threat event is under current conditions. It turns vague concern into an input that can be compared, ranked, and revisited as controls, exposure, and attacker behaviour change.
That distinction matters because likelihood often drives prioritisation more than raw technical severity. Two issues with the same impact can deserve very different treatment if one is far more probable given the asset profile, internet exposure, or current threat activity.
How Likelihood Is Estimated
Likelihood is usually built from evidence rather than intuition alone. Practitioners combine exposure indicators, known exploitability, threat prevalence, environmental dependencies, and any control weakness that makes a threat more feasible.
In operational settings, that estimate is rarely static. A vulnerability that is low likelihood in a segmented internal system can become much more likely after it is exposed to the internet, added to an accessible workflow, or paired with a widely observed attack pattern.
Why Likelihood Changes Over Time
Likelihood should move when the threat landscape moves. New exploitation methods, changes in attacker incentives, altered user behaviour, or a weak control that degrades over time can all make an event more probable than it was during the last review.
Business changes matter too. Asset sprawl, new integrations, mergers, cloud migrations, and control exceptions can all increase the practical chance that a threat will find and use a vulnerability, even if the vulnerability itself has not changed.
Likelihood in Risk Prioritisation
Likelihood is most useful when paired with impact. A risk register or scoring model becomes more decision-relevant when it explains why one item deserves attention now, not just that it is technically possible.
For that reason, likelihood should be expressed consistently enough to support comparison across risks, owners, and review cycles. One useful reference for building that discipline is Risk Register Template, which covers likelihood and impact scoring, treatment, residual risk, and review cadence.
Risk and Threat Considerations
Likelihood becomes dangerous when it is treated as a one-time judgment. If teams do not reassess it, they can miss the point at which a previously tolerable issue becomes a realistic attack path, especially when exposure, exploit availability, or control weakness changes.
Failure mechanism: The estimate becomes stale, or is based on assumptions that no longer match the environment, so the organisation under-ranks a risk that has become easier to exploit.
Impact: Mispriced likelihood can leave high-probability weaknesses untreated, distort remediation priority, and create avoidable exposure across operational, financial, or compliance outcomes.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST CSF 2.0, CIS Controls v8 and NIST SP 800-53 Rev 5 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | GV.RM-01 — Risk Management Strategy | Risk likelihood supports enterprise risk scoring and prioritization decisions. |
| ID.RA-01 — Asset Vulnerabilities and Threats are Identified and Recorded | Likelihood depends on known threats, vulnerabilities, and exposure conditions. | |
| Recommendation — Define a repeatable risk scoring method that updates likelihood as conditions change. Maintain current threat and vulnerability records to inform likelihood estimates. | ||
| CIS Controls v8 | CIS-7 — Continuous Vulnerability Management | Likelihood increases or decreases with exploitability and exposure over time. |
| Recommendation — Continuously track vulnerable assets so likelihood reflects current exploit conditions. | ||
| NIST SP 800-53 Rev 5 | RA-3 — Risk Assessment | Risk assessment explicitly evaluates likelihood and impact for security risks. |
| Recommendation — Assess likelihood and impact together and refresh the assessment when conditions change. | ||
| ISO/IEC 27001:2022 | A.5.8 — Information security in project management | Projects and system changes can alter exposure and therefore likelihood. |
| Recommendation — Reassess likelihood when projects change systems, trust boundaries, or exposure. | ||
Practitioner Guidance
Why practitioners should care: Likelihood is the part of risk analysis most likely to drift quietly, because it depends on current conditions rather than a fixed asset property. Revisit it whenever the threat environment, architecture, or control state changes.
Common misunderstanding: Likelihood is often mistaken for “how bad the issue looks.” In practice, it is about plausible occurrence, while impact answers how harmful the event would be if it happened.
Practitioner takeaway: Treat likelihood as a living estimate, not a permanent label, and make sure the reasoning behind it is visible enough for review and challenge.
Related resources from NHI Mgmt Group
- Why does Exposure Management help organisations reduce breach likelihood and operational risk?
- Why does weak AI governance increase the likelihood that AI risk controls fail later in the lifecycle?
- Why do organisations need both likelihood and impact when assessing security risk?
- Why do behavior, likelihood, and impact need separate risk dimensions?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org