Beyond "not tampered with," what are the four sub-states that make up data integrity?

Integrity isn't just "unaltered" — it splits into correct content, unmodified state, detection of modification, and temporal correctness.

In data protection, integrity is richer than a single "hasn't been changed" check. It breaks into four distinct guarantees:

1. Correct content — the data accurately represents the real-world facts it claims to (the value is right, not just unchanged).
2. Unmodified state — messages are delivered and processes run exactly as intended, without unauthorized alteration in transit or storage.
3. Detection of modification — where changes can't be prevented, they can at least be detected (e.g. via hashes, checksums, signatures), so tampering doesn't go unnoticed.
4. Temporal correctness — timing, ordering, and maximum-delay constraints are respected (a correct message delivered too late, or out of order, can still break integrity).

Tip: "Integrity = unchanged" is the beginner's version. The full picture also asks: is it correct, can we notice if it changes, and did it arrive on time and in order?