ISO/IEC 27005 Qualitative vs Quantitative Risk Analysis
Use a well-defined qualitative method for efficient screening and communication. Use a quantitative method when numeric ranges can improve a material decision and the inputs support them. Combine methods when different decisions need different depth.
ISO/IEC 27005:2022 allows qualitative, quantitative, and semiquantitative analysis. The chosen method must still support consistent, valid, and comparable results.
ISO/IEC 27005:2022 does not require one calculation model. A qualitative method uses defined nonnumeric categories such as low, medium, and high. A quantitative method uses numbers whose units and proportional meaning are maintained, such as annual frequency, probability, money, downtime, or lives affected. A assigns numbers to ordered bins or categories without making them true measurements. Choose the least complex method that can support the decision, document it, calibrate it against a shared reference scale, and make repeated assessments consistent, valid, and comparable.
Side-by-side comparison
Qualitative vs quantitative risk analysis: practical differences
Compare what each method measures, when it helps, what evidence it needs, and how to avoid false precision under ISO/IEC 27005:2022.
Define non-overlapping categories and examples, assess likelihood and consequence with evidence, explain each rating, combine them under a defined rule, and compare the result with criteria.
ISO's official listing identifies the fourth edition as guidance for managing information security risks; method details remain organization-specific.
Guidance on managing information security risks
Define the scenario, time horizon, and units; gather data and elicited estimates; model uncertainty; calculate ranges; test sensitivity; validate; and compare with criteria.
ISO's official listing identifies the fourth edition as guidance for managing information security risks; method details remain organization-specific.
Guidance on managing information security risks
Data provenance, units, distributions or ranges, assumptions, calculation or simulation logic, calibration, uncertainty, sensitivity, validation, and decision record.
ISO's official listing identifies the fourth edition as guidance for managing information security risks; method details remain organization-specific.
Guidance on managing information security risks
A quantitative method is not automatically more conformant or reliable; its units, assumptions, data, uncertainty, and calculations must fit the decision.
ISO's official listing identifies the fourth edition as guidance for managing information security risks; method details remain organization-specific.
Guidance on managing information security risks
Process
Qualitative method
Define non-overlapping categories and examples, assess likelihood and consequence with evidence, explain each rating, combine them under a defined rule, and compare the result with criteria.
ISO's official listing identifies the fourth edition as guidance for managing information security risks; method details remain organization-specific.
Guidance on managing information security risks
Quantitative method
Define the scenario, time horizon, and units; gather data and elicited estimates; model uncertainty; calculate ranges; test sensitivity; validate; and compare with criteria.
ISO's official listing identifies the fourth edition as guidance for managing information security risks; method details remain organization-specific.
Guidance on managing information security risks
Quantitative method
Data provenance, units, distributions or ranges, assumptions, calculation or simulation logic, calibration, uncertainty, sensitivity, validation, and decision record.
ISO's official listing identifies the fourth edition as guidance for managing information security risks; method details remain organization-specific.
Guidance on managing information security risks
Quantitative method
A quantitative method is not automatically more conformant or reliable; its units, assumptions, data, uncertainty, and calculations must fit the decision.
ISO's official listing identifies the fourth edition as guidance for managing information security risks; method details remain organization-specific.
Guidance on managing information security risks
1
Section 1
What does ISO/IEC 27005 say about qualitative and quantitative methods?
ISO/IEC 27005:2022 permits qualitative analysis using defined attributes, quantitative analysis using numerical values, and semiquantitative analysis using qualitative scales with assigned values. It does not make one approach inherently more conformant. The organization documents the chosen approach and uses criteria detailed enough to produce repeatable, valid, and comparable results.
Risk levels can be qualitative, such as very high, high, medium, and low, or quantitative, such as expected monetary loss, loss of life, or market share over a stated period. Both need a reference scale understood by interested parties and periodic calibration. Qualitative levels should be unambiguous, non-overlapping, and expressed in objective language.
ISO/IEC 27005 is guidance, while ISO/IEC 27001 contains the certifiable ISMS requirements. ISO/IEC 27001 requires consistent, valid, and comparable results but does not mandate a heat map, 1-to-5 matrix, Monte Carlo simulation, or financial risk model.
Define the decision, scope, time horizon, consequence types, likelihood criteria, and acceptance authority before choosing a scale.
Use qualitative categories only when each category and boundary has a clear meaning and supporting rationale.
Use quantitative units only when arithmetic on those units is meaningful; a numbered ordinal scale is still semiquantitative.
Supplemental official guidance distinguishes qualitative, quantitative, and semiquantitative scales and explains the strengths and limits of each.
2
Section 2
Which records make the selected analysis method reviewable?
For any method, record the purpose, scope, scenario, owner, time horizon, risk criteria, source evidence, assumptions, uncertainty, result, treatment decision, approval, and review trigger. Define every category, threshold, unit, and combination rule so another competent assessor can reproduce the reasoning.
For quantitative work, also retain data provenance, elicited estimates, ranges or distributions, model logic, calculation or simulation settings, sensitivity, validation, and known limitations. For qualitative work, retain the rationale and evidence behind each rating, examples anchoring the categories, and any equivalence used across different scales.
Link conclusions to current source evidence and assumptions.
Keep approval, version, date, owner, and review trigger with the decision.
Record uncertainty and exceptions instead of hiding them in a score.
How should teams select and apply an analysis method?
Start with the decision. Qualitative analysis is often enough for broad inventories, rapid screening, or communication where clear categories separate treatment priorities. Quantitative analysis is useful when the decision depends on the size and distribution of possible loss, a cost-benefit comparison, a treatment budget, or the difference between close options.
Use a combined approach when it reduces effort without hiding material risk. For example, screen a large inventory with calibrated qualitative criteria, then quantify the scenarios near an acceptance threshold or those tied to large investment decisions. Evaluate every result against approved criteria and keep the accountable risk owner separate from the analyst.
Apply an explicit branch. If well-defined categories clearly separate accept, treat, and escalate outcomes, use the qualitative method. If two options remain close, the exposure crosses a material threshold, or cost and benefit depend on the range of possible loss, quantify the selected scenario. If data are sparse, use ranges and record expert judgment and uncertainty instead of manufacturing a precise point estimate.
Qualitative example: define "major" operational consequence with observable downtime, affected services, and recovery limits; record why the scenario meets that band and which evidence supports it.
Semiquantitative example: assign 1 through 5 to ordered likelihood bands for prioritization, but do not claim that a rating of 4 is twice a rating of 2 unless the underlying scale establishes that relationship.
Quantitative example: estimate event frequency over a stated period and consequence in money, downtime, records, or another defined unit; use ranges or distributions when uncertainty affects the decision.
Combined example: screen all scenarios with calibrated categories, then quantify high-cost treatments, borderline acceptance decisions, or exposures whose cumulative effect a matrix hides.
NIST explains when qualitative communication, quantitative cost-benefit analysis, and semiquantitative prioritization can help, subject to clear assumptions and scales.
4
Section 4
Which method-selection mistakes should teams avoid?
Numbers do not make weak evidence objective, and labels do not excuse vague reasoning. Do not multiply or average ordinal 1-to-5 ratings as if the intervals and ratios were measured quantities. Do not compare a 'high' rating from one scale with a 'high' rating from another until their definitions and thresholds are mapped.
Avoid a single-point estimate when a range would show material uncertainty. Do not buy extra precision that cannot change the decision. A rough but traceable estimate can be sufficient, while a detailed model can still be misleading when subjective judgments or unknown dependencies are hidden.
Do not present guidance as a legal mandate or standalone certification requirement.
Do not confuse a template, matrix, or register with evidence that the process operated.
Do not leave ownership, rationale, residual risk, or review conditions implicit.
NIST warns that unclear qualitative categories, buried subjective judgments, and significant uncertainty can weaken assessment rigor.
5
Section 5
When should the selected method be reviewed?
Review the method and the affected assessments when the decision, scope, criteria, data, threat conditions, controls, assumptions, time horizon, or acceptance thresholds change. Also review it when independent assessors cannot reproduce the result, when similar risks produce incomparable results, or when the model's precision does not improve the decision. ISO/IEC 27005 sets no universal annual method-review deadline; use a planned cadence and change-driven triggers appropriate to the ISMS.
Set a planned review date.
Define event-driven triggers and evidence owners.
Preserve change history so reviewers can understand why the decision changed.
Supplemental official guidance explaining qualitative, quantitative, and semiquantitative approaches, their tradeoffs, uncertainty, and the need to define scales clearly.
Supplemental official guidance distinguishes qualitative, quantitative, and semiquantitative scales and explains the strengths and limits of each.
NIST explains when qualitative communication, quantitative cost-benefit analysis, and semiquantitative prioritization can help, subject to clear assumptions and scales.
Show 1 more
NIST warns that unclear qualitative categories, buried subjective judgments, and significant uncertainty can weaken assessment rigor.