A Secure Robust Integrity Reporting Protocol of Trusted Computing for Remote Attestation under Fully Adaptive Party Corruptions
Trusted computing has been proposed to enhance the security of computing environment in disparate computer platforms. Remote attestation is necessary to prove integrity and authenticity of system environments. Stumpf et al. propose a robust integrity reporting protocol for remote attestation. However, their protocol is not secure under fully adaptive party corruptions. In this paper, we propose a secure integrity reporting protocol for remote attestation under fully adaptive party corruptions.
KeywordsIntegrity Reporting Protocol Adaptive Party Corruptions Trusted Computing
Unable to display preview. Download preview PDF.
- 1.Trusted Computing Group, TCG Specification Architecture Overview Version 1.4, Revision 4 (August 2007), http://www.trustedcomputinggroup.org/resources/tcg_architecture_overview_version_14
- 2.Trusted Computing Group, TNC Architecture for Interoperability, Specification Version 1.4, Revision 4 (May 2009), https://www.trustedcomputinggroup.org/specs/TNC
- 3.Trusted Computing Group, TNC IF-T:Protocol Bindings for Tunneled EAP Methods Specification Version 1.1, Revision 10 (May 2007), https://www.trustedcomputinggroup.org/specs/TNC
- 4.Trusted Computing Group, TCG Trusted network connect TNC IF-TNCCS Specification Version 1.1, Revision 10 (May 2007), https://www.trustedcomputinggroup.org/specs/TNC
- 5.Sailer, R., Jaeger, T., Zhang, X., van Doorn, L.: Attenstation-based policy enforcement for remote access. In: The Proceedings of the 11th ACM Conference on Computer and Communications Security, pp. 308–317. ACM Press, New York (2004)Google Scholar
- 6.Stumpf, F., Tafreschi, O., Roder, P., Eckert, C.: A robust intergrity reporting protocol for remote attestation. In: The Proceedings of the 2nd Workshop on Advances in Trusted Computing (WATC 2006 Fall), Tokyo, Japan, pp. 308–317 (2006)Google Scholar
- 7.Bruno, B.: Automatic verification of correspondences for security protocols. Journal of Computer Security 17(4), 363–434 (2009)Google Scholar