Skip to main navigation Skip to search Skip to main content

Mitigating insider threat without limiting the availability in concurrent undeclared tasks

  • University of Arkansas System

Research output: Chapter in Book/Report/Conference proceeding › Conference contribution › peer-review

Abstract

Insider threat is a critical problem due to the immense harm that it poses to organizations. This paper investigates this problem in relational database systems. Generally, defending systems against insider threat may require rejecting insiders' requests to access some data items. The paper focuses on preventing unauthorized knowledge acquisition by insiders in concurrent undeclared tasks, where a task is executed as one operation at a time instead of a batch of operations, without affecting the availability of data items. It proposes approaches to predict the complete operations of undeclared tasks, and then, to organize the operations in a safe sequence that prevents the possible threat of insiders without rejecting any request. Theorems, proofs and simulations are provided to show the effectiveness of the proposed approaches.

Original languageEnglish
Title of host publicationProceedings of the 2012 IEEE 6th International Conference on Software Security and Reliability, SERE 2012
Pages235-244
Number of pages10
DOIs
StatePublished - 2012
Externally publishedYes
Event2012 IEEE 6th International Conference on Software Security and Reliability, SERE 2012 - Gaithersburg, MD, United States
Duration: 20 Jun 2012 → 22 Jun 2012

Publication series

NameProceedings of the 2012 IEEE 6th International Conference on Software Security and Reliability, SERE 2012

Conference

Conference2012 IEEE 6th International Conference on Software Security and Reliability, SERE 2012
Country/TerritoryUnited States
CityGaithersburg, MD
Period20/06/12 → 22/06/12

Keywords

  • Database
  • Dependencies
  • Insider threat
  • Security

Fingerprint

Dive into the research topics of 'Mitigating insider threat without limiting the availability in concurrent undeclared tasks'. Together they form a unique fingerprint.

Cite this