May 29, 2026

ISO 27001 Roadmap Part 6: Gap Assessment, Risk Identification, Analysis and Evaluation

ISO 27001 Roadmap Part 6: Gap Assessment, Risk Identification, Analysis and Evaluation
By Maria Luz Pereyra - Cybersecurity Consultant - Cycubix
Part 6 of our series: Audit-Ready, Team-Friendly: A Beginner’s Guide to ISO 27001

Building on Parts 4 and Part 5 of the ISO 27001 Roadmap series, this article moves into the practical execution of information security risk assessment activities.

In this part of the roadmap, we examine that activity in greater detail by exploring how organisations can perform gap assessments, establish risk assessment criteria, identify and analyse risks, and evaluate risk exposure in alignment with ISO/IEC 27001:2022 and ISO/IEC 27005.

From Risk Methodology to Practical Implementation

One of the most common challenges during ISO 27001 implementation is translating high-level risk management concepts into a structured, repeatable, and audit-ready operational process.

While ISO/IEC 27001 requires organisations to perform information security risk assessments, ISO/IEC 27005 provides guidance on how to perform those activities consistently and effectively within the wider ISMS lifecycle.

In this article, we examine the core activities involved in performing an ISO 27001-aligned risk assessment, including:

  • Gap Assessment
  • Risk Assessment Criteria
  • Risk Identification
  • Risk Analysis
  • Risk Evaluation

To support implementation progression and readability, the practical walkthrough has been divided into two parts:

  • Part 6 (this article): Gap Assessment, Risk Identification, Risk Analysis, and Risk Evaluation
  • Part 7: Risk Treatment, Statement of Applicability (SoA), Monitoring, and Continuous Improvement

Throughout this article, we reference practical examples, scoring models, and implementation templates commonly used during ISO 27001 implementation. To keep the roadmap focused on methodology, governance, and decision-making, these operational examples are provided separately in the accompanying ISO 27001 Risk Assessment Toolkit.

Under ISO/IEC 27005, information security risk management is presented as a structured and iterative lifecycle covering:

  • Context establishment
  • Risk assessment
  • Risk treatment
  • Communication and consultation
  • Monitoring and review
  • Reporting and documentation

This lifecycle provides the foundation for effective information security risk management and supports the operation of an ISO 27001-aligned Information Security Management System (ISMS).

Gap Assessment

Under ISO/IEC 27005, establishing context ensures that information security risks are assessed consistently against organisational objectives, operating environment, and risk appetite.

The context defines the boundaries, assumptions, and evaluation criteria governing the entire risk management process.

A key activity in establishing this context is performing a Gap Assessment to understand the organisation’s current control environment and identify areas requiring improvement.

Gap Assessment Activities

The Gap Assessment begins with a review of all 93 Annex A controls, documenting each control and categorising it by implementation status and control theme.

For each control, organisations should capture:

  • Control reference and description
  • Control category
  • Implementation status
  • Supporting evidence
  • Gap description where applicable

Detailed examples and templates are included in the accompanying ISO 27001 Risk Assessment Toolkit.

How the Gap Assessment Informs Risk Assessment

Once completed, the Gap Assessment becomes a core input into the wider risk assessment process. It is not a standalone exercise, but a living document supporting ongoing ISMS monitoring and improvement activities.

The Gap Assessment supports:

  • Asset identification and register development
  • Vulnerability identification
  • Evaluation of existing controls
  • Control maturity assessment
  • Residual risk analysis

For example:

  • A gap in malware protection controls may introduce increased exposure to malicious software threats.
  • Partial implementation of encryption controls may increase the likelihood of data-at-rest compromise.
  • Asset-related Annex A controls support development of a structured asset inventory.

The Gap Assessment establishes the baseline control posture used to evaluate both inherent and residual risk exposure.

Risk Assessment Criteria

Before risks can be assessed consistently, organisations should define how risks will be measured and evaluated across the ISMS.

ISO/IEC 27005 establishes that risk assessment criteria specify how the significance of a risk is determined in terms of:

  • Consequence
  • Likelihood
  • Resulting risk level

Risk assessment criteria should be standardised across the organisation to support consistency, comparability, and informed decision-making.

At a minimum, organisations should formally define:

  • How impact is measured
  • How likelihood is measured
  • How risk levels are determined
  • Which risks may be accepted and under what conditions

Impact Scoring

Impact should be assessed across business-relevant dimensions such as:

  • Financial impact
  • Operational disruption
  • Legal and regulatory exposure
  • Reputational impact
  • Service delivery impact
  • Organisational disruption

For example, a critical operational impact may involve prolonged inability to deliver core client services or significant business disruption.

Detailed impact scoring examples and templates are included in the accompanying ISO 27001 Risk Assessment Toolkit.

Where multiple dimensions apply, organisations should define how the overall impact score is determined.

The Cycubix methodology uses the highest applicable impact rating unless otherwise justified and formally approved. This supports conservative, risk-based decision-making aligned with ISO expectations.

Likelihood Scoring

Likelihood estimates the probability of a risk event occurring using the most appropriate measurable basis available.

Organisations should consider:

  • Threat capability and motivation
  • Vulnerability exposure
  • Existing control effectiveness
  • Historical frequency and operational context

Detailed likelihood scoring examples and assessment templates are included in the accompanying toolkit.

Risk Acceptance Criteria

Once impact and likelihood have been assessed, organisations can determine the overall risk level using their approved risk evaluation model.

The resulting risk score is then evaluated against documented risk acceptance criteria to determine whether the risk:

  • Falls within acceptable thresholds
  • Requires treatment
  • Requires escalation for management approval

Detailed risk matrices and acceptance threshold examples are included in the ISO 27001 Risk Assessment Toolkit.

Risk Identification

Once the organisation has established its assessment criteria and baseline control posture, it can move into the operational phase of risk assessment.

Risk identification involves systematically documenting the events and conditions that could negatively affect information security objectives.

This process examines three key elements:

  • Assets
  • Threats
  • Vulnerabilities

Organisations should identify environmental, human, technological, and process-related threat sources, then assess how existing vulnerabilities and control gaps may increase exposure.

ISO/IEC 27005 supports multiple identification techniques, including:

  • Asset-based analysis
  • Threat-based analysis
  • Vulnerability assessments
  • Scenario-based approaches

Supporting documentation commonly developed during this phase includes:

  • Asset registers
  • Threat and vulnerability lists
  • Risk assessment procedures
  • Business impact assessments

The result is a structured inventory of risks documented within the organisation’s Risk Register.

Risk Analysis

Once risks are identified, organisations evaluate each risk using the approved assessment criteria and risk matrix.

This includes assessing:

  • Likelihood
  • Impact
  • Existing controls
  • Inherent risk exposure

The purpose of risk analysis is to establish a consistent and evidence-based understanding of organisational risk exposure prior to treatment decisions.

The analysis phase also helps organisations prioritise resources and remediation activities according to actual business impact.

Risk Evaluation

The evaluation phase compares analysed risks against documented risk acceptance criteria to determine the appropriate course of action.

Risks may:

  • Be accepted
  • Require treatment
  • Require escalation
  • Require further assessment

Residual risk may only be accepted where:

  • It falls within approved thresholds
  • A risk owner has been assigned
  • A review date has been established
  • Formal approval requirements have been satisfied

As a default principle, residual high or very high risks should not be accepted without documented justification, formal approval, and a time-bound remediation plan.

Special Considerations in Risk Evaluation

ISO/IEC 27005 recognises that some risks may require additional scrutiny regardless of numerical score.

These may include:

  • Regulatory risks
  • Reputational risks
  • Aggregated risks
  • Contractual risks
  • Critical service delivery risks

For example, a medium-scored GDPR-related risk may still require treatment due to regulatory sensitivity and potential legal exposure.

Similarly, multiple individually acceptable risks affecting the same business process may collectively create unacceptable operational exposure.

Organisations should therefore evaluate risks not only numerically, but also within a broader business and regulatory context.

Determining Residual Risk Levels

Once mitigation controls have been identified, organisations must determine the remaining residual risk exposure based on control implementation and effectiveness.

The Cycubix methodology uses implementation coverage as a supporting indicator to justify residual risk scoring within the organisation’s defined risk evaluation model.

Residual risk evaluation should consider:

  • Control implementation status
  • Control operating effectiveness
  • Monitoring capability
  • Residual business exposure
  • Organisational risk appetite

While ISO/IEC 27005 does not prescribe specific residual risk calculation models, organisations should apply a methodology that is consistent, defensible, and aligned with business context.

Conclusions

In Part 4, Step 3 introduced Risk Assessment as a key activity for driving informed implementation decisions. In this article, we explored that activity in greater detail by examining the core components of an effective ISO 27001-aligned risk assessment process:

  • Conducting a Gap Assessment
  • Defining risk assessment criteria
  • Identifying risks
  • Analysing risk exposure
  • Evaluating risks against organisational acceptance criteria

Together, these activities establish the operational foundation of an effective ISMS.

They help organisations ensure that risk management activities remain:

  • Evidence-based
  • Consistent
  • Defensible
  • Aligned with business objectives
  • Supportive of long-term operational resilience

Every organisation approaches ISO 27001 implementation from a different operational, regulatory, and resource context. The challenge is not simply performing a risk assessment, but building a process that remains practical, maintainable, and audit-ready over time.

Need Support With Your ISO 27001 Implementation?

At Cycubix, we help organisations design and operationalise ISO 27001-aligned ISMS programmes that support certification readiness and long-term business resilience. Contact us to discuss how we can support your ISO 27001 implementation journey.

What’s Next?

In Part 7, we will continue with:

  • Risk Treatment
  • Statement of Applicability (SoA)
  • Monitoring and review
  • Continuous improvement activities

We will also examine how organisations document and operationalise risk treatment decisions within the Risk Register and wider ISMS governance framework.

Continue the ISO 27001 Roadmap >>>

Part 7: Upcoming!

Missed a step?

The ISO 27001 Roadmap series by Cycubix provides a step-by-step guide to building, implementing, and maintaining an Information Security Management System (ISMS), helping organisations worldwide turn ISO 27001 from theory into action.