2000
DOI: 10.1007/10722599_2
|View full text |Cite
|
Sign up to set email alerts
|

Verification of a Formal Security Model for Multiapplicative Smart Cards

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
36
0

Year Published

2001
2001
2013
2013

Publication Types

Select...
4
4
1

Relationship

0
9

Authors

Journals

citations
Cited by 40 publications
(36 citation statements)
references
References 3 publications
0
36
0
Order By: Relevance
“…There were investigations [12,21,22,23] of static scenarios, when all applets are known and the composition is analyzed off-device. For example, Avvenuti et al [24] have developed the JBIFV tool which verifies whether a JC applet respects pre-defined information flow policies.…”
Section: Related Workmentioning
confidence: 99%
“…There were investigations [12,21,22,23] of static scenarios, when all applets are known and the composition is analyzed off-device. For example, Avvenuti et al [24] have developed the JBIFV tool which verifies whether a JC applet respects pre-defined information flow policies.…”
Section: Related Workmentioning
confidence: 99%
“…These multi-level functions can be modeled by trusted subjects that have a label range spanning multiple nodes of the lattice. [47][10] [20] [40] It is a significant distinction that trusted subjects do not violate the security policy: rather their defined behavior is an explicit part of the security policy, as follows. The set of flows allowed by the system MLS security policy is the union of: (a) the flows allowed by the strict MLS policy; and (b) the set of flows defined to be allowed for the system's trusted subjects (here, called the relaxed MLS policy).…”
Section: Trusted Subjectsmentioning
confidence: 99%
“…It does not describe the granularity of control required to represent the principle of least privilege. Schellhorn, et al [41] describe a formal model that includes non-interference between blocks (called "applications"), as well as a mandatory access control (MAC) policy regarding both confidentiality and integrity for references to resources within a block. There is one subject per block, which is associated with a set of private resources ("files").…”
Section: Separation Kernel Formal Modelsmentioning
confidence: 99%