Platform

How does enterprise risk management work in Acuna GRC?

Direct answer

Enterprise risk management in Acuna GRC runs in the Operate workspace. Each risk or opportunity carries impact, likelihood, a computed risk value, a treatment strategy (Mitigate, Accept, Transfer or Avoid) and target values after treatment, shown as a register, an editable table, an impact by likelihood matrix coloured by your risk appetite, or by category.

Risks link to assets, threats, processes, processing activities, third parties, measures and controls. They move through an approval workflow, and approval sets a yearly review with reminders. Treatment plans link the controls, measures and tasks that carry them out, and their health rolls up into the risk.

What does a risk register need to hold up in an audit?

Most frameworks ask for the same core. ISO/IEC 27001:2022 clause 6.1.2 requires a defined risk assessment process: risk criteria, including risk acceptance criteria, risks identified with an owner, consequences and likelihood analysed, and risk levels compared with the criteria to set priorities. Clause 6.1.3 then covers treatment, and clauses 8.2 and 8.3 require you to keep the results of risk assessment and treatment. See what a risk treatment plan is.

In practice, each risk needs:

  • A named owner who can approve it and accept what remains.
  • An inherent level (impact and likelihood before treatment) and a target or residual level.
  • A treatment strategy and the controls and measures that carry it out.
  • Links to what it concerns: assets, processes, suppliers, processing activities.
  • A review date and a history of decisions.

How does a risk move from identification to review in Acuna GRC?

  • Create the risk or opportunity in Risks & Opportunities, assess impact and likelihood, choose a treatment strategy (Mitigate, Accept, Transfer or Avoid) and set target values after treatment. Acuna GRC computes the risk value.
  • Link the assets, threats, processes, processing activities, third parties, measures and controls it concerns. The Threats register starts with a curated catalogue of threat sources, classified by source type and by Confidentiality, Integrity, Availability and Traceability.
  • Request approval. The risk moves through In progress, Approval required, Approved, To be reviewed and Archived; only the owner or an administrator can approve, and approving sets a next review date one year ahead.
  • Create a treatment plan with an owner and a status, linked to the controls, measures, tasks, documents and records that carry it out.
  • Work the tasks. Plan health is computed from the linked controls, measures and tasks and rolls up into the risk.
  • Confirm the review when it comes round. The owner is reminded 30 days and 3 days before, and once if overdue; confirming moves the date forward a year and records it in the workflow history.

How do you read the register?

The register has four views: Register (read-only), Table (inline editing), Matrix and Categories. The Matrix is an impact by likelihood heatmap coloured by your risk appetite, with an Actual or Target toggle, so you can see where risks sit today and where treatment should take them. The detail panel shows each risk’s level over time.

You can filter by status, category, likelihood, impact, treatment or owner, set status in bulk, and export the filtered list to XLSX or CSV. Scopes and tags narrow every view to an entity, site or department, and access profiles restrict each person to the scopes they work in.

What are the common risk management mistakes?

  • Risks with no owner, or owned by the security team on behalf of the business.
  • Scores typed in once and never connected to the controls meant to reduce them.
  • A register kept apart from assets, processes and suppliers, so nobody sees what a single incident would touch.
  • Treatment chosen but never followed through with a plan, tasks and evidence.
  • No review cycle, so last year’s assessment stays in place after the business changes.

In Acuna GRC, the links to controls and their health and the yearly review on each approved risk are what address the last three.

How Acuna GRC handles it

Sources

  1. ISO/IEC 27001:2022, clauses 6.1.2, 6.1.3, 8.2 and 8.3

This page explains the rules in general terms and is not legal advice.

Frequently asked

Is enterprise risk management a separate module in Acuna GRC?

Risks and Opportunities, threats and treatment plans are part of the Operate workspace of Acuna GRC, alongside the business impact analysis, tasks and documents.

Can Acuna GRC record opportunities as well as risks?

Yes. The register holds risks and opportunities, each assessed for impact and likelihood in the same way.

Who can approve a risk?

Only the risk owner or an administrator. Approval records the approval date and sets the next review one year ahead.

See how Acuna GRC runs this.

Tell us your frameworks and your team. We show you how Acuna GRC runs the program.

Hosted in Switzerland, the EU or the US