Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Risk appetite is the amount of risk a board is willing to accept in pursuit of its objectives; risk tolerance is the measurable limit around a specific risk before action is required.

What Are Risk Appetite and Risk Tolerance?
Risk appetite is a board-level statement of how much risk an organisation is prepared to accept while pursuing its objectives. Risk tolerance is the measurable boundary around a particular risk: the point at which a situation stops being acceptable and someone has to act. Appetite sets direction; tolerance sets thresholds.
The distinction sounds academic until an incident forces it. If nobody has agreed in advance how long an outage is tolerable or how many unpatched critical vulnerabilities is too many, every decision becomes a negotiation at the worst possible moment.
Appetite statements are qualitative and strategic, and they vary by risk category. A single sentence saying the organisation has a “low appetite for cyber risk” is useless, because it is true of everyone and guides nothing. Useful statements name the trade-off:
We have no appetite for unauthorised disclosure of client personal data and will delay product launches to prevent it. We have a moderate appetite for availability risk in internal tooling, where we will accept short outages in exchange for faster delivery.
Written that way, an appetite statement answers a real question: when speed and safety conflict in this area, which wins. It also gives the security function authority to say no without relitigating the principle each time.
Tolerance converts appetite into thresholds that can be measured and breached. Each one needs a metric, a limit, and a defined response:
| Risk area | Tolerance threshold | Action on breach |
|---|---|---|
| Internet-facing critical vulnerabilities | None open beyond 14 days | Emergency change, CISO notified, reported to the risk committee |
| Privileged accounts without MFA | Zero | Account disabled within 24 hours |
| Recovery of a tier 1 service | Restored within four hours | Continuity plan invoked, executive escalation |
| Supplier assessments overdue | Fewer than 5% of tier 1 suppliers | Procurement hold on new contracts |
Thresholds like these become key risk indicators, reported monthly. The reporting is the point: a tolerance nobody measures is an aspiration, and a tolerance breached every month without consequence has quietly become the new appetite.
Appetite is what you evaluate against. During a risk assessment, each rated risk is compared with the agreed appetite to decide whether it needs treatment or can be accepted. The risk left after controls are applied is residual risk, and the test for accepting it is whether it falls inside appetite. ISO 31000 and ISO/IEC 27005 both expect these criteria to be set before assessment begins, precisely so that the answer is not reverse-engineered from what the organisation can afford.
Appetite should also be asymmetric across the business. The appetite applied to a customer payment platform has no business governing an internal wiki, and treating them identically either paralyses the wiki or under-protects the platform.
British financial services firms meet a related but distinct concept. Under the FCA and PRA operational resilience rules introduced in Policy Statement 21/3, firms must identify important business services and set an impact tolerance for each: the maximum tolerable disruption, expressed in time, beyond which harm to consumers or market integrity becomes intolerable. Firms were required to be able to remain within those tolerances by 31 March 2025. Impact tolerance is a hard outer limit assuming disruption occurs, which is a stricter idea than a risk tolerance you hope not to reach.
Similar thinking appears in DORA for EU financial entities, which requires risk tolerance levels for ICT disruption to be set in the digital operational resilience strategy. Outside regulated sectors, UK GDPR accountability has the same practical effect: the ICO expects security measures appropriate to the risk, which presupposes that somebody decided what level of risk was acceptable.
Appetite drifts. Acquisitions, new products, and a change of chief executive all move it, and statements written three years ago rarely match current behaviour. Review them annually with the board, test them against a real decision taken in the past year, and check whether the organisation actually behaved as the statement claims. Where it did not, either the statement or the behaviour needs to change, and saying so is the most useful thing a risk function does.
If you need defensible thresholds grounded in technical evidence, our cyber risk analysis services turn assessment findings into measurable tolerance levels.
The board or an equivalent governing body owns it, usually on a proposal from executive management and the risk function. Security teams draft and advise but should not set appetite alone, because the statement commits the organisation to accepting consequences. Board ownership is also what gives the statement weight when a project team wants an exception.
Risk tolerance is the limit you aim to stay within under normal operation, such as no critical internet-facing vulnerability open beyond 14 days. Impact tolerance, used in UK financial services operational resilience rules, assumes disruption has already happened and sets the maximum tolerable duration or extent of that disruption. One manages likelihood, the other plans for the worst case.
Enough to cover the categories where trade-offs genuinely differ, typically between five and ten for cyber and technology risk. Fewer than that and the statements become too general to guide decisions; many more and nobody reads them. Each should name the risk area, the level of appetite, and what the organisation will give up to stay inside it.
The defined response triggers automatically: escalation to a named owner, a time-bound remediation plan, and reporting to the risk committee. Breaches should also be reviewed in aggregate. Persistent breaches usually mean either the threshold was set unrealistically or the organisation has accepted a higher level of risk in practice, and the register should be corrected to say so.
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.