Risk Register

The risk register is where you record the risks your organisation has chosen to track, rate each one for likelihood and consequence, and show what you are doing about it. It sits alongside findings, which are specific issues in your systems. A risk is the broader question of what could go wrong and how much it would matter.

Find it under Risk → Risk register. The register has three tabs: Risk register, Risk matrix and Threat library.

Risks are rated by people, with help from the AI. Unlike findings, nothing re-rates a risk behind your back: the AI can draft risks and vendor assessments can add them, but both arrive as Draft for you to review.

How a risk is rated

Every risk is scored on two scales, each from 1 to 5. QuantAssure combines them into a risk level using a standard 5x5 matrix.

Score Likelihood Consequence
1RareInsignificant
2UnlikelyMinor
3PossibleModerate
4LikelyMajor
5Almost CertainSevere

The resulting level is Low, Medium, High or Extreme:

Likelihood \ Consequence 1 2 3 4 5
5HighHighExtremeExtremeExtreme
4MediumHighHighExtremeExtreme
3MediumMediumHighHighExtreme
2LowMediumMediumHighHigh
1LowLowMediumMediumHigh

You never pick the level directly. Change the likelihood or consequence and the level follows. A risk can carry up to three ratings:

  • Inherent: the rating before any treatment. Required.
  • Residual: the rating that remains once your controls are in place. Optional. It is set with Residual Likelihood and Residual Consequence on the risk's edit form and shows as Not assessed until you do.
  • Target: the rating you are working towards, with an optional Target Date. Optional.

The register list

The Risk register tab lists every risk, apart from ones that were superseded by a vendor reassessment. The tiles at the top show Total Risks, the count at each level (Extreme, High, Medium, Low), Overdue Reviews and Over Tolerance.

Search with Search risks... and narrow the list with the Status, Risk Level, Category and Treatment filters. The sort options are Updated (Newest), Updated (Oldest), Risk Level (Highest) and Code.

Each row shows the risk's code (for example RISK-001), its category, owner and next review date, then four pills: the inherent level, the residual level (a dash when not assessed), the treatment and the status. An Overdue flag appears when the next review date has passed.

Statuses

Status Meaning
DraftWork in progress. Every new risk starts here, including risks drafted by the AI, imported from a file or raised by a vendor assessment. Drafts are left out of the risk matrix and reports.
ActiveA reviewed risk you are managing. Only active risks count towards Overdue Reviews.
Under ReviewA risk being reassessed. It is still plotted and reported.
ClosedNo longer a concern. Closed risks stay on the register but are left out of the matrix and, unless you ask for them, out of reports.
SupersededA draft risk replaced by a newer vendor assessment. QuantAssure sets this itself; you cannot, and superseded risks are hidden from the register.

Treatment and categories

Treatment records what you intend to do: Mitigate, Accept, Transfer or Avoid. Category groups risks as Strategic, Operational, Financial, Compliance, Cyber, Third-Party or Legal.

Adding risks

People who can make changes (owners, admins and members) see three buttons above the list. Viewers can read the register but not change it.

Add Risk

Add Risk opens a form. Title, Risk Category, Likelihood and Consequence are required. You can also set a Description, the Treatment (it starts as Mitigate), an Owner (free text, such as "CISO"), the Impact Types (Confidentiality, Integrity, Availability) and the Review Frequency (Monthly, Quarterly, Semi-Annual or Annual; it starts as Quarterly). Choose Create Risk and the risk is added as a draft with the next free code.

Review dates

QuantAssure sets the Next Review Due date for you from the Review Frequency: one month, three months, six months or twelve months after the risk was last reviewed, or after it was created if it has never been reviewed. The date is set when you add, import or generate a risk, and it moves when you change the frequency. Once a risk is Active and its date passes, it shows an Overdue flag and counts towards Overdue Reviews. Risks added before this was automatic show a date worked out the same way. A risk with no review frequency has no review date. To record a review, open the risk and choose Mark reviewed (people who can make changes see it). You can add a note, which is kept in the audit log. QuantAssure sets Last Reviewed, shows who reviewed it, and moves the next review date on by the review frequency. Last Reviewed and the reviewer can only be set this way, so they always record the signed-in person and the time of the review. They cannot be typed into a risk, set through the API or changed from an AI assistant; a request that includes them is refused. Imported risks start with no review recorded.

Import CSV

Import CSV adds many risks at once. Choose Download CSV Template for the exact columns and an example row, choose your file under CSV File, then select Import. Limits are 500 rows and 5 MB per file. QuantAssure checks every row before it imports anything. If any row has a problem, the form lists each row number with what is wrong and nothing is imported, so you can fix the file and try again. Imported risks arrive as drafts. In the Review Frequency column use monthly, quarterly, semi_annual or annual (semi_annually and annually are also accepted). A frequency sets the next review date; leave the column blank for none.

Generate with AI

Generate with AI asks the risk register agent to draft a starting register for your organisation. It reads your systems, findings, policies and compliance targets, works through the enabled sources in your threat library, and takes your risk tolerance into account. The message Risk register generation started. Risks will appear shortly. shows while it works, and the list refreshes after a few seconds. Only one generation runs at a time. If you start a second you see A risk register generation is already in progress. The run counts towards your organisation's AI usage.

Treat generated risks as a first draft. Each one carries the agent's reasoning, a confidence level and suggested controls on its page, so you can judge it before you activate it.

A risk's page

Select a row to open the risk. The header shows the level, status, code, category, owner and next review date, with an Overdue flag when that date has passed.

The main column holds the Description, Existing Controls and Treatment Notes when you have written them; the AI Analysis card when the AI drafted the risk (Reasoning, Evidence Summary and Suggested Controls); the Threat Sources the risk is linked to; the Affected Systems; and the Impact Types. The Risk Assessment card shows the inherent, residual and target ratings, and Exceeds org risk tolerance when the residual level is above the limit you set for that category. Beside it are Treatment & Ownership, Review Schedule (review frequency, when it was last reviewed and the next review due) and Metadata.

People who can make changes also get these buttons in the header:

  • Status changes the status in one step to Draft, Active, Under Review or Closed.
  • Mark reviewed records a review today, with an optional note, and sets the next review date.
  • Edit opens Edit Risk, with every field above plus Existing Controls, Treatment Notes, the residual and target scores and Target Date. Choose Save Changes when done.
  • Delete asks you to confirm in Delete Risk and then removes the risk permanently. Consider setting it to Closed instead if you want to keep the history.

Creating, changing and deleting a risk are all written to the audit log.

Risk tolerance

Under Settings → Compliance → Risk tolerance you set the highest residual level you will accept for each category. A risk whose residual level is above the limit for its category is flagged Exceeds org risk tolerance and counted in the Over Tolerance tile. The flag needs a residual rating, so a risk with no residual assessment is never flagged.

Risk matrix

The Risk matrix tab plots your register on a 5x5 heat map with likelihood up the side and consequence along the bottom, so you can see where risk concentrates. Each cell shows its level and how many risks sit there.

  • Switch between Inherent Risk and Residual Risk to see the register before and after treatment. Until a risk has a residual rating it appears only in the inherent view, and the page notes No residual assessments yet.
  • Select a cell to list the risks at that position under Risks at .... Each links to the risk.
  • The matrix is a reporting view, so Draft, Superseded and Closed risks are not plotted. Until you have activated at least one risk the page shows No reportable risks yet.

The Risk Register report follows the same rule, so the matrix and your audit pack agree. Tick Include closed risks when generating the report if you want history. Drafts and superseded risks are never included.

Threat library

The Threat library tab lists the threat sources a risk can be assessed against, such as cybercriminals, state-sponsored actors, insiders or natural events. Each has a code (for example TS-1), a category, a source name and the impact types it can cause. Platform sources come with QuantAssure and are shared by every organisation. Custom sources are yours.

The tiles show Total Sources, Enabled, Platform and Custom. The categories are External Human, Internal Human, System/Technical, Environmental and Third-Party.

  • The Enabled switch turns a source on or off for your organisation. Only enabled sources are given to the AI when it drafts a register. You can switch off platform sources you do not want; you cannot edit or delete them.
  • Add Threat Source opens Add Custom Threat Source. Give it a Code (such as TS-15), a Category, a Source name and at least one impact type, separated by commas, then choose Add Source.
  • The bin icon on a custom source deletes it after a confirmation (Delete Threat Source).

Viewers can see the library but cannot change it.

How the register connects to the rest of QuantAssure

  • Vendors. A vendor assessment adds Third-Party risks as drafts, linked back to the vendor. Re-running an assessment supersedes the old drafts and keeps any risk you have already triaged.
  • Systems. A risk can name the systems it affects, shown under Affected Systems and linking to each system.
  • Reports. The Risk Register report and the risk matrix use the same rules, described above.
  • Findings and actions. The register does not link findings or actions to risks. Findings stay on the Findings page, and remediation work on Actions.
  • AI clients. Risks can also be read and changed through AI client access, with the same rules.