Home / Trust / Risk Management Framework
Security policy

Risk Management Framework

How risks to information are found, rated, treated or accepted, and how often they are reviewed.

Purpose

To make sure the risks to the information HealthOS holds are found, written down, rated the same way each time, and either treated or accepted by someone with the authority to accept them. It sits under Information Security Policy.

Roles

RoleWhoDoes
DirectorsAaron Le Saux (sole director)Set the risk appetite; accept High and Critical risks
Risk owner (security owner)Aaron Le SauxKeeps the register, runs the quarterly review, accepts Low and Medium risks
Treatment ownerNamed per riskCarries out the treatment by its date
Everyone—Raises a risk when they see one

Risk appetite

The director adopts this statement unchanged, on the date of adoption. It is drafted from how the system is already built.

  • No appetite for one tenant's information reaching another, for unauthorised disclosure of health information or government-sourced information, or for breaching a government agency's or licensor's terms. A risk of this kind rated Medium or above is treated, not accepted.
  • Low appetite for loss of integrity or availability of clinical records.
  • Moderate appetite for risks to delivery speed, cost and convenience, where the information above is not affected.

How a risk is rated

Rate the risk as it stands with current controls (the residual risk).

Likelihood

ScoreLevelMeaning
1RareNot expected in five years
2UnlikelyCould happen in the next five years
3PossibleCould happen in the next year
4LikelyExpected in the next year
5Almost certainExpected within months, or already happening

Impact — take the highest that applies.

ScoreLevelInformationServiceLegal and commercial
1MinorNo personal information involvedUnder an hour, one customerNone
2ModerateInternal or Confidential information, a few recordsHours, one customerA customer complaint
3MajorPersonal information of a few people, not serious harmA day, or several customersA contract breach; a finding by an assessor
4SevereAn eligible data breach affecting one customerDaysNotification to the OAIC or an agency; loss of a customer
5CriticalAn eligible data breach across customers, or loss of clinical recordsA week or more, or data unrecoverableLoss of a government connection or licence; the business at risk

Rating = likelihood × impact.

ScoreRatingWho may accept itAction
1–4LowRisk ownerAccept and review yearly
5–9MediumRisk ownerTreat within 90 days, or accept with a written reason
10–16HighA directorTreat within 30 days; a treatment plan within 7
20–25CriticalA director, and only for a stated short periodTreat at once; reported to the directors the same day

Treatment

Each risk gets one of four decisions, recorded with its reason:

  • Reduce — add or strengthen a control. The usual choice.
  • Avoid — stop doing the thing that creates the risk.
  • Transfer — to an insurer or a supplier under contract. This moves cost, not accountability.
  • Accept — by the person the table above allows, with a reason and a review date. An acceptance without a review date lapses after 12 months.

Where risks come from

A risk is added to the register when any of these produces one:

  • a penetration test or scanner finding (pentest/findings-log.md), including each finding dispositioned "risk accepted";
  • a threat model for a change that crosses a trust boundary (secure-development.md);
  • a security incident or near miss (Security Incident and Data Breach Response);
  • a dependency or platform advisory (patching-and-vulnerability-management.md);
  • a new supplier, integration, customer type or kind of data;
  • a change in law or in an agency's or licensor's terms;
  • an exception granted under the information security policy;
  • anybody saying so.

The findings log remains the detailed record of test findings. The register holds the risk each one represents, so an accepted finding has an owner and a review date instead of only a line in a log.

The register

Kept in SharePoint: HealthOS ISMS > Risk register. It is Confidential. Each entry has:

FieldContent
IDR-nnn
RiskWhat could happen, to what, and why
SourceWhere it came from, with a link
Existing controlsWhat limits it today
Likelihood, impact, ratingBy the tables above
DecisionReduce, avoid, transfer or accept
TreatmentWhat will be done
Treatment owner, due dateA person and a date
Accepted by, review dateFor an accepted risk
StatusOpen, in treatment, accepted, closed

Review

  • Quarterly: the risk owner reviews every open and accepted entry, closes what is done, re-rates what has changed, and chases overdue treatments.
  • Yearly: a full assessment — walk the assets and suppliers in the information security policy and ask what is missing from the register — and a report to the directors of the High and Critical risks and the acceptances in force.
  • On the day: after an incident, a new integration, or a new kind of data.

Each review is recorded with its date and who took part.

Questions about security? Email security@healthos.net.au