Public Key Infrastructure
Public key infrastructure, or PKI, is the system of authorities, policies, certificates, and trust stores that binds public keys to identities. It lets software decide which keys to trust for authentication, encryption, and digital signatures without arranging a separate secret with every party.
itIdentity, access, and cryptography | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Intro
Public Key Infrastructure
Public key infrastructure, or PKI, is a system for creating, distributing, validating, and retiring digital certificates. A certificate binds a public key to a named subject or other certified identity information. A certification authority signs that binding. A relying party accepts it only when the certificate satisfies policy and builds a valid path to a trusted anchor.
PKI solves a distribution problem. Public-key cryptography provides a key pair, but a bare public key does not identify its owner. PKI adds governed evidence about identity, permitted use, validity, and issuer. It supports TLS server authentication, mutual TLS, user and device identity, code signing, document signatures, and secure email.
Architecture and trust
A common hierarchy has an offline root certification authority, one or more online intermediate certification authorities, and end-entity certificates. The root is a trust anchor installed through a controlled trust-store process. It signs intermediate CA certificates infrequently. Intermediates handle routine issuance, which limits the root key's exposure and creates smaller failure domains.
Continue the course
This section is part of the paid course.
See pricing to subscribe, or log in if you already have access.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://www.nist.gov/publications/introduction-public-key-technology-and-federal-pki-infrastructure
Supports
- PKI functions, participants, hierarchies, trust models, and applications
- Certification authority, registration authority, repository, subscriber, and relying-party roles
- https://www.itu.int/rec/t-rec-x.509/en
Supports
- Public-key certificate and revocation-list frameworks
- Certification authorities, relying parties, trust anchors, and path validation
- First X.509 recommendation in November 1988
- https://www.rfc-editor.org/rfc/rfc5280.html
Supports
- X.509 version three certificate and CRL fields and extensions
- Certification-path construction and validation
- Basic Constraints, Key Usage, Extended Key Usage, Name Constraints, and critical-extension handling
- https://www.rfc-editor.org/rfc/rfc9525.html
Supports
- Matching an expected TLS service identity to certificate identifiers
- Identity mismatch as a validation failure despite a signed chain
- https://www.rfc-editor.org/rfc/rfc3647.html
Supports
- Certificate policy and certification practice statement structure
- Governance topics for identification, operations, compromise, audit, and termination
- https://csrc.nist.gov/pubs/sp/800/57/pt1/r5/final
Supports
- Key protection, lifecycle, cryptoperiod, backup, recovery, compromise, and destruction
- Different handling requirements based on cryptographic key purpose
- https://www.rfc-editor.org/rfc/rfc6960.html
Supports
- OCSP request and signed-response processing
- Good, revoked, and unknown status meanings and their limits
- https://www.rfc-editor.org/rfc/rfc8555.html
Supports
- ACME accounts, orders, authorization challenges, finalization, issuance, and revocation
- Renewal through creation of a new certificate order
- https://cabforum.org/working-groups/server/baseline-requirements/requirements/
Supports
- Current governance and issuance requirements for publicly trusted TLS certificates
- https://github.com/ripienaar/free-for-dev/blob/master/README.md#security-and-pki
Supports
- Discovery of Let's Encrypt, CertObserver, Otterwatch, SSL and TLS testing resources in an actual awesome list reached from sindresorhus/awesome
- https://letsencrypt.org/how-it-works/
Supports
- Domain-control challenges, CSR issuance, renewal, revocation, and CT submission in a public ACME CA
- Awesome Links rationale for Let's Encrypt
- https://certobserver.com/
Supports
- Certificate inventory, CT search and alerts, endpoint validation, expiry, chain, hostname, and trust signals
- Awesome Links rationale for CertObserver
- https://otterwatch.dev/
Supports
- Daily endpoint reachability and presented-certificate expiry monitoring
- Awesome Links rationale for Otterwatch
- https://testtls.com/
Supports
- Live TLS service checks for configuration, certificate, and chain information
- Awesome Links rationale for TestTLS.com
- https://ee.stanford.edu/~hellman/publications/24.pdf
Supports
- November 1976 publication of public-key distribution and digital-signature concepts
- https://people.csail.mit.edu/rivest/Rsapaper.pdf
Supports
- February 1978 RSA public-key encryption and signature publication
- https://www.itu.int/rec/dologin_pub.asp?id=T-REC-X.509-198811-S%21%21PDF-E&lang=e&type=items
Supports
- 1988 X.509 authentication framework and certificate model
- https://www.rfc-editor.org/info/rfc1422
Supports
- February 1993 PEM certificate-based key management milestone
- https://csrc.nist.gov/nist-cyber-history/cryptography/chapter
Supports
- Formation of the NIST and IETF PKIX working group in 1995
- Shift of Internet PKI profiling work toward the IETF
- https://www.rfc-editor.org/info/rfc2459
Supports
- January 1999 Internet X.509 certificate and CRL profile milestone
- https://www.rfc-editor.org/info/rfc3647
Supports
- November 2003 CP and CPS framework publication milestone
- https://www.rfc-editor.org/info/rfc5280
Supports
- May 2008 publication and predecessor obsolescence milestone
- https://www.rfc-editor.org/info/rfc6962
Supports
- June 2013 Certificate Transparency publication milestone
- https://letsencrypt.org/2015/06/16/lets-encrypt-launch-schedule
Supports
- Let's Encrypt 2015 launch schedule and automation-centered CA model
- https://letsencrypt.org/2025/12/09/10-years.html
Supports
- September 14, 2015 first publicly trusted Let's Encrypt certificate
- https://www.rfc-editor.org/info/rfc8555
Supports
- March 2019 ACME standardization milestone
- https://www.digicert.com/digicert-one
Supports
- DigiCert ONE public and private PKI, lifecycle, and signing placement
- https://www.sectigo.com/enterprise-solutions/certificate-manager
Supports
- Sectigo public and private certificate lifecycle management placement
- https://www.keyfactor.com/products/command/
Supports
- Keyfactor certificate discovery and lifecycle automation placement
- https://www.cyberark.com/products/certificate-manager/
Supports
- CyberArk certificate inventory, policy, renewal, and deployment placement
- https://www.appviewx.com/products/kubeplus/
Supports
- AppViewX cloud-native certificate lifecycle automation placement
- https://www.keyfactor.com/products/ejbca-enterprise/
Supports
- EJBCA CA, RA, certificate profile, and status-service placement
- https://smallstep.com/certificate-manager/
Supports
- Smallstep private authority and automated enrollment placement
- https://smallstep.com/docs/step-ca/
Supports
- step-ca offline-root, online-intermediate, ACME, provisioner, and key-protection capabilities
- https://learn.microsoft.com/en-us/windows-server/identity/ad-cs/active-directory-certificate-services-overview
Supports
- Active Directory Certificate Services CA, enrollment, and template placement
- https://aws.amazon.com/private-ca/
Supports
- AWS managed private root and subordinate CA placement
- https://cloud.google.com/certificate-authority-service
Supports
- Google managed private CA pools, policies, keys, and audit placement
- https://developer.hashicorp.com/vault/docs/secrets/pki
Supports
- Vault PKI root and intermediate operation, role policy, and short-lived issuance placement
