Database concurrency control in multilevel secure database management systems

Thomas F. Keefe, W. T. Tsai, Jaideep Srivastava

Research output: Contribution to journalArticle

29 Citations (Scopus)

Abstract

Transactions are vital for database management systems (DBMSs) because they provide transparency to concurrency and failure. Concurrent execution of transactions may lead to contention for access to data, which in a multilevel secure DBMS (MLS/DBMS) may lead to insecurity. In this paper we examine security issues involved in database concurrency control for MLS/DBMSs and show how a scheduler can affect security. We introduce Data Conflict Security, (DC-Security) a property that implies a system is free of convert channels due to contention for access to data. We present a definition of DC-Security based on noninterference. Two properties that constitute a necessary condition for DC-Security are introduced along with two other simpler necessary conditions. We have identified a class of schedulers we call Output-State-Equivalent for which another criterion implies DC-Security. The criterion considers separately the behavior of the scheduler in response to those inputs that cause rollback and those that do not. We characterize the security properties of several existing scheduling protocols and find many to be insecure.

Original languageEnglish
Pages (from-to)1039-1055
Number of pages17
JournalIEEE Transactions on Knowledge and Data Engineering
Volume5
Issue number6
DOIs
Publication statusPublished - Dec 1993
Externally publishedYes

Fingerprint

Concurrency control
Security of data
Transparency
Scheduling
Network protocols

ASJC Scopus subject areas

  • Artificial Intelligence
  • Information Systems
  • Control and Systems Engineering
  • Electrical and Electronic Engineering

Cite this

Database concurrency control in multilevel secure database management systems. / Keefe, Thomas F.; Tsai, W. T.; Srivastava, Jaideep.

In: IEEE Transactions on Knowledge and Data Engineering, Vol. 5, No. 6, 12.1993, p. 1039-1055.

Research output: Contribution to journalArticle

@article{669b51338c064403b060b0d59710860e,
title = "Database concurrency control in multilevel secure database management systems",
abstract = "Transactions are vital for database management systems (DBMSs) because they provide transparency to concurrency and failure. Concurrent execution of transactions may lead to contention for access to data, which in a multilevel secure DBMS (MLS/DBMS) may lead to insecurity. In this paper we examine security issues involved in database concurrency control for MLS/DBMSs and show how a scheduler can affect security. We introduce Data Conflict Security, (DC-Security) a property that implies a system is free of convert channels due to contention for access to data. We present a definition of DC-Security based on noninterference. Two properties that constitute a necessary condition for DC-Security are introduced along with two other simpler necessary conditions. We have identified a class of schedulers we call Output-State-Equivalent for which another criterion implies DC-Security. The criterion considers separately the behavior of the scheduler in response to those inputs that cause rollback and those that do not. We characterize the security properties of several existing scheduling protocols and find many to be insecure.",
author = "Keefe, {Thomas F.} and Tsai, {W. T.} and Jaideep Srivastava",
year = "1993",
month = "12",
doi = "10.1109/69.250090",
language = "English",
volume = "5",
pages = "1039--1055",
journal = "IEEE Transactions on Knowledge and Data Engineering",
issn = "1041-4347",
publisher = "IEEE Computer Society",
number = "6",

}

TY - JOUR

T1 - Database concurrency control in multilevel secure database management systems

AU - Keefe, Thomas F.

AU - Tsai, W. T.

AU - Srivastava, Jaideep

PY - 1993/12

Y1 - 1993/12

N2 - Transactions are vital for database management systems (DBMSs) because they provide transparency to concurrency and failure. Concurrent execution of transactions may lead to contention for access to data, which in a multilevel secure DBMS (MLS/DBMS) may lead to insecurity. In this paper we examine security issues involved in database concurrency control for MLS/DBMSs and show how a scheduler can affect security. We introduce Data Conflict Security, (DC-Security) a property that implies a system is free of convert channels due to contention for access to data. We present a definition of DC-Security based on noninterference. Two properties that constitute a necessary condition for DC-Security are introduced along with two other simpler necessary conditions. We have identified a class of schedulers we call Output-State-Equivalent for which another criterion implies DC-Security. The criterion considers separately the behavior of the scheduler in response to those inputs that cause rollback and those that do not. We characterize the security properties of several existing scheduling protocols and find many to be insecure.

AB - Transactions are vital for database management systems (DBMSs) because they provide transparency to concurrency and failure. Concurrent execution of transactions may lead to contention for access to data, which in a multilevel secure DBMS (MLS/DBMS) may lead to insecurity. In this paper we examine security issues involved in database concurrency control for MLS/DBMSs and show how a scheduler can affect security. We introduce Data Conflict Security, (DC-Security) a property that implies a system is free of convert channels due to contention for access to data. We present a definition of DC-Security based on noninterference. Two properties that constitute a necessary condition for DC-Security are introduced along with two other simpler necessary conditions. We have identified a class of schedulers we call Output-State-Equivalent for which another criterion implies DC-Security. The criterion considers separately the behavior of the scheduler in response to those inputs that cause rollback and those that do not. We characterize the security properties of several existing scheduling protocols and find many to be insecure.

UR - http://www.scopus.com/inward/record.url?scp=0027848097&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=0027848097&partnerID=8YFLogxK

U2 - 10.1109/69.250090

DO - 10.1109/69.250090

M3 - Article

AN - SCOPUS:0027848097

VL - 5

SP - 1039

EP - 1055

JO - IEEE Transactions on Knowledge and Data Engineering

JF - IEEE Transactions on Knowledge and Data Engineering

SN - 1041-4347

IS - 6

ER -