Critical findings still open on scanned hosts
A scanned host's worst open finding should never be critical — a critical vulnerability left open is an active, known route to compromise, not a backlog item.
Interpret the result in context
Scanner severity is a prioritisation signal. Validate the finding and consider exposure, exploitability and business impact when planning a response.
Configure the expectation.
Use this baseline as a starting point. You can also build your own controls and standards from integration data, with client-specific requirements and documented exceptions.
A fixed baseline expectation
This shipped control has no adjustable numerical threshold. Review its applicability and record approved exclusions for the client.
Review. Remediate. Verify.
Use one-click remediation where the integration and action support it, or the evidence to guide the technician’s next step.
- 01
Inspect the critical finding and validate the affected software or configuration.
- 02
Apply the approved fix or record a reviewed mitigation and owner.
- 03
Rescan to confirm closure rather than relying only on a completed work item.
A completed action is only part of the record. Refresh the supporting evidence to establish whether the finding has cleared.
Make your baseline part of every client review.
Connect checks, findings and remediation to the same client record.