Scope, Context, and Criteria

Scope, Context, and Criteria

The practical execution of risk management is impossible without a defined perimeter. According to ISO 31000:2018, the foundational step in the operational risk management process is establishing the scope, context, and criteria. This initial phase ensures that the subsequent risk assessment is not a generic, off-the-shelf exercise, but rather a highly customised intervention calibrated to the specific strategic objectives, constraints, and operational realities of the enterprise.

Delineating Scope and Establishing Context

Risk only exists in the context of organisational objectives; without a defined objective, there is no risk, only abstract uncertainty. Establishing the scope refers to defining the precise breadth and depth of the risk management activities the organisation intends to address. This requires delineating explicit boundaries, which may include physical geographic locations, specific technological architectures, localised project lifecycles, or enterprise-wide strategic horizons. When multiple risk management scopes overlap, for example, departmental assessments under a broader corporate ERM, organisations must ensure consistency to avoid conflicting controls and operational complacency.

Establishing the context requires a deep diagnostic understanding of both the internal and external operational environments. The external context encompasses macroeconomic volatility, geopolitical fragmentation, evolving regulatory mandates, and supply chain fragility, all of which generate unprecedented external threats. At the same time, the internal context assesses the organisation's capabilities, including its structure, financial position, technology maturity, and risk culture. Researchers stress that establishing the context is not a static preliminary step but a continuous feedback loop; as external signals shift or internal strategic objectives pivot, the context must be iteratively redefined to maintain the relevance of the risk architecture.

The Operational Distinction Between Risk Appetite and Risk Tolerance

Once the contextual boundaries are drawn, the organisation must set clear risk criteria to evaluate the significance of identified risks. These criteria must directly reflect the organisation's formally codified risk appetite and risk tolerance. While often used interchangeably in casual business settings, professional standards recognise them as distinct, complementary concepts that serve different roles in governance.

Risk appetite represents a broad, high-level philosophical statement regarding the total amount and type of risk an organisation is willing to accept, retain, or pursue to achieve its strategic objectives. It is formulated at the highest levels of corporate governance, typically by the board of directors, and serves as the strategic guiding philosophy. Risk appetite is inherently strategic, broadly scoped, and often expressed through qualitative statements. It defines the organisational willingness to engage in certain industry sectors, pursue aggressive mergers, or invest in unproven technologies to capture market share.

Conversely, risk tolerance is the tactical, operational translation of that strategic appetite into specific, measurable boundaries. It reflects the acceptable variation in outcomes related to specific performance measures. If risk appetite dictates the strategic destination, risk tolerance provides the operational guardrails needed to navigate there safely. Risk tolerance is highly granular, specific to individual business units or risk categories. It is almost exclusively expressed through quantitative metrics, such as acceptable percentage variances in operating expenditures, strict budgetary thresholds, or maximum allowable system downtime.

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