In brief
An ISO 27001 risk register example for software and IT outsourcing teams: the columns clause 6.1 asks for, sample risks mapped to Annex A, and upkeep.
An ISO 27001 risk register is the record of your risk assessment and risk treatment results that clauses 6.1.2, 6.1.3, 8.2 and 8.3 of ISO/IEC 27001:2022 require you to keep as documented information. Each row holds one specific risk, its owner, the risk level before and after treatment, the treatment decision and the controls that address it. Below is an ISO 27001 risk register example for a software company, the columns that map to each requirement, and how to keep the register current after certification.
This guide is for Vietnamese software and IT outsourcing vendors building an ISMS, and for their international clients who receive a register extract during vendor due diligence and want to know what a credible one looks like. The assessment method itself (criteria, scales, repeatability) is covered in the ISO 27001 risk assessment guide; this post focuses on the register.
What is an ISO 27001 risk register and why does it matter?
A risk register is where risk assessment turns into a work list. ISO/IEC 27001 does not prescribe the name or a template. It requires you to retain the results of risk assessments (8.2) and of risk treatment (8.3), and to have risk owners approve the treatment plan and accept residual risk (6.1.3 f). Most organizations keep all of this in one register.
The register is also the link to the Statement of Applicability. Every control you mark as applicable in the SoA should trace back to a risk in the register or to a legal, regulatory or contractual requirement. If the register does not reflect real risks, the SoA and the controls behind it do not hold up either. The ISO 27001 Statement of Applicability guide covers the SoA side of that link.
Which columns does an ISO 27001 risk register need?
There is no mandatory format; the auditor assesses content, not layout. The columns below are enough to demonstrate each requirement in clauses 6.1.2, 6.1.3 and 8.2.
| Column | What it holds | Related requirement |
|---|---|---|
| Risk ID and title | A short, specific description | 6.1.2 c (identify risks) |
| Asset or process | What is affected, within the ISMS scope | 6.1.2 c |
| Threat and vulnerability | What could happen and why | 6.1.2 c |
| Risk owner | The person accountable for managing the risk | 6.1.2 c |
| Likelihood, impact, inherent risk level | Scored on the scale defined in your method | 6.1.2 d, e |
| Treatment option | Modify (mitigate), retain (accept), share (transfer) or avoid | 6.1.3 a |
| Controls and actions | Annex A or additional controls, action owner, due date | 6.1.3 b, c, e |
| Residual risk | Level once controls operate, with the owner's approval | 6.1.3 f |
| Last and next review date | Evidence that the assessment is repeated on schedule | 8.2 |
How do you build the register step by step?
- Fix the scope. The register covers only the systems, data, people and third parties inside the ISMS scope defined under clause 4.3. Too broad and the register becomes unmanageable; too narrow and you miss real risks.
- Start from the asset inventory. Annex A control 5.9 requires an inventory of information and other associated assets. Use it as the frame so nothing is missed. Group assets by type and criticality; you do not need a row per laptop.
- Write each risk as a scenario. A risk is an asset plus a threat plus a vulnerability, written specifically enough that you can choose a control for it.
- Score it using the scale and definitions in your approved methodology.
- Choose a treatment option and actions for every risk above your acceptance threshold.
- Map controls from Annex A, or additional controls, and update the Statement of Applicability.
- Re-score residual risk and get the risk owner's approval.
What does a risk register example for a software company look like?
The rows below illustrate typical risks for a software product or outsourcing team. They are an example, not a template to copy as-is: the scores and actions depend on your own scale and context.
| Asset | Threat / vulnerability | Risk | Annex A controls | Example action |
|---|---|---|---|---|
| Source code repository | Leavers keep access / no periodic access review | Former staff can still read or change code | 5.18 Access rights, 8.4 Access to source code | Revoke access in offboarding; quarterly access review |
| Production database | SQL injection / missing input validation | Customer data exposed | 8.28 Secure coding, 8.29 Security testing in development and acceptance | Secure coding standard; security testing before release |
| Developer laptops | Loss or theft / unencrypted disk | Source code and credentials exposed | 8.1 User endpoint devices, 8.24 Use of cryptography | Enforce FileVault or BitLocker; device management |
| API keys in code | Credential leak / keys hardcoded in the repository | Keys exposed through git history | 5.17 Authentication information, 8.28 Secure coding | Secret scanning before merge; keys kept in a secret manager |
| Backups | Ransomware / restores never tested | Unable to recover after an incident | 8.13 Information backup | Scheduled restore tests with a written record |
For outsourcing vendors, client-specific risks belong here too: a client's source code on a shared build server, or a client's production credentials held by your engineers. Clients increasingly ask about these in security questionnaires, so it helps when the register already names them. How to decide inclusion or exclusion for all 93 controls is covered in the ISO 27001 Annex A controls guide.
How should risks in the register be scored?
ISO 27001 does not prescribe a scoring formula, but the scoring must be consistent and explainable. The most common approach is likelihood × impact, each on a 1 to 5 scale, giving a risk level from 1 to 25 that you band into levels such as low, medium, high and critical using thresholds you set yourself.
What matters is that each level is defined in the methodology. "Likelihood 3" should carry a concrete description, for example "could happen within the next 12 months", not just "medium". If every risk in the register lands on the same level, the scale definitions are probably too vague.
Who owns each risk and who approves residual risk?
The risk owner is the person with the accountability and authority to manage the risk, usually the head of the function or the owner of the affected system: the CTO or Head of Engineering for technical risks, the COO for operational ones. Clause 6.1.3 f requires risk owners to approve the risk treatment plan and accept the residual risk, so the register should record who approved and when.
How do you maintain the risk register after certification?
Clause 8.2 requires risk assessments at planned intervals and when significant changes are proposed or occur. Most organizations review the register at least once a year, plus whenever:
- a new product or feature processes sensitive data;
- infrastructure changes, such as a cloud migration or a new critical supplier;
- a security incident occurs;
- key people change;
- legal or contractual requirements change.
Each review should leave evidence: the date, who reviewed, and the outcome (no change, which risks were updated, which were added). Surveillance auditors look for that trail. For the wider maintenance cycle, see maintaining ISO 27001 after certification and the ISO 27001 internal audit guide.
What are the most common risk register mistakes?
- Copying an internet template unchanged. Auditors notice quickly because the risks do not match the real environment.
- Every risk scored "medium". A sign the scale was never defined properly.
- No risk owner. Nobody follows the risk up.
- A register detached from reality. Controls are listed but there is no evidence they operate.
- No update after change. A register not reviewed for 18 months is a serious weakness at a surveillance audit.
Spreadsheet or software for the risk register?
A spreadsheet satisfies the standard; nothing in ISO 27001 requires dedicated software. The difficulty usually shows up during maintenance: proving reviews happened on schedule, tracking whether treatment actions are done, and linking each control to its evidence.
pTrackly has a risk register that scores likelihood × impact on a 1–5 scale and records inherent and residual risk (residual is set by the user, not calculated), threat, vulnerability, risk owner and linked assets from the asset inventory. Treatment actions carry an owner, a due date, a control reference such as "ISO 27001 A.5.17" and an evidence reference, and are verified by the owner or an admin. Accepted risks need a justification and an expiry date, and every risk has a last and next review date. Identifying risks, scoring them and deciding treatment remain your team's work. See pTrackly for ISO 27001.
Frequently asked questions
Is a risk register mandatory for ISO 27001?
The standard does not mandate the name "risk register", but it does require documented information about the risk assessment process, the assessment results and the treatment results. A register is the most common way to meet those requirements.
What is the difference between a risk register and the Statement of Applicability?
The risk register lists risks, their levels and how each is treated. The Statement of Applicability covers all 93 Annex A controls and states which apply, why, and whether they are implemented. The two must agree: applicable controls should trace back to a risk or another requirement.
How often should the ISO 27001 risk register be reviewed?
At the interval set in your methodology, commonly once a year, and whenever significant changes occur, as clause 8.2 requires. Each review should record the date, the reviewer and the outcome.
Can one risk map to several controls?
Yes, and it usually does. A data leak from a lost laptop, for example, relates to 8.1 user endpoint devices, 8.24 use of cryptography and 6.8 information security event reporting. One control can also treat several risks.
References:
- ISO/IEC 27001:2022, Information security management systems (iso.org/standard/82875.html)
- ISO/IEC 27005:2022, Guidance on managing information security risks (iso.org/standard/80585.html)