Glossary
Vulnerability
Definition
A weakness in a system, process or security control that could be exploited or triggered to cause harm.
Weaknesses may exist in software, configuration or work processes. Whether a vulnerability needs immediate action depends on exposure, affected systems and likely consequences.
A customer may include “Vulnerability” 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 is a weakness that could let something go wrong. It may be a software flaw, an exposed administrative page or a process that allows a payment change without checking who requested it. Discovering a vulnerability does not, by itself, mean someone has used it.
For example, a small retailer might discover that its booking software still allows former employees to sign in. The weakness is the access left behind. Someone using that access to export customer records would be an incident.
Deciding what to fix first requires context. Consider whether the affected service is exposed, what an attacker could reach and whether a practical fix exists. A long list of findings gives little direction unless someone owns those decisions.
Match a reported weakness to the product, version, configuration and exposure in use. Apply a fix or temporary mitigation, then verify the system again; an unresolved issue needs an owner and review date. A clean scan cannot prove that every possible weakness has been found.
Sources: NIST: vulnerability.