Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Residual risk is what remains after your controls have done their work. Every organisation carries it; the question is whether the right person has seen it and accepted it.

What Is Residual Risk?
Residual risk is the exposure that remains once your controls are in place and working. It is not a failure—reducing risk to zero is neither possible nor affordable—but it is something that has to be measured, named, and formally accepted by someone with the authority to carry it. Risk that nobody has accepted has not been managed; it has been ignored.
Three figures appear in most risk registers, and confusing them makes the register meaningless.
The gap between current and residual is the value of the work still outstanding. Registers that record only an inherent and a residual figure hide that gap, and they tend to flatter the organisation, because residual is quietly calculated as though every planned control already worked.
A risk assessment scores likelihood and impact for each identified risk, then considers control effectiveness. The arithmetic can be qualitative (a five-by-five matrix) or quantitative (expected annual loss, or a FAIR-style distribution). What matters is that the reduction claimed for each control is justified rather than assumed.
Two habits keep the numbers honest. First, test the controls: a backup regime counts towards risk reduction only if a restore has been proven, and multi-factor authentication only reduces credential risk for the systems it actually covers. Second, distinguish reduction from transfer. Cyber insurance moves part of the financial consequence; it does not reduce the probability of compromise, restore your data, or discharge your duties to the ICO.
ISO/IEC 27001:2022 is explicit. Clause 6.1.3 requires the organisation to obtain risk owners’ approval of the information security risk treatment plan and acceptance of the residual risks. That is a named individual who owns the business outcome, not the security team, and not a committee that met once.
Acceptance works when the record answers five questions: what the risk is in business terms, what the residual rating is, which controls are assumed to be operating, why further treatment is not proportionate, and when the acceptance expires. An expiry date is the single most useful field. Risk acceptances written without one quietly become permanent, long after the compensating control was decommissioned.
Acceptance should also sit inside a stated risk appetite. Without a board-level statement of what the organisation is prepared to tolerate, every acceptance is an individual judgement and the register drifts.
Residual risk is usually concrete rather than abstract. A legacy application that cannot support modern authentication, kept alive behind network segmentation and heavier monitoring. An unsupported operating system on a medical device, isolated on its own VLAN because the manufacturer’s approval would be invalidated by patching. A single supplier with no viable alternative. A critical vulnerability where the vendor patch breaks a production integration, so a virtual patch at the web application firewall holds the line for ninety days.
Each of those is a defensible decision when written down with an owner, a compensating control, and a review date. Each becomes a finding when it is not.
Keeping the register current is dull, unglamorous work, and it is what distinguishes a managed security posture from an optimistic one. Our cyber risk analysis services test the controls behind the numbers, so the residual figures you report are ones you can defend.
Inherent risk is the exposure that would exist with no controls at all, which makes it a hypothetical reference point. Residual risk is what remains after the agreed controls are implemented and working. The difference between the two represents the value your control environment delivers, which is why both figures appear in a well-maintained risk register.
The risk owner—the person accountable for the business activity affected, such as a service owner, director, or head of department. ISO 27001 clause 6.1.3 requires their explicit acceptance. The security team advises and quantifies but should not accept risk on the organisation’s behalf, because they do not own the outcome or the budget to treat it differently.
It transfers part of the financial consequence rather than reducing the likelihood or the operational impact. Insurance will not restore your data, keep your service running, or discharge your obligations to the ICO and your customers. Treat it as one treatment option alongside mitigation and avoidance, and read the exclusions, which often require the controls you are relying on it to replace.
Give every acceptance an expiry date, typically six or twelve months depending on severity, and review it at that point rather than when someone remembers. Review earlier if the threat changes, a compensating control is removed, the system’s scope expands, or an incident shows the original assumptions were wrong. Acceptances without expiry dates become invisible permanent exposure.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.