Public Key Infrastructure (PKI)

The Certificate Authority (CA) is the trusted root of the PKI hierarchy. It is responsible for issuing, signing, and managing the lifecycle of digital certificates. The CA's own public key is distributed as a root certificate and is inherently trusted by relying parties.

• Functions: Validates the identity of certificate applicants, signs certificates with its private key, and publishes Certificate Revocation Lists (CRLs).
• Trust Anchor: The security of the entire PKI chain depends on the CA's private key being kept secure, often within a Hardware Security Module (HSM).

The Registration Authority (RA) acts as a front-end verifier for the CA. It offloads the initial identity proofing and validation of certificate applicants before the CA performs the final signing.

• Role Separation: The RA handles the manual or automated vetting process but does not possess the CA's signing keys, enforcing a principle of least privilege.
• Workflow: Receives certificate signing requests (CSRs), validates the requester's credentials (e.g., domain ownership, organizational identity), and forwards approved requests to the CA.

A digital certificate is a cryptographically signed electronic document that binds a public key to an identity (a person, server, or organization). The standard format is X.509.

• Key Contents: Contains the subject's public key, identifying information (Subject Name), issuer (CA) details, validity dates, and a digital signature from the issuing CA.
• Purpose: Enables authentication (proving identity) and facilitates secure key exchange for protocols like TLS/SSL. It is the primary credential used in PKI-based systems.

Certificate Revocation is the mechanism to invalidate a certificate before its natural expiration, critical for responding to key compromise or identity changes. Two primary methods are used:

• Certificate Revocation List (CRL): A periodically published, CA-signed list of serial numbers for revoked certificates. Clients must fetch and check the CRL.
• Online Certificate Status Protocol (OCSP): A real-time query protocol where a client requests the revocation status of a single certificate from an OCSP responder, reducing latency compared to CRLs.

The asymmetric key pair is the fundamental cryptographic element. It consists of two mathematically linked keys:

• Private Key: A secret, non-shareable key used to create digital signatures or decrypt data encrypted with the corresponding public key. It must be stored securely, often in a keystore or HSM.
• Public Key: A publicly distributable key used to verify a signature created by the private key or to encrypt data intended for the private key holder.

The certificate contains the public key; the security of the system depends entirely on the secrecy of the private key.

The certificate repository is a publicly accessible directory or database that stores and distributes issued certificates and Certificate Revocation Lists (CRLs).

• Function: Provides a standard location (e.g., via LDAP or HTTP) for relying parties to retrieve the public certificates of entities they wish to communicate with and to check for revocation status.
• Availability: High availability of the repository is essential for the ongoing operation of the PKI, as clients need to access certificates and CRLs to establish trust.

Zero Trust Architecture (ZTA) is a security model that eliminates implicit trust, requiring continuous verification of every access request. PKI is a fundamental enabler of ZTA by providing strong, cryptographically verifiable identities for users, devices, and workloads.

• Mutual TLS (mTLS): Uses PKI certificates to authenticate both client and server, a common ZTA pattern for service-to-service communication.
• Device Identity: Machine certificates provisioned via PKI authenticate devices before granting network access (network access control).
• Contrast with Perimeter Security: ZTA assumes the network is hostile, whereas traditional PKI was often deployed only at the network edge.

An X.509 certificate is the standardized format for a public key certificate, defining the data structure that binds an identity to a public key. It is the primary credential issued and managed by a PKI.

• Key Fields: Subject (owner), Issuer (CA), Validity Period, Public Key, Digital Signature.
• Extensions: Define certificate usage (e.g., keyUsage, extendedKeyUsage for server auth, client auth, code signing).
• Encoding: Commonly in PEM (Base64) or DER (binary) formats.
• Hierarchy: Forms chains of trust from root CA certificates to intermediate CAs to end-entity certificates.

Certificate Revocation is the process by which a Certificate Authority (CA) invalidates a digital certificate before its scheduled expiration, a critical component of PKI lifecycle management for responding to compromises or policy violations.

• Certificate Revocation List (CRL): A time-stamped, CA-signed list of revoked certificate serial numbers, periodically published to a distribution point.
• Online Certificate Status Protocol (OCSP): A real-time protocol where a client queries a CA's OCSP responder to check a certificate's status (good, revoked, unknown).
• OCSP Stapling: Allows the server to provide a time-stamped OCSP response signed by the CA during the TLS handshake, improving privacy and performance.

A Certificate Authority (CA) is the trusted entity within a PKI that issues, manages, and revokes digital certificates. It acts as the root of trust by digitally signing certificates, vouching for the binding between a public key and the identity of the certificate holder.

• Types:
  • Public CAs (e.g., DigiCert, Let's Encrypt): Trusted globally by browsers and operating systems for public-facing websites.
  • Private/Enterprise CAs: Operated by an organization for internal systems, devices, and employees.
• Hierarchy: Often structured with a root CA (offline, highly protected) that signs intermediate CAs, which issue end-entity certificates.
• Policy: Governed by a Certificate Policy (CP) and Certification Practice Statement (CPS).

Mutual TLS (mTLS) is an authentication protocol where both the client and the server present and verify each other's X.509 certificates during the TLS handshake. It extends standard TLS (which only authenticates the server) to provide strong, two-way identity verification, essential for microservices, API security, and zero-trust networks.

• Process: Client sends its certificate; server validates it against a trusted CA, and vice-versa.
• Use Cases: Service mesh communication (e.g., Istio, Linkerd), IoT device-to-cloud authentication, internal API gateways.
• Contrast with PKI: mTLS is an application of PKI, utilizing the certificates and trust chains that a PKI provides.