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.

4.9 Summary<br />

whereas the online attestation is not part of the TPM specications.<br />

Similarly, other proposals concentrate on the software attestation without binding it to<br />

a particular hardware. Such proposals include SCUBA [150], SBAP [151], and SWATT<br />

[152]. These protocols utilise execution time as a parameter in the attestation process.<br />

This is dicult to guarantee remotely, even with the delegation of time measurement to<br />

neighbouring trustworthy nodes [150]. Other mechanisms that use trusted hardware are<br />

proposed by Schellekens et al. [153] and PUF-based protocols [123, 135, 154].<br />

There is no such proposal <strong>for</strong> remote attestation in smart card frameworks like Java Card,<br />

Multos, or GlobalPlat<strong>for</strong>m. The nearest thing is the Data Authentication Pattern (DAP)<br />

in the GlobalPlat<strong>for</strong>m card specication that checks the signature on the downloaded<br />

application (if the application provider chooses this option). Furthermore, we have opted<br />

out of having execution measurement as part of the attestation process as it is dicult to<br />

ascertain the trustworthiness of the remote device that measures it. However, unlike other<br />

proposed protocols we have an explicit requirement that third party evaluation is used to<br />

provide an implicit trust in the attestation process. Furthermore, our proposal binds the<br />

software attestation with the hardware protection (tamper-evident) mechanism to provide<br />

added assurance.<br />

4.9 Summary<br />

In this chapter, we discussed the overall architecture of the UCTD and its components and<br />

the ways in which the UCTD is dierent from mainstream smart card proposals. We also<br />

extended the discussion to the security assurance and validation framework that requires<br />

a third party evaluation and an attestation process. The attestation process includes<br />

hardware validation with the traditional software attestation. We proposed two modes<br />

<strong>for</strong> the attestation process: oine and online attestation. In designing the attestation<br />

processes, we based our proposal on two dierent architectures. First proposal is based on<br />

the PRNG and the second approach includes the PUFs in the device attestation process. To<br />

have an online attestation, we proposed the attestation protocol that communicates with<br />

the card manufacturer to get a dynamic certicate of assurance (a signed message from<br />

the card manufacturer) that the smart card is still secure and reliable. We implemented<br />

oine and online attestation mechanisms, along with an attestation protocol on 16-bit Java<br />

Cards. We also detailed the per<strong>for</strong>mance measurements of the implemented mechanisms<br />

and protocols.<br />

109

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

Saved successfully!

Ooh no, something went wrong!