A vulnerability scanner is software that probes hosts, networks, containers or web applications and compares what it finds against a database of known weaknesses and insecure settings. It produces a report of issues ranked by severity.
Why it matters
Manual checking cannot keep pace with the number of systems and published flaws. Regular scans give a repeatable view of exposure and help prove that patching works. Different types exist: network scanners enumerate services and versions, web application scanners test pages and forms, and dependency scanners check libraries used in code.
Example
A weekly authenticated scan of a server fleet lists an outdated web server version with a known flaw. The ticket links to the vendor advisory and a fixed version. After patching, a re-scan confirms the finding is closed. The same report notes a low-severity banner disclosure that is scheduled for the next cycle.
Common mistakes
- Treating a clean scan as proof of safety. Scanners miss logic flaws and unknown issues.
- Scanning systems you do not own or have no permission to test.
- Accepting every result without checking for false positives.
- Producing reports that nobody triages.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.