2013 IEEE Symposium on Security and Privacy 2013
DOI: 10.1109/sp.2013.35
|View full text |Cite
|
Sign up to set email alerts
|

seL4: From General Purpose to a Proof of Information Flow Enforcement

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
110
0

Year Published

2013
2013
2020
2020

Publication Types

Select...
8
1
1

Relationship

0
10

Authors

Journals

citations
Cited by 152 publications
(110 citation statements)
references
References 34 publications
0
110
0
Order By: Relevance
“…As is the case with most re nement/simulation-based approaches, this work does not address information ow. In recent work on seL4 veri cation, Murray et al [14,15] present an unwinding-style characterization of intransitive noninterference. They introduce a proof calculus on nondeterministic state monads that is similar to that of this work.…”
Section: Related Workmentioning
confidence: 99%
“…As is the case with most re nement/simulation-based approaches, this work does not address information ow. In recent work on seL4 veri cation, Murray et al [14,15] present an unwinding-style characterization of intransitive noninterference. They introduce a proof calculus on nondeterministic state monads that is similar to that of this work.…”
Section: Related Workmentioning
confidence: 99%
“…CoSMeDis belongs to a small, but expanding club of running systems proved to be secure using proof assistants, which includes an aircraft microprocessor [34] (in ACL2), a hardware architecture with information flow primitives [22] (in Coq), a separation kernel [21] (in HOL4), a noninterferent operating system kernel [51] (in Isabelle/HOL), a secure browser [36] (in Coq), and an e-voting system [39] (using the KeY theorem prover jointly with the Joana information flow analyzer).…”
Section: Related Workmentioning
confidence: 99%
“…On the other hand, the hypervisor should be unable to affect guest state even indirectly: The only desired effects of hypervisor actions should be to allocate/deallocate, map, remap, and unmap virtual memory resources, leaving any observation a guest may make unaffected. This is essentially a second-order information flow property, needed to break guest-to-guest (or guest-to-service) information channels in much the same way as intransitive noninterference is used in [19] to break guest-to-guest channels passing through the scheduler in seL4.…”
Section: Tls Consistency Propertiesmentioning
confidence: 99%