Workflow
Triage & Remediation
A scan tells you what is wrong. This is what happens next: you triage each finding, and when you need a human, you talk to us. Remediation tracking gives every finding a status, an assignee, and a due date that carry over to the next rescan of the same target. Support tickets open a threaded conversation with staff from the Contact page, on any plan including free.
- Remediation statuses
- 5
- Findings per bulk update
- 200
- Plan can open a ticket
- Free
Overview
VulnRadar splits the after-scan workflow into two things a scan report cannot do for you. The first is deciding what to do about each finding and remembering that decision: remediation tracking. The second is asking a human when a scan alone is not enough: support tickets. Both are private to you: remediation is per-user and never appears on a shared or public view of a scan, and a ticket is visible only to you, staff, and any teammate you explicitly loop in.
Remediation tracking is separate from the accuracy feedback on a finding (confirmed, false positive, not applicable). That feedback tunes the global detection confidence model; remediation records what you have done about the finding and nothing else. The two controls sit next to each other on an open finding but never touch the same data.
The HTTP endpoints below live under https://vulnradar.dev/api/v3/, the same base as the rest of the app. The support ticket UI lives on the Contact page under the Support Ticket option.
Remediation tracking
Open any finding on your own scan and you get a Your remediation tracking control: a status, and once the status leaves Open, a note, an assignee, and a due date. It is stored per finding, per user, and it is remembered the next time you scan the same target.
Statuses
Five states, in the order they appear in the control. Open is the default and is never stored as a row; the other four persist.
| Stored value | Control label | In the list |
|---|---|---|
| open | Open | No badge. Open is the implicit default, so no row is stored: setting a finding back to Open deletes any row it had. |
| in_progress | In progress | Brand-coloured badge. Counts as active work, so the row keeps full opacity in the list. |
| fixed | Fixed | Success-coloured badge. The row dims slightly so still-open findings stand out. |
| accepted_risk | Accepted risk | Muted badge (shown as Accepted). Dims in the list like Fixed. |
| wont_fix | Won't fix | Muted badge. Dims in the list like Fixed. |
Assignee, note, and due date
Once a finding is anything other than Open, three optional fields appear:
- Note (max 2000 chars): free text, for a release number or an internal ticket reference.
- Assignee (max 120 chars): a free-text field with a datalist that suggests people you share a team with. Solo users just type a name; the field never forces a real account.
- Due date: a target or SLA date. When it is in the past and the finding is still open work (not Fixed, Accepted risk, or Won't fix), the finding shows an
Overduebadge. A due date on a finding you have already closed out never nags.
Surviving rescans
This is the part that makes tracking worth doing. A remediation row is keyed on the finding, not on the scan that surfaced it. The finding id is deterministic: the same check firing against the same URL always produces the same id, which is the same identity the compare, diff, and regression-alert features already rely on.
finding_id = <checkId>--<fnvHash(scannedUrl)>
// Deterministic: the same check against the same URL always
// yields the same id, so a remediation row is keyed on the
// finding, not on the scan_history row that surfaced it.
remediation key = (user_id, finding_id, finding_url)So a finding you marked fixed on Monday still reads fixed when you rescan the same host on Friday, even though that is a brand new scan row. The status is attached only on the owner's own result-load paths (scan status and history); the public /shared/[token] and /host/[hostname] views never read it, so your private tracking never leaks onto a link you share. If the underlying table has not been migrated yet, the read fails soft to an empty map and the result page still loads.
Bulk actions
Setting one finding at a time is fine for a couple of them, but a fresh scan can surface dozens. The findings list on your own scan has an opt-in Select mode: the list stays clean (no checkboxes) until you turn it on, and only then do row checkboxes and a sticky bulk bar appear. Pick a status, optionally an assignee and a due date, and apply it to everything you selected, up to 200 findings per request.
// POST /api/v3/scan/remediation/bulk
{
"items": [
{ "findingId": "hsts-missing--9f2c1a", "findingUrl": "https://example.com" },
{ "findingId": "csp-missing--9f2c1a", "findingUrl": "https://example.com" }
],
"status": "in_progress",
"assignee": "alex"
}Remediation API
One route handles the single-finding lifecycle, plus a bulk variant. All of it is session-gated and owner-scoped: there is no way to read or write another user's remediation state.
| Method | Endpoint | What it does |
|---|---|---|
| POST | /scan/remediation | Set or update one finding's status, note, assignee, and due date. status "open" clears the row. |
| GET | /scan/remediation | List your remediation rows, optionally filtered by ?url= and/or ?findingId=. Up to 500, newest first. |
| DELETE | /scan/remediation | Clear one finding's remediation (back to Open). Requires ?url= and ?findingId=. |
| POST | /scan/remediation/bulk | Apply one status, plus an optional assignee and due date, to up to 200 findings at once. |
/scan/remediationSet a finding's remediation status
Record what you have done about one finding: its status, plus an optional note, assignee, and due date. Upserts on (user_id, finding_id, finding_url), so calling it again for the same finding updates the row rather than duplicating it. This is the owner's private tracking, separate from the accuracy feedback that feeds the global confidence model.
Request Body
{
"findingId": "hsts-missing--9f2c1a",
"findingUrl": "https://example.com",
"status": "in_progress",
"note": "patched in release 4.2, ticket VR-118",
"assignee": "alex",
"dueAt": "2026-09-01"
}Response 200 OK
{
"ok": true,
"remediation": {
"status": "in_progress",
"note": "patched in release 4.2, ticket VR-118",
"assignee": "alex",
"due_at": "2026-09-01",
"updated_at": "2026-08-24T12:00:00.000Z"
}
}Error Responses
Support tickets
When a finding needs a person rather than a fix step, open a ticket. It is a tracked, two-way thread with our team, not a fire-and-forget email form. It lives on the Contact page under the Support Ticket option, and it is available on every plan, including free.
Opening a ticket
Sign in, pick the Support Ticket option on the Contact page, and fill in a subject, a category, and a first message. The thread opens immediately and staff reply into the same thread. There is one guard rail: you can hold at most 20 open tickets at a time, so you cannot stockpile them, and a captcha protects creation when Turnstile is configured.
Categories and statuses
Four categories, chosen when you open the ticket: Billing, Scanning, Account, Other. The status then tracks whose turn it is:
| Stored value | Label | What it means |
|---|---|---|
| open | Open | Brand new, no staff reply yet. |
| awaiting_staff | Awaiting staff | You (or a shared teammate) replied. The ball is with staff. |
| awaiting_user | Awaiting your reply | Staff replied. The ball is with you. |
| resolved | Resolved | Marked done by you or staff. Replying reopens it as awaiting staff. |
| closed | Closed | No further replies accepted. A reply returns 409; open a new ticket to continue. |
The flow is automatic: a new ticket is Open, your reply flips it to awaiting staff, a staff reply flips it to awaiting your reply. You can resolve or close your own ticket; staff can move it to any state, including reopening. In a thread, you see your own messages as "You" and staff replies as "Support": a staffer's real name is never exposed to a non-staff viewer, and your identity is exposed only to staff.
Replies and notifications
A staff reply reaches you two ways at once: an in-app bell notification and an email. Both are transactional (you opened the ticket), so they are sent directly and are not subject to marketing notification preferences, and both link straight back to the thread via /contact?ticket={id}. In the other direction, a new ticket or a user reply emails the staff support inbox.
Support ticket API
The same routes the Contact page UI calls. Every one is session-gated; access to a specific ticket resolves to owner, staff, or a shared teammate.
| Method | Endpoint | What it does |
|---|---|---|
| GET | /support-tickets | List your own tickets plus any shared with you, newest first. |
| POST | /support-tickets | Open a new ticket (subject, category, message). Any plan. |
| GET | /support-tickets/{id} | Fetch a ticket and its full message thread. |
| POST | /support-tickets/{id} | Add a reply to the thread. |
| PATCH | /support-tickets/{id} | Change status: resolve, close, or (staff) reopen. |
| GET | /support-tickets/{id}/shares | List current shares and the teammates eligible to add. |
| POST | /support-tickets/{id}/shares | Share the ticket with a teammate ({ userId }). Owner only. |
| DELETE | /support-tickets/{id}/shares | Stop sharing with a teammate (?userId=N). Owner only. |
/support-ticketsOpen a support ticket
Create a tracked ticket and its first message. Available on every plan, including free. The only gate is a signed-in session (plus Cloudflare Turnstile when it is configured). The response is the new ticket row; the UI then opens its thread.
Request Body
{
"subject": "Scan times out on staging",
"category": "scanning",
"message": "Every scan of https://staging.example.com stalls at 90%."
}Response 200 OK
{
"ticket": {
"id": 128,
"subject": "Scan times out on staging",
"category": "scanning",
"status": "open",
"created_at": "2026-08-24T12:00:00.000Z",
"last_message_at": "2026-08-24T12:00:00.000Z"
}
}