ISMS and ISO 27001

ISO 27001 Risk Analysis, Risk Treatment and SoA

First we set up the risk assessment methodology. We define risks together with their owners and draw up the risk treatment plan. Within risk treatment, we determine the necessary controls and compare them with Annex A to verify that no necessary control has been missed.

ISO/IEC 27005

Clause 6.1.2Clause 6.1.3Risk acceptance criteriaRisk treatment planSoAResidual risk approval

Service definition

What are ISO 27001 risk analysis and the SoA, and who are they for?

Risk analysis means assessing the likelihood and impact of events that could affect information security, using the organization’s own criteria. Risk treatment sets the decision for each risk (reduce, avoid, transfer, accept) and the controls to apply. The Statement of Applicability shows the necessary controls, the reasons they were chosen, whether they’re implemented, and the justification for controls excluded from Annex A. Necessary controls can also be chosen from outside Annex A.

01

Should we do asset-based or scenario-based risk analysis?

Both conform to the standard. In small and mid-sized organizations, the scenario-based method gives more manageable results; in sectors requiring a detailed inventory, the asset-based approach can be chosen.

02

Do we have to implement all controls in the SoA?

No. Necessary controls are determined by risk treatment decisions and requirements. Controls excluded from Annex A are written into the Statement of Applicability with their justification.

03

How often is the risk analysis updated?

At planned intervals (usually once a year) and when significant changes occur. The schedule is written into the methodology document.

04

What tool is it kept in?

It can be Excel, a SharePoint list or your existing GRC tool. The tool is secondary; the method must be consistent and the records traceable.

Project stages

How do we proceed?

01 / STAGE

Methodology

We define the scales and acceptance criteria together with management.

02 / STAGE

Workshops

We define risks together with process owners.

03 / STAGE

Treatment and SoA

Controls are chosen, the SoA is written and the treatment plan is drawn up.

04 / STAGE

Approval

Risk owners and management approve the residual risks.

Compliance and Audit

Base your control choices on a risk analysis with written justification

Share your scope, existing risk records and target standard. Let’s prepare a proposal with work items for the risk methodology, risk register and SoA work.