Zero-Day
In , including the security of systems, “zero-day” is ambiguous: —flaw unknown to responsible maintainers; —technique exploiting such a flaw; or —attack using such an exploit. The term does not require recent discovery, and an unpatched flaw is not automatically a zero-day. In pipelines, , , and infrastructure can be targets of security attacks, potentially compromising or enabling ; these are security concerns, not a distinct machine-learning meaning of zero-day. and use to investigate vulnerabilities and unsafe behaviors in , but and are attack classes, not inherently zero-day exploits. Mitigation may involve , , compensating controls, or vendor fixes; AI-powered is not a defining element of zero-day defense. Mitigation does not require or need to await a identifier, which may be assigned before or after disclosure.
[PREVIEW MODE] Definitions streamed at five depths, references, and related terms are available to signed-in readers — [SIGN IN]
Contextual terminology map
KEEP IN VIEW
Ethics, safety & society
Moving as fast as the field, and easier to overlook
- Explainable AI
- Interpretability
- Model Card
- AI Audit
- Algorithmic Bias
- Disparate Impact
- Digital Divide
- WCAG (Web Content Accessibility Guidelines)
- AI Alignment
- Red Teaming
- EU AI Act
- NIST AI RMF (AI Risk Management Framework)
- Frontier Model
- Deepfake
- Content Credentials
- AI Watermarking
- Job Displacement
- Prompt Injection
- Data Poisoning
- Differential Privacy
- GDPR (General Data Protection Regulation)
- Zero-Day
- End-to-End Encryption
- Data Broker
Infrastructure, markets & the economy
The compute, power and capital behind the boom