Biba Model: Integrity Protection
What you'll learn: How the Biba Model prevents low-quality or untrusted information from corrupting high-integrity data through simple read/write rules.
The Core Problem
You've learned about the Bell-LaPadula Model, which protects confidentiality by controlling who can read secrets. The Biba Model solves the opposite problem: protecting integrity by preventing unreliable data from contaminating trusted information.
Think of integrity levels like water quality grades: bottled spring water (high integrity) vs. puddle water (low integrity). You don't want puddle water mixing into your drinking supply.
The Two Rules
Biba enforces integrity with two mirror-opposite rules to Bell-LaPadula:
-
No Read Down – You cannot read data below your integrity level
- Why? Reading low-integrity data might mislead you or corrupt your judgment
- Example: A financial auditor (high integrity) shouldn't base reports on unverified social media posts (low integrity)
-
No Write Up – You cannot write data to a higher integrity level than yours
- Why? You might contaminate high-integrity resources with unreliable information
- Example: An untrusted user process shouldn't be allowed to modify critical system files
Real-World Analogy
Imagine a hospital pharmacy:
- High integrity: Sterile medications ready for patients
- Low integrity: Unverified supplies from an unknown vendor
No Read Down: Pharmacists don't use unverified ingredients in sterile preparations.
No Write Up: Untrusted vendors can't add items directly to the sterile medication shelf.
This prevents contamination flowing upward from less-trusted sources.
Key Takeaway: The Biba Model protects integrity by blocking low-integrity subjects from corrupting high-integrity data—preventing reads down and writes up to maintain trust in critical information.