2010
DOI: 10.1007/978-3-642-12510-2_9
|View full text |Cite
|
Sign up to set email alerts
|

Firewall Mechanism in a User Centric Smart Card Ownership Model

Abstract: Abstract. Multi-application smart card technology facilitates applications to securely share their data and functionality. The security enforcement and assurance in application sharing is provided by the smart card firewall. The firewall mechanism is well defined and studied in the Issuer Centric Smart Card Ownership Model (ICOM), in which a smart card is under total control of its issuer. However, it is not analysed in the User Centric Smart Card Ownership Model (UCOM) that delegates the smart card control to… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2

Citation Types

0
4
0

Year Published

2010
2010
2015
2015

Publication Types

Select...
4
2
1

Relationship

3
4

Authors

Journals

citations
Cited by 11 publications
(4 citation statements)
references
References 14 publications
0
4
0
Order By: Relevance
“…shareable resources) that are provided by partner applications. To access a partner's application services, the downloaded application will establish an application-sharing relationship that is discussed in detail in [34,35].…”
Section: Application Installationmentioning
confidence: 99%
“…shareable resources) that are provided by partner applications. To access a partner's application services, the downloaded application will establish an application-sharing relationship that is discussed in detail in [34,35].…”
Section: Application Installationmentioning
confidence: 99%
“…This access to the SSO application has to take place when the rst application connects with the internet services. Such an access is termed as synchronous access in the UCTD and is based on the Java Card architecture [186]. Such an access can be based on the Java Card Remote Method Invocation (RMI) [28].…”
Section: Application Sharing In Cdammentioning
confidence: 99%
“…The issues involved are: a) an inability to dynamically authenticate an application on a smart card, b) di culty in ascertaining the security and reliability of the current state of an application, c) an inability to verify and restrict application sharing (privilege-based access), d) no provision for privacy preservation for cardholders, and e) no cryptographic binding between applications. Therefore, in this chapter, we discuss the proposed rewall mechanism [186] that provides an extension to the traditional mechanisms deployed in Multos and Java Card, in order to deal with the listed issues.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation