What are the benefits of using a lattice-based access control model?

1 What is a lattice?

A lattice is a set of elements that are ordered by a relation called "less than or equal to". This relation means that for any two elements in the set, either one is less than or equal to the other, or they are incomparable. For example, the set of natural numbers is a lattice, where the relation is the usual arithmetic order. A lattice can also have a graphical representation, where the elements are nodes and the relation is shown by edges. The bottom element of a lattice is the one that is less than or equal to all other elements, and the top element is the one that is greater than or equal to all other elements.

3 What are the benefits of LBAC?

LBAC has several benefits over other access control models, such as the ability to support multiple security policies and domains within the same system by using different lattices for different types of information and subjects. It also provides fine-grained access control, allowing for the creation of custom security levels and categories that match specific needs and requirements. Furthermore, LBAC enforces strong confidentiality by preventing unauthorized information flow and leakage between different security levels and categories, which is also known as the *-property or the no-read-up and no-write-down property. Additionally, LBAC facilitates information sharing and collaboration by allowing subjects to access information objects at different security levels as long as they have the necessary clearance and need-to-know - a property referred to as tranquility.

4 How to implement LBAC?

LBAC can be implemented in various ways, depending on the architecture and design of the information system. For example, a reference monitor or security kernel can mediate all access requests and check them against the lattice of security levels and categories. Additionally, encryption and decryption techniques can encode and decode information objects and subjects according to their security levels and categories. Moreover, labels and tags can mark the information objects and subjects with their security levels and categories, enforcing the access policy based on the labels and tags. Finally, a database management system or file system that supports LBAC as a built-in feature or an extension can also be used.

5 How to design a lattice?

Careful analysis and planning is essential when designing a lattice for LBAC, as it can have an impact on the performance, usability, and security of the information system. It is important to consider the number and type of classifications and categories that are necessary for the system, as well as the size and complexity of the lattice. Additionally, one must evaluate the flexibility and granularity of the lattice to ensure that it allows for the creation and modification of security levels and categories. Finally, the confidentiality and integrity of the lattice must be ensured to prevent unauthorized changes and breaches of the access policy.

6 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?