How to Create a Risk
A step-by-step guide to adding a risk to your register, describing it with the bow-tie model, rating its inherent position, and setting out how it will be treated and reviewed
Creating a risk records something that could affect your organisation so that it can be owned, scored, treated and reviewed in one place. Once a risk is linked to its Risk Categories and controls, CyberHQ works out its residual position for you, so the register reflects your real control posture rather than a number someone typed in once and forgot. This article walks through the Create Risk page field by field.
- From the left-hand menu, go to Catalogue > Risks and click Add Risk to open the Create Risk page. As you fill in the form, the Risk Scores panel updates live. It shows the inherent risk score and its severity band, the residual risk score (shown as Not set until it has been calculated), where the risk sits on your likelihood × impact matrix, and which governance zone that puts it in: Within Appetite, Within Tolerance or Beyond Tolerance.
- Identify the risk. The Identification section defines what the risk is.
- Risk ID is required. Click the regenerate icon in the field to generate an ID, or type your own to match an existing numbering scheme.
- Risk Title is required.
- Date Identified is required, and defaults to today. Change it if the risk was found earlier.
- Identified By records who raised the risk, and Risk Source records where it came from, in your own words.
- Event: what risk scenario could occur. A short summary of what could happen, for example A threat actor gains unauthorised access to ICS via the OT network.
- Cause: why it could happen. The underlying reason or root cause that would let the event occur, for example Unpatched legacy PLCs and shared credentials on the engineering workstation.
- Consequence: what would result. A plain description of the impact if the event happened, for example Plant shutdown, safety incident, and regulatory notification within 72 hours.
- Choose the Risk Categories. Toggle Yes on every category this risk could affect. At least one is required. This is the link that lets CyberHQ score the risk automatically, because your controls are mapped to Risk Categories. See Getting Started With The Risk Register for how this works.
- Assess the risk. In the Risk Assessment section:
- Status is required and starts as Active. The other options are Mitigated, Accepted, Transferred and Closed. Update it as the risk moves through its life. Status is a label for tracking; a risk counts in the register's KPI cards whatever its status. Status and Treatment are set separately, and changing one doesn't change the other.
- Priority is a Low, Medium or High label for your own triage. It defaults to Medium and does not affect the risk's score.
- Inherent Likelihood and Inherent Impact are required. Rate the risk as it would stand before your controls are taken into account. Each runs from 1 up to the size of your risk matrix (5 or 6).
- Residual Likelihood is calculated for you, from the effectiveness of the risk's linked controls, your Master Control Framework maturity and any open or accepted issues linked to it. It can't be higher than the inherent likelihood. If your organisation needs a value of its own, you can override it later from the risk's Update Risk page (see How to Manage a Risk).
- Residual Impact is set by you, and the options stop at the inherent impact.
- Inherent Severity and Residual Severity are shown for you from the scores, using the severity bands in your risk matrix.
- Financial Impact ($) is your estimate of what the risk would cost if it happened. The Total financial exposure card on the register adds these up across your risks.
- Plan the treatment. In the Risk Treatment section:
- Treatment is required. Choose Accept, Mitigate, Transfer or Avoid to record how the risk will be handled. The register can be filtered by treatment, and the Treatment Strategy widget (switch it on under Widgets above the charts) shows the split across your register.
- Due Date is the target date for completing the treatment.
- Owner is the person accountable for the risk. Choose from the users in your workspace. Owning Team optionally records the team the risk belongs to.
- Assignees are the people working on the treatment.
- Related Risks links this risk to others in your register. Start typing to search for them. This records the relationship; it doesn't change either risk's score.
- Treatment Actions lets you break the treatment into individual actions, each with its own name, assignees and due date. Expand it and add as many as you need, or add them later.
- Link controls. In the Controls section, select any controls that have a material effect on this risk beyond those already mapped to its Risk Categories. Linked controls feed the residual likelihood calculation, so link them accurately. See Getting Started With The Risk Register for how key and compensating controls are weighted.
- Set the review cycle. In Risk Monitoring and Review, set how often the risk must be re-attested, meaning reviewed and confirmed as still accurate. Enter a number in Attestation Interval and choose the unit (Day, Week, Month or Year) in Attestation Period. The default is every 6 months, and a period is required. Attested On shows when the risk was last attested. When a risk's attestation lapses, CyberHQ flags it and notifies the people concerned; switch on Failed to Attest under Risk in your email notifications to receive an email. Risk attestation is set on each risk. It is separate from the attestation rules for capability controls under Settings > Capabilities.
- Click Save. The risk is added to your register and plotted on the heat map, and its residual likelihood is calculated from its linked controls and issues. It is recalculated automatically whenever its linked controls or issues change. Reset clears the form if you want to start again.
Risks can also be imported in bulk from a CSV using the import icon at the top of the register, rather than created one at a time. See How to Bulk Upload your Data via CSV.
With the risk created, it is ready to be reviewed and worked. See How to Manage a Risk to update, attest or delete it, and Getting Started With The Risk Register for how its scores are worked out.