2009 Sixth International Conference on Information Technology: New Generations 2009
DOI: 10.1109/itng.2009.67
|View full text |Cite
|
Sign up to set email alerts
|

Insider Threat in Database Systems: Preventing Malicious Users' Activities in Databases

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
22
0

Year Published

2010
2010
2018
2018

Publication Types

Select...
5
2

Relationship

1
6

Authors

Journals

citations
Cited by 28 publications
(22 citation statements)
references
References 5 publications
0
22
0
Order By: Relevance
“…In [10], SQL statements are summarized as regular expressions, which are then considered "fingerprints" for legitimate transactions. In [11,12,13], database transactions are represented by directed graphs describing execution paths (select, insert, delete etc.) and these are used for malicious data access detection.…”
Section: Related Workmentioning
confidence: 99%
“…In [10], SQL statements are summarized as regular expressions, which are then considered "fingerprints" for legitimate transactions. In [11,12,13], database transactions are represented by directed graphs describing execution paths (select, insert, delete etc.) and these are used for malicious data access detection.…”
Section: Related Workmentioning
confidence: 99%
“…McCormick assesses the threat of confidential data leakage, focusing on its most virulent form --insider data theft attacks [16]. Chagarlamudi et al present a model that can prevent malicious insider activities at the database application level [17]. Jabbour and Menasce present the Insider Threat Security Architecture (ITSA) and a security scenario where privileged users can compromise the system that they protect, and they discuss ways in which that same scenario can be mitigated under the ITSA framework [18].…”
Section: Related Workmentioning
confidence: 99%
“…For instance, consider the dependency constraints between the two attributes a 1 and a 2 , that says the value of a 2 must equal c 3 when a 1 is in the range c 1 and c 2 . And a 2 must equal c 4 when the value of a 1 is less than c 1 ; otherwise, the value of a 2 is c 5 , where c 1 , c 2 , c 3 , c 4 and c 5 are constants. We use Petri Nets [13] to construct a dependency graph that represents all types of dependencies as well as constraints.…”
Section: Using Petri Nets For Representing Constraints and Dependenciesmentioning
confidence: 99%
“…Suppose that figure 7 represents the NIDG of a relational database, where the attributes a 1 and a 5 are in the table T 1 , a 2 is in the table T 2 , and a 3 , a 4 and a 6 are in the table T 3 . Also, assume that the set of attributes to which the insider has direct access is {a 1 }.…”
Section: An Example Scenariomentioning
confidence: 99%
See 1 more Smart Citation