Risk Appetite and Tolerance

Risk Appetite and Tolerance

This section explains the configuration of Risk Appetite and Risk Tolerance in GRC for Jira.

What are Risk Appetite and Risk Tolerance?

  • Risk Appetite is the amount or type of risk that an organization is willing to accept in pursuit of its objectives.

  • Risk Tolerance defines the acceptable deviation from the Risk Appetite - representing thresholds beyond which risk becomes unacceptable.

Configuring Risk Appetite in Risk Settings

Risk Appetite options and their mapping to Risk Levels were introduced earlier in the Risk Parameters section of this guide.

In GRC for Jira, Risk Appetite plays an important role in the risk response process. Specifically, it determines whether the user conducting the risk assessment is allowed to select the "Accept" response type.

From the Risk Settings page, you can define when the "Accept" option is available based on the relationship between the residual risk and the defined appetite or tolerance:

  • Always – Accept response is always allowed.

  • Within Risk Appetite – Allowed only if residual risk is within appetite.

  • Within Risk Tolerance – Allowed if residual risk is within the defined tolerance (even if outside appetite).

  • Never – Accept response is never allowed.

These options ensure that your risk acceptance policy aligns with your organization’s risk governance practices.

appetite.jpg
Configure Accept risk response availability

Configuring Appetite and Tolerance Levels in Operation

While the global rules for allowing the Accept response are defined in Risk Settings, specific Risk Appetite and Risk Tolerance levels for the assessed risks should be configured at different levels within your operational risk structure: Entity, Risk Statement, or Risk Framework.

appetite-riskstatement.jpg
Example of Risk Appetite and Tolerance configuration on the Risk Statement

Note: The scoring engine follows a strict priority order when determining Risk Appetite and Tolerance levels: Entity → Risk Statement → Risk Framework.
If a configuration is found at the Entity level, it is used directly - higher levels are not checked further. The same logic applies if nothing is set at the Entity level but is found at the Risk Statement level.

Once these levels are identified, the residual risk level is compared against them. Based on the configured rules, the system then determines whether the "Accept" response type is permitted.

appetite-operational-example.jpg
Risk Appetite and Tolerance validation in Risk Assessment flow