TRUST ATLAS WORKSHEET
Statement of Applicability
ISO 27001 · Step 2 · Assess risks and select controls- Who prepares it
- Risk owners
- When to prepare it
- Before implementation
Worked example
This example uses fictional details. Use the same fields with evidence from your work.
- Reference and control
- Annex A 8.2, Privileged access rights. Internal control IAM-03.
- Included and why
- Included. Seven named administrators and two automation identities can change production systems supporting hosted invoicing.
- Risk and treatment
- R-014. Misuse or theft of an administrator identity could expose customer invoices. Restrict privileges by role, require approval for elevation and review access quarterly.
- Implementation and evidence
- Implemented in the production billing accounts. Role policy POL-19, quarterly review EV-021 and deployment access test EV-022 show operation.
- Exclusion rationale
- Not applicable to this row. Every excluded Annex A control has its own documented rationale.
- Owner, approval and review
- A. Singh owns IAM-03. Operations Director approved treatment and accepted remaining risk in R-014 on 2026-10-09. Reassess if identity or cloud scope changes.
Gather first
- Licensed standard and applicable amendments
- Approved ISMS scope, risk assessment and treatment plan
- Control implementation records
- Relevant obligations and risk-owner approvals
How to prepare it
- List every control necessary for the selected risk treatments, including controls from outside Annex A. Compare the list with Annex A to identify omissions. Capture each required inclusion and justify each Annex A exclusion using a concrete fact about risk, scope or obligations.
- Create one row per control reference. Record the reason it is needed, implementation status and proof. Link the risk and treatment decision where applicable. For a planned control, name its owner, date and interim treatment.
- Have the ISMS lead reconcile the rows with the treatment plan, actual controls and obligations. Obtain risk owners’ approval of treatment and acceptance of remaining risks, and preserve version history and review triggers.
Review
A reviewer can trace selected controls to the reasons they are needed and supporting evidence, and can locate a justified decision for every excluded Annex A control.
Handoff
The ISMS lead holds the controlled SoA and makes the current version available for audit. Control owners update implementation evidence and notify the lead when treatment or scope changes.