Bell-LaPadula and Biba Models
What you'll learn: The two foundational theoretical models that formalize Mandatory Access Control (MAC) for confidentiality and integrity.
You've seen how MAC uses security labels and clearances to enforce system-wide policies. Now meet the mathematical frameworks that define how those policies work.
Bell-LaPadula Model: Protecting Confidentiality
The Bell-LaPadula (BLP) model prevents information from flowing from higher security levels to lower ones. Think of it like classified government documents.
Core rules:
- No Read Up (Simple Security): You cannot read data at a higher classification than your clearance. A "Secret" user cannot read "Top Secret" files.
- No Write Down (*-property): You cannot write data to a lower classification. A user handling "Top Secret" data cannot save it to a "Secret" location.
The goal is confidentiality: prevent sensitive information from leaking downward to less-trusted levels.
Biba Model: Protecting Integrity
The Biba model is BLP's mirror image, focused on data integrity rather than secrecy. Think of it like protecting critical system files from untrusted sources.
Core rules:
- No Read Down (Simple Integrity): You cannot read data at a lower integrity level (prevents contamination by untrusted data).
- No Write Up (Integrity *-property): You cannot write to higher integrity levels (prevents corruption of trusted data).
The goal is integrity: prevent untrusted or corrupted information from polluting higher-trust systems.
Real-World Application
In hardened systems like SELinux, these models inform policy design. A high-integrity system process cannot be modified by lower-integrity user processes (Biba). Sensitive user data cannot be read by lower-clearance services (BLP).
Key Takeaway: Bell-LaPadula prevents confidential data from leaking downward; Biba prevents untrusted data from corrupting upward. Together, they formalize the mathematical foundation of MAC security policies.