Skip to content

Documentation

Remediations

Plan and track the work that fixes vulnerabilities, on a board, in a ranked queue or in a table.

Overview

A remediation is a task to fix a vulnerability: patch a package, upgrade a firmware, change a configuration. Each task belongs to a CVE, can be linked to an asset, and has a priority, an SLA, an assignee and a status. Use Remediations to see all the work in one place, decide what to do next and move tasks through to Resolved.

You create remediations here, from Triage, or from a CVE. You need remediation:read to view tasks and remediation:write to create and change them.

Screen tour

  1. The status chips (Open, In progress, Resolved, Dismissed) and priority chips with their counts. Click a chip to filter by it.
  2. Past SLA: how many open tasks are past their SLA. Click it to show only those.
  3. A one-line summary of where you stand, for example 2 open tasks, none past SLA. Work the queue in order.
  4. Search remediations…: finds tasks by title or description.
  5. Views, Filters and Export.
  6. Board, Queue and Table: switch views.
  7. New remediation: creates a task.
  8. A Board column. Drag a card to another column to change its status.

The header shows how many tasks there are (8 tasks, or 3 of 8 tasks when filtered) and when the list last changed.

Views

Board

The Board has one column per status: Open, In progress, Resolved and Dismissed. Each card shows the priority, the CVE, the title, the asset (or Asset not linked), the assignee (or Unassigned), the SLA countdown and a thin SLA progress bar.

  • Click the card title to open the remediation.
  • Drag a card by its handle to another column to change its status.
  • Or click ⋯ on the card and choose the new status from the menu.

Moving a card to Open or In progress applies straight away. Moving it to Resolved or Dismissed asks you to confirm. See Change the status.

Queue

The Queue shows one task at a time, in the order you should work on them. Tasks are ranked by priority and age: critical counts eight times as much as low, tasks past their SLA count double, and tasks assigned to someone else count half.

The card shows the priority and status, a line such as Up next: Critical priority, 12 days open, 5 past SLA, assigned to you, the title and SLA, the description, and the asset, CVE, assignee and opening date. Click Open detail to open the task. The Up next list on the right shows the ranking.

Use Previous task and Next task, or k and j.

Table

The Table lists tasks in rows with the columns Title, Status, Priority, Asset, CVE, SLA, Assignee and Created. Click Title, Status, Priority or Created to sort.

Select tasks with the checkboxes to show the bulk bar:

  • Mark in progress: moves the selected tasks to In progress.
  • Dismiss selected: asks Dismiss N tasks?; click Confirm dismiss.
  • Clear: clears the selection.

If some tasks can’t be updated, DeviceQuest lists them with Retry failed.

Create a remediation

  1. CVE: required. Type a CVE ID such as CVE-2024-3094 and pick it from the list.
  2. Asset: optional. Search for the asset the task is for.
  3. Title: required, for example “Patch nginx to 1.27”.
  4. Description: optional steps, ticket links and context.
  5. Due date: the target date for completing the fix.
  6. Priority: critical, high, medium (the default) or low.
  1. Click New remediation (or press m in Queue view).
  2. Fill in the fields.
  3. Click Create. Create is available once CVE and Title are filled in. If you leave either empty, the dialog shows CVE is required or Title is required.

The new task starts as Open.

SLA

Each priority has an SLA, counted from the day the task was created:

PrioritySLA
Critical7 days
High14 days
Medium30 days
Low90 days

Cards and rows show the time left, for example 5d left, Due today or 3d overdue. The SLA bar turns amber at 80% of the SLA and red when the SLA has passed. Open and in-progress tasks past their SLA are counted in Past SLA.

Change the status

StatusMeaningNext possible status
OpenNot started.In progress, Resolved, Dismissed
In progressSomeone is working on it.Open, Resolved, Dismissed
ResolvedThe fix is done. DeviceQuest records who resolved it and when.Open, In progress, Dismissed
DismissedNot needed, for example because the asset was retired.Open, In progress, Resolved

You can move a task from any status to any other, from the Board, the Table or the task page.

Moving a task to Resolved or Dismissed asks you to confirm:

  1. The dialog asks Mark as resolved? or Mark as dismissed?.
  2. Optionally, enter a Reason, for example what was done to fix it. The reason is saved as a comment marked [Resolution] or [Dismissal] and appears in the task’s activity.
  3. Click Confirm resolved or Confirm dismissed.

You can reopen a dismissed or resolved task at any time by moving it back to Open or In progress. Every status change is recorded in the audit log.

Filter tasks

Click Filters to open the panel:

FilterOptions
Statusopen, in progress, resolved, dismissed
Prioritycritical, high, medium, low
OtherPast SLA only, Resolved in last 7 days
CVE containsPart of a CVE ID, for example CVE-2023
Asset containsPart of the asset’s name or ID

Active filters show as chips. Click × on a chip to remove it, or Clear all. Filters and the current view are kept in the page address, so you can bookmark or share them.

Saved views

Click Views to apply a view. Applying a view replaces the current filters.

ViewShows
My openOpen and in-progress tasks assigned to you
Past SLATasks past their SLA
Critical openOpen and in-progress critical tasks
Resolved this weekTasks resolved in the last 7 days
All openAll open and in-progress tasks

To save your own view, set the filters, click Views, then + Save current view…, enter a name and click Save. Your saved views appear under Saved in this browser. Click × next to one to delete it.

Export

Click Export and choose:

  • Download CSV: remediations.csv with the columns ID, Title, Status, Priority, CVE ID, Asset ID, Assigned To and Created At, for the tasks currently shown.
  • Copy as Slack message: the first 10 tasks as a bulleted list with links.
  • Copy as Jira/Linear markdown: the first 10 tasks as Markdown.

Keyboard shortcuts

These shortcuts work in Queue view, when you are not typing in a field.

KeyAction
jNext task
kPrevious task
oOpen the task
vSwitch to Table view
mCreate a remediation