Issues in distributed database security

Downing, Alan; Greenberg, I.B.; Lunt, Teresa F.

doi:10.1109/csac.1989.81051

Cited by 9 publications

(5 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This approach allows a simple and uniform model of a scheduler for a large class of scheduling protocols.We can also imagine scheduling being carried out by several untrusted schedulers, each one scheduling the actions of subjects at a single classification level. This is the approach taken in [4], [7], [15], [23], and [28]. Adopting this approach can simplify arguments about the security of scheduling.…”

Section: Researchm Ethodologymentioning

confidence: 99%

“…Several untrusted schedulers have been proposed. In [7], the authors suggest modifications to the optimistic scheduling protocol [20] for use in MLS/DBMS"s. In [20], two variations on the optimistic approach are described; they are serial validation and parallel validation. Both approaches make use of at least one critical section.…”

Section: Ansari Et Al International Journal Of Advanced Research Inmentioning

confidence: 99%

See 1 more Smart Citation

Survey on Database Concurrency Control in Multilevel Secure Database Management Systems

Ansari

Vishwakarma

2018

IJARCSSE

View full text Add to dashboard Cite

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 (MLSIDBMS) 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

show abstract

Section: Researchm Ethodologymentioning

confidence: 99%

Section: Ansari Et Al International Journal Of Advanced Research Inmentioning

confidence: 99%

Survey on Database Concurrency Control in Multilevel Secure Database Management Systems

Ansari

Vishwakarma

2018

IJARCSSE

View full text Add to dashboard Cite

show abstract

“…Designing scalable system for supporting extremely large number of requests caring about security issues is stated by Alan R. Downing [6]. Privacy is another important feature for such important data because of its static nature like fingerprint and iris scan etc.…”

Section: Related Workmentioning

confidence: 99%

An Efficient Model for Securing Identity Access in Scalable System

Singh¹,

Kumar²,

Das³

2013

IJCA

View full text Add to dashboard Cite

This paper proposes an identity management system model which will ensure secure storage and retrieval of the IDs information in the scalable identity database. The proposed model uses the distributed database technology for information storage and retrieval to make the system more reliable. The IDs information storage is secured by using cryptography mechanism of data conversion in the identity database. Authenticated link by internet service providers is used for secure communication of the user information between the authenticated service agencies/ user service providers and the Identity server. For retrieval of the user sensitive information, this paper proposes an access method based on request and authorization of the service provider.

show abstract

“…A number of secure concurrency control techniques have been prop0~d ifl the literature which address the problem of covert timing channels. Some of these works [12,7] that employ a lock based protocol on single version data, abort a higher level transaction Ti that is reading down, when a lower level updating transaction Tj conflicts with T~. The drawback of these protocols is that transactions that read down may be subject to starvation.…”

Section: Introductionmentioning

confidence: 99%

Secure concurrency control in MLS databases with two versions of data

Mancini

Ray

1996

Computer Security — ESORICS 96

View full text Add to dashboard Cite

In multilevel secure database systems, higher level transactions are either delayed or aborted when they read lower level data, due to lock conflicts with updating lower level transactions. Multiversion data has been suggested in the literature as a way to prevent lower reading transaction from getting delayed or aborted. In these multiversion protocols transactions that read lower level data are provided older versions of the data and thus low reading and writing operations are allowed to proceed concurrently. However almost all of these algorithms suffer from shortcomings -either they require a potentially unbounded number of versions to be maintained in the system, or they enforce a time limit in which higher level transactions have to complete. Maintaining multiple committed versions adds additional overhead to the system. Moreover, these algorithms always provide older copies of data for reading by higher level transactions which may not be acceptable for certain applications. We propose a secure concurrency control algorithm that is based on a locking strategy and that requires only two versions -one committed and one non-committed version -of data. All read operations, high or low, are performed on the previous committed version while the write operation proceeds on the uncommitted version. Thus no read operation is ever given an outdated copy. Moreover, extra overhead for version management is lesser than the other protocols because almost all transaction management systems maintains a before-image of data for recovery purposes and our scheme takes advantage of this before-image value.

show abstract

Issues in distributed database security

Cited by 9 publications

References 15 publications

Survey on Database Concurrency Control in Multilevel Secure Database Management Systems

Survey on Database Concurrency Control in Multilevel Secure Database Management Systems

An Efficient Model for Securing Identity Access in Scalable System

Secure concurrency control in MLS databases with two versions of data

Contact Info

Product

Resources

About