PKI (public key infrastructure)
What is PKI (public key infrastructure)?
Public key infrastructure (PKI), profiled for internet use in RFC 5280, is the system of certificate authorities, certificates and trust chains that lets a client verify a server's identity without ever sharing a secret in advance. AdminKit's SSL check tool verifies whether a site's certificate chains up to a trusted root, PKI's core guarantee.
By AdminKit team, Netbase JSC · Updated
Public key infrastructure (PKI) is the overall system of certificate authorities, certificates, and trust relationships, profiled for internet use in RFC 5280 — also tracked on its IETF Datatracker page — that lets one party prove its identity to another using public-key cryptography without the two ever having met or exchanged a secret in advance. NIST’s CSRC glossary defines it more compactly as “a framework that is established to issue, maintain and revoke public key certificates.” A client trusts a certificate not because it inspects the server’s key directly, but because it can verify an unbroken chain of signatures leading from that certificate back to a root the client’s operating system or browser already trusts. PKI covers more than issuance: it also defines how a certificate is revoked before its stated expiry, via a certificate revocation list or OCSP stapling — the CA/Browser Forum’s Baseline Requirements bind every publicly-trusted CA to make that revocation information available via CRL and/or OCSP — and how a private key is protected, since PKI’s entire guarantee collapses the moment a CA’s or server’s private key is exposed. The web’s HTTPS trust model runs on these same PKI foundations.
PKI (public key infrastructure) is part of AdminKit’s machine protocols cluster; the full AdminKit glossary lists other related terms.
Frequently asked questions
How does a client trust a certificate without inspecting the server's key directly?
It verifies an unbroken chain of signatures leading from that certificate back to a root the client's operating system or browser already trusts, rather than inspecting or exchanging the server's key out of band.
Does PKI only cover certificate issuance?
No -- it also defines how a certificate is revoked before its stated expiry, via a certificate revocation list or OCSP stapling, and how a private key is protected.
What breaks PKI's entire guarantee?
The exposure of a CA's or server's private key -- PKI's entire guarantee collapses the moment that happens, since every signature that key ever produced can no longer be trusted as genuine.
What RFC profiles PKI for internet use?
RFC 5280 profiles public key infrastructure specifically for internet use, defining the certificate and CRL formats the web's HTTPS trust model runs on.
Sources
- RFC 5280 -- Internet X.509 Public Key Infrastructure Certificate and CRL Profile
- RFC 6960 -- X.509 Internet PKI Online Certificate Status Protocol (OCSP)
- IETF Datatracker -- RFC 5280 document page
- CA/Browser Forum -- Baseline Requirements for the Issuance and Management of Publicly-Trusted TLS Server Certificates
- NIST CSRC Glossary — public key infrastructure (PKI)