|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
2009 22nd IEEE Computer Security Foundations Symposium
A Secure Cryptographic Token Interface
Port Jefferson, New York
July 08-July 10
ISBN: 978-0-7695-3712-2
| ASCII Text | x | ||
| Christian Cachin, Nishanth Chandran, "A Secure Cryptographic Token Interface," 2012 IEEE 25th Computer Security Foundations Symposium, pp. 141-153, 2009 22nd IEEE Computer Security Foundations Symposium, 2009. | |||
| BibTex | x | ||
| @article{ 10.1109/CSF.2009.7, author = {Christian Cachin and Nishanth Chandran}, title = {A Secure Cryptographic Token Interface}, journal ={2012 IEEE 25th Computer Security Foundations Symposium}, volume = {0}, year = {2009}, issn = {1063-6900}, pages = {141-153}, doi = {http://doi.ieeecomputersociety.org/10.1109/CSF.2009.7}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - CONF JO - 2012 IEEE 25th Computer Security Foundations Symposium TI - A Secure Cryptographic Token Interface SN - 1063-6900 SP141 EP153 A1 - Christian Cachin, A1 - Nishanth Chandran, PY - 2009 VL - 0 JA - 2012 IEEE 25th Computer Security Foundations Symposium ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/CSF.2009.7
Cryptographic keys must be protected from exposure. In real-world applications, they are often guarded by cryptographic tokens that employ sophisticated hardware-security measures. Several logical attacks on the key management operations of cryptographic tokens have been reported in the past, which allowed to expose keys merely by exploiting the token API in unexpected ways. This paper proposes a novel, provably secure, cryptographic token interface that supports multiple users, implements symmetric cryptosystems and public-key schemes, and provides operations for key generation, encryption, authentication, and key wrapping. The token interface allows only the most important operations found in real-world token APIs; while flexible to be of practical use, it is restricted enough so that it does not expose any key to a user without sufficient privileges. The security policy can be applied to the industry-standard PKCS #11 interface.
Citation:
Christian Cachin, Nishanth Chandran, "A Secure Cryptographic Token Interface," csf, pp.141-153, 2009 22nd IEEE Computer Security Foundations Symposium, 2009
Usage of this product signifies your acceptance of the Terms of Use.
