Few terms cause more confusion in risk management than appetite, tolerance and capacity. They show up in board papers, audit findings and certification exams, and people often use them interchangeably. They are different, and the difference matters when you have to decide whether a risk is acceptable.
The short version
| Term | Question it answers | Set by | Example |
|---|---|---|---|
| Risk capacity | How much risk could we absorb before failing? | Facts: finances, regulation, reputation | "An outage beyond 5 days would breach our licence conditions." |
| Risk appetite | How much risk are we willing to take to pursue our goals? | The board | "We have a low appetite for risks to customer data." |
| Risk tolerance | How far from the target are we prepared to vary, for a specific measure? | Management, within appetite | "Critical vulnerabilities patched within 14 days; up to 21 days acceptable with sign-off." |
Capacity is the outer wall. Appetite sits well inside it. Tolerance turns appetite into measurable limits for specific risks.
Risk capacity
Capacity is the maximum risk the organisation can bear without threatening its survival or its obligations: capital, liquidity, regulatory limits, contractual commitments, and how much reputational damage it could survive. It is mostly a matter of fact rather than preference. An appetite that exceeds capacity is a governance failure.
Risk appetite
Appetite is a strategic choice: the amount and type of risk the organisation is willing to pursue or retain to achieve its objectives. It differs by category. A fintech might have a high appetite for product innovation risk and a very low appetite for regulatory or customer-data risk.
Good appetite statements are:
- set by the board and reviewed at least yearly;
- specific by category: strategic, financial, operational, technology, cyber, privacy, compliance;
- linked to measures, otherwise nobody can tell whether the organisation is inside them.
Risk tolerance
Tolerance is the acceptable variation around a specific objective or measure. It makes appetite operational. If the appetite for cyber risk is low, tolerances might include:
- multi-factor authentication on 100% of remote access, with no tolerance for exceptions;
- critical patches applied within 14 days, with exceptions up to 21 days approved by the CISO;
- no more than 2% of staff clicking in phishing simulations, with action above 4%.
Tolerances are where key risk indicators come in: a KRI with thresholds tells you when you are approaching or breaching tolerance. See key risk indicators that predict trouble.
How they work together in a decision
Say a business unit wants to launch a feature that stores additional customer data in a new SaaS tool.
- Assess the risk: likelihood and impact of a breach at the vendor.
- Compare the residual risk to tolerance for privacy risk. If it is above tolerance, it is outside appetite.
- Respond: reduce it (encryption, contract terms, less data), transfer part of it (insurance), avoid it (don't launch), or accept it. Acceptance must come from someone with the authority to accept that level of risk.
- Never accept a risk that exceeds capacity.
Writing a usable appetite statement for cyber risk
A one-line statement such as "we have a low appetite for cyber risk" is a start, but it doesn't help anyone decide. Add:
- what you won't accept: for example, unpatched internet-facing critical vulnerabilities, or customer data processed without encryption;
- what you will accept to move fast: for example, early-stage products with reduced controls in isolated environments;
- the measures and tolerances that show where you are;
- escalation: who must approve going outside tolerance, and when the board hears about it.
Exam tip
Certification exams often test the order: capacity bounds appetite, which is expressed through tolerances, monitored with KRIs. When a question asks who sets appetite, the answer is almost always senior management and the board, not the risk practitioner. The practitioner advises and reports.
Learn more
Risk appetite, assessment and response sit at the heart of our free CRISC and CISM tracks, with lessons and practice questions for each domain.
Written and reviewed by the DigiTrust Asia editorial team. How we research, review and correct articles.
General information, not legal advice. Laws and official guidance change; check the current text before acting.