Public-Key Infrastructure

Public-key infrastructure, usually shortened to PKI, is the system of rules, organisations and software that binds a public key to the identity of a person, company, website or device. It does this through digital certificates: signed electronic documents in which a trusted issuer, called a certificate authority, vouches that a particular public key belongs to a particular name. Browsers, operating systems, banks and payment networks rely on PKI to decide which keys to trust.

PKI is the trust layer that sits on top of public-key cryptography. The maths proves that a message was signed with a given private key; PKI answers the separate question of whose key that is. Public blockchains mostly work without it, treating keys as self-issued pseudonyms, which is one of the clearest differences between crypto and traditional financial security.

Think of a passport. Anyone can make a booklet with a photo in it, but border staff trust a passport because a government they recognise issued it and built in features that are hard to forge. The passport links a face to a name, and the government's reputation stands behind that link.

A digital certificate does the same for a public key. When a browser connects to a bank's website, the site shows a certificate saying "this key belongs to this bank", signed by an authority the browser already trusts. If the signature checks out and the certificate has not expired or been cancelled, the browser shows the connection as secure.

A working PKI has several parts:

• Certificate authorities. These organisations verify an applicant's identity, then sign certificates. A small number of root authorities have their own certificates built into browsers and operating systems.
• Registration authorities. These handle the identity checks on behalf of a certificate authority in some set-ups.
• Certificates. Most follow the X.509 standard and contain the subject's name, the public key, a validity period, the issuer and the issuer's digital signature.
• Revocation services. Certificate revocation lists and online status checks let users find out whether a certificate has been cancelled early, for example because its key was stolen.

Certificates usually form a chain. A root authority signs an intermediate certificate, which in turn signs the certificate for an individual website. Software checks each link up to a root it already trusts.

PKI is built into much of the financial system's plumbing:

• Secure websites. Online banking and card checkout pages use certificates for the Transport Layer Security protocol, the successor to SSL.
• Payment cards. Chip cards carry keys and certificates issued under a hierarchy run by the card schemes, which terminals use to check that a card is genuine.
• Bank messaging. Interbank networks and open banking regimes use certificates to identify participating institutions and sign their messages.
• Electronic signatures. Qualified electronic signatures under the EU's eIDAS regulation depend on certificates from supervised trust service providers.

Bitcoin and similar networks deliberately avoid a central certificate authority. Anyone can generate a key pair, and the network only checks that a transaction was signed by the right private key. This makes the system open and censorship-resistant, but it also means there is no authority to confirm who controls an address or to cancel a stolen key. Identity, where needed, is added outside the chain through exchange know your customer checks or through newer schemes built on the decentralised identifier, some of which borrow PKI ideas such as signed credentials.

PKI concentrates trust in a relatively small number of authorities, so a single compromised authority can undermine many systems. The best-known case is the 2011 breach of the Dutch authority DigiNotar, whose fraudulent certificates were used to intercept traffic and which went bankrupt soon afterwards. Revocation has long been unreliable in practice, because many clients do not check status consistently. Managing certificate lifetimes is also an operational burden, and expired certificates regularly cause outages at large firms. Efforts such as Certificate Transparency, which publishes issued certificates in public logs that anyone can monitor, aim to make misissuance easier to spot, and browser makers have steadily shortened the maximum life of website certificates to limit the damage a stolen key can do. Critics also note that the identity checks behind the cheapest certificates only confirm control of a domain name, not that the site belongs to a legitimate business, so a padlock icon alone says little about whether a site is honest. Like the cryptography beneath it, PKI will need to move to quantum-resistant algorithms over time, a transition standards bodies began planning after NIST's post-quantum standards appeared in August 2024.

• NIST Post-Quantum Cryptography project
• Certificate Transparency