Subject, object, operation and permission
From Erights
(→See also) |
|||
| Line 12: | Line 12: | ||
== See also == | == See also == | ||
| + | |||
| + | During security audit, through permissions we should determine the [[authority]] of a given subject; because it is [[authority]] what ultimately matters. | ||
Description of similar notions can be found in Section 5.5 (Protection Mechanisms) in [http://www.amazon.com/Operating-Systems-Implementation-Prentice-Software/dp/0131429388/ref=sr_1_14?ie=UTF8&s=books&qid=1245137182&sr=8-14 The MINIX Book]. They use a term '''domain''' instead of '''subject'''. | Description of similar notions can be found in Section 5.5 (Protection Mechanisms) in [http://www.amazon.com/Operating-Systems-Implementation-Prentice-Software/dp/0131429388/ref=sr_1_14?ie=UTF8&s=books&qid=1245137182&sr=8-14 The MINIX Book]. They use a term '''domain''' instead of '''subject'''. | ||
Revision as of 08:42, 19 June 2009
Definition
From a security point of view, we recognize subjects and objects
Subjects are active entities (e.g. UNIX processes) with some behavior. Subjects can designate objects and try to perform some supported operations with them.
What kind of operations can be performed with an object depends on its type.
In general, the set of existing objects and subjects changes over time.
Permissions is a relation that defines which operations on what objects are permitted for particular subjects. One way how to capture permissions is the protection matrix.
See also
During security audit, through permissions we should determine the authority of a given subject; because it is authority what ultimately matters.
Description of similar notions can be found in Section 5.5 (Protection Mechanisms) in The MINIX Book. They use a term domain instead of subject.
