Glossary
Vulnerability scan
Definition
An automated check for known security weaknesses in specified devices, software or services.
A scan is useful when its coverage is clear and findings lead to confirmed fixes. Validation, prioritisation and proof of remediation remain separate steps.
A customer may include “Vulnerability scan” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.
A vulnerability scan checks selected systems for signs of known weaknesses. A scanner may identify outdated software, exposed services or settings that match its checks. The result is a set of findings to investigate, not a guarantee that the system is safe.
A small online retailer might scan its public website from outside and scan staff computers using authenticated access. These checks see different things. An external scan cannot necessarily inspect the software and settings visible only after sign-in.
Findings need confirmation and prioritisation. A reported software version may be misleading, while a serious flaw may be missed if the scanner lacks access. Resolve the underlying problem and check again rather than treating delivery of a report as completion.
Define scope and credentialed coverage, review excluded systems and prioritise findings by exposure and impact. Track remediation to a verified fix; a scan is a point-in-time view, not proof that everything is secure. A scan is also different from a penetration test, which examines whether weaknesses can be combined or exploited within an agreed scope.
Sources: NIST: technical guide to information security testing and assessment.