Public key infrastructure

A public key infrastructure (PKI) is a set of roles, policies, hardware, software and procedures needed to create, manage, distribute, use, store and revoke digital certificates and manage public-key encryption.

Diagram of a public key infrastructure

The purpose of a PKI is to facilitate the secure electronic transfer of information for a range of network activities such as e-commerce, internet banking and confidential email. It is required for activities where simple passwords are an inadequate authentication method and more rigorous proof is required to confirm the identity of the parties involved in the communication and to validate the information being transferred.

In cryptography, a PKI is an arrangement that binds public keys with respective identities of entities (like people and organizations).[1][2] The binding is established through a process of registration and issuance of certificates at and by a certificate authority (CA). Depending on the assurance level of the binding, this may be carried out by an automated process or under human supervision. When done over a network, this requires using a secure certificate enrollment or certificate management protocol such as CMP.

The PKI role that may be delegated by a CA to assure valid and correct registration is called a registration authority (RA). An RA is responsible for accepting requests for digital certificates and authenticating the entity making the request.[3] The Internet Engineering Task Force's RFC 3647 defines an RA as "An entity that is responsible for one or more of the following functions: the identification and authentication of certificate applicants, the approval or rejection of certificate applications, initiating certificate revocations or suspensions under certain circumstances, processing subscriber requests to revoke or suspend their certificates, and approving or rejecting requests by subscribers to renew or re-key their certificates. RAs, however, do not sign or issue certificates (i.e., an RA is delegated certain tasks on behalf of a CA)."[4] While Microsoft may have referred to a subordinate CA as an RA,[5] this is incorrect according to the X.509 PKI standards. RAs do not have the signing authority of a CA and only manage the vetting and provisioning of certificates. So in the Microsoft PKI case, the RA functionality is provided either by the Microsoft Certificate Services web site or through Active Directory Certificate Services which enforces Microsoft Enterprise CA, and certificate policy through certificate templates and manages certificate enrollment (manual or auto-enrollment). In the case of Microsoft Standalone CAs, the function of RA does not exist since all of the procedures controlling the CA are based on the administration and access procedure associated with the system hosting the CA and the CA itself rather than Active Directory. Most non-Microsoft commercial PKI solutions offer a stand-alone RA component.

An entity must be uniquely identifiable within each CA domain on the basis of information about that entity. A third-party validation authority (VA) can provide this entity information on behalf of the CA.

The X.509 standard defines the most commonly used format for public key certificates.[6]



PKI provides "trust services" - in plain terms trusting the actions or outputs of entities, be they people or computers. Trust service objectives respect one or more of the following capabilities: Confidentiality, Integrity and Authenticity (CIA).

Confidentiality: Assurance that no entity can maliciously or unwittingly view a payload in clear text. Data is encrypted to make it secret, such that even if it was read, it appears as gibberish. Perhaps the most common use of PKI for confidentiality purposes is in the context of Transport Layer Security (TLS). TLS is a capability underpinning the security of data in transit, i.e. during transmission. A classic example of TLS for confidentiality is when using an internet browser to log on to a service hosted on an internet based web site by entering a password.

Integrity: Assurance that if an entity changed (tampered) with transmitted data in the slightest way, it would be obvious it happened as its integrity would have been compromised. Often it is not of utmost importance to prevent the integrity being compromised (tamper proof), however, it is of utmost importance that if integrity is compromised there is clear evidence of it having done so (tamper evident).

Authenticity: Assurance that every entity has certainty of what it is connecting to, or can evidence its legitimacy when connecting to a protected service. The former is termed server-side authentication - typically used when authenticating to a web server using a password. The latter is termed client-side authentication - sometimes used when authenticating using a smart card (hosting a digital certificate and private key).



Public-key cryptography is a cryptographic technique that enables entities to securely communicate on an insecure public network, and reliably verify the identity of an entity via digital signatures.[7]

A public key infrastructure (PKI) is a system for the creation, storage, and distribution of digital certificates which are used to verify that a particular public key belongs to a certain entity. The PKI creates digital certificates which map public keys to entities, securely stores these certificates in a central repository and revokes them if needed.[8][9][10]

A PKI consists of:[9][11][12]

  • A certificate authority (CA) that stores, issues and signs the digital certificates;
  • A registration authority (RA) which verifies the identity of entities requesting their digital certificates to be stored at the CA;
  • A central directory—i.e., a secure location in which keys are stored and indexed;
  • A certificate management system managing things like the access to stored certificates or the delivery of the certificates to be issued;
  • A certificate policy stating the PKI's requirements concerning its procedures. Its purpose is to allow outsiders to analyze the PKI's trustworthiness.

Methods of certification


Broadly speaking, there have traditionally been three approaches to getting this trust: certificate authorities (CAs), web of trust (WoT), and simple public-key infrastructure (SPKI).[citation needed]

Certificate authorities


The primary role of the CA is to digitally sign and publish the public key bound to a given user. This is done using the CA's own private key, so that trust in the user key relies on one's trust in the validity of the CA's key. When the CA is a third party separate from the user and the system, then it is called the Registration Authority (RA), which may or may not be separate from the CA.[13] The key-to-user binding is established, depending on the level of assurance the binding has, by software or under human supervision.

The term trusted third party (TTP) may also be used for certificate authority (CA). Moreover, PKI is itself often used as a synonym for a CA implementation.[14]

Certificate revocation


A certificate may be revoked before it expires, which signals that it is no longer valid. Without revocation, an attacker would be able to exploit such a compromised or mis-issued certificate until expiry.[15] Hence, revocation is an important part of a public key infrastructure.[16] Revocation is performed by the issuing certificate authority, which produces a cryptographically authenticated statement of revocation.[17]

For distributing revocation information to clients, timeliness of the discovery of revocation (and hence the window for an attacker to exploit a compromised certificate) trades off against resource usage in querying revocation statuses and privacy concerns.[18] If revocation information is unavailable (either due to accident or an attack), clients must decide whether to fail-hard and treat a certificate as if it is revoked (and so degrade availability) or to fail-soft and treat it as unrevoked (and allow attackers to sidestep revocation).[19]

Due to the cost of revocation checks and the availability impact from potentially-unreliable remote services, Web browsers limit the revocation checks they will perform, and will fail-soft where they do.[20] Certificate revocation lists are too bandwidth-costly for routine use, and the Online Certificate Status Protocol presents connection latency and privacy issues. Other schemes have been proposed but have not yet been successfully deployed to enable fail-hard checking.[16]

Issuer market share


In this model of trust relationships, a CA is a trusted third party – trusted both by the subject (owner) of the certificate and by the party relying upon the certificate.

According to NetCraft report from 2015,[21] the industry standard for monitoring active Transport Layer Security (TLS) certificates, states that "Although the global [TLS] ecosystem is competitive, it is dominated by a handful of major CAs — three certificate authorities (Symantec, Sectigo, GoDaddy) account for three-quarters of all issued [TLS] certificates on public-facing web servers. The top spot has been held by Symantec (or VeriSign before it was purchased by Symantec) ever since [our] survey began, with it currently accounting for just under a third of all certificates. To illustrate the effect of differing methodologies, amongst the million busiest sites Symantec issued 44% of the valid, trusted certificates in use — significantly more than its overall market share."

Following major issues in how certificate issuing were managed, all major players gradually distrusted Symantec issued certificates, starting in 2017 and completed in 2021.[22][23][24][25]

Temporary certificates and single sign-on


This approach involves a server that acts as an offline certificate authority within a single sign-on system. A single sign-on server will issue digital certificates into the client system, but never stores them. Users can execute programs, etc. with the temporary certificate. It is common to find this solution variety with X.509-based certificates.[26]

Starting Sep 2020, TLS Certificate Validity reduced to 13 Months.

Web of trust


An alternative approach to the problem of public authentication of public key information is the web-of-trust scheme, which uses self-signed certificates and third-party attestations of those certificates. The singular term "web of trust" does not imply the existence of a single web of trust, or common point of trust, but rather one of any number of potentially disjoint "webs of trust". Examples of implementations of this approach are PGP (Pretty Good Privacy) and GnuPG (an implementation of OpenPGP, the standardized specification of PGP). Because PGP and implementations allow the use of e-mail digital signatures for self-publication of public key information, it is relatively easy to implement one's own web of trust.

One of the benefits of the web of trust, such as in PGP, is that it can interoperate with a PKI CA fully trusted by all parties in a domain (such as an internal CA in a company) that is willing to guarantee certificates, as a trusted introducer. If the "web of trust" is completely trusted then, because of the nature of a web of trust, trusting one certificate is granting trust to all the certificates in that web. A PKI is only as valuable as the standards and practices that control the issuance of certificates and including PGP or a personally instituted web of trust could significantly degrade the trustworthiness of that enterprise's or domain's implementation of PKI.[27]

The web of trust concept was first put forth by PGP creator Phil Zimmermann in 1992 in the manual for PGP version 2.0:

As time goes on, you will accumulate keys from other people that you may want to designate as trusted introducers. Everyone else will each choose their own trusted introducers. And everyone will gradually accumulate and distribute with their key a collection of certifying signatures from other people, with the expectation that anyone receiving it will trust at least one or two of the signatures. This will cause the emergence of a decentralized fault-tolerant web of confidence for all public keys.

Simple public key infrastructure


Another alternative, which does not deal with public authentication of public key information, is the simple public key infrastructure (SPKI) that grew out of three independent efforts to overcome the complexities of X.509 and PGP's web of trust. SPKI does not associate users with persons, since the key is what is trusted, rather than the person. SPKI does not use any notion of trust, as the verifier is also the issuer. This is called an "authorization loop" in SPKI terminology, where authorization is integral to its design.[28] This type of PKI is specially useful for making integrations of PKI that do not rely on third parties for certificate authorization, certificate information, etc.; a good example of this is an air-gapped network in an office.

Decentralized PKI


Decentralized identifiers (DIDs) eliminates dependence on centralized registries for identifiers as well as centralized certificate authorities for key management, which is the standard in hierarchical PKI. In cases where the DID registry is a distributed ledger, each entity can serve as its own root authority. This architecture is referred to as decentralized PKI (DPKI).[29][30]



Developments in PKI occurred in the early 1970s at the British intelligence agency GCHQ, where James Ellis, Clifford Cocks and others made important discoveries related to encryption algorithms and key distribution.[31] Because developments at GCHQ are highly classified, the results of this work were kept secret and not publicly acknowledged until the mid-1990s.

The public disclosure of both secure key exchange and asymmetric key algorithms in 1976 by Diffie, Hellman, Rivest, Shamir, and Adleman changed secure communications entirely. With the further development of high-speed digital electronic communications (the Internet and its predecessors), a need became evident for ways in which users could securely communicate with each other, and as a further consequence of that, for ways in which users could be sure with whom they were actually interacting.

Assorted cryptographic protocols were invented and analyzed within which the new cryptographic primitives could be effectively used. With the invention of the World Wide Web and its rapid spread, the need for authentication and secure communication became still more acute. Commercial reasons alone (e.g., e-commerce, online access to proprietary databases from web browsers) were sufficient. Taher Elgamal and others at Netscape developed the SSL protocol ('https' in Web URLs); it included key establishment, server authentication (prior to v3, one-way only), and so on.[32] A PKI structure was thus created for Web users/sites wishing secure communications.

Vendors and entrepreneurs saw the possibility of a large market, started companies (or new projects at existing companies), and began to agitate for legal recognition and protection from liability. An American Bar Association technology project published an extensive analysis of some of the foreseeable legal aspects of PKI operations (see ABA digital signature guidelines), and shortly thereafter, several U.S. states (Utah being the first in 1995) and other jurisdictions throughout the world began to enact laws and adopt regulations. Consumer groups raised questions about privacy, access, and liability considerations, which were more taken into consideration in some jurisdictions than in others.[33]

The enacted laws and regulations differed, there were technical and operational problems in converting PKI schemes into successful commercial operation, and progress has been much slower than pioneers had imagined it would be.

By the first few years of the 21st century, the underlying cryptographic engineering was clearly not easy to deploy correctly. Operating procedures (manual or automatic) were not easy to correctly design (nor even if so designed, to execute perfectly, which the engineering required). The standards that existed were insufficient.

PKI vendors have found a market, but it is not quite the market envisioned in the mid-1990s, and it has grown both more slowly and in somewhat different ways than were anticipated.[34] PKIs have not solved some of the problems they were expected to, and several major vendors have gone out of business or been acquired by others. PKI has had the most success in government implementations; the largest PKI implementation to date is the Defense Information Systems Agency (DISA) PKI infrastructure for the Common Access Cards program.



PKIs of one type or another, and from any of several vendors, have many uses, including providing public keys and bindings to user identities which are used for:

Open source implementations

  • OpenSSL is the simplest form of CA and tool for PKI. It is a toolkit, developed in C, that is included in all major Linux distributions, and can be used both to build your own (simple) CA and to PKI-enable applications. (Apache licensed)
  • EJBCA is a full-featured, enterprise-grade, CA implementation developed in Java. It can be used to set up a CA both for internal use and as a service. (LGPL licensed)
  • XiPKI,[36] CA and OCSP responder. With SHA-3 support, implemented in Java. (Apache licensed)
  • XCA[37] is a graphical interface, and database. XCA uses OpenSSL for the underlying PKI operations.
  • DogTag is a full featured CA developed and maintained as part of the Fedora Project.
  • CFSSL[38][39] open source toolkit developed by CloudFlare for signing, verifying, and bundling TLS certificates. (BSD 2-clause licensed)
  • Vault[40] tool for securely managing secrets (TLS certificates included) developed by HashiCorp. (Mozilla Public License 2.0 licensed)
  • Boulder, an ACME-based CA written in Go. Boulder is the software that runs Let's Encrypt.



Some argue that purchasing certificates for securing websites by SSL/TLS and securing software by code signing is a costly venture for small businesses.[41] However, the emergence of free alternatives, such as Let's Encrypt, has changed this. HTTP/2, the latest version of HTTP protocol, allows unsecured connections in theory; in practice, major browser companies have made it clear that they would support this protocol only over a PKI secured TLS connection.[42] Web browser implementation of HTTP/2 including Chrome, Firefox, Opera, and Edge supports HTTP/2 only over TLS by using the ALPN extension of the TLS protocol. This would mean that, to get the speed benefits of HTTP/2, website owners would be forced to purchase SSL/TLS certificates controlled by corporations.

Currently the majority of web browsers are shipped with pre-installed intermediate certificates issued and signed by a certificate authority, by public keys certified by so-called root certificates. This means browsers need to carry a large number of different certificate providers, increasing the risk of a key compromise.[43]

When a key is known to be compromised, it could be fixed by revoking the certificate, but such a compromise is not easily detectable and can be a huge security breach. Browsers have to issue a security patch to revoke intermediary certificates issued by a compromised root certificate authority.[44]

See also



  1. ^ Chien, Hung-Yu (2021-08-19). "Dynamic Public Key Certificates with Forward Secrecy". Electronics. 10 (16): 2009. doi:10.3390/electronics10162009. ISSN 2079-9292.
  2. ^ "Public Key Infrastructure (PKI)". The European Union Agency for Cybersecurity (ENISA) :: Incident Response :: Glossary. European Union. Retrieved 14 May 2024.
  3. ^ Fruhlinger, Josh (29 May 2020). "What is PKI? And how it secures just about everything online". CSOOnline. Retrieved 26 August 2021.
  4. ^ "Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices Framework". IETF. Retrieved 26 August 2020.
  5. ^ "Public Key Infrastructure". MSDN. Retrieved 26 March 2015.
  6. ^ "Using Client-Certificate based authentication with NGINX on Ubuntu - SSLTrust". SSLTrust. Retrieved 13 June 2019.
  7. ^ Adams, Carlisle; Lloyd, Steve (2003). Understanding PKI: concepts, standards, and deployment considerations. Addison-Wesley Professional. pp. 11–15. ISBN 978-0-672-32391-1.
  8. ^ Trček, Denis (2006). Managing information systems security and privacy. Birkhauser. p. 69. ISBN 978-3-540-28103-0.
  9. ^ a b Vacca, Jhn R. (2004). Public key infrastructure: building trusted applications and Web services. CRC Press. p. 8. ISBN 978-0-8493-0822-2.
  10. ^ Viega, John; et al. (2002). Network Security with OpenSSL. O'Reilly Media. pp. 61–62. ISBN 978-0-596-00270-1.
  11. ^ McKinley, Barton (January 17, 2001). "The ABCs of PKI: Decrypting the complex task of setting up a public key infrastructure". Network World. Archived from the original on May 29, 2012.
  12. ^ Al-Janabi, Sufyan T. Faraj; et al. (2012). "Combining Mediated and Identity-Based Cryptography for Securing Email". In Ariwa, Ezendu; et al. (eds.). Digital Enterprise and Information Systems: International Conference, Deis, [...] Proceedings. Springer. pp. 2–3. ISBN 9783642226021.
  13. ^ "Mike Meyers CompTIA Security+ Certification Passport", by T. J. Samuelle, p. 137.
  14. ^ Henry, William (4 March 2016). "Trusted Third Party Service". Archived from the original on 4 March 2016. Retrieved 4 March 2016.
  15. ^ Smith, Dickinson & Seamons 2020, p. 1.
  16. ^ a b Sheffer, Saint-Andre & Fossati 2022, 7.5. Certificate Revocation.
  17. ^ Chung et al. 2018, p. 3.
  18. ^ Smith, Dickinson & Seamons 2020, p. 10.
  19. ^ Larisch et al. 2017, p. 542.
  20. ^ Smith, Dickinson & Seamons 2020, p. 1-2.
  21. ^ "Counting SSL certificates". 13 May 2015.
  22. ^ "CA:Symantec Issues". Mozilla Wiki. Retrieved 10 January 2020.
  23. ^ "Chrome's Plan to Distrust Symantec Certificates". Google security blog. Retrieved 10 January 2020.
  24. ^ "JDK-8215012 : Release Note: Distrust TLS Server Certificates Anchored by Symantec Root CAs". Java Bug Database. Retrieved 10 January 2020.
  25. ^ "Information about distrusting Symantec certificate authorities". Apple Support. 2023-09-05. Retrieved 2024-01-16.
  26. ^ Single Sign-On Technology for SAP Enterprises: What does SAP have to say? "Single Sign-On Technology for SAP Enterprises: What does SAP have to say? | May 2010 | SECUDE AG". Archived from the original on 2011-07-16. Retrieved 2010-05-25.
  27. ^ Ed Gerck, Overview of Certification Systems: x.509, CA, PGP and SKIP, in The Black Hat Briefings '99, and Archived 2008-09-05 at the Wayback Machine
  28. ^ Gonzalez, Eloi. "Simple Public Key Infrastructure" (PDF).
  29. ^ "Decentralized Identifiers (DIDs)". World Wide Web Consortium. 9 December 2019. Archived from the original on 14 May 2020. Retrieved 16 June 2020.
  30. ^ "Decentralized Public Key Infrastructure". 23 December 2015. Retrieved 23 June 2020.
  31. ^ Ellis, James H. (January 1970). "The Possibility of Secure Non-Secret Digital Encryption" (PDF). Archived from the original (PDF) on 2014-10-30.
  32. ^ Prodromou, Agathoklis (2019-03-31). "TLS Security 2: A Brief History of SSL/TLS". Acunetix. Retrieved 2024-05-25.
  33. ^ "PKI Assessment Guidelines" (PDF). Information Security Committee. 0.3: 43. 2001.
  34. ^ Stephen Wilson, December 2005, "The importance of PKI today" Archived 2010-11-22 at the Wayback Machine, China Communications, Retrieved on 2010-12-13
  35. ^ Mark Gasson, Martin Meints, Kevin Warwick (2005), D3.2: A study on PKI and biometrics, FIDIS deliverable (3)2, July 2005
  36. ^ "xipki/xipki · GitHub". Retrieved 2016-10-17.
  37. ^ Hohnstädt, Christian. "X - Certificate and Key management". Retrieved 2023-12-29.
  38. ^ Sullivan, Nick (10 July 2014). "Introducing CFSSL - Cloudflare's PKI toolkit". CloudFlare's Blog. CloudFlare. Retrieved 18 April 2018.
  39. ^ "cloudflare/cfssl · GitHub". Retrieved 18 April 2018.
  40. ^ "hashicorp/vault · GitHub". Retrieved 18 April 2018.
  41. ^ "Should We Abandon Digital Certificates, Or Learn to Use Them Effectively?". Forbes.
  42. ^ "HTTP/2 Frequently Asked Questions". HTTP/2 wiki – via Github.
  43. ^ "Root Certificate vs Intermediate Certificates". About SSL. Retrieved 2022-05-02.
  44. ^ "Fraudulent Digital Certificates could allow spoofing". Microsoft Security Advisory. Microsoft. March 23, 2011. Retrieved 2011-03-24.

Works cited