Evaluate detection confidence without counting alerts
Describe why an observation supports a claim before deciding how many alerts to send to engineering. A confidence label without its evidence usually adds another opinion to the queue.
Write the claim narrowly
In an illustrative case, a tool observes a server header associated with an older software release. The supported claim is that the response contained that header. Whether it identifies the deployed origin, whether a fix was backported and whether the vulnerable feature is enabled remain separate questions.
Keep the rule’s wording and the raw observation. Add a reviewer statement that names the missing condition rather than turning the entire alert into a binary true-or-false verdict too early.
Choose the evidence that would resolve uncertainty
A package inventory from the responsible owner may resolve a version question. A configuration record may resolve whether a relevant module is enabled. An authorized behavioral check may be needed for a different class of claim. The evidence request should follow the uncertainty; repeating the same weak observation from another dashboard does not always add independent support.
Record the source and time of the new material. Evidence about last month’s host is not automatically evidence about today’s deployment.
Use dispositions with distinct meanings
| Disposition | What it means | Next action |
|---|---|---|
| Supported | Available evidence establishes the stated condition | Assign a remediation or risk decision |
| Contradicted | Specific evidence disproves the stated condition | Retain the reason and close that claim |
| Unresolved | A material condition remains unknown | Assign an evidence request and review date |
| Not examined | The relevant check did not run or lacked access | Repair the checking process or use another method |
These are workflow categories, not a universal scanner scoring system. A team may use different names if it preserves the distinctions.
Carry the limit forward
Suppose a reviewer accepts that a component is installed but cannot establish which application instance serves a customer route. The record can support a package update task while the exposure question remains open. Preserve both decisions; do not force one confidence label to describe two different claims.
Use the asset identity guide before assigning the owner. Store the reasoning in the evidence record so a later change can be assessed against the same claim.
Continue reading
Cite this entry
Vulnerability Detection Tools. “Evaluate detection confidence without counting alerts.” Reviewed 2026-11-16.
https://vulnerabilitydetectiontools.com/detection-confidence/