Remediation

Fix-first: why the order of remediation matters more than the count of open alerts

A backlog of a thousand open alerts is not a program. A queue that tells a third party which ten to close this week, ranked by severity and effect on the score, is.

Blog

August 25, 2026 · 10 min read

01

Not every open finding deserves the same attention

Open alerts differ by severity, by how many controls they affect, and by how much closing them moves the Security Score. A fix-first queue ranks findings by that combination, so the third party's team spends its first hour on the item with the largest effect, not the oldest ticket in an inbox.

Risk Overview — Priority: open findings ranked so the highest-effect item is worked first.
Risk Overview — Priority: open findings ranked so the highest-effect item is worked first.
02

From queue to case

An item in the queue becomes a remediation case with a named owner, a description of the failing control and the affected resource, and a recommended fix. From there it is tracked like any other piece of accountable work.

  • Ranked by severity and by effect on the Security Score
  • One click turns a ranked alert into a case with an owner
  • Recommended remediation attached to the affected control and resource
03

Measuring the program, not just the backlog

Mean time to resolution (MTTR) and the count of resolved versus open cases are the two numbers that tell a contracting organization whether a third party's remediation program is converging or merely accumulating findings.

Remediation: cases open and resolved, with MTTR tracked over time.
Remediation: cases open and resolved, with MTTR tracked over time.
1stone Research

Talk to the team about a third-party program

A working session against your actual third-party portfolio: how workspaces are created, which accounts get connected first, and what the Security Score looks like in week one.

Request a walkthrough