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

Another potential protection strategy is to utilise Physical Unclonable Functions (PUFs)<br />

[116] to provide hardware validation. It is dicult to nd a single and consistent denition<br />

of PUF in the literature [117]. However, a property description denition of the<br />

PUF is provided by Gassend et al. in [116]. Usual applications of the PUF described<br />

in the literature are in anti-counterfeiting [118], Intellectual Property protection [119]<br />

[121], tamper-evident hardware [122], hardware based cryptography [60, 123][125] and<br />

secure/trusted processors [126].<br />

Based on the above listed features, table 4.1 shows the comparison between dierent possible<br />

functions that can act as the self-test mechanism. Although the debate regarding the<br />

viability, security, and reliability of the PUFs is still open in both academic circles and<br />

industry [127]; <strong>for</strong> completeness, we use them as a self-test mechanism in our proposals<br />

because they meet most of the requirements listed in table 4.1.<br />

Table 4.1: Comparison of dierent proposals <strong>for</strong> self-test mechanism<br />

Features Active-Shield Keyed-HMAC PRNG PUF<br />

Robustness Yes Yes Yes Yes<br />

Independence No No Yes Yes<br />

Pseudo-randomness No Yes Yes Yes<br />

<strong>Tamper</strong>-evidence Yes Yes* Yes<br />

Un<strong>for</strong>geable No Yes Yes* Yes<br />

Assurance Yes No Yes Yes*<br />

Note. Yes means that the mechanism supports the feature. No indicates that the mechanism does<br />

not support the required feature. The entry Yes* means that it can supports this feature if adequately<br />

catered <strong>for</strong> during the design.<br />

If a manufacturer maintains separate keys <strong>for</strong> individual smart cards that support the<br />

HMAC then it can provide the independence feature. However the HMAC key is hardwired<br />

and this makes it dicult <strong>for</strong> it to be dierent on individual smart cards of the same<br />

batch. Furthermore, it requires other features to provide tamper evidence, like activeshield.<br />

On the other hand, PUFs and adequately designed Pseudo-Random Number Generators<br />

(PRNGs) can provide assurance that the plat<strong>for</strong>m state and the tamper-resistant<br />

protections of a UCTD are still active.<br />

Be<strong>for</strong>e we discuss how a self-test manager and an attestation handler can be implemented<br />

based on PUF and/or PRNG, we rst discuss the overall framework that is responsible <strong>for</strong><br />

providing security assurance and validation of a smart card.<br />

89

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

Saved successfully!

Ooh no, something went wrong!