Editing Data loss (section)

==Types==
*''Procedural''
* ''Intentional action''
** Intentional deletion of a file or program
* ''Unintentional action''
** Accidental deletion of a file or program
** Misplacement of physical storage media
** Administration errors
** Inability to read unknown file format
* ''Failure''
** [[Power failure]], resulting in data in volatile memory not being saved to permanent memory.
** Hardware failure, such as a [[head crash]] in a hard disk.
** A software [[crash (computing)|crash]] or freeze, resulting in data not being saved.
** Software bugs or poor [[usability]], such as not confirming a file delete command.
** Business failure (vendor bankruptcy), where data is stored with a software vendor using [[Software-as-a-service]] and [[SaaS data escrow]] has not been provisioned.
** [[Data corruption]], such as file system corruption or database corruption.
* ''Disaster''
** [[Natural disaster]], [[earthquake]], [[flood]], [[tornado]], etc.
** [[Fire]]
* ''Crime''
** Theft, hacking, SQL injection, sabotage, etc.
** A malicious act, such as a [[computer worm|worm]], [[computer virus|virus]], [[Ransomware]], [[Hacker (computer security)|hacking]] or theft of [[physical media]].

Studies show hardware failure and human error are the two most common causes of data loss, accounting for roughly three quarters of all incidents.<ref>[http://gbr.pepperdine.edu/033/dataloss.html The cost of lost data] - Graziadio Business Report</ref> Another cause of data loss is a natural disaster, which is a greater risk dependent on where the hardware is located. While the probability of data loss due to natural disaster is small, the only way to prepare for such an event is to store backup data in a separate physical location. As such, the best backup plans always include at least one copy being stored off-site.<ref>{{Cite web|url = http://blog.trendmicro.com/trendlabs-security-intelligence/world-backup-day-the-3-2-1-rule/|title = World Backup Day: The 3-2-1 Rule|date = 2 April 2013|access-date = 29 April 2015|website = TrendLabs Security Intelligence Blog|publisher = Trend Micro|last = Leopando|first = Jonathan}}</ref>