Questions about this topic? Sign up to ask in the talk tab.
Difference between revisions of "Zero-day"
From NetSec
m (moved Zero-Day attack to Zero-day) |
|||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
A '''zero-day attack''', or 0day attack, occurs on the 0th day when a [[vulnerability]] is discovered an affects an [[application]] in such a way that the security industry has never seen before, attacking the [[application]] before it can be [[patched]]. Large-scale zero-day attacks are typically pre-distributed and set in motion before the attack actually takes place, granting maximum effectiveness between the initial attack and successful patch. | A '''zero-day attack''', or 0day attack, occurs on the 0th day when a [[vulnerability]] is discovered an affects an [[application]] in such a way that the security industry has never seen before, attacking the [[application]] before it can be [[patched]]. Large-scale zero-day attacks are typically pre-distributed and set in motion before the attack actually takes place, granting maximum effectiveness between the initial attack and successful patch. | ||
| + | |||
| + | {{expand}} | ||
Revision as of 07:28, 9 May 2012
A zero-day attack, or 0day attack, occurs on the 0th day when a vulnerability is discovered an affects an application in such a way that the security industry has never seen before, attacking the application before it can be patched. Large-scale zero-day attacks are typically pre-distributed and set in motion before the attack actually takes place, granting maximum effectiveness between the initial attack and successful patch.
| This article contains too little information, it should be expanded or updated. |
|---|
Things you can do to help:
|
