Missing patches identified by vulnerability scanning
An RMM-managed endpoint should carry no outstanding missing-patch findings from the vulnerability scanner — a device that is both unpatched and unscanned-for-gaps is the pattern that precedes most ransomware incidents.
Interpret the result in context
This check connects the managed endpoint estate with missing-patch findings. A scanner’s result can differ from the RMM patch-compliance verdict, so reconcile both sources.
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
Match scanner findings to the managed endpoint.
- 02
Validate applicability and deploy the approved patches in a maintenance window.
- 03
Rescan the device and confirm the missing-patch findings have cleared.
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.