corruption
Damage to stored or transmitted data that leaves it wrong, incomplete or unreadable.
In more detail
Corruption can come from failing disks, software bugs, interrupted writes, bad memory or a faulty update, as well as from deliberate tampering. It is dangerous because it may go unnoticed for a long time and then be copied into every backup. Checksums and hashes detect it, and versioned backups kept long enough let you restore a copy from before the damage began.
Example
An update that corrupts a table is one of the three events backups must answer, alongside deletion and ransomwareRelated terms
- integrity — The guarantee that data has not been changed, by accident or on purpose, without the change being detected.
- checksum — A small value calculated from data and stored or sent with it, so the data can later be checked for accidental errors.
- backup — An extra copy of data kept separately so it can be restored if the original is lost, damaged, deleted or encrypted by an attacker.
- hash — A short fixed-length fingerprint calculated from data, which changes completely if even one byte of the data changes.
Taught in
- Cryptographic Hashing: SHA-256, SHA-3 & Passwords — Cybersecurity Fundamentals, GRC & Cryptography
- Backup Architectures: 3-2-1, Immutability & Air-Gaps — Cybersecurity Fundamentals, GRC & Cryptography