Public Key Infrastructure
In plain English
Plain definition
Public Key Infrastructure (PKI) is the combination of hardware, software, policies, and procedures used to create, distribute, store, and revoke digital certificates, and to manage the public and private key pairs that those certificates bind to an identity.
Technical definition
Formally, a PKI is a trust framework built around asymmetric cryptography. A Certificate Authority (CA) issues X.509 certificates that bind a public key to a subject identity after a Registration Authority (RA) verifies that identity. Relying parties validate a certificate by checking its signature against the issuing CA’s public key, confirming the certificate has not expired, and checking revocation status through a Certificate Revocation List (CRL) or the Online Certificate Status Protocol (OCSP). The RFC Editor publishes the Internet standards that define these certificate formats and validation behaviours as part of the RFC Series.
Operational relevance
Engineers encounter PKI wherever encrypted transport, mutual authentication, or code signing is required: TLS termination on load balancers, service-to-service mTLS in a service mesh, VPN client authentication, and signed software packages. Because certificates expire and revocation state changes over time, PKI failure is rarely a single event; it is usually a slow drift toward an expired or improperly trusted chain. Observable success for a PKI-dependent workflow includes: the full certificate chain validates to a trusted root without warnings, the certificate’s not-after date remains in the future with an agreed renewal margin, and revocation checks (CRL or OCSP) return a definite “not revoked” response rather than a timeout that is silently treated as valid.
Architecture relationship
PKI sits between identity systems and transport security. A CA hierarchy (root CA, intermediate CA, issuing CA) typically keeps its root offline or inside a hardware security module (HSM) to limit exposure, while issuing CAs handle day-to-day certificate issuance. Directory services or automated enrolment mechanisms distribute certificates to endpoints. Relying applications – web servers, mesh sidecars, VPN concentrators – depend on PKI but do not themselves manage the CA’s key material; separating issuance from consumption is what allows a compromised leaf certificate to be revoked and reissued without rebuilding the CA hierarchy.
Example
Consider issuing a certificate for an internal API service. The service generates a key pair and submits a certificate signing request (CSR) to the issuing CA. The RA verifies the request against an approved naming policy, the CA signs and returns the certificate, and the service presents it during TLS negotiation. A client validates the chain to the trusted root, checks the expiry date, and queries OCSP for revocation status before completing the handshake. If the private key is later suspected compromised, the correct recovery path is to revoke the certificate at the CA, publish that revocation via CRL or OCSP, and issue a replacement certificate with a new key pair – not to reuse the same key material.
Common misunderstanding
A frequent misunderstanding is treating “PKI” as synonymous with “TLS” or “SSL”. TLS is one consumer of PKI, but PKI itself is the broader issuance, trust, and revocation framework; the same infrastructure also underpins code signing, S/MIME email, and client certificate authentication. A related misunderstanding is assuming that a certificate which validates successfully guarantees the certified identity is trustworthy: chain validation only confirms that a trusted CA vouched for the binding between key and subject, which is only as reliable as that CA’s issuance policy and how well its private key has been protected.
Related terms
- Certificate Authority (CA)
- Registration Authority (RA)
- X.509 certificate
- Certificate Revocation List (CRL)
- Online Certificate Status Protocol (OCSP)
- Transport Layer Security (TLS)
- Hardware Security Module (HSM)
Further reading
The RFC Editor maintains the RFC Series, the authoritative publication channel for the Internet standards that define certificate formats, revocation mechanisms, and related PKI protocols. Confirm the specific RFC number and revision applicable to a given implementation before relying on version-specific behaviour, since standards evolve and are superseded.