ISO 27001 Risk Assessment, Risk Treatment and Statement of Applicability
A risk register lists unauthorised access as a high risk. The treatment plan says access reviews are complete. The Statement of Applicability says the relevant controls are implemented. Yet the latest review still contains accounts belonging to former contractors.
The records describe different versions of the same situation. Before an audit, the organisation needs to understand the gap and make its decisions traceable.
This guide follows the connection between risk assessment, risk treatment, the Statement of Applicability and operating evidence. For the wider standard and certification journey, start with the SCS ISO 27001 overview. The examples below are fictional illustrations, not SCS client cases or prescribed scoring methods.
What each record should explain
The risk assessment identifies and evaluates information-security risks. Treatment records explain the response. The Statement of Applicability, commonly called the SoA, records the necessary controls, their inclusion justifications, whether they are implemented, and justifications for excluding Annex A controls. Operating records support what the organisation says actually happens.
ISO/IEC 27001 sets the ISMS requirements. ISO/IEC 27005 provides supporting risk-management guidance; it does not require every applicant to use an identical spreadsheet or scoring formula.
|
Record |
Main question |
Useful connection |
|
Risk assessment |
What could affect the confidentiality, integrity or availability of information? |
Relevant activity, consequence, evaluation and risk owner |
|
Treatment plan |
What response has been selected and who will deliver it? |
Necessary controls, actions, responsibilities and progress |
|
Statement of Applicability |
Which controls are necessary and what is their implementation status? |
Inclusion basis, Annex A comparison and exclusion justifications |
|
Operating evidence |
What supports the stated control operation? |
Relevant systems, dates, populations, exceptions and follow-up |
This is an explanatory structure. It is not a mandatory four-document filing system.
Establish criteria before assigning risk scores
Decide how likelihood and consequences will be assessed, how risk levels will be evaluated and what makes a risk acceptable. Make the method understandable to the people using it. A service owner should be able to explain why a customer-information exposure received its rating.
Avoid unexplained precision. A five-by-five matrix can be useful, but a score of 12 has little meaning without defined scales and a consistent assessment basis. Consider existing controls honestly: an approved access policy and a completed access review provide different information about present exposure.
Describe the risk with enough context to support a decision. “Cyberattack” is too broad for assigning useful treatment. “A former support contractor can still enter the customer administration portal because supplier termination does not trigger account removal” identifies an activity, weakness and possible consequence.
Work through one risk before expanding the register
A fictional Malaysian SaaS company uses an external support team. A UAE customer raises concerns about access after a support contract ends. The SaaS company retains responsibility for the access it grants, even where the support provider has its own certificate.
The company checks who can enter its production support tools, which accounts remain active and how termination instructions reach the application owners. It identifies three contractor accounts that no longer have a business purpose.
|
Step |
Illustrative decision or record |
What still needs checking |
|
Describe the risk |
Former contractors retain access to customer support information |
Which tools and information are reachable? |
|
Evaluate it |
Apply the approved likelihood and consequence criteria to the current arrangements |
Were existing safeguards considered on a supported basis? |
|
Select treatment |
Remove unnecessary access and introduce a supplier-exit notification process |
Who owns notifications and application-level removal? |
|
Assign delivery |
Procurement confirms contract endings and system owners record removals |
Do responsibilities cover subcontractors and emergency access? |
|
Evaluate residual risk |
Reassess after the implemented measures have been checked |
Does the authorised risk owner accept the remaining risk? |
|
Connect the SoA |
Explain the necessary supplier and access controls and their actual status |
Do the descriptions agree with operating records? |
The example does not establish a universal access-removal deadline. The organisation must determine appropriate arrangements in light of its risks and applicable obligations. For more operational examples, use the existing SaaS evidence guide.
Select treatment and obtain the necessary decisions
Treatment may involve changing controls, avoiding an activity, sharing aspects of exposure through an appropriate arrangement, or retaining a risk through an authorised decision. Insurance or outsourcing does not automatically remove the organisation's obligations or its need to manage the remaining risk.
Give actions identifiable owners and explain their completion basis. “Enable stronger authentication” is incomplete if nobody knows which applications are included, who will implement the change or how unsupported integrations will be handled.
Keep planned and implemented measures distinguishable. Obtain risk-owner approval of the treatment plan and acceptance of residual risks through the organisation's established process. Do not reduce the recorded risk simply because a purchase order has been issued.
Build a Statement of Applicability that reflects the decisions
Determine the controls necessary for treatment and compare them with Annex A so that necessary controls have not been overlooked. Relevant controls can also arise from contractual or other applicable requirements and can extend beyond Annex A.
ISO's auditing-practices note on the Statement of Applicability explains the role of the SoA and why it is more than a table showing Annex A implementation. The note predates the final 2022 publication and includes references to the 2013 edition; read it as explanatory guidance alongside the applicable current requirements.
Useful SoA entries explain the inclusion basis and implementation position clearly. Where a provider performs an activity, identify the arrangement and the organisation's retained responsibility. “Not applicable because we use the cloud” is unlikely to explain a decision about a responsibility that the customer organisation still holds.
Avoid copying another business's exclusions. A software company with no owned server room may still have office access, laptops, storage areas or provider interfaces that need consideration. The justification must follow its own scope and risks.
A data centre example involving tenant responsibilities
A fictional colocation operator supplies space, power, cooling and controlled physical access. Its tenant administers the tenant's operating systems. The operator should explain the physical and operational risks within its own ISMS and record the actual boundary for tenant administration.
If the operator later offers managed backup, the decision changes. It must assess the newly accepted access, retention and restoration responsibilities instead of reusing the old boundary unchanged. The existing data-centre scope article explains operator and tenant responsibilities; the certified data-centre expansion article addresses changes to certification coverage.
The SoA supports the control decisions. It does not replace the scope statement or independently determine what the certificate covers.
Keep risk decisions current as the operation changes
Review risk assessments at planned intervals and when significant changes are proposed or occur. Examples include an overseas support team, a new cloud region, an acquisition, a changed customer requirement or evidence that a selected control is ineffective.
Revisit the affected treatment decisions and SoA entries. A changed risk rating does not always require a new control, but the organisation should be able to explain what it considered and decided. Where a change may affect certified coverage, discuss it with the issuing certification body.
Use the general ISO 27001 audit-evidence guide for the wider evidence register. Keep sensitive risk details in an appropriately controlled location rather than publishing them in a customer-facing version of the SoA.
Using the same approach in UAE Malaysia and other countries
The technical connection between risks, treatments and controls can support operations in different countries. The facts may differ: the contracting entity, system ownership, information flows, supplier arrangements and applicable obligations still need to be established for each operation.
For certification enquiry context, use the existing UAE and Malaysia guides, followed by Saudi Arabia, Oman, Qatar, Kuwait and Bahrain. Separate guidance is available for India, Canada and Singapore. These country articles explain their local certification context; they do not change the technical requirements into separate national risk methods.
Discuss assessment information with SCS
Before enquiring, identify the proposed ISMS scope, operating locations, risk-assessment approach and current implementation position. Explain any significant outsourcing or change affecting the proposed assessment. Do not send unrestricted vulnerability details or customer datasets with a general enquiry.
Use the SCS ISO 27001 certification service page or contact SCS to discuss certification arrangements. The organisation owns its risk and control decisions; independent certification evaluates conformity and effectiveness rather than approving a business's risk choices in advance.
Need ISO 27001 Certification for Your Business?
Speak with our certification specialists to understand certification requirements, audit process, implementation timelines and accredited certification services.