A vulnerability was found, and you've implemented a fix by installing an update, patch, or making a configuration change. Phew! We're done, right?
Our Portal allows you to accept or mark a vulnerability as resolved manually. This way you have control over the status of a vulnerability and note your changes for audit logs. However, to keep large environments safe, it can be time-consuming to mark each vulnerability as resolved.
Your scanner will automatically mark vulnerabilities as resolved at the following scan when it tested a vulnerability but couldn't find it again. An example:
Your webserver is running on ports 80/TCP and 443/TCP. A sensitive file is found on /phpinfo.php and our Portal marks this as a vulnerability. You implement a patch resulting in /phpinfo.php becoming unreachable via port 80/TCP, but it's still reachable via port 443/TCP. Your scanner will mark the vulnerability on port 80/TCP as resolved, but 443/TCP will stay unresolved.
Rules for automatically marking vulnerabilities as resolved
The following rules must apply for a scanner to automatically mark vulnerabilities as resolved:
The vulnerability still exists in the vulnerability database.
The vulnerability was tested against the device.
The vulnerability has not been found on this port on this host.