Trust Management for Public Key Infrastructures: Implementing the X.509 Trust Broker

Ahmad Samer Wazan, Romain Laborde, David W. Chadwick, Francois Barrere, Abdelmalek Benzekri, Mustafa Kaiiali, Adib Habbal

Research output: Contribution to journalArticle

4 Citations (Scopus)
260 Downloads (Pure)

Abstract

A Public Key Infrastructure (PKI) is considered one of the most important techniques used to propagate trust in authentication over the Internet. This technology is based on a trust model defined by the original X.509 (1988) standard and is composed of three entities: the certification authority (CA), the certificate holder (or subject), and the Relying Party (RP). The CA plays the role of a trusted third party between the certificate holder and the RP. In many use cases, this trust model has worked successfully. However, we argue that the application of this model on the Internet implies that web users need to depend on almost anyone in the world in order to use PKI technology. Thus, we believe that the current TLS system is not fit for purpose and must be revisited as a whole. In response, the latest draft edition of X.509 has proposed a new trust model by adding new entity called the Trust Broker (TB). In this paper, we present an implementation approach that a Trust Broker could follow in order to give RPs trust information about a CA by assessing the quality of its issued certificates. This is related to the quality of the CA’s policies and procedures and its commitment to them. Finally, we present our Trust Broker implementation that demonstrates how RPs can make informed decisions about certificate holders in the context of the global web, without requiring large processing resources themselves.
Original languageEnglish
Number of pages23
JournalWiley Security and Communication Networks Journal
DOIs
Publication statusPublished - 09 Feb 2017

Fingerprint Dive into the research topics of 'Trust Management for Public Key Infrastructures: Implementing the X.509 Trust Broker'. Together they form a unique fingerprint.

  • Cite this