Clear a scanner backlog at scale with multi-select, state-machine-enforced bulk actions, and per-item success and failure reporting.
This guide shows you how to turn a multi-thousand finding backlog from a scanner import into a handful of governed grid selections. You will drive bulk status change, bulk assign, bulk link-template, and bulk re-match from the SelectionBar and the REST API. Every batch runs under the same status state machine and scope enforcement that single-finding edits already follow, so scale does not loosen governance.
It is written for triage teams working down large queues after Nessus, Qualys, Rapid7, DAST, or SAST imports. By the end you will be able to run the read-only ticket-link summary to avoid duplicate ITSM tickets, read the per-item success and failure breakdown after every call, and re-run only the failed items along a legal status path.
Inside this guide
- Scope the queue, multi-select rows, and read the SelectionBar action set.
- Run a bulk status change with full state-machine enforcement per finding.
- Bulk assign findings to users and teams.
- Bulk link a VulnDB template and bulk re-match with Smart Match.
- Run the ticket-link summary before creating bulk tickets so no duplicate is raised.
- Read the per-item success and failure report and re-run only the failed items.
- Verify scope, audit, and realtime fan-out across the batch.
Before you start
- A PMAP account with finding read and edit permissions in your company scope.
- At least one completed scan import (Nessus, Qualys, Rapid7, DAST, or SAST) so the queue holds a real backlog to clear.
- Familiarity with your status policy, because every target transition is validated per finding by the state machine.
- The VulnDB template library populated, so bulk link-template and bulk re-match have candidates to backfill from.
- If your tenant gates a target status behind approval, a second reviewer available, because bulk operations do not bypass the approval gate.
