Proceedings 1995 IEEE Symposium on Security and Privacy
DOI: 10.1109/secpri.1995.398923
|View full text |Cite
|
Sign up to set email alerts
|

Practical Domain and Type Enforcement for UNIX

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
147
0

Publication Types

Select...
5
2
1

Relationship

0
8

Authors

Journals

citations
Cited by 132 publications
(147 citation statements)
references
References 14 publications
0
147
0
Order By: Relevance
“…Furthermore, s i has the right to access o i in the op i mode. A run π has a flow from an objectô 1 to a subjectŝ k provided there is a flow pathô 1 …”
Section: Preliminariesmentioning
confidence: 99%
See 1 more Smart Citation
“…Furthermore, s i has the right to access o i in the op i mode. A run π has a flow from an objectô 1 to a subjectŝ k provided there is a flow pathô 1 …”
Section: Preliminariesmentioning
confidence: 99%
“…While MAC is not susceptible to Trojan Horse attacks, many solutions proposed to prevent any such data leakage exploit employing labels or type based access control. Boebert et al [3], Badger et al [1] and Boebert and Kain [4] are some of the studies that address confidentiality violating data flows. Mao et al [21] propose a label based MAC over a DAC system.…”
Section: Related Workmentioning
confidence: 99%
“…Domain and Type Enforcement (DTE) (see [28] for example) assigns a subject to a specific domain and an object to a specific type and enforces information flow by specifying the read and write permissions in the form of a matrix. A classic example of the application of DTE is to address the problem of trusted pipelines.…”
Section: Configuring Domain and Type Enforcement In G-sis Cmentioning
confidence: 99%
“…In this paper, we outline our vision on building the connected, undifferentiated group model and compare it with classic access control models such as LBAC, Domain and Type Enforcement [28] and RBAC. We show that our proposed connected, undifferentiated group model can express such policies and conveniently handle more dynamic information sharing scenarios.…”
Section: Introductionmentioning
confidence: 99%
“…Our current implementation is limited to filesystems, but the same approach should be generalized to these other namespaces. To confront the practical challenges connected with virtualizing network stacks, we plan to draw on the wisdom of the Vimage project 3 for FreeBSD [15]. 2 The sudoer-style matching and aliasing are not yet implemented 3 http://www.tel.fer.hr/zec/BSD/vimage/…”
Section: Overviewmentioning
confidence: 99%