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.sha256
entry 0: published cf7cd4bf7343, recomputed 1dcae8da6c2e broken

Related terms

Taught in

References