Glossary
Zero-day
Definition
A zero-day vulnerability is a security weakness unknown to its vendor when attackers discover or exploit it.
The term concerns previously unknown flaws. An old vulnerability left unpatched is a different problem, even when it remains dangerous.
A customer may include “Zero-day” 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 zero-day vulnerability is a security weakness that is not yet known to the responsible vendor when discovered or exploited by attackers. A zero-day exploit is a way of using that weakness; a zero-day attack is an actual attempt to do so. The terms are related but describe different things.
A fix may not be available when exploitation begins, leaving customers to reduce exposure or apply temporary measures. An already known weakness does not become a zero-day simply because a particular business has not installed its update. The timing of discovery and disclosure matters.
Hypothetical example: a provider warns a small law firm that attackers are exploiting a previously unknown flaw in its remote-access product. Until a fix is released, the firm follows the provider's instructions to disable an affected feature and uses an alternative working process.
Maintain an inventory of exposed services and a route for urgent supplier notices. Check whether the affected feature is enabled and which temporary safeguards reduce exposure. General endpoint protection or a vulnerability scan may not detect a new attack. Once a fix exists, installation and verification still require an owner; publicity around the flaw does not close it.
Sources: NIST zero-day attack definition; Microsoft Security Response Center glossary.