1989
DOI: 10.1016/0167-4048(89)90081-3
|View full text |Cite
|
Sign up to set email alerts
|

SODA: A secure object-oriented database system

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
13
0

Year Published

1991
1991
2010
2010

Publication Types

Select...
4
3
2

Relationship

0
9

Authors

Journals

citations
Cited by 36 publications
(13 citation statements)
references
References 10 publications
0
13
0
Order By: Relevance
“…The resulting model was called SORION [Thuraisingham, 1989]. The resulting model was called SORION [Thuraisingham, 1989].…”
Section: Mandatory Access Control For Object Dmssmentioning
confidence: 99%
“…The resulting model was called SORION [Thuraisingham, 1989]. The resulting model was called SORION [Thuraisingham, 1989].…”
Section: Mandatory Access Control For Object Dmssmentioning
confidence: 99%
“…It may very well be the caae that an instance of LIST is classified, while an instance of ORDERED-LIST may not have to be. Past research emphasizes the notion of a class inheriting its security label from its superclass [3,4,8].…”
Section: Securitymentioning
confidence: 99%
“…Hybrid policies have also been proposed, where a content-based policy is essentially used, but where the labels that may be associated with data in a given container is restricted to be within some predetermined range [8].…”
Section: Dimension 2: Flow Controlmentioning
confidence: 99%
“…A typical container-based flow control policy, but with content-based activation records (similar to that used by SODA [8] and many others) may be implemented as described in figure 4. Note that All is assumed to be a subject label associated with all subjects.…”
Section: Dimension 2: Flow Controlmentioning
confidence: 99%