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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

4.2 Plat<strong>for</strong>m Architecture<br />

manager can take action and restrict the application by either blocking it so it cannot<br />

execute, or by deleting it. In the GlobalPlat<strong>for</strong>m card specication, such a mechanism<br />

requires the card issuer's permission whereas in the UCOM the card security manager<br />

wants to delete an application it only requires permission from the cardholder.<br />

In addition, when the ownership of a smart card is changed or if the card is decommissioned,<br />

the card security manager is responsible <strong>for</strong> resetting the smart card conguration.<br />

This process includes the deletion of all installed applications and any data related to<br />

applications/users. The resetting operation will set the smart card to the default factory<br />

setting, as a blank card. Such a mechanism does not exist in the GlobalPlat<strong>for</strong>m card<br />

specication and it is discussed as part of the decommissioning of the UCTD in chapter 9.<br />

The card security manager provides functionality that ensures the plat<strong>for</strong>m is in con<strong>for</strong>mance<br />

with the requirements CR1, CR2, CR5, SCR5, SCR6, SPR1, SPR2, and SPR6 that<br />

are listed in section 3.5.<br />

4.2.3 Card Services Manager<br />

Services provided by the smart card plat<strong>for</strong>m are under the control of the card services<br />

manager. The services include the o-card interface, the runtime Application Programming<br />

Interface (API), and default applications. The access rights to these services are designated<br />

(requested) by the respective application's SP and the card services manager en<strong>for</strong>ces them.<br />

This functionality enables an SP to manage the behaviour of its application(s) on a smart<br />

card.<br />

Furthermore, a smart card might have multiple applications from dierent SPs that provide<br />

the same service, like banking applications from distinct banks. In such a situation, the<br />

user would have the option of making one application the default application of the group<br />

to which it belongs. The card services manager deals with a list of default applications<br />

when a smart card is presented at a Services Access Point (SAP). If the SAP only requests<br />

an application that belongs to a particular group (e.g. transport, banking, telecom or access<br />

control) without specifying a particular member of that group, the card services manager<br />

selects the default application <strong>for</strong> the group. However, if the SAP wants to select a specic<br />

application, which may not be the default application of its group the SAP has to request<br />

that application explicitly.<br />

The card services manager ensures that the plat<strong>for</strong>m satises requirements CR3, CR4,<br />

SCR5, SPR6, and SPR7 (dened in section 3.5).<br />

83

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

Saved successfully!

Ooh no, something went wrong!