At a board meeting the IT director asks whether the company may keep running, for six months, a sales system for which the vendor has stopped issuing patches. The CEO replies that the company has a low risk appetite. The answer sounds serious but settles nothing: the IT director still does not know whether he has approval, who will sign it and how he will tell that the situation has slipped out of control.
Risk appetite is the board’s decision on how much risk the company accepts in order to achieve its objectives, in cybersecurity too. It works only when it flows downwards: into tolerances for specific systems, into thresholds in the risk matrix and into indicators that show when a limit has been crossed. Without that translation, every decision to accept a risk ends up back at the board meeting anyway.
What is risk appetite?
Risk appetite is the type and amount of risk an organisation is willing to take in pursuit of its objectives. That is the definition given in NIST IR 8286r1 “Integrating Cybersecurity and Enterprise Risk Management (ERM)” of December 2025, which cites the 2017 COSO enterprise risk management framework. The document adds that appetite is established by the most senior-level leadership and serves as the guidepost for decisions on strategy and the choice of objectives.
In the DORA Regulation the concept appears in Article 6(8)(b): the ICT risk tolerance level is set in accordance with the risk appetite of the financial entity. Language versions differ in wording, and the Polish text, for instance, renders “risk appetite” as the entity’s “readiness to take risk” in the same provision. It is worth knowing both forms, because supervisory documents and corporate policies use them side by side.
Appetite is not only about threats. NIST IR 8286r1 notes that enterprise risk management balances security objectives with limited resources, and it describes responses for positive risks, that is opportunities, as well. A company entering a new market or launching a new cloud service knowingly accepts more risk because it expects a benefit. Appetite says where that willingness ends.
How does risk appetite differ from risk tolerance?
Appetite sets the direction for the whole organisation, while tolerance draws a concrete limit for a system, process or objective. NIST IR 8286r1 defines risk tolerance as the organisation’s readiness to bear the risk that remains after a response, and notes that legal requirements influence that readiness. NIST takes this definition from ISO Guide 73:2009, the risk management vocabulary.
The document gives an example that shows the scale of both concepts well. An appetite statement might read: “Email service shall be available during the large majority of a 24-hour period.” The associated tolerance statement is narrower: “Email services shall not be interrupted for more than five minutes during core hours.” The first sentence states the board’s intent; the second can be measured.
Tolerance is often defined at the enterprise level, but NIST quotes guidance from the US Office of Management and Budget (OMB) that allows it to be set at the programme, objective or component level, and its application reaches down to the system level. It is also worth knowing that the older NIST SP 800-39 uses the term “risk tolerance” for both concepts, so in documents based on it “tolerance” may mean appetite.
Who sets risk appetite and why should it be the board?
The board sets risk appetite, because only the board can decide how much risk the company accepts in exchange for achieving its objectives. NIST IR 8286r1 assigns the setting of appetite to senior leadership, and NIST CSF 2.0 of 26 February 2024 requires in subcategory GV.RM-02 that risk appetite and risk tolerance statements are established, communicated and maintained.
Regulations point to the same level. As of 30 September 2026. Article 20(1) of the NIS2 Directive requires Member States to ensure that the management bodies of essential and important entities approve cybersecurity risk-management measures, oversee their implementation and can be held liable for infringements; in each country the obligation applies through national transposition law. In Poland, that law is the Act on the National Cybersecurity System as amended on 23 January 2026 (Journal of Laws 2026, item 252, in Polish), in force since 3 April 2026: the head of an essential or important entity is responsible for the performance of cybersecurity obligations (Article 8c(1)) and takes decisions on the information security management system (Article 8d(1)). Essential and important entities that existed when the amendment entered into force have 12 months to meet the obligations of Chapter 3 of the Act, which contains both provisions (Article 33(1) of the amending act). In the financial sector, Article 5(2)(d) of the DORA Regulation makes the management body bear the overall responsibility for determining the appropriate ICT risk tolerance level.
The security team plays an advisory role in this process, not a decision-making one. The CISO prepares the risk picture, proposes limits and shows the consequences of different options. The board signs the statement, because the board is accountable for the objectives the appetite is meant to protect.
How do you write a risk appetite statement?
A risk appetite statement is a short document that says, for each risk category, what the company wants, what it does not accept and how to check it. NIST IR 8286r1 names appetite and tolerance statements as the usual means by which leadership communicates this guidance. A well-written statement starts from business objectives, not from a list of threats.
Each entry should have four elements: the risk category, an appetite sentence, tolerance limits and an indicator. An example for data confidentiality: the company does not accept the risk of processing customer data outside controlled systems, the tolerance is no shared accounts in systems holding customer data, and the indicator is the number of such accounts found in the quarterly access review.
NIST gives a similar example from public administration. For the objective of protecting user data, the appetite statement reads “ensure that only authorized parties have access to federal systems”, and the tolerance statement speaks of unique user accounts and auditing both positive and negative logon events. Such a pair shows at once what an auditor should check.
Key takeaways:
- The board sets risk appetite, and tolerance is translated into limits for specific systems and processes.
- Each entry in the statement needs a category, an appetite sentence, a tolerance limit and an indicator.
- A statement saying “we have a low risk appetite” without tolerances and indicators settles nothing.
How do you translate risk appetite into thresholds in a risk matrix?
Appetite enters the risk matrix as the boundary between the cells a risk owner may accept alone and the cells that need a decision higher up. How to build the scales and combine likelihood with impact is covered in the article on how to build a risk matrix. Appetite answers a different question: which cells of the matrix fall within tolerance and which do not.
NIST IR 8286r1 links tolerance directly to acceptance. In its table of response types, acceptance applies to risks within tolerance levels and needs no further action except monitoring. A risk above tolerance must receive a different response or a decision by someone entitled to accept it despite the excess.
In practice each colour of the matrix gets a decision rule. A green cell is accepted by the risk owner and noted in the register. A yellow cell is accepted by the director responsible for the area, with a date for reassessment. A red cell needs a board decision and a reduction plan. The cell boundaries are set once, when the statement is approved, not at every assessment.
How do you measure whether the company stays within its risk appetite?
Appetite is measured with key risk indicators (KRIs) whose thresholds derive from the tolerances. NIST states that KRI measurements show where risk tolerances have been exceeded or confirm that the organisation is operating within the defined appetite. Article 6(8)(c) of DORA requires financial entities to set information security objectives, including key performance indicators and key risk metrics.
NIST stresses the value of leading indicators and notes that a logon audit shows a breach only after the fact, whereas an indicator such as increasing external reconnaissance scanning may signal an impending attack. NIST IR 8286r1 also gives examples of positive KRIs, such as the number of critical business systems with strong authentication, and negative ones, such as the number of severe customer disruptions in the last 90 days.
Each indicator needs a threshold derived from tolerance and an owner who reacts when it is crossed. NIST describes monitoring that detects risks approaching the tolerance level and triggers their review. The board does not need to see every indicator each month; a report on breaches and trends is enough.
What should you do when a risk exceeds tolerance?
A risk above tolerance must be brought down to an acceptable level or explicitly accepted at a higher level, with a deadline and a justification. NIST IR 8286r1 lists four responses to negative risk: accept, transfer, mitigate and avoid. Transfer, for example through insurance, applies according to the document to risks outside tolerance, but some consequences, such as the loss of customer trust, cannot be transferred.
Exceeding tolerance is also a signal about the statement itself. If the same indicator crosses its threshold quarter after quarter and the board accepts the exception every time, the statement no longer describes reality. Either the tolerance has to change, or the resources needed to meet it have to be allocated.
NIST describes this flow as a loop: the results of risk assessments reach the executives, and changes to risk appetite go back down to managers and restart the cycle. An exception accepted without an expiry date breaks this loop, because nobody ever returns to it.
How often should you review risk appetite?
Risk appetite is reviewed at every strategy review and after every event that changes the company’s risk picture. NIST CSF 2.0 speaks in subcategory GV.RM-02 of maintaining the statements, and in the GV.OV category of reviewing and adjusting the risk management strategy based on its results.
As of 30 September 2026. The financial sector has a deadline written into law: Article 6(5) of DORA requires the ICT risk management framework to be documented and reviewed at least once a year (periodically in the case of microenterprises) and upon major ICT-related incidents. The strategy in which the ICT risk tolerance level is set is part of that framework, so the review covers it too.
Beyond the calendar date, it is worth listing the events that trigger a review on their own: a major incident, the acquisition of another company, entry into a new market, a change of key supplier or new regulatory obligations. The statement then changes together with the company, rather than once a year out of habit.
Which mistakes undermine a risk appetite statement?
A statement is undermined above all by vague wording, missing tolerances and no owner. The sentence “we have a low appetite for cyber risk” does not say whether a system without vendor support may stay in operation. A single sentence for all categories hides the fact that the company treats project risk differently from the risk of losing data.
The second mistake is a statement written by the IT department without the board. Such a document may be technically sound, but it carries no weight, because it does not answer how much risk the company accepts in exchange for its objectives. The third mistake is no link to the budget: a tolerance that cannot be met with the available resources is taken seriously by nobody.
The fourth mistake is a statement without indicators. If no KRI measures the limits in the document, the board learns of a breach only when an incident happens. The fifth is no review date, so a statement written before a new cloud service still describes a company that no longer exists.
How do you implement risk appetite step by step?
Implementation starts with the company’s objectives and ends with indicators and a review rhythm. The table sets out the steps together with the person responsible and the evidence an auditor may ask for.
| Step | What is produced | Who is responsible | Evidence for the auditor | Typical mistake |
|---|---|---|---|---|
| 1. Objectives and risk categories | List of business objectives and the risk categories that threaten them | Board with area directors | Minutes of a workshop with the board | Categories copied from a standard with no link to company objectives |
| 2. Appetite sentences | One appetite sentence per category | Board | Statement approved by resolution or signature | One sentence for the whole company |
| 3. Tolerances | Measurable limits for systems, processes and objectives | Risk owners with the CISO | Tolerance table linked to the statement | Tolerance without a unit or time horizon |
| 4. Matrix thresholds | Decision rules for the cells of the risk matrix | CISO, approved by the board | Risk acceptance policy with decision levels | Colours without an assigned decision |
| 5. KRIs | Indicators with thresholds and owners | CISO and risk owners | KRI report showing breaches | Only lagging indicators, no leading ones |
| 6. Exception workflow | Procedure for accepting risk above tolerance | Board | Exception register with expiry dates | Exceptions with no deadline |
| 7. Review | Schedule and events that trigger a review | Board | Review minutes with decisions | A review reduced to changing the date in the header |
Step three is worth running separately for each category, checking straight away the data source for every limit.
How can nFlo help you set your risk appetite?
nFlo helps build a risk management framework together with the appetite statement as part of the ISO 31000 - Enterprise Risk Management service. The service belongs to the “Governance, risk and compliance” area and covers a risk management maturity assessment, a risk appetite statement, a methodology with criteria and scales, an enterprise risk register and a dashboard with key risk indicators for the board.
We define appetite together with the board in quantitative and qualitative terms, from the maximum acceptable financial impact to the acceptable level of operational, strategic and compliance risk. The ISO 31000 standard in its 2018 edition is a set of guidelines, so the implementation uses it as a framework for risk management rather than as requirements for certification.
If you want to turn a general sentence about risk appetite into a statement with tolerances and indicators, contact us.
What else should you know about risk appetite?
Is risk appetite the same as risk tolerance?
No. According to NIST IR 8286r1, appetite is the type and amount of risk an organisation is willing to take in pursuit of its objectives, while tolerance is the readiness to bear the risk that remains after a response. Senior leadership sets the appetite; tolerance turns it into concrete limits for a system or process.
Who in the company approves risk appetite?
Senior leadership, which in a company means the board. As of 30 September 2026. The NIS2 Directive requires Member States to ensure that management bodies approve cybersecurity risk-management measures; in each country the obligation applies through national transposition law (in Poland, Articles 8c–8d of the National Cybersecurity System Act). The DORA Regulation assigns the management body the determination of the ICT risk tolerance level.
Does risk appetite have to be expressed in money?
It does not have to be, but it helps. A statement can combine qualitative limits, such as no processing of customer data outside controlled systems, with quantitative ones, such as the maximum length of a service outage. Numbers make it easier to check whether the company stays within its limits.
Does ISO 31000 require a risk appetite statement?
ISO 31000:2018 is titled “Risk management — Guidelines” and is a set of guidelines rather than requirements, so it mandates nothing and does not lead to certification. A risk appetite statement nevertheless fits well into a risk management framework built on this standard.
How often should you update risk appetite?
At every strategy review and after events that change the risk picture, for example a major incident or a change in the business model. In the financial sector, DORA requires the ICT risk management framework to be reviewed at least once a year.
