HRU (security)

From HandWiki
Revision as of 00:55, 17 November 2021 by imported>Jworkorg (url)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

The HRU security model (Harrison, Ruzzo, Ullman model) is an operating system level computer security model which deals with the integrity of access rights in the system. It is an extension of the Graham-Denning model, based around the idea of a finite set of procedures being available to edit the access rights of a subject [math]\displaystyle{ s }[/math] on an object [math]\displaystyle{ o }[/math]. It is named after its three authors, Michael A. Harrison, Walter L. Ruzzo and Jeffrey D. Ullman.[1]

Along with presenting the model, Harrison, Ruzzo and Ullman also discussed the possibilities and limitations of proving the safety of systems using an algorithm.[1]

Description of the model

The HRU model defines a protection system consisting of a set of generic rights R and a set of commands C. An instantaneous description of the system is called a configuration and is defined as a tuple [math]\displaystyle{ (S,O,P) }[/math] of current subjects [math]\displaystyle{ S }[/math], current objects [math]\displaystyle{ O }[/math] and an access matrix [math]\displaystyle{ P }[/math]. Since the subjects are required to be part of the objects, the access matrix contains one row for each subject and one column for each subject and object. An entry for subject [math]\displaystyle{ s }[/math] and object [math]\displaystyle{ o }[/math] is a subset of the generic rights [math]\displaystyle{ R }[/math].

The commands are composed of primitive operations and can additionally have a list of pre-conditions that require certain rights to be present for a pair [math]\displaystyle{ (s,o) }[/math] of subjects and objects.

The primitive requests can modify the access matrix by adding or removing access rights for a pair of subjects and objects and by adding or removing subjects or objects. Creation of a subject or object requires the subject or object not to exist in the current configuration, while deletion of a subject or object requires it to have existed prior to deletion. In a complex command, a sequence of operations is executed only as a whole. A failing operation in a sequence makes the whole sequence fail, a form of database transaction.

Discussion of safety

Harrison, Ruzzo and Ullman[1] discussed whether there is an algorithm that takes an arbitrary initial configuration and answers the following question: is there an arbitrary sequence of commands that adds a generic right into a cell of the access matrix where it has not been in the initial configuration?

They showed that there is no such algorithm, thus the problem is undecidable in the general case. They also showed a limitation of the model to commands with only one primitive operation to render the problem decidable.

See also

References

  1. 1.0 1.1 1.2 Harrison, Michael A.; Ruzzo, Walter L.; Ullman, Jeffrey D. (August 1976). "Protection in Operating Systems". Communications of the ACM 19 (8): 461–471. doi:10.1145/360303.360333.