# Risk-based vulnerability management

GLOSSARY, read 10 Nov 2026

**Definition.** Risk-based vulnerability management ranks findings by the likelihood and consequence of an attack on your own assets, not by severity alone. Inputs usually include exploitation evidence, asset criticality and business context. The output is a short queue of what to fix first, with an owner and a due date attached.

In a working program the ranking is a rule set, not a number from a vendor. Someone decides which signals count, how much a crown-jewel asset adds, and when a finding is exempt. Auditors ask for that rule set, so it needs to be written down and versioned.

The term covers the method. The platform that applies it across many scanners is usually called unified vulnerability management. A scanner alone can rank, but only the findings it produced.

## A sourced example

On 2026-11-10 ArmorCode's risk-based vulnerability management FAQ listed the exploitation signals behind its Adaptive Risk Scoring, including CISA KEV and EPSS.

## Related terms

- [Unified vulnerability management](/glossary/unified-vulnerability-management/)
- [Asset criticality](/glossary/asset-criticality/)
- [Business context](/glossary/business-context/)
- [Platform risk score](/glossary/platform-risk-score/)

## Sources

- Source for the example: Risk-based vulnerability management: https://www.armorcode.com/risk-based-vulnerability-management (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/risk-based-vulnerability-management/
