Editing Biba Model

The '''Biba Model''' or '''Biba Integrity Model''' developed by Kenneth J. Biba in 1975,<ref>Biba, K. J.  "Integrity Considerations for Secure Computer Systems",  [http://seclab.cs.ucdavis.edu/projects/history/papers/biba75.pdf MTR-3153], The [[Mitre Corporation]], June 1975.</ref> is a formal [[state transition system]] of [[computer security]] policy describing a set of [[access control]] rules designed to ensure [[data integrity]].  Data and subjects are grouped into ordered levels of integrity.  The model is designed so that subjects may not corrupt data in a level ranked higher than the subject, or be corrupted by data from a lower level than the subject.

In general the model was developed to address integrity as the core principle, which is the direct inverse of the [[Bell–LaPadula model]] which focuses on confidentiality.{{Ref RFC|4949|notes=no|rp=35}}

== Features ==
In general, preservation of data ''integrity'' has three goals:

* Prevent data modification by unauthorized parties
* Prevent unauthorized data modification by authorized parties
* Maintain internal and external consistency (i.e. data reflects the real world)

This security model is directed toward data ''integrity'' (rather than ''confidentiality'') and is characterized by the phrase: "read up, write down". This is in contrast to the Bell-LaPadula model which is characterized by the phrase "read down, write up".

In the Biba model, users can only ''create content at or below'' their own integrity level (a monk may write a prayer book that can be read by commoners, but not one to be read by a high priest).  Conversely, users can only ''view content at or above'' their own integrity level (a monk may read a book written by the high priest, but may not read a pamphlet written by a lowly commoner).  Another analogy to consider is that of the military [[command hierarchy|chain of command]].  A General may write orders to a Colonel, who can issue these orders to a Major.  In this fashion, the General's original orders are kept intact and the mission of the military is protected (thus, "read up" integrity).  Conversely, a Private can never issue orders to his Sergeant, who may never issue orders to a Lieutenant, also protecting the integrity of the mission ("write down").

The Biba model defines a set of security rules, the first two of which are similar to the [[Bell–LaPadula model]]. These first two rules are the reverse of the Bell–LaPadula rules:

# The Simple Integrity Property states that a subject at a given level of integrity must not read data at a lower integrity level (''no read down'').
# The * (star) Integrity Property states that a subject at a given level of integrity must not write to data at a higher level of integrity (''no write up'').<ref>{{Cite book|title=All in One CISSP Exam Guide|last=Harris|first=Shon|publisher=McGraw-Hill|year=2013|location=New York|pages=372}}</ref>
# Invocation Property states that a process from below cannot request higher access; only with subjects at an equal or lower level.

== Implementations ==
* In [[FreeBSD]], the Biba model is implemented by the mac_biba MAC policy.<ref>{{Cite web|url=http://man.freebsd.org/mac_biba|title = Mac_biba}}</ref>
* In [[Linux]], the Biba model is implemented in the General Dynamics Mission Systems PitBull product.
* In [[XTS-400]], the Biba model is implemented in the BAE Systems's XTS-400 operating system.

== See also ==
* [[Discretionary access control|Discretionary Access Control]] – DAC
* [[Graham–Denning model]]
* [[Mandatory access control|Mandatory Access Control]] – MAC
* [[Multilevel security]] – MLS
* [[Security-Enhanced Linux]]
* [[Security modes|Security Modes of Operation]]
* [[Take-grant protection model]]
* [[Clark–Wilson model]]
* [[Bell–LaPadula model]]

==References==
{{Reflist}}

== External links ==
* [http://cs.uccs.edu/~cs691/confidentialityPolicyies/IntegrityPolicy.ppt "Integrity Policies" PowerPoint presentation from University of Colorado at Colorado Springs]

[[Category:Computer security models]]