Tampering with Data Threats
What you'll learn: How attackers can modify data without authorization to break system integrity and trust.
What is Tampering?
Tampering threats involve unauthorized modification of data — changing information that should remain accurate and trustworthy. This directly attacks the "I" in the CIA Triad: Integrity. Remember, integrity means data stays correct, complete, and unaltered by unauthorized parties.
Attackers can tamper with data in three places:
- At rest — modifying files stored on disk, database records, or configuration files
- In transit — altering network packets as they travel between systems across your trust boundaries
- In memory — changing values in RAM while a program runs
Why Tampering Matters
Think of tampering like someone rewriting pages in a medical chart. If lab results are altered, doctors make wrong decisions. The same applies to software: modified prices in a shopping cart, changed account balances, or altered log files covering tracks.
When you create a Data Flow Diagram (DFD), look at every data store and communication channel. Ask: "Could an attacker with access to this trust boundary modify this data?"
Real-World Examples
- Changing the price in a web request before checkout
- Modifying a configuration file to grant yourself admin privileges
- Altering log entries to hide evidence of an attack
- Intercepting and changing bank transfer amounts on the network
Defense Approaches
To counter tampering, use compensating controls like:
- Digital signatures to detect modifications
- Access controls following Least Privilege
- Encryption protecting data in transit
- Input validation and Complete Mediation to verify all data
Key Takeaway: Tampering threats target data integrity by unauthorized modification; identify where attackers could alter data at rest, in transit, or in memory, then apply controls to detect or prevent changes.