Determination of risk levels

Determination of risk levels

Once the potential consequences and the likelihood of an event have been independently and rigorously assessed, the information security risk assessment process proceeds to determine the overall risk level. ISO/IEC 27005 states that the level of risk is determined by mathematically or categorically combining the assessed likelihood and consequences for all relevant risk scenarios. The ultimate, strategic purpose of this calculation is to provide risk owners and executive leadership with a standardised, highly defensible metric to prioritise risks across the enterprise and make informed, resource-backed decisions about risk treatment.

Determining risk levels requires establishing criteria that accurately reflect the organisation's operating environment and threat landscape. Likelihood, a critical component of this equation, represents the probability or frequency of a threat event occurring and successfully exploiting a vulnerability within a given timeframe. Depending on the organisational methodology, likelihood can be expressed in probabilistic terms (the percentage chance that an event will occur within a specific timeframe, typically annualised) or in frequentist terms (the notional average number of occurrences within a given period, such as once every ten years).

To accurately capture the vast disparities inherent in cyber risk events, ISO/IEC 27005 recommends using logarithmic scales (e.g., Base 10) for both likelihood and consequence when determining risk levels. A logarithmic scale allows organisations to model high-frequency, low-impact events (such as automated, volumetric botnet scans) alongside exceedingly rare, catastrophic events (such as a nation-state supply chain compromise or an insider threat sabotage) within the same analytical framework. By summing the logarithmic indices of likelihood and consequence, organisations can calculate a consolidated risk value that accurately reflects exponential increases in severity, avoiding the flattening effect of linear addition.

When organisations rely on non-numerical matrices to determine risk levels, ISO/IEC 27005 explicitly cautions against using symmetrical grids. A risk matrix that is perfectly symmetrical about its diagonal assumes that a high-likelihood/low-consequence event represents the same business exposure as a low-likelihood/high-consequence event. In reality, an organisation's risk profile is normally asymmetrical. Trivial events are generally the most frequent, and expected frequency typically reduces as consequences increase. Therefore, the matrix used to determine the final risk level must be weighted to reflect the organisation's specific aversion to catastrophic outcomes, ensuring that existential threats always produce the highest risk level, regardless of their perceived improbability.

The primary challenge in determining accurate risk levels lies in navigating the triad of uncertainty: personal uncertainty (the inherent cognitive bias of the human assessor), methodological uncertainty (flaws in simplistic modelling tools or poorly designed matrices), and systemic uncertainty (a fundamental lack of historical data regarding novel, emerging threat vectors). The rapid evolution of the threat landscape, particularly the weaponisation of artificial intelligence by threat actors to automate phishing campaigns and exploit discovery, means that historical frequency data is increasingly unreliable for predicting future likelihood.

How to mathematically or categorically score a risk. However, these mechanics don't exist in a vacuum; they're shaped by the organisation’s governance (appetite, tolerance, and acceptance criteria).

  1. Risk Appetite (The Strategic Direction): Risk appetite is the highest-level governance concept. It is the amount and type of risk an organisation is broadly willing to pursue or retain to achieve its strategic objectives. The Board of Directors sets it.

  2. Risk Tolerance (The Operational Boundaries):  While appetite is a broad strategic statement, tolerance is the specific, measurable level of variance the organisation will accept around a specific objective.

  3. Risk Assessment Criteria (The Measurement Mechanics): This is exactly what we have described above. Once appetite and tolerance are defined, the organisation must establish the mathematical or categorical rules for measuring likelihood and consequence to ensure risks are scored consistently.

  4. Risk Acceptance Criteria (The Decision Thresholds): Risk acceptance criteria are the definitive thresholds that determine whether a scored risk is acceptable to the business or unacceptable and requires active treatment (mitigation, transfer, or avoidance).

Advanced Risk Management

Buy nowLearn more
  • Course Motivation

0.0 Shifting from technical execution to strategic risk management.

  • The Strategic Imperative of the Security Function
  • IBM - Motivation for Risk Analysis in CyberSecurity (11 min)
  • Google - Security Frameworks (30 min)
  • Introduction: The Evolution of Security Management

1. Introduction to ISO/IEC 27005 and information security risk management

  • Introduction: The Evolution of Risk Management Standardisation
  • International Standardisation: ISO 31000 versus ISO 27005
  • The ISO Risk Management and other frameworks
  • The Psychology of Risk Perception and Decision-Making
  • The ISO 31000 Architecture: Principles, Framework, and Process
  • Review of Risk Assessment Methodologies (IEC 31010)
  • Scope, Context, and Criteria
  • Leadership, Governance, and Corporate Commitment
  • Quiz01 - Risk Management [Day01]

2. Information Security Risk Identification, Assessment, and Treatment (ISO/IEC 27005)

Delayed 1 day

  • Identification and description of information security risks
  • Identification of risk owners
  • Assessment of potential consequences
  • Determination of risk levels
  • Comparison of risk analysis results with established risk management criteria
  • Risk prioritization
  • Determination of required controls for risk treatment
  • Risk treatment plan
  • Quiz02 - Risk Identification, Assessment and Treatment [day2]

3 - Risk Acceptance, Communication, Monitoring and Review

Delayed 2 days

  • Key Take aways (Module 01 - Module 02)
  • Quiz03 - Recap - Session 1 & 2
  • Communication and Consultation of Results
  • Documentation of the Risk Analysis Process
  • Documentation of Results
  • Monitoring of Risk-Generating Factors
  • Deep Dive: Navigating Complexity with ISO/TS 31050 and the Risk Intelligence Cycle
  • Future-Looking Challenges for Risk Management and ISO/IEC 27005

4 - Risk Assessment Methodologies

Delayed 3 days

  • The Methodological Shift: Transcending Traditional Frameworks
  • Technique 1: STRIDE for Cloud and PaaS Architectures
  • Technique 2: Subjective Evaluation of Opaque AI Risks
  • FMEA, Red Teaming, and Risk Register Integration
  • Risk Monitoring Processes
  • Part B: Procedure to Execute an FMEA Analysis

05 - ISO 27005 Risk Assessment Using FMEA

Delayed 4 days

  • Process Overview - Lab: AI and Cloud Services
  • Quiz - Simulation exam
  • Quiz - summary