Timedora

Risk Treatment and Monitoring

A practical guide to choosing risk treatments, assigning responsibility, and checking whether responses remain effective.

Choosing a

Choosing a

Choose a treatment by weighing the risk’s likelihood and impact against the organization’s objectives and tolerance. Also consider each option’s costs, effort, benefits, and possible side effects. The best choice is not necessarily the option that reduces exposure the most: it must also be appropriate to the organization’s goals and feasible to carry out. Options can be combined.

  • Avoid: Stop, do not start, or change the activity that creates the risk. For example, an organization might discontinue a service that cannot be secured to an acceptable level.

  • Reduce: Change the likelihood or consequences using controls or other actions. Preventing unauthorized access, testing backups, and preparing a recovery plan are examples.

  • Share or transfer: Distribute some exposure through an arrangement such as insurance or a contract. This may shift financial consequences, but it does not necessarily eliminate the underlying risk or the organization’s responsibilities.

  • Retain (accept): Make an informed decision to live with the risk, for example when it falls within approved tolerance or further treatment is not justified. Acceptance should be authorized at the appropriate level and documented; it is not simply overlooking the risk.

Assessing What Remains

Assessing What Remains

Treatment does not guarantee that the original risk disappears. It may also introduce new risks. The exposure left after treatment is called .

After taking action, reassess the remaining exposure and compare it with the organization’s acceptance criteria. If it meets those criteria, the organization can proceed according to its authorized decision. If it remains unacceptable, select further treatment or escalate the decision to an authorized . In other words, choosing a treatment is not the end of the decision: the result must be checked before deciding whether the risk can be accepted.

Planning Actions and Assigning Ownership

Planning Actions and Assigning Ownership

Turn a treatment choice into a plan that can be carried out and reviewed. For each action, record the risk it addresses and why the treatment was chosen; the specific work, required resources, and dependencies; and who is accountable and who will do the work. Include milestones and due dates, evidence of completion, expected results, measures of effectiveness, reporting arrangements, and how will be assessed and approved.

Integrate actions into ordinary business, project, or operational plans where possible. Track progress, address delays, and update the plan if assumptions or circumstances change. Keep implementation and effectiveness distinct: evidence that a task was completed does not by itself show that the risk was reduced.

A is accountable for understanding the risk, deciding or recommending how it should be handled, and ensuring the response is monitored. An implements or operates a particular treatment. These roles may belong to different people. For a critical service outage, for example, a business unit leader may own the overall risk while an IT team operates backups and a supplier provides recovery capacity. The coordinates the response and considers whether remaining exposure needs escalation; the other owners provide evidence about their assigned work and controls. If acceptance is beyond the ’s delegated authority or tolerance, a senior leader or other designated authority must approve it.

Monitoring and Adapting the Response

Monitoring and Adapting the Response

Monitoring checks whether the risk, its context, and its controls have changed—and whether the treatment is still appropriate and effective. Set the method and frequency according to the risk’s importance and how quickly it may change. Methods can include scheduled reviews, control tests, operational reports, incident analysis, audits, and automated alerts.

Review four areas:

  1. Risk conditions: Have the threat, vulnerability, exposure, likelihood, impact, or business context changed? New technology, suppliers, regulations, processes, or incidents may affect the assessment.

  2. Control operation: Are controls in place and being used as intended? Check for exceptions, failures, or overdue actions.

  3. Indicators: Track measures against defined thresholds, with a specified review or action when a threshold is reached. Overdue security patches are a possible leading indicator; service outages are a lagging indicator.

  4. Effectiveness: Did the treatment achieve its intended result, and is within tolerance? Use suitable evidence such as tests, trend data, incident rates, or independent assessment—not only a report that a task was completed.

For example, a company addressing ransomware risk strengthens access controls, keeps tested backups, and prepares a recovery procedure. It monitors patch delays, suspicious-access alerts, backup failures, and recovery-test results. If a test shows that services cannot be restored within the agreed time, that finding calls for reassessment; the company may add recovery capacity, change the service design, or escalate the decision. More generally, a material change, control failure, missed target, or unacceptable should prompt review of the risk and, as needed, revision of the treatment, monitoring plan, or acceptance decision. Communicate significant changes to relevant owners and decision-makers, and keep risk records and action plans current.

  • : A measure tracked against a defined threshold that should prompt a specified review or action.