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.3 Trusted Environment & Execution Manager<br />

one smart card to another, the backup & restoration manager retrieves these tokens from<br />

the backup token handler, encrypts them, and communicates to the intended entity (e.g.<br />

backup server or new smart card). The details of this mechanism are further elaborated<br />

in chapter 9.<br />

4.3.3 Runtime <strong>Security</strong> Manager<br />

The runtime security manager deals with the en<strong>for</strong>cement of the plat<strong>for</strong>m policies regarding<br />

the smart card runtime environment. These policies may deal with the security and<br />

reliability of an application execution, and they ensure that an application executes in a<br />

trustworthy manner. The runtime security manager is discussed in detail in chapter 8<br />

where we examine the threats to the smart card runtime environment and related countermeasures.<br />

4.3.4 Attestation Handler<br />

The attestation handler and the self-test manager are part of the security assurance and<br />

validation mechanism discussed in section 4.4. The dierence between these two modules<br />

(i.e. the attestation handler and the self-test manager) of the TEM is that one focuses<br />

on the software and the other on the hardware. However, in the proposed attestation<br />

mechanism (section 4.5) they complement each other to provide proof that a smart card<br />

is secure, reliable and trustworthy.<br />

During the application installation process, the attestation handler will verify the current<br />

state of the plat<strong>for</strong>m runtime environment (e.g. security and operationally sensitive parts of<br />

the SCOS) and arm to the appropriate SP that the plat<strong>for</strong>m is as secure and reliable as it<br />

is claimed to be the evaluation certicate discussed in section 4.4. Once the application is<br />

installed the relevant SP can ask the TEM to generate the state validation of an application<br />

(e.g. signed hash of the application), ensuring that the application is downloaded without<br />

any errors onto the plat<strong>for</strong>m. This function of the TEM is similar to the DAP [30, 74].<br />

Furthermore, SPs can request the state validation of their applications at any time during<br />

the lifetime of the applications on a smart card. In addition, as part of the application<br />

sharing mechanism the TEM also provides application state validation to the applications<br />

that share each other's resources (discussed in chapter 7).<br />

87

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

Saved successfully!

Ooh no, something went wrong!