Platform

What does the Operate workspace do in Acuna GRC?

Direct answer

Operate is the Acuna GRC workspace where you run the management system day to day. It holds the risks and opportunities you assess and approve, the threat sources behind them and the treatment plans that bring risks within appetite, plus objectives, tasks and the policies and procedures in Documents.

It also holds the business impact analysis of your processes, with RTO, RPO and MTPD, and a single point of failure analysis. Recurring tasks keep a completion history with a record attached, risks and documents move through approval workflows with yearly reviews, and the Annual Plan lays the year's recurring work on one grid.

What does running a management system day to day involve?

Setting up a programme is a project. Running it is a routine, and the standards describe that routine. ISO/IEC 27001:2022 asks you to assess information security risks (clause 6.1.2) and treat them (clause 6.1.3), to set information security objectives and plan how to achieve them (clause 6.2), to perform risk assessments at planned intervals or when significant changes occur (clause 8.2), to implement the risk treatment plan (clause 8.3), and to keep documented information under control (clause 7.5).

In practice this means registers that change every week: risks reviewed and approved, treatment plans carried out, objectives tracked, tasks done on time, and policies approved, published and reviewed. Operate is where those registers live in Acuna GRC.

How are risks handled in Operate?

Each risk carries an impact, a likelihood, a computed risk value, a treatment strategy (Mitigate, Accept, Transfer or Avoid) and target values after treatment, so you see inherent and residual risk side by side. The register has four views: Register, Table with inline editing, a Matrix heatmap of impact by likelihood coloured by your risk appetite with an Actual or Target toggle, and Categories.

Risks follow an approval workflow: In progress, Approval required, Approved, To be reviewed, Archived. Only the owner or an administrator can approve. Approving sets a next review date one year ahead, and the owner is reminded 30 days before, 3 days before and once overdue.

Threats hold the sources that could bring a risk about, classified by source type, subtype and applicability (Confidentiality, Integrity, Availability, Traceability), with a curated catalogue on day one. Treatment plans link a risk to the controls, measures, tasks, documents and records that carry it out, and the plan’s computed health rolls up into the risk. See how enterprise risk management works and what a risk treatment plan is.

How do business impact analysis and SPOF analysis fit in?

The BIA Overview lists every process in BIA scope with its impact assessment, RTO and earliest-impact columns. For each process you set RTO, RPO and MTPD from a Time Threshold list your administrator maintains, describe impact scenarios as an outage lengthens, and record the assets, staff, third parties and critical assets it depends on. Suppliers get a criticality for that process, suggested from their risk exposure and tier.

The SPOF Analysis lists the assets that support several critical processes, above a threshold you set, so you can prioritise redundancy, cross-training and supplier diversification. See business impact analysis in Acuna GRC.

How do tasks, documents and the Annual Plan keep the system moving?

  • Tasks have a Table and a Board view. Recurring tasks come back on schedule, and completing one records who did it and lets you attach a record. Curated task templates, filtered to your frameworks, arrive pre-linked to the requirements they fulfil. See how recurring tasks work.
  • Documents are written in Acuna GRC, uploaded as a file or linked from another system. They move through Draft, Pending Approval, Approved, Published, In Review and Retired, with one or several approvers, a numbered revision for every change, and a yearly review with reminders.
  • Objectives carry an owner, a target date and a status from Draft to Completed or Cancelled, linked to the requirements, controls and KPIs that support them.
  • The Annual Plan lays the year on one 12-month grid: recurring tasks, scheduled controls and the yearly review of each approved risk and published document. See what a compliance calendar is.

See the Operate workspace.

How Acuna GRC handles it

Sources

  1. ISO/IEC 27001:2022, clauses 6.1.2, 6.1.3, 6.2, 7.5, 8.2 and 8.3
  2. Acuna GRC, Operate workspace

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

Frequently asked

Who can approve a risk in Acuna GRC?

Only the risk owner or an administrator. The approval waits in the owner’s My Actions, and approving sets the next review date one year ahead.

What happens when a policy needs changes at its yearly review?

Confirm review moves the review date forward a year when nothing changes. Start Review takes the document back through approval when it does, and the change becomes a new numbered revision.

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