Public Key Infrastructure (PKI)

The foundational trust anchor in a PKI hierarchy. A CA is a trusted entity that issues, manages, and revokes digital certificates. It cryptographically signs a certificate with its own private key, vouching for the binding between a public key and the identity of its owner.

• Root CA: The ultimate trust anchor; its self-signed certificate is distributed via secure out-of-band methods.
• Issuing CA: A subordinate authority that issues end-entity certificates, enforcing specific policies.
• Validation Levels: Domain Validation (DV), Organization Validation (OV), and Extended Validation (EV) represent increasing levels of identity verification.

The gatekeeper that performs identity verification before a certificate is issued. The RA acts as an intermediary between end-users and the CA, offloading the administrative burden of authenticating subscriber identity.

• Identity Proofing: Validates organizational documents, domain control, or individual credentials.
• Key Generation: In some architectures, the RA securely generates key pairs on behalf of the subscriber.
• Separation of Duties: Isolates the credential vetting process from the cryptographic signing operation performed by the CA.

A publicly accessible directory storing issued certificates and their revocation status. This component ensures relying parties can always verify the current validity of a credential.

• Certificate Revocation List (CRL): A periodically published, signed list of serial numbers for certificates that have been revoked before their expiration date.
• Online Certificate Status Protocol (OCSP): A real-time query protocol that returns the status of a single certificate, offering lower latency than downloading a full CRL.
• OCSP Stapling: The server includes a time-stamped OCSP response in the TLS handshake, improving privacy and performance.

The governance documents that define the operational and legal framework of a PKI. They establish the rules that determine the trustworthiness of a certificate.

• Certificate Policy (CP): A named set of rules that indicates the applicability of a certificate to a particular community or class of applications with common security requirements.
• Certification Practice Statement (CPS): A detailed statement of the operational procedures and technical controls a CA uses to issue and manage certificates, effectively implementing the CP.
• Relying Party Agreement: Defines the obligations and liability limitations for entities that trust the certificates.

A dedicated, tamper-resistant physical computing device that safeguards and manages the CA's private signing keys. The HSM performs all cryptographic operations internally, ensuring the key material never leaves the secure boundary.

• FIPS 140-2 Level 3: The minimum security standard typically required for CA key storage, providing physical tamper-evidence and response.
• Key Ceremony: A rigorously audited, multi-person control procedure used to generate, backup, and activate the root CA key within the HSM.
• Private Key Protection: Prevents extraction and duplication of the signing key, which is the single most critical asset in the entire PKI.

The human and system actors that form the operational endpoints of a PKI. Their responsibilities are defined in the CP/CPS and are critical to maintaining the chain of trust.

• Subscriber: The entity that applies for and is bound to the certificate. They are obligated to protect their private key and promptly request revocation if it is compromised.
• Relying Party: Any entity that validates a digital signature or establishes an encrypted session by trusting a certificate issued by the CA.
• Key Lifecycle Management: Subscribers must manage key generation, secure storage, renewal, and destruction according to the policy.

The most ubiquitous application of PKI, enabling the HTTPS protocol. When a browser connects to a bank or e-commerce site, the server presents an X.509 certificate issued by a trusted Certificate Authority (CA). The browser validates the certificate chain up to a pre-installed root CA, performs a cryptographic challenge to verify the server possesses the corresponding private key, and establishes an encrypted session.

• Extended Validation (EV) Certificates: Require rigorous legal entity verification, historically displaying the organization's name in the browser bar.
• Certificate Revocation: Browsers check Certificate Revocation Lists (CRLs) or use the Online Certificate Status Protocol (OCSP) to ensure a certificate hasn't been revoked before granting trust.
• Certificate Transparency (CT): A mandatory framework where CAs must log all issued certificates to public, append-only logs, allowing domain owners to monitor for fraudulent issuance.

PKI assures that software originates from a verified publisher and hasn't been tampered with since compilation. Developers use a code signing certificate and its associated private key to digitally sign executables, scripts, and drivers. The operating system then uses the corresponding public key to verify the signature before execution.

• Authenticode: Microsoft's standard for signing Windows executables, ensuring users aren't tricked into running malware.
• Software Bill of Materials (SBOM): An emerging practice where every component in a software build is cryptographically attested, creating a verifiable chain of custody from source code to deployment.
• SLSA Framework: Uses PKI-based attestations to create tamper-proof metadata about the build process itself, preventing supply chain attacks like the SolarWinds incident.

PKI-based smart cards and hardware tokens provide phishing-resistant multi-factor authentication (MFA) for high-security environments. Each employee is issued a physical device containing a unique private key and an X.509 certificate. Logging into a workstation or VPN requires presenting the device and a PIN, proving physical possession and knowledge.

• Active Directory Certificate Services: Microsoft's PKI implementation that auto-enrolls domain-joined machines and users for certificate-based authentication to network resources.
• 802.1X Network Access Control: Uses EAP-TLS, a certificate-based authentication protocol, to grant a device access to the physical network only after its machine certificate is validated, preventing rogue device connections.
• Defense-in-Depth: Even if a password is phished, an attacker cannot authenticate without the physical cryptographic token containing the private key.

In regulated industries like finance and healthcare, a digital signature provides legal non-repudiation. Applying a digital signature to a PDF contract or an email uses the sender's private key to create a cryptographic hash of the document. The recipient can verify that the document hasn't been altered and that it originated from the claimed sender.

• eIDAS Regulation: The EU's legal framework that gives qualified electronic signatures the same legal standing as handwritten signatures.
• S/MIME (Secure/Multipurpose Internet Mail Extensions): A protocol for sending signed and encrypted emails using X.509 certificates, ensuring end-to-end confidentiality and authenticity.
• Long-Term Validation (LTV): A mechanism that embeds all necessary certificate chain information, CRLs, and timestamps into the signed document itself, ensuring the signature can be verified decades later, even after the issuing CA has expired.

PKI provides a unique, cryptographically verifiable identity to billions of connected devices, from smart meters to medical sensors. During manufacturing, a unique private key and device certificate are injected into the hardware's secure element. This identity is used for mutual TLS (mTLS) authentication with cloud platforms, ensuring only genuine devices can connect.

• Secure Boot: The device's firmware uses a manufacturer's public key to verify the digital signature of the bootloader and operating system before execution, preventing persistent malware.
• AWS IoT Core / Azure IoT Hub: Cloud platforms that require devices to present a valid X.509 certificate for provisioning and data ingestion, forming the root of trust for the entire IoT fleet.
• Matter Protocol: The smart home standard mandates a PKI-based device attestation certificate to verify the device's authenticity and certification status before it can join a home network.

In the era of generative AI, PKI is the foundation for proving the origin and edit history of digital media. The Coalition for Content Provenance and Authenticity (C2PA) standard uses PKI to cryptographically sign a manifest that is bound to an image or video. This manifest records the initial capture device, the editing software used, and any AI modifications.

• Hardware Root of Trust: A camera's secure hardware signs the raw sensor data at the moment of capture, creating a verifiable chain from photon to pixel.
• Verifiable Credentials: The C2PA manifest is a specialized verifiable credential, allowing a news platform to automatically validate a photo's provenance before publication.
• Combating Deepfakes: By checking for a valid C2PA signature chain, a viewer can distinguish an authentic photograph from a synthetically generated one, even if they are visually indistinguishable.