OWASP Risk Rating, Worked Through

Penetration testers and application-security teams need to say how serious a finding is, and “High” from one tester should mean what it means from another. OWASP’s answer is a checklist of sixteen factors. Here is every factor, how they combine, and where the method’s own authors tell you to be careful.

16factors, each picked from a short list of options
0–9rating behind every option
3bands: Low under 3, Medium 3 to under 6, High 6–9
5severities: Note, Low, Medium, High, Critical

The OWASP Risk Rating Methodology is the Open Worldwide Application Security Project’s method for rating the risk of a specific vulnerability — typically a finding from a penetration test or code review. It starts from the standard model, Risk = Likelihood × Impact, but never multiplies anything. Instead each side is estimated from eight factors, the factors are averaged, each average is banded Low, Medium or High, and a 3×3 table turns the two bands into a severity. It is a semi-quantitative method with a qualitative finish.

1 · Six Steps

  1. Identify the risk — the threat agent, the attack, the vulnerability and the business impact. OWASP: when there are several possible attackers, “err on the side of caution by using the worst-case option.”
  2. Estimate likelihood from eight factors: four about the threat agent, four about the vulnerability.
  3. Estimate impact from four technical factors and four business factors.
  4. Determine severity — average, band, and read the severity matrix.
  5. Decide what to fix — most severe first, and not every risk is worth fixing: if the fix costs more than the loss, accepting it can be the right call.
  6. Customise the model — add factors, change options, or weight factors that matter more in your business.

2 · Likelihood: Who Attacks, and How Easily

Likelihood is the average of eight ratings. The threat agent factors describe the most likely attacker group; the vulnerability factors describe the flaw itself.

GroupFactorOptions and ratings
Threat agentSkill levelNo technical skills 1; Some technical skills 3; Advanced computer user 5; Network and programming skills 6; Security penetration skills 9
Threat agentMotiveLow or no reward 1; Possible reward 4; High reward 9
Threat agentOpportunityFull access or expensive resources required 0; Special access or resources required 4; Some access or resources required 7; No access or resources required 9
Threat agentSizeDevelopers 2; System administrators 2; Intranet users 4; Partners 5; Authenticated users 6; Anonymous Internet users 9
VulnerabilityEase of discoveryPractically impossible 1; Difficult 3; Easy 7; Automated tools available 9
VulnerabilityEase of exploitTheoretical 1; Difficult 3; Easy 5; Automated tools available 9
VulnerabilityAwarenessUnknown 1; Hidden 4; Obvious 6; Public knowledge 9
VulnerabilityIntrusion detectionActive detection in application 1; Logged and reviewed 3; Logged without review 8; Not logged 9

OWASP says likelihood need not be over-precise: Low, Medium or High is usually enough.

3 · Impact: Technical and Business

Impact is estimated twice. Technical impact covers the classic security properties plus accountability. Business impact covers what the business actually loses — and OWASP is explicit that it is “ultimately” the more important of the two: if good business information exists, use it instead of the technical estimate.

GroupFactorOptions and ratings
Technical impactLoss of confidentialityMinimal non-sensitive data disclosed 2; Minimal critical data disclosed 6; Extensive non-sensitive data disclosed 6; Extensive critical data disclosed 7; All data disclosed 9
Technical impactLoss of integrityMinimal slightly corrupt data 1; Minimal seriously corrupt data 3; Extensive slightly corrupt data 5; Extensive seriously corrupt data 7; All data totally corrupt 9
Technical impactLoss of availabilityMinimal secondary services interrupted 1; Minimal primary services interrupted 5; Extensive secondary services interrupted 5; Extensive primary services interrupted 7; All services completely lost 9
Technical impactLoss of accountabilityFully traceable 1; Possibly traceable 7; Completely anonymous 9
Business impactFinancial damageLess than the cost to fix the vulnerability 1; Minor effect on annual profit 3; Significant effect on annual profit 7; Bankruptcy 9
Business impactReputation damageMinimal damage 1; Loss of major accounts 4; Loss of goodwill 5; Brand damage 9
Business impactNon-complianceMinor violation 2; Clear violation 5; High profile violation 7
Business impactPrivacy violationOne individual 3; Hundreds of people 5; Thousands of people 7; Millions of people 9

4 · From Averages to Severity

Each side is the plain average of its factors, then banded:

0 to under 3 = LOW  ·  3 to under 6 = MEDIUM  ·  6 to 9 = HIGH

The two bands meet in OWASP’s severity matrix:

Impact ↓  /  Likelihood →LOWMEDIUMHIGH
HIGHMediumHighCritical
MEDIUMLowMediumHigh
LOWNoteLowMedium

Unlike NIST’s matrix, OWASP’s is symmetric: High likelihood with Low impact and Low likelihood with High impact both come out Medium.

OWASP’s own example: threat agent ratings 5, 2, 7, 1 and vulnerability ratings 3, 6, 9, 2 average to 4.375 — Medium likelihood. Technical impact 9, 7, 5, 8 averages 7.25 — High, but business impact 1, 2, 1, 5 averages only 2.25 — Low. Technically that is a High; because the business would barely notice, OWASP concludes the overall severity is best described as Low.

5 · Worked Example: a Password-Only VPN

The series’ standard risk, framed as a finding: the remote-access VPN accepts password-only logins, and ransomware crews buy stolen VPN credentials.

SideRatingsAverageBand
Threat agentskill 6, motive 9, opportunity 7, size 97.75HIGH
likelihood 7.75
Vulnerabilitydiscovery 9, exploit 5, awareness 9, detection 87.75
Technical impactconfidentiality 7, integrity 7, availability 7, accountability 77.00HIGH
Business impactfinancial 7, reputation 5, compliance 5, privacy 76.00HIGH
SeverityHIGH likelihood × HIGH business impactCritical

▸ Now enforce MFA. Opportunity drops to 4 (special access needed) and ease of exploit to 3 — and likelihood only falls from 7.75 to 7.125, still HIGH. Averaging eight factors dilutes the one control that actually decides the attack. Where a single factor is decisive, override the average and say why.

Try it: OWASP risk rating

Threat agent

Vulnerability

Technical impact

Business impact

Likelihood
Technical impact
Business impact
Severity

6 · OWASP’s Own Caveats

The methodology page carries an unusually frank disclaimer. It notes there has been “lots of debate” about the methodology and the weighting of threat-actor skill levels, and points readers to more established alternatives: NIST SP 800-30, the Government of Canada Harmonized TRA methodology, and Mozilla’s Risk Assessment Summary and Rapid Risk Assessment, alongside OWASP’s threat-modelling projects. Add to that:

  • All factors weigh the same by default — the model “assumes that all the factors are equally important”. Step 6 allows a weighted average; most teams never use it.
  • Averaging hides the decisive factor — as the MFA example shows.
  • The numbers are uneven — Skill level jumps 1, 3, 5, 6, 9; two different options can share a rating. Treat the ratings as ordered labels, not measurements.
  • It rates a vulnerability, not an enterprise risk — use it for findings and roll the results up into the risk register, not instead of it.
  • “Quite a lot of uncertainty” — OWASP’s phrase for its own estimates. Record the reasoning behind each pick so a second tester can challenge it.

For a severity-only score that the whole industry shares, see CVSS, EPSS, KEV & SSVC; OWASP Risk Rating adds the business context CVSS leaves out.

Bottom line

  • 16 factors, 0–9 each — eight for likelihood, eight for impact (four technical, four business).
  • Average, band, look up — under 3 Low, under 6 Medium, else High; a symmetric 3×3 matrix gives Note to Critical.
  • Business impact wins when you have it.
  • Override the average when one factor decides the attack, and write down why.
  • A finding-level tool — feed its results into the enterprise register.

Sources & method. Steps, factors, option ratings, bands, severity matrix, OWASP’s worked example and the quoted caveats from the OWASP Risk Rating Methodology (OWASP Foundation, community page; content licensed CC BY-SA 4.0), read in November 2026. Factor ratings are reproduced as published; the VPN example and the MFA variation are illustrative. Original analysis; no third-party graphics reproduced.

← Back to Cyber security