Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Public key infrastructure (PKI) is the framework of policies, systems, and certificate authorities that issues and manages digital certificates, binding public keys to verified identities.

What Is Public Key Infrastructure (PKI)?
Public key infrastructure (PKI) is the system of roles, policies, software, and hardware used to create, distribute, manage, and revoke digital certificates. A certificate binds a public key to an identity, such as a website, a person, a device, or a software publisher, and PKI provides the trusted framework that lets everyone else rely on that binding.
Every time your browser shows a padlock, PKI is at work. It also secures email signing and encryption, VPN and Wi-Fi authentication, code signing, smart card logins, and the machine-to-machine connections inside modern cloud platforms.
Public key cryptography uses a pair of mathematically linked keys. Data encrypted with the public key can only be decrypted with the private key, and a signature created with the private key can be verified with the public key. The weakness is distribution: how do you know a public key really belongs to your bank and not to an attacker staging a man-in-the-middle attack?
PKI answers this by having a trusted third party, a certificate authority, vouch for the binding between a key and an identity.
Browsers and operating systems ship with a trust store containing a few hundred root CA certificates. When a website presents its certificate, the client checks that it was signed by an intermediate CA, that the intermediate was signed by a trusted root, that the name matches the site, that nothing has expired, and that nothing has been revoked. If any link fails, the connection is flagged as untrusted.
This model is powerful but depends on every CA behaving correctly. When the Dutch CA DigiNotar was compromised in 2011, attackers issued fraudulent certificates for Google and other domains, which were used to intercept users’ traffic. DigiNotar was removed from trust stores and went bankrupt. The incident accelerated Certificate Transparency, a system of public logs in which every publicly trusted certificate must be recorded, making mis-issuance far easier to detect.
Public CAs issue certificates trusted by browsers worldwide, governed by the rules of the CA/Browser Forum. Organisations also run private PKIs, often based on Active Directory Certificate Services, to issue certificates for internal systems, Wi-Fi authentication, VPN access, and device identity. Private PKIs are only as strong as their configuration, and misconfigured certificate templates in Active Directory Certificate Services have become a well-known route to domain compromise during penetration tests.
Certificates expire, and expired certificates cause outages. Major services have gone offline because a single certificate was missed. The challenge is growing: in 2025 the CA/Browser Forum approved a plan to reduce the maximum lifetime of public TLS certificates in stages, from 398 days to 200 days in March 2026, 100 days in 2027, and 47 days by 2029. Manual renewal will no longer be practical.
Good lifecycle management means keeping an inventory of every certificate, automating issuance and renewal with protocols such as ACME, protecting private keys properly, monitoring Certificate Transparency logs for unexpected certificates issued for your domains, and planning ahead for post-quantum cryptography.
PKI underpins TLS, phishing-resistant authentication with smart cards and FIDO2 keys, mutual TLS between microservices, and device identity in Zero Trust architectures.
At Privia Security, our Infrastructure and Architecture Review Services assess PKI design, certificate management, and Active Directory Certificate Services configuration for weaknesses attackers could exploit.
A root CA is the top of the trust hierarchy, and its certificate is pre-installed in browsers and operating systems. Because compromising it would be catastrophic, it is usually kept offline. Intermediate CAs are signed by the root and handle day-to-day certificate issuance, so that the root’s private key is rarely exposed.
Clients will refuse to trust it, which usually means browser warnings, failed API connections, broken VPN access, or complete service outages. Expired certificates are a surprisingly common cause of major incidents. Automated renewal through protocols such as ACME, together with an accurate certificate inventory and expiry monitoring, prevents most of these failures.
Shorter lifetimes limit how long a compromised or mis-issued certificate can be abused and encourage automation, which makes it easier to replace certificates quickly, for example when moving to new algorithms. The CA/Browser Forum has approved a phased reduction of public TLS certificate lifetimes to 47 days by 2029.
It can be if it is poorly managed. Weak protection of CA keys, overly permissive certificate templates, and missing revocation checks can allow attackers to issue themselves trusted certificates and impersonate users, including administrators. Internal PKIs should be designed carefully, use HSMs for key protection, and be reviewed regularly by specialists.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.