Abstract
Multilevel security requirements introduce a new dimension to traditional database concurrency control protocol as they cause covert channels. To prevent covert channels, concurrency control protocol for multilevel secure database should ensure that transactions at low security level are never delayed by high security level transactions in the event of a data conflict. This may subjected to an indefinite delay if it is forced to abort repeatedly to high security level transactions and making the secure concurrency control protocol unfair towards high security level transactions (Kaur et al., 2005). This paper proposes secure multiversion database concurrency control protocol that is free from covert channels without starving the high security level transactions that may often occur in pervious works.
Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
