Every secure website, every signed email, and every encrypted login a company runs depends on a system most people never see. That system is called Public Key Infrastructure (PKI). Ask what PKI is, and the short answer is this: it is a framework of software, policies, and trusted third parties. It issues, manages, and revokes digital certificates so computers can prove who they are to each other.
PKI is not optional background plumbing. The National Institute of Standards and Technology (NIST) defines it plainly. A Public Key Infrastructure is a framework set up to issue, maintain, and revoke digital certificates tied to public keys. That framework sits behind browser padlocks, VPN logins, code-signing, and the encrypted email many businesses rely on daily.
For a founder or IT manager without a cryptography background, the goal here is not to master the math. It is to understand three things. First, the three moving parts of PKI. Second, why certificate authorities matter. Third, where PKI shows up in audits for frameworks like SOC 2, HIPAA, and CMMC (Cybersecurity Maturity Model Certification). This guide covers all three plainly, using the terms regulators and standards bodies actually use.
What Is Public Key Infrastructure, Exactly?
Public Key Infrastructure is the mix of technology, rules, and organizations that makes secure digital identity possible at scale. NIST describes it as software, public key technology, and services combined. Together they let a company run a security system built on public-key methods. In plain terms, PKI lets two parties who have never met confirm each other’s identity and swap data privately. That could be a browser and a web server, or two companies emailing contracts.
The core problem PKI solves is trust at a distance. A laptop cannot simply ask a website whether it is really a customer’s bank and trust the answer. It needs a neutral third party to vouch for that identity, backed by cryptographic proof rather than a claim. That neutral vouching is exactly what a certificate authority does, covered below.
Public Keys, Private Keys, and Why They Come in Pairs
PKI rests on asymmetric cryptography, also called public-key cryptography. NIST defines it as a cryptographic method that uses two related keys: a public key and a private key. Each key pair works as a matched set, not two separate secrets.
Anyone can share the public key freely. The matching private key stays secret, and only its owner controls it. Data locked with one key in the pair can only be unlocked with the other. That is what makes identity checks and encrypted messaging possible without ever sharing a password.
This pairing matters for practical reasons. A private key never has to travel across a network, so no one can intercept it in transit the way they could a password. A server proves its identity by using its private key to sign data that anyone can check against the matching public key. If the signature checks out, the identity claim holds up.
What Is a PKI Certificate?
A PKI certificate, formally called a digital certificate, is the document that ties a public key to a specific identity. NIST’s definition is direct: a digital certificate is a set of data that uniquely identifies an entity and contains that entity’s public key. A trusted party digitally signs it, binding the public key to the entity.
That trusted-party signature is the whole point. Anyone can generate a key pair and claim to be a company. A certificate only carries weight because a recognized certificate authority checked the claim and signed off on it. Without that signature, a public key is just a string of characters with no verified owner behind it.
Certificates also expire. Every certificate carries a validity period: the stretch of time between its issue date and its expiration date. For public certificates that secure websites, that window keeps shrinking by design. The CA/Browser Forum is the industry group whose baseline rules browsers and certificate authorities follow. It approved a phased schedule that cuts maximum certificate lifespan from the long-standing 398-day cap down to 47 days by 2029. Shorter lifespans limit how long a stolen or misused certificate stays valid. But they also mean businesses need automated renewal instead of manual tracking.
What Does a Certificate Authority Do?
A certificate authority is the organization responsible for checking identity claims and issuing certificates. NIST’s key management guidance calls it the entity in a Public Key Infrastructure that issues certificates and enforces a PKI policy.
Think of a CA as a notary for the internet. Before signing a certificate, a reputable CA checks that the requester actually controls the domain, organization, or device named in the request. Public CAs that browsers trust by default must follow baseline rules set by the CA/Browser Forum. This voluntary group sets minimum security standards for publicly trusted certificates.
Some organizations run a private CA instead of relying on public ones. A private CA issues certificates only for internal use. Examples include securing traffic between a company’s own servers or verifying employee devices on a corporate network. Public CAs serve external-facing trust instead, like confirming to a customer’s browser that a company website is genuine.
How the Pieces Work Together
A simple transaction shows the whole chain in action. A server operator generates a key pair and keeps the private key secured. The operator then sends the public key to a certificate authority along with proof of identity. The CA verifies the claim, then issues a certificate binding that public key to the organization’s name.
When a visitor’s browser connects to that server, several checks happen automatically and in order:
- The browser receives the certificate and checks the CA’s digital signature on it.
- The browser confirms the CA itself is trusted. It traces back through a chain of signatures to a trust anchor already built into the browser or operating system.
- The server proves it holds the matching private key by signing a piece of session data.
- If every check passes, the browser shows the padlock and the encrypted connection begins.
None of this requires the user to understand cryptography. It happens in milliseconds, invisibly. That is why PKI counts as foundational infrastructure rather than a visible product.
Why PKI Matters for Compliance
Security frameworks that Bay Area small and mid-size businesses pursue, including SOC 2, HIPAA, and CMMC, all expect encryption in transit and at rest for sensitive data. PKI is the mechanism that makes encryption in transit work for web traffic, email, and VPN connections. An auditor reviewing encryption controls is, in effect, reviewing how a company issues, renews, and revokes certificates.
Problems tend to show up in predictable places. Expired certificates break services and create downtime, which shows up in availability-focused SOC 2 controls. Weak or outdated signing algorithms can fail HIPAA’s requirement to protect electronic patient health information in transit. CMMC assessors reviewing a defense contractor’s environment expect to see proof that sensitive unclassified information moves only across properly encrypted, authenticated channels. That depends on a sound certificate setup behind the scenes.
Certificate management also becomes a visibility problem as companies grow. A business running a handful of servers can track certificate expiration by hand. A business running dozens of internal services, cloud workloads, and employee devices usually cannot. An expired certificate discovered during an audit raises hard questions about change management and monitoring more broadly.
Common PKI Mistakes Smaller Companies Make
Few small and mid-size businesses set out to build a PKI deployment badly. Most problems come from treating certificates as a one-time setup task instead of an ongoing operational control.
- No central inventory. Different teams issue certificates for different services with no single list of what exists or when each one expires.
- Manual renewal. Someone sets a calendar reminder, the reminder gets missed, and a public-facing service goes down or shows a browser warning.
- Weak private key storage. A private key sitting in a shared drive or unencrypted config file defeats the purpose of the whole system.
- Mixing public and private CA use without a clear policy on which systems need which type of certificate.
Each of these gaps is fixable with process, not new cryptography. The fix is usually a certificate inventory, automated renewal tooling, and a written policy. That policy should spell out who can request a certificate and how to store private keys.
Getting PKI Right Before an Audit
PKI is not a product a company buys once. It is an ongoing set of policies and technical controls covering how a company requests, issues, renews, and revokes certificates. Getting it right means fewer outages, stronger encryption claims in an audit, and one less gap for an assessor to flag.
Planet 9 is a Bay Area cybersecurity consulting firm specializing in SOC 2, HIPAA, and CMMC readiness for small and mid-size businesses in healthcare, SaaS, and technology. Our vCISOs and compliance managers help organizations choose the right approach, configure governance, risk, and compliance tools if needed, and get audit-ready without wasted time.






