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.5 <strong>Security</strong> and Operational Requirements of the UCOM<br />

CR5. Ownership Mechanism: A mechanism is required that securely authenticates the<br />

owner of the smart card and facilitates the exercise of her privileges (i.e. installing<br />

and deleting applications).<br />

3.5.3 <strong>User</strong> <strong>Centric</strong> Smart Card's Requirements<br />

The security and operational requirements of smart cards are listed below, and most of<br />

these requirements should be implemented by smart card suppliers:<br />

SCR1. <strong>Security</strong> Assurance: A smart card should have a mechanism(s) that will provide<br />

assurance to a requesting SP that adequate security and privacy measures have been<br />

implemented to ensure the security and privacy requirements of the application(s).<br />

SCR2. <strong>Security</strong> Evaluation: A smart card should be able to evaluate the downloaded<br />

applications and verify that they do not pose any threat to the safe execution of the<br />

other application(s) on the card.<br />

SCR3. Interoperability: A smart card should have the capability to support a wide<br />

range of applications and communication interfaces/channels.<br />

SCR4. Runtime Environment Fairness: A smart card should require that no application<br />

installed on it tries to monopolise the runtime environment.<br />

SCR5. Application Management: A smart card should have mechanisms to securely<br />

manage the applications. The management of the applications includes application<br />

downloading, installation, and deletion.<br />

SCR6. Application Lease Management: A smart card should require adequate mechanisms<br />

to manage an application lease. The lease of an application may have certain<br />

limits or restrictions that a smart card has to satisfy over the lifetime of the application.<br />

For instance, the limit could be an expiry date or the number of times used, and<br />

restrictions may be the runtime environment's conguration. The mechanism should<br />

be able to provide assurance to the SP that their application will be deleted if the<br />

limit is reached, or cease to execute if lease restrictions are violated. The application<br />

leased from the SP is governed by an application lease policy described in section<br />

3.4.6.2.<br />

SCR7. Ownership Validation: A smart card should support a mechanism to authenticate<br />

its owner using some security parameters (i.e. Personal Identication Numbers:<br />

PIN, password, pass-phrase, or biometric, etc.). There should be the functionality<br />

to reset these values securely.<br />

73

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

Saved successfully!

Ooh no, something went wrong!