An information security risk register is a record of what could go wrong with an organisation’s information and the systems that hold it. For each risk, it shows how likely and how harmful it would be, who owns it, and what has been decided about it. It is the record that every other security decision should come back to: which controls to put in, where to spend money, which suppliers to look at more closely and what to tell leadership.
Most organisations know they should have one. Fewer have one that people use. A register can easily become a spreadsheet filled in before an audit and forgotten afterwards, with risks nobody owns, scores nobody can explain and decisions nobody remembers making. This Insight article sets out what a useful register contains and how to keep it that way, using the five core requirements of the RiskWitness Blueprint.
- What could go wrong?The risk, written as a sentence
- Who is responsible for it?A named owner
- How serious is it?How likely, and how harmful
- What are we doing about it?A decision, and the actions that follow
- When do we look again?A review date
What a risk register is, and who it’s for
A risk register is more than a list of threats. A few terms are worth being clear about, because they’re often mixed up:
- Risk is, in the NCSC’s plain words, the possibility of something bad happening. In practice it is described by how likely that is and how much harm it would do.
- A threat is a potential cause of harm with intent behind it, such as a criminal group that uses ransomware. Harm without intent, such as a flood or a member of staff emailing a file to the wrong person, is often called a hazard.
- A vulnerability is a weakness that a threat could exploit, such as an unpatched server or an account without a second sign-in step.
- A control is anything that makes a risk less likely or less harmful, whether technical, procedural, physical or about people.
A register brings these together for each risk, in one place, in a form people can compare.
It has several readers, and each wants something different from it:
- Leadership wants to know which risks are serious, whether they are within what the organisation is prepared to accept, and what it has been asked to approve.
- Risk owners want to know what they are responsible for, what has been agreed and what is due.
- Auditors, customers and regulators want evidence that risks are identified, assessed and decided on in a consistent way, and that the decisions were made by the right people.
A good register serves all of them from the same record. That is why it matters less which tool it is kept in than whether each entry is complete, consistent and current.
About the RiskWitness Blueprint
The RiskWitness Blueprint is a free information security framework that we publish for organisations of every size. It sets out 249 requirements across a core and eleven areas, from identity and access to suppliers and artificial intelligence. Each requirement says what to do and why it matters, and leaves the choice of how to the organisation.
Requirements sit in three tiers, and each tier includes everything below it:
- Foundation: what every organisation should have, whatever its size, including the controls that stop the most common attacks.
- Established: a managed programme, with deeper risk work, supplier assurance, testing, monitoring and regular review.
- Advanced: for organisations with more at stake, with round-the-clock monitoring and deeper, independent testing.
The Blueprint is also proportionate. It says what to achieve, not how far to take it, so a small firm and a large one can both meet the same requirement in ways that suit their size and risks. The full framework can be downloaded free.
What the requirements ask
RW-CORE-01Foundation
A risk register with an owner for every risk
Identify the main information security risks to your organisation and record each one in a risk register, with a named owner who is responsible for it.
RW-CORE-02Foundation
One way of judging every risk
Assess every risk in the register using one agreed method for judging how likely it is and how much harm it would do.
RW-CORE-03Foundation
An agreed appetite for risk
Have senior leadership agree and write down how much information security risk the organisation is prepared to accept.
RW-CORE-04Foundation
A decision for every significant risk
Decide how each risk above your agreed appetite will be dealt with, whether by reducing, avoiding, transferring or accepting it, have senior leadership approve any decision to accept one, and follow each agreed action through until it is done.
RW-CORE-05Foundation
The register kept up to date
Review the risk register regularly, and whenever something significant changes, so that every risk, its assessment and the decision about it stay current.
All five are Foundation requirements, and they sit in the Blueprint’s core because everything else depends on them.
Two more terms matter here. Risk appetite is the broad statement of how much, and what kinds of, risk the organisation is prepared to accept in pursuit of its goals. Risk tolerance puts that into practice as specific limits, such as the highest rating or the largest cost the organisation will bear for a single risk once it has been dealt with. Leadership agrees the appetite; the tolerance lets everyone check a risk against it. Together they describe a register in a working state: the main risks are written down, each with someone responsible for it; they are judged the same way; leadership has said how much risk it will live with; each risk above that line has a decision; and the whole register is kept up to date.
Why they matter
Most organisations still don’t assess their risks
The UK government’s Cyber Security Breaches Survey, published on 30 April 2026, found that around a third of businesses had carried out a risk assessment covering cyber security in the previous year. Without one, decisions about security are made one at a time, as problems come up, rather than against a picture of what matters most. The same survey found that fewer than a third of businesses had a board member responsible for cyber security, so in many organisations nobody at the top owns the answer.
A register is how risk reaches the people who decide
National guidance treats the register as the link between security work and the rest of the organisation. The US National Institute of Standards and Technology (NIST), in its series on integrating cybersecurity with enterprise risk management, uses the cybersecurity risk register as the organising record through which organisations identify, assess, communicate and manage their cyber risks in the context of their mission and objectives. Later reports in the series describe how priorities and risk responses are added to it, and how registers from different parts of an organisation are combined for leadership.
The UK’s National Cyber Security Centre (NCSC) makes a related point about communication. Its risk management guidance says that analysis is of little use if decision makers can’t interpret it. And in its writing on risk appetite, it describes appetites as the way to set out an organisation’s risk “red lines”, which must be communicated to the people who work with them in a way that is accessible and understood. A register written in plain sentences, scored one way and compared with an agreed appetite does exactly that.
Compliance isn’t the same as managing risk
The NCSC also warns about risk management done only to satisfy an auditor or a customer. It says that compliance and security are not the same thing, and that a risk can seem managed when it has only been processed. A register that is only opened before an audit is a clear sign of that problem. The international guidance on information security risk management, ISO/IEC 27005:2022, describes the work as a continuing cycle of assessment, treatment, communication, monitoring and review, not a one-off exercise, and says it applies to organisations of every type and size.
How to meet them
How far an organisation takes these requirements depends on its size and how much it has at stake, but every organisation can meet all five.
A small organisation
Typical set-up
Around twenty people, with an office manager who looks after IT alongside other work, and an IT provider for anything technical.
What it could look like
- Spend an hour with the directors listing the ten to fifteen most likely ways the business could be harmed, such as losing the email account, a ransomware attack, a laptop left on a train or a supplier failing. Write each as a sentence and give it an owner.
- Agree a simple scale for likelihood and impact, with a line for each level saying what it means for you, such as “a day without email” or “a cost over £10,000”, and score every risk with it.
- Have the directors agree, in a sentence or two, how much risk they’re prepared to live with, and which ratings that means are acceptable and which are not.
- For each risk above that line, record what you’ll do and by when. If you decide to live with one, have a director approve it.
- Look at the register together every three to six months, and after anything significant: an incident, a new system or a new supplier.
A larger organisation
Typical set-up
Several hundred people, with a security lead, IT and data teams, and a leadership team that reports to a governing body.
What it could look like
- Identify risks from several directions: the services that matter most, the threats to them, incidents and near misses, audits, supplier reviews and the news. Record each with an owner in the business, not only in IT.
- Write a risk method with defined levels for likelihood and for each kind of impact, such as financial, operational, legal and reputational, and a matrix that turns them into ratings. Apply it to every risk.
- Have leadership approve a written risk appetite, turned into tolerance limits that can be checked against a rating or a cost, and say who may accept a risk at each level.
- Record a treatment decision for every risk above the appetite, with costed actions, owners and dates, and leadership’s approval for any risk it chooses to keep.
- Set review periods by rating, so the most serious risks are looked at most often, and report the register’s state to leadership on a regular cycle.
How to show it’s done
Leadership, auditors and customers will want to see more than a spreadsheet. Useful evidence includes:
- The register itself, with each risk described in a sentence, its owner, its scores before and after controls, its decision and its next review date.
- The written method for judging likelihood and impact, with what each level means.
- The risk appetite, approved by leadership, with the date it was agreed.
- For each risk accepted above the appetite, who approved it, why, and until when.
- The actions agreed for each risk, with their owners, due dates and progress.
- A history showing when each risk was last reviewed, and what changed.
Where it usually falls short
Risks that are really labels
Owners that are teams
Scores nobody can explain
Only updated before an audit
Acceptances that never end
No record of what changed
How RiskWitness helps
RiskWitness is a hosted information security risk register, built to meet these five requirements. It ships with the Blueprint built in, with starter controls already mapped to its requirements. Risks, acceptance, controls, actions and reports are on every plan, and all five requirements here are in the Foundation tier, which every plan includes.
Start with the risks you have
Add risks from a library of common information security risks, or import the spreadsheet you already keep. Each risk is described in three parts, its cause, what could happen and what that could lead to, and RiskWitness puts them together as a sentence: “Because of…, there is a risk that…, which could lead to…”. Each has a named owner.Set your method once
Describe what each level of likelihood and impact means for you, add impact types such as financial or operational, and choose how many ratings to use and which square of the five by five matrix has which rating. Every risk is then scored the same way. If you change the method later, earlier ratings stay as they were when they were made.Score before and after controls
Score each risk’s likelihood and impact before and after its controls (often called inherent and residual risk), with a cost range if you want one, and link the controls that reduce it. Each control has an owner, its effectiveness for that risk, and its tests and their results.Turn your appetite into limits
Record your tolerance as the highest rating you’re prepared to accept, the most a single risk may cost, or both. RiskWitness compares each open risk with it, and each risk’s page shows whether it’s within tolerance and why.Record each decision
Choose to reduce, transfer, avoid or accept each risk. An acceptance is recorded with its reason and an expiry date. Outside tolerance, a named approver signs it off and confirms it’s really them.Follow the actions through
Turn each decision into actions with owners and due dates, on a board or a list. Overdue actions show on the dashboard.Keep it current
Set how often risks of each rating are reviewed, so the most serious come round most often. RiskWitness suggests each risk’s next review date from its rating and flags any that are overdue. PDF reports and slide decks show leadership where the register stands.
Every step is kept in a history that shows who did what, when, and the old and new values, and nobody can edit or delete it. When leadership, an auditor, a customer or a regulator asks how a risk was assessed, who decided to keep it and when it was last looked at, the answer is already written down.
Sources
- Cyber security breaches survey 2025/2026, Department for Science, Innovation and Technology and Home Office (UK), 30 April 2026
- The fundamentals and basics of cyber risk, NCSC (UK), 23 June 2023
- Are you hungry? A two-part blog about risk appetites, NCSC (UK)
- Risk appetite and risk tolerance, NIST Computer Security Resource Center glossary
- Integrating Cybersecurity and Enterprise Risk Management (ERM): NISTIR 8286, NIST, 13 October 2020
- Prioritizing Cybersecurity Risk for Enterprise Risk Management: NIST IR 8286B, NIST
- Staging Cybersecurity Risks for Enterprise Risk Management and Governance Oversight: NIST IR 8286C, NIST
- ISO/IEC 27005:2022, Guidance on managing information security risks, ISO
