Certificate Authority
Subject: Computer and Technology noun /sərˈtɪf.ɪ.kət əˈθɔːr.ə.ti/ 1 definition
- public-key-infrastructure
- network-security
- digital-certificates
- information-security
-
Definition (noun)
Entry #117 · UpdatedA Certificate Authority (CA) is a trusted entity within a Public Key Infrastructure (PKI) that verifies the identity of subjects—such as domains, servers, software publishers, or users—and issues digitally signed certificates binding each subject to a specific public key. By signing X.509 certificates with its own private key, a CA lets clients whose trust stores contain the CA's root certificate verify an unfamiliar endpoint's public key without prior key exchange. A CA also enforces trust boundaries by limiting certificate lifespans and publishing revocation status via Certificate Revocation Lists (CRLs) or the Online Certificate Status Protocol (OCSP), attesting to identity binding rather than the subject's intent or security.
Common Types
Root CA: Sits at the apex of a PKI trust hierarchy with a self-signed certificate distributed in operating system, browser, or runtime trust stores, typically kept offline inside hardware security modules (HSMs) and used exclusively to sign subordinate CA certificates.
Intermediate CA: Operates beneath a root CA (or another intermediate) to sign end-entity leaf certificates for daily issuance, shielding the root private key from online exposure and allowing compromised branches to be revoked independently.
Publicly Trusted CA: Complies with industry governance such as the CA/Browser Forum Baseline Requirements and undergoes independent audits to remain embedded in vendor trust stores for public HTTPS, email, and code signing.
Private CA: Managed internally by an organization to issue certificates for corporate infrastructure, VPNs, employee devices, and mutual TLS (mTLS) microservices where relying parties already trust an internal root certificate.
Example
Before launching
https://shop.example.com, an administrator uses an ACME client to prove domain control to a publicly trusted Certificate Authority, which signs a 90-day X.509 leaf certificate from its intermediate CA. When a customer's browser connects, it validates the cryptographic signature chain from that leaf certificate through the intermediate up to the CA's pre-installed root certificate in the local trust store before completing the TLS handshake.