06.11.2014 Views

A User Centric Security Model for Tamper-Resistant Devices

A User Centric Security Model for Tamper-Resistant Devices

A User Centric Security Model for Tamper-Resistant Devices

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

5.3 Multos Card Management Framework<br />

the application provider to sign their applications be<strong>for</strong>e they are loaded onto the smart<br />

card. The Mandated DAP Authority will verify the signature and notify the application<br />

provider.<br />

One thing to note is that in any framework, whether it is pre-issuance or post-issuance<br />

application loading in the GlobalPlat<strong>for</strong>m card specication [30] or application loading<br />

via OTA in the NFC mobile phone [155], the loading of cryptographic keys is dependent<br />

on an entity (e.g. GP-CA or CKLA). The application provider has to trust these entities<br />

and their aim is to provide the key material <strong>for</strong> application loading and management to<br />

the respective application provider without revealing it to any malicious entity. There<strong>for</strong>e,<br />

such entities (e.g. GP-CA or CKLA) which in most cases belongs to an o-card actor (i.e.<br />

card issuer), cannot be entertained in the UCOM proposal.<br />

5.3 Multos Card Management Framework<br />

In this section, we discuss Multos architecture <strong>for</strong> card management operations along with<br />

the possibility that the architecture can be accommodated into the TSM-based framework<br />

<strong>for</strong> NFC mobile phones.<br />

5.3.1 Architecture Overview<br />

The card management architecture <strong>for</strong> Multos is more straight<strong>for</strong>ward than GlobalPlat<strong>for</strong>m<br />

(section 5.2.1). An overview of the Multos card management architecture is illustrated in<br />

gure 5.2 and discussed below:<br />

Public Key &<br />

Application Header<br />

Application<br />

Provider<br />

Signature<br />

Verification Key &<br />

Application Header<br />

Multos Certification<br />

Authority<br />

Signature Key &<br />

Application<br />

Application Load<br />

Certificate<br />

<strong>User</strong> Personalisation Data<br />

Application Load<br />

Unit Generator<br />

Smart Card<br />

Cardholder<br />

Card Issuer<br />

Application Load Unit<br />

Application Load<br />

Certificate<br />

Application Load<br />

Facility<br />

Application<br />

Card Issued<br />

Figure 5.2: Multos card management architecture<br />

The shaded entities in gure 5.2 represent various roles, but traditionally they reside with<br />

a single entity, <strong>for</strong> example the card issuer [97, 159]. An application provider will generate<br />

114

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!