Risk Management

Risk statement

A risk statement is the short, structured wording of a risk, setting out the cause or source, the event that may occur and the consequence for an objective. A good risk statement makes a risk testable, comparable and assignable to an owner, and points to suitable controls. A more detailed, step-by-step elaboration is called a risk scenario.

Source: NIST IR 8286 Rev. 1 (2025); DNB, Good Practices SIRA (2025); Regulation (EU) 2022/2554 (DORA) Article 8

Board members and supervisory directors read risks through their description in the risk register or risk report. A vague description, such as just "cyber" or "reputation", makes it hard to assess likelihood and impact, assign an owner or decide which control helps. For each risk register entry, NIST asks for a brief explanation of the risk scenario, using common phrasing and elements such as threats, assets, methods and impacts (NIST IR 8286 Rev. 1, 2025). That makes descriptions from different units comparable.

A practical structure is: because of [cause or source], [event] may occur, with [consequence] for [objective]. For example: because the payment service provider has no fallback, customers cannot pay for two days, resulting in lost revenue and complaints. The Good Practices SIRA (systematic integrity risk analysis, 2025) of the Dutch Central Bank (DNB), which are indicative, describe as good practice an institution that sets requirements for an integrity scenario: it is concrete and describes a series of observable actions, decisions or events, it is specific to the institution, and it concerns the actual manifestation of the risk rather than process shortcomings. DORA requires financial entities to review their ICT risk scenarios at least yearly (Article 8(2)).

A risk statement can exist at different levels. NIST shows how a broad enterprise-level statement, such as information security, breaks down into intermediate statements and into individual risk register entries. An opportunity can be described in the same way, with a positive consequence for the objective. A risk statement differs from the risk source, which forms only its first part, and from the risk register, which records the owner, assessment and measures alongside the statement.

Through Risk Insight, ONE Risk Advisory uses Enterprise, Process and IT Risk Assessments to identify the risks and opportunities that most affect an organisation's objectives.

Last updated: · Editor: ONE Risk Advisory

Related service Risk Insight

Further reading Risk and opportunity assessment: method, matrix and example

Frequently asked questions

What does a good risk statement look like?

A good risk statement names the cause or source, the event and the consequence for an objective, in one or two sentences. It is concrete and observable, fits the organisation and concerns the risk itself rather than a shortcoming in a process; DNB presents this as good practice for scenarios in the SIRA (Good Practices SIRA, 2025). A single word such as "cyber risk" names a category; a risk register entry needs more.

What is the difference between a risk statement and a risk scenario?

The risk statement is the short wording of a risk. A risk scenario elaborates it step by step: a series of actions, decisions or events and what happens next. NIST calls the description in the register a brief explanation of the scenario (NIST IR 8286 Rev. 1, 2025). In DNB's Good Practices SIRA, institutions work out scenarios to estimate how a risk could manifest itself and what its impact would be.

← All terms