Views for Multilevel Database Security

Abstract

Abstract-Because views on relational database systems mathematically define arbitrary sets of stored and derived data, they have been proposed as a way of handling context-and content-dependent classification, dynamic classification, inference, aggregation, and sanitization in multilevel database systems. This paper describes basic view concepts for a multilevel-secure relational database model that addresses the above issues. All data entering the database are labeled according to views called classification constraints, which specify access classes for related data. In addition, views called aggregation constraints restrict access to aggregates of information. All data accesses are confined to a third set of views called access views.

An efficient key assignment scheme for access control in a large leaf class hierarchy

“…In most social organizations, such as companies, governments and militaries, the employees are divided into different security classes according to their positions and access authorities [3,6,7,14,15,17,19,22,29,30]. The access control privilege is assigned into different privileged classes as a user tree-structure.…”

Intrusion detection using hierarchical neural networks

“…A rule-based expert IDS can detect some well-known intrusions with high detection rate, but it is difficult to detect novel intrusions, and its signature database needs to be updated manually and frequently (Lindqvist and Porras, 1999;Denning and Dorothy, 1987;Michael, 2002). A statistical-based IDS needs to collect enough data to build a complicated mathematical model, which is impractical in the case of complicated network traffic (Gordeev, 2000).…”

The SeaView security model

“…The SeaView policy requires that users be able to specify rules, called classification constraints [3], that define how information entering the system is to be assigned an access class. Classification constraints are similar to value constraints, except that they restrict the access classes of data elements rather than their values.…”

“…The project began by investigating how basic view concepts could be used for specifying instances of multilevel relations a t different access classes, for discretionary access control, for assigning labels to new data (through classification constraints), and for sanitization [3]. This investigation then led to the security policy and policy interpretation, to a basic strategy for a system design, to a multilevel relational data model 141, and to a formal security policv model that incorporates the essential security features of the multilevel relational data model (51.…”