Public Key Infrastructure
What is public key infrastructure?
Public key infrastructure, or PKI, is a security framework that verifies digital identities and protects data with certificates and cryptographic key pairs. It helps software confirm who it is talking to, encrypt information when needed, and detect tampering. PKI includes trust rules, identity checks, certificate management, and secure key handling, not only a public and private key.
How PKI works: keys, certificates, and trust
PKI creates a trusted link between an identity and a public key.
- A person, service, or device generates a public and private key pair.
- The private key stays secret, while the public key can be shared.
- A registration process validates the identity requesting a certificate.
- A certificate authority issues a certificate that binds that identity to its public key.
- Software presents the certificate, then checks its signature and trusted issuer.
- Certificates are renewed before expiry or revoked if a key is compromised.
Core components of a PKI
These components establish and maintain trust. Policies and secure key storage control how each is used.
| Component | Purpose |
|---|---|
| Certificate authority | Issues and signs certificates. |
| Registration authority | Checks an applicant's identity. |
| Digital certificate | Connects an identity to a public key. |
| Key pair | Supports encryption or digital signatures. |
| Certificate repository | Stores or publishes certificates. |
| CRL or OCSP | Reports whether a certificate was revoked. |
PKI vs. TLS and SSL
PKI provides identity and trust. TLS uses that trust to protect a connection.
| Technology | Role |
|---|---|
| PKI | Manages certificates, keys, and trusted issuers. |
| TLS | Encrypts data moving between software systems. |
| SSL | An obsolete predecessor to modern TLS. |
Where public key infrastructure is used in software
PKI supports many everyday security controls.
- HTTPS websites and browser certificate checks.
- Mutual TLS for service-to-service API authentication.
- Code signing and verified software updates.
- Signed or encrypted email and documents.
- Device, container, and workload identities.
Benefits of public key infrastructure
PKI makes trust more scalable than manually sharing secrets.
- Authenticates websites, services, users, and devices.
- Supports encryption for confidentiality.
- Uses signatures to reveal altered data.
- Can provide proof of signing when controls are strong.
Practical limits and risks of PKI
A certificate alone does not make an application secure.
- Expired certificates can interrupt production systems.
- Exposed private keys can let attackers impersonate an identity.
- Weak validation or incorrect trust settings undermine PKI.
- Revocation checks may not always be available or enforced.
PKI practices for application teams
Good operations matter as much as sound cryptography.
- Automate renewal and monitor certificate expiry.
- Keep private keys in managed secret stores or hardware-backed systems.
- Use short-lived credentials where practical.
- Test expired, revoked, and untrusted certificate failure paths.
- Use an API key only where it fits, and protect every public API with appropriate authentication.
Public key infrastructure in apps built with Emergent
Teams using an AI app builder still need to define trusted integrations, protect secrets, use HTTPS, and plan certificate management for external services. Build trusted apps with Emergent.
on Emergent today

