Actions

Once you're onboarded, this is where the remediation work lives. Actions are tasks — generated by AI from your findings or created manually by your team — that you track from creation to completion.

How Actions Are Created

AI-Generated (Action Review)

QuantAssure queues potential actions whenever something happens that may warrant remediation work:

  • New findings detected by a scan
  • Findings approaching or breaching their SLA deadline
  • Policies due for scheduled review

An AI review agent evaluates the queue and decides whether each trigger warrants an action — considering effective severity (a person's override, else the AI-adjusted severity), system criticality, and compliance impact. Warranted triggers become prioritised actions with a rationale; dismissed triggers are recorded in the audit trail, so nothing disappears silently.

Manual

  • Choose New Action on the Actions page (people who can edit see it)
  • From a finding's page, use Create Manual Action in the Quick Actions panel, or Generate AI Action to have the AI draft one. Create Manual Action opens the form already filled in from the finding: the title, the AI's recommended action (or the finding's description), the system, a priority matching the finding's effective severity, and the finding's SLA due date. Change any of it before you save
  • Link to specific findings, policies, or compliance controls
  • Useful for tasks not tied to a specific finding

Managing Actions

Viewing

  • Navigate to Risk → Actions
  • Filter by Status (Open, In Progress, Blocked, Resolved, Closed, Cancelled) or Priority
  • Sort by created date (the default is Created (Newest)), updated date, due date, or priority

Assigning

  • Assign an action to a team member with the Assignee field on the New Action form, or later with the change-assignee button beside Assignee on the action's page (Assign To). The new assignee gets an Action assigned notification unless you assigned it to yourself
  • Every action gets a due date from your SLA policy: an item linked to a finding is due when the finding's SLA is (based on its effective severity: a person's override, else the AI-adjusted severity, else the scanner's); any other item is due after your SLA days for its priority. You can change the date in the Due Date field on the New Action form; the action's page shows it but doesn't edit it
  • Assignees see their open actions in My work, grouped by how overdue they are

Updating Status

  • Choose Update Status on the action's page. An open action usually goes Open → In Progress → Resolved, and a resolved one can then be Closed. The menu offers the next steps that make sense from the current status. A resolved action can be Closed or reopened, and closed or cancelled actions can be reopened
  • Mark items Blocked while waiting on something external. A reason is required and is shown on the item. Blocked items still count as open and overdue, since they still need to be addressed
  • Add comments on the detail page as you work
  • Resolving, closing or cancelling an item requires a note explaining why; it is kept as audit evidence
  • Cancel items that are no longer relevant

Priority Levels

Priority Use when
Critical Immediate action required — active exploitation risk
High Address within days — significant security gap
Medium Address within weeks — moderate risk
Low Address when convenient — minimal risk

Compliance Linkage

  • Actions linked to findings appear on the ISM control pages those findings map to
  • Completing actions improves your compliance readiness
  • Actions can also link to systems, policies, and compliance targets

Learn more about compliance management