Tampering

In practice, prevention and detection are both important. A related concept is Tamper Resistance.

What to Watch in Practice

Tampering names the attack or unauthorized modification side, not the defensive design property. It is useful when talking about binary edits, parameter changes, local data rewrites, or other forms of untrusted manipulation as one class of risk.

In practice, the important question is how much the system assumes tampering can happen. It is usually more realistic to decide where it should be detected and what must stop being trusted after modification rather than pretending perfect prevention is available.

Practical Note

Tampering usually appears in contexts related to security, tampering, integrity. In practice, it helps to know not only the definition, but also what this term is trying to name quickly in a conversation, design note, or document.

Nearby words often overlap and make the explanation fuzzy. It is easier to use the term well when the target, role, and typical situation are kept one step more concrete.

Reading Note

The easiest way to read this term is to look at three things first: what it is about, what nearby concept it should be separated from, and what kind of decision it usually supports. For Tampering, the security, tampering, integrity context is already a good starting point.

It also helps not to stop at the definition alone. The more useful view is to see what the term is trying to name quickly inside a working conversation.