Multiversion concurrency control for multilevel secure database systems

Keefe, T.F.; Tsai, Wei Tek

doi:10.1109/risp.1990.63865

Cited by 66 publications

(27 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In [KT90], a scheduler is proposed which is secure and produces one-copy serializable histories to which our model can be applied. However, it uses a multilevel scheduler which, therefore, has to be trusted, thus it is only suitable for the trusted subject architecture.…”

Section: Fix Information Maintenancementioning

confidence: 99%

Trusted Recovery from Information Attacks

Jajodia¹,

Ammann²,

Liu³

2001

View full text Add to dashboard Cite

Section: Fix Information Maintenancementioning

confidence: 99%

Trusted Recovery from Information Attacks

Jajodia¹,

Ammann²,

Liu³

2001

View full text Add to dashboard Cite

“…The architecture for the systems under consideration is based on one that is frequently proposed [7,8]. The security features are enforced by a security kernel, the trusted computing base of the trusted operating system, together with whatever additional trusted processes are necessary in the database application to enforce the overall system's security policy.…”

Section: The Security Modelmentioning

confidence: 99%

“…There is a set D of data items of the database system that serve as the objects of the multilevel system. The subjects of the system, denoted Sub, are quite similar to the single-level transactions used in earlier work [3,6,7,8,9,10]. However our transactions will be more complex and will be formed by interleaving the subjects of the database system.…”

Section: The Security Modelmentioning

confidence: 99%

Maintaining Multilevel Transaction Atomicity in MLS Database Systems with Kernelized Architecture

Costich¹,

Kang²

1993

View full text Add to dashboard Cite

In most models of trusted database systems, transactions are considered to be single-level subjects. As a consequence, users are denied the ability to execute some transactions which can be run on conventional (untrusted) database systems, namely those that perform functions that become inherently multilevel in the MLS environment. This paper introduces a notion of multilevel transaction and proceeds to an algorithm for their concurrent execution. The algorithm is proven to be correct in the sense that resulting schedules for executing the multilevel transactions is one-copy serializable.

show abstract

“…Further work was carried out by Keefe and Tsai [KEEF90]. The algorithm developed was based on multiversion schedulers.…”

Section: Multiversion Algorithmsmentioning

confidence: 99%