integrity
The guarantee that data has not been changed, by accident or on purpose, without the change being detected.
In more detail
Integrity is usually checked with hashes or digital signatures: if the data changes, its hash no longer matches. It is one of the three classic goals of information security, alongside confidentiality and availability.
Example
Git names every object by its hash, so a single changed byte changes the IDs of that commit and every commit after it.Related terms
- hash — A short fixed-length fingerprint calculated from data, which changes completely if even one byte of the data changes.
- object ID — The hash that names a Git object, such as a commit, and that you type to refer to it.
- content addressing — Storing and finding data by a hash of its content instead of by a name someone chose.
Taught in
- CIA Triad, Non-Repudiation & Parkerian Hexad — Cybersecurity Fundamentals, GRC & Cryptography
- Regulatory Compliance: SOC 2, HIPAA, GDPR & PCI-DSS — Cybersecurity Fundamentals, GRC & Cryptography
- Symmetric Encryption: AES-GCM & ChaCha20 — Cybersecurity Fundamentals, GRC & Cryptography
- Asymmetric Cryptography: RSA, ECC & Diffie-Hellman — Cybersecurity Fundamentals, GRC & Cryptography
- Cryptographic Hashing: SHA-256, SHA-3 & Passwords — Cybersecurity Fundamentals, GRC & Cryptography
- Privacy Principles, GDPR Subject Rights & Minimization — Cybersecurity Fundamentals, GRC & Cryptography
- Why Version Control, And Why Git Won — Advanced Git Internals & Distributed Workflows