How to Set Risk Acceptance Criteria and Risk Appetite

A practical guide to defining risk acceptance criteria in a single setup together with risk appetite, likelihood and impact scales, matrix thresholds and an approval authority matrix.
Technical summary
Technology
ISO/IEC 27001:2022, ISO/IEC 27005:2022, ISO 31000:2018
Topic
Risk acceptance criteria, risk appetite and approval authority
Level
Intermediate
Prerequisites
  • The basic steps of the risk assessment methodology
  • Knowledge of the organization’s business processes and RTO targets
In this article7 sections

Can a risk scoring 12 in the risk matrix be accepted? The answer isn’t in the matrix but in the risk acceptance criteria the organization wrote in advance. Without criteria, the decision belongs to whoever is loudest in the meeting that day. ISO/IEC 27001:2022 clause 6.1.2 a) explicitly requires risk acceptance criteria and criteria for performing risk assessments to be established; clause 6.1.3 f) requires residual risks to be accepted by risk owners. The steps below are for ISMS owners who want to bring risk appetite, scale definitions, matrix thresholds and approval authority together into a single consistent setup.

Risk appetite, tolerance and acceptance criteria

These three concepts are constantly confused. Yet they work at different levels:

Concept Question Owner
Risk appetite What type and how much risk are we prepared to take on for our objectives? Top management / board
Risk tolerance What deviation is acceptable for a specific objective or area? Top management, business units
Risk acceptance criterion Under which conditions, and by whom, can this risk score be accepted? ISMS management, risk owners

Risk appetite starts with a qualitative sentence, but it’s useless until made measurable. The sentence “We have a low risk appetite for the confidentiality of customer data” doesn’t steer any decision on its own. This rule should be added next to it: “No risk affecting the confidentiality of customer data with an impact of 4 or above is accepted without a treatment plan.” The appetite statement thus becomes an acceptance criterion. Defining different appetites by topic is normal. A manufacturing company may have a high appetite for a short office IT outage and a low appetite for a production line stoppage. A single appetite sentence doesn’t cover everything.

Defining likelihood and impact scales

Applying the criteria consistently depends on everyone reading the scale the same way. Labels such as “high” and “medium” aren’t enough on their own; every level must have a concrete definition and an observable indicator. A problem you may come across is the finance manager reading as “1” a likelihood the system administrator calls “3”. Same risk, two scores.

Likelihood scale

Level Definition Indicator
1 – Very low Not expected except in exceptional circumstances No known example in the sector
2 – Low Could happen once every few years Examples in the sector, none in the organization
3 – Medium Could happen about once a year Has happened in the organization in the past
4 – High Could happen several times a year Happened or an attempt was detected in the last 12 months
5 – Very high Continuous, or once a month or more often Observed regularly

Impact scale

Don’t define impact on a single dimension. The example below has four dimensions; a risk takes the value of the dimension where it scores highest. The values are examples; the organization fills in financial thresholds according to its own scale.

Level Operational Legal / contractual Customer / reputation
1 An hour-long outage in a non-critical service No impact Stays inside the organization
2 Outage in a critical service below the RTO Internal policy violation A single customer complaint
3 RTO exceeded for a critical service Warning of contract breach Information requests from more than one customer
4 Loss of a production shift A breach requiring notification under KVKK Customer audit or suspension of orders
5 Production stoppage lasting days Administrative fine, lawsuit Loss of customers, public exposure

Tying the operational dimension to the RTO values in the business impact analysis stops the two pieces of work from contradicting each other. Writing an 8-hour RTO for the ERP in the business impact analysis and counting an 8-hour ERP outage as “2” on the risk scale is one of the inconsistencies auditors catch first. If you’re also adding a financial dimension to the table, get the thresholds from the finance unit; made-up amounts become a subject of debate the following year.

Setting matrix thresholds

In a 5×5 matrix, the likelihood × impact product can take 14 different values between 1 and 25 (1, 2, 3, 4, 5, 6, 8, 9, 10, 12, 15, 16, 20, 25). Thresholds are built on these values. An example setup:

  • Low (1–4): Routine monitoring is enough; the risk owner can accept.
  • Medium (5–9): A treatment option is assessed; justified acceptance is possible.
  • High (10–16): A treatment plan is mandatory; acceptance only with top management approval and a time limit.
  • Critical (20–25): Not accepted; urgent treatment or avoiding the activity is required.

Pure multiplication has a known weakness: it understates low-likelihood but devastating risks. A scenario with likelihood 1 and impact 5 appears “medium” with a score of 5. To balance this, adding an impact-based rule to the matrix is common practice: “Every risk with an impact of 5 is assessed at least at High level, regardless of its score.” This rule must be consistent with the low-appetite areas in the risk appetite statement. Multiplication alone doesn’t decide.

Risk acceptance authority matrix

The acceptance criterion must answer “who can accept?” as much as “which risk can be accepted?”. Without an authority matrix, the typical picture in the field is this: the IT team accepts a high risk on its own, because the treatment action would increase its own workload. That’s a conflict of interest.

Level Acceptance authority Maximum acceptance period Review
Low Risk owner Until the next annual assessment Yearly
Intermediate Risk owner + ISMS manager 12 months Yearly
High Top management (general manager or a person they authorize) 6 months Quarterly
Critical Not accepted; board decision in exceptional cases Temporary only, shortest possible period Monthly

The periods are examples; what matters is that every acceptance carries an end date. Open-ended acceptance means forgetting the risk. A risk whose acceptance period has expired must automatically fall onto the reassessment list; tie this to the risk register itself, not to a calendar reminder. This structure works on the same logic as policy exception management; combining the two into a single approval flow reduces administrative burden.

Residual risk acceptance record

Under clause 6.1.3 f), acceptance of residual risk is recorded. An email saying “Fine, I accept” is weak evidence on its own. The record should contain at least these fields:

Risk No            : R-2026-014
Risk description   : Measuring device PCs running an old OS version
                     on the production VLAN; the manufacturer doesn't support upgrading
Risk owner         : Quality Manager
Initial risk       : L 4 x I 4 = 16 (High)
Treatment applied  : Separate VLAN, access permitted only to the MES server,
                     USB ports disabled, network monitoring rule added
Residual risk      : L 2 x I 4 = 8 (Medium)
Acceptance reason  : Device replacement planned for the next investment period
Accepted by / date : General Manager / 2026-10-15
Acceptance expiry  : 2027-04-15
Reassessment trigger: change to the segmentation rule,
                     security incident involving the device

In this example the residual risk is “medium”, and under the authority matrix approval by the risk owner and the ISMS manager could have been enough. But because the initial risk was high, approval was obtained from top management. Write this rule (“top management approval for acceptances where the initial risk is high”) explicitly into the methodology; then there’s no debate at the moment of decision. Planning the treatment actions that lead to the residual risk is covered in the risk treatment plan guide.

Reviewing the criteria

Acceptance criteria aren’t a document written once and shelved. These situations are review triggers:

  • A new legal obligation or customer requirement (for example a customer asking for a TISAX label)
  • A change in the business model or scope: a new location, a new product, a cloud migration
  • An accepted risk materializing; a sign that the scales or thresholds don’t reflect reality
  • All risks in the register clustering at the same level; it means the scale doesn’t discriminate

The last item comes up in the field more often than you’d think. If the risks in the register pile up between “9” and “12”, the scale isn’t producing decisions. Recalibrate it.

The natural place for the annual review is the management review meeting: risk assessment results and the status of the risk treatment plan are already management review inputs under ISO/IEC 27001 clause 9.3. Defining key risk indicators that show threshold breaches early makes the criteria work continuously, not once a year.

Checklist

  • The risk appetite statement has been approved by top management and tied to at least one measurable rule
  • There’s a concrete definition for every level of the likelihood and impact scales
  • The impact scale is consistent with RTOs and legal obligations
  • Matrix thresholds and the impact-based exception rule are written down
  • The authority matrix states the acceptance authority and maximum period for each level
  • Every residual risk acceptance has a dated, signed record with an end date

Designing acceptance criteria for the organization and applying them to the existing risk register is part of our information security risk assessment work. For the text of the requirement itself, refer to the ISO/IEC 27001 standard page.

Frequently asked questions

Are risk acceptance criteria and risk appetite the same thing?

No. Risk appetite is a high-level statement of the type and amount of risk the organization is prepared to take on for its objectives. A risk acceptance criterion turns that statement into an applicable rule: which risk score can be accepted, under which conditions and with whose approval.

Can a critical-level risk never be accepted?

The methodology can state that critical risks won’t be accepted, but in practice there are temporary situations where treatment isn’t possible. In such a case, acceptance is recorded at the highest authority level, with a short time limit and together with compensating measures.

Is email approval enough for residual risk acceptance?

Email can be used as evidence, but it’s weak if it doesn’t contain the risk number, residual score, justification and end date. Creating an acceptance record that carries these fields and linking the approval to it is the sounder method.

How often should risk acceptance criteria be updated?

They should be assessed at least once a year in management review; interim reviews should also be held on triggers such as a scope change, a new legal obligation or an accepted risk materializing.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Compliance

We work with you on compliance with ISO 27001, IATF 16949, TISAX and similar standards, covering risk assessment, control design, documentation and audit preparation.

Knowledge Center

Other articles