Skip to content
Automated Vulnerability Remediation

With agents in the loop, the weekly remediation meeting should review decisions and exceptions, not the whole queue

What the meeting used to be

The classic remediation meeting walks a list sorted by severity. Each item gets a name, a status and a promise. Most of the hour goes to items that will not move this week, and the items that will move are decided before the meeting by whoever has the time.

With agents doing the first pass, the list is shorter and the discussion can change. The meeting no longer needs to read findings. It needs to read decisions.

A five-item agenda

The spot check is the one that keeps the arrangement honest. If the platform dismissed a finding as not exploitable, someone reads the evidence and agrees or disagrees. A disagreement is recorded and fed back to the vendor or to the policy.

  • Newly exploited this week: items added to the Known Exploited Vulnerabilities catalog or reported exploited by a vendor, and whether each has an exposed asset. Rapid7's Q3 2026 report puts the average at three days from disclosure to exploitation, so this item cannot wait for the next cycle.
  • Waiting for approval: changes the agents have proposed that need a person, oldest first, with the evidence the agent attached.
  • Owner-less or bounced: findings with no owner or reassigned more than once, with the cause.
  • Mitigations due to expire: controls recorded with an expiry date that falls before the next meeting.
  • Spot check: five decisions the agents made alone, chosen at random, read in full.

Bring four numbers

Bring the count of open items past SLA by tier, the median time to decide, the share removed before analysis with evidence, and the number of approvals waiting. The calculator on this site converts the first into hours, which tells the room whether the team can clear it by hand or needs the agents to take more. The guide on honest mean time to remediate lists the definitions.

Keep the authority with people

Agents propose and people approve what crosses the limits. CISA BOD 22-01 requires agencies to assign roles and responsibilities and to set internal validation and enforcement procedures. The same structure applies in a private company: a named person approves each class of change, and the meeting is where that person is held to the date.

NIST SP 800-40 Rev. 4 frames patching as preventive maintenance with a plan. The meeting is where the plan is checked against what happened.

Keep the minutes short and dated

Four lists are enough. The minutes become the evidence trail for the exceptions in an audit, and they show whether the agents are improving. A meeting that produces no disagreements for a quarter is either working very well or not reading the decisions.

  • Decisions made: finding, decision, approver, date.
  • Owners assigned: team and due date.
  • Mitigations accepted: control, expiry date, review trigger.
  • Disagreements with an agent's decision, and what was changed in the policy.

Adjust the meeting as trust grows

In the first month of agent use, the spot check should cover many decisions, perhaps ten a week, and the meeting should run longer. If the spot checks agree with the agents, reduce to five, then to three. If a spot check finds a wrong dismissal, widen again and change the policy that allowed it.

Keep a running count of agreements and disagreements. It is a plain measure of trust that a CISO can read, and it gives the team a reason to widen approval settings that is based on its own results rather than on a vendor's page.

Finally, write down what the meeting decided not to do. A list of items deliberately left open, with the reason and the date to revisit, is the most useful page in an audit and the one most often missing. It also shows new attendees that the queue is managed rather than ignored.

Sources

3 sources, each with its read date
  1. Rapid7, Q3 2026 Threat Update, 21 Oct 2026, read 10 Nov 2026
  2. CISA BOD 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities (archived copy), read 10 Nov 2026
  3. NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning, read 10 Nov 2026

Last reviewed 10 Nov 2026.