tamper-evident
Built so that any unauthorised change leaves visible signs, even if the change itself cannot be prevented.
In more detail
Tamper evidence does not stop someone editing data or opening a device; it makes sure the edit is noticed. In software this usually means storing hashes, signatures or authentication tags somewhere the attacker cannot rewrite, and chaining hashes so that one edit breaks every later link. Audit evidence, backups and logs are made tamper-evident so their integrity can be proved later.
Examples
sha256sum -c manifest.sha256entry 0: published cf7cd4bf7343, recomputed 1dcae8da6c2e brokenRelated terms
- hash chain — A sequence of records in which each hash covers the previous hash as well as the new data, so changing any earlier record changes every hash after it.
- evidence sealing — Recording a cryptographic hash of collected evidence at a fixed moment, so that any later change to the files can be detected.
- integrity — The guarantee that data has not been changed, by accident or on purpose, without the change being detected.
- digest — The short, fixed-size output of a hash function, which acts as a fingerprint of the input data.
Taught in
- Symmetric Encryption: AES-GCM & ChaCha20 — Cybersecurity Fundamentals, GRC & Cryptography
- Cryptographic Hashing: SHA-256, SHA-3 & Passwords — Cybersecurity Fundamentals, GRC & Cryptography
- Backup Architectures: 3-2-1, Immutability & Air-Gaps — Cybersecurity Fundamentals, GRC & Cryptography
- Internal Audits, Sampling & Evidence Chains — Cybersecurity Fundamentals, GRC & Cryptography