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.

3.6 Coopetitive Architecture<br />

SPR9. Feature Interaction Management: The SPs require that any changes to the<br />

smart card plat<strong>for</strong>m that can aect their application's execution should be avoided.<br />

In the best-case scenario, the smart card plat<strong>for</strong>m follows the SP's delegated process<br />

that removes the interdependencies between applications in such situations. However,<br />

if this does not solve the problem, then the card should simply block the application<br />

or possibly delete it (with the card owner's consent).<br />

SPR10. Protection from Malicious <strong>User</strong>s: The SPs would like to have their applications<br />

protected by the underlying smart card plat<strong>for</strong>m. There<strong>for</strong>e, even if the<br />

application were issued to the malicious user, he would not be able to obtain any<br />

sensitive in<strong>for</strong>mation about the application.<br />

3.6 Coopetitive Architecture<br />

A UCTD can be a single-user, and/or a multi-user device, depending upon its deployment<br />

architecture. In a multi-user architecture, a device (e.g. a computer or tablet) might be used<br />

by multiple users. Furthermore, a UCTD might be part of a corporate network, as in the<br />

case of a mobile phone issued to employees by an organisation. The organisation (referred<br />

as an administrative authority) would like to retain the control of the UCTD issued as<br />

part of the mobile phone, while giving freedom to the user to have/manage the UCTD<br />

independently of the organisation. It is necessary to consider these deployment scenarios<br />

in order to achieve true scalability that will enable small to medium-sized organisations<br />

like leisure facilities, local libraries, schools, surgeries and colleges, as well as large-scale<br />

organisations like banks, MNOs and transport operators, to provide their services through<br />

a UCTD to a user without any restrictions from a centralised authority (e.g. card issuer).<br />

To accommodate the role of an administrative authority on a UCTD, we extend the UCOM<br />

architecture and propose the Coopetitive Architecture <strong>for</strong> Smart Cards (CASC). In the<br />

CASC a cardholder retains the application choice but under the provision of an administrative<br />

authority (e.g. TSM). Nevertheless, the baseline architecture of the UCTD is<br />

based the UCOM, as the CASC is an extension of the UCOM architecture that provides<br />

centralised ownership of the device while preserving the user's freedom of choice.<br />

The CASC combines the TSM architecture with the openness, scalability, and exibility<br />

of the UCOM architecture. In this architecture, users get their choice of selecting which<br />

application they want on their smart cards, and administrative authorities (or the TSM, the<br />

administrator of the corporate network) have a permanent presence on the cards along with<br />

possibly being part of the revenue loop. The CASC requires all the necessary modications<br />

to the existing smart card architecture (i.e. deployed in the ICOM) to achieve its goals.<br />

So while we focus on the UCOM in this thesis, we are implicitly also catering to the<br />

76

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

Saved successfully!

Ooh no, something went wrong!