liveBook · Manning

Risk tolerance

As explained in Fundamentals of Cybersecurity

Risk tolerance is the level of risk an organization is willing to accept for specific business areas or activities within its broader risk appetite.

Risk tolerance is the level of risk an organization is willing to accept in a particular business area, process, or activity. It sits within risk appetite: the broader amount of risk the organization is willing to take in pursuit of its goals. A risk acceptable in one activity may be unacceptable in another. section 2.4 section 2.2.2

Downtime depends on the activity

A hospital cannot tolerate system downtime in the same way a sports club can. The consequence of an outage helps determine whether the risk needs action or can be accepted. Accepting downtime for a non-critical service may be reasonable when it falls within defined limits. section 2.2.2 section 2.2.3

Risk Level
Risk Rating
Meaning
1 (Very High)
Unacceptable
Immediate action required. Activity must stop until the risk is reduced or avoided.
2 (High)
Undesirable
Risk above acceptable threshold. Requires treatment with defined controls and timeline.
3 (Medium)
Moderate
Acceptable with formal approval. Requires justification and monitoring.
4 (Low)
Acceptable
Within acceptable limits. No additional controls required; monitor as needed.

The risk-rating table illustrates decision bands: very high risks require immediate action, while medium risks may be accepted with formal approval and monitoring. These bands help turn an assessed risk into a decision; an organization still needs criteria suited to its activities. section 2.2.2

Risk tolerance does not mean eliminating every risk. Once a risk is assessed, the organization can reduce it with controls, avoid the activity, transfer some exposure, or formally accept it within defined limits. Treatment should bring risk to a tolerable level without costing more—in money or operational impact—than the benefit warrants. Any risk remaining after treatment must be evaluated for acceptance or further action. section 2.2.3 section 2.3

How Fundamentals of Cybersecurity covers it

How deep it goes
Defines area-specific acceptable risk and illustrates decision bands and treatment choices without prescribing universal thresholds.
Examples
Contrasts hospital and sports-club downtime, illustrates four risk-rating bands, and gives non-critical service downtime as an accepted risk.
What it assumes
Builds on risk assessment and introduces risk appetite before distinguishing area-specific risk tolerance.
What you can do after
Evaluate/understand it to judge whether a risk can be accepted, monitored, or needs treatment against an activity’s limits.
How it connects
Links risk appetite and risk assessment to risk treatment, security controls, and residual risk.

Also explained in

Compare how 4 books explain risk tolerance →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Fundamentals of Cybersecurity. The section links point to the parts of the book it draws on.