Prioritize advisory ingestion by severity

Release notes

Problem to solve

Advisories are scanned in the order in which they are returned by Postgres. This means that continuous scans don't prioritize high or critical severity vulnerabilities.

Proposal

Continuous Vulnerability Scanning queues scans in the same order it parses the export files. This gives us an opportunity to add a priority queue that's backwards compatible by updating the exporter instead of the GitLab monolith application.

Intended users

• Amy (Application Security Engineer)
• Alex (Security Operations Engineer)
• Cameron (Compliance Manager)

Feature Usage Metrics

Does this feature require an audit event?