Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is the Chain of Trust?

The chain of trust is the path a client follows from a server certificate, through one or more intermediates, to a root it already trusts. If any link fails validation, the whole connection fails.

Illustration for the cybersecurity term Chain of Trust
Home / Blog / Cybersecurity Terms / What Is the Chain of Trust?
17 November 2026

What Is the Chain of Trust?

What Is the Chain of Trust?

A client cannot verify a server certificate on its own. It verifies a chain: the server’s leaf certificate is signed by an intermediate, the intermediate is signed by another intermediate or by a root, and the root is already present in the client’s trust store. Trust flows downwards from an anchor the client decided to accept before the connection started.

This is why a certificate is never trusted because it is valid, but because it is reachable. A perfectly well-formed certificate whose issuer is unknown to the client is worthless.

Why Three Tiers

Root keys are extraordinarily valuable and almost impossible to replace, because replacing one means updating every operating system, browser, and embedded device on earth. So roots are generated in ceremonies, stored offline in hardware security modules, and used only to sign a small number of intermediates.

Intermediates do the daily work. If an intermediate key is compromised, the certificate authority revokes it and issues a new one, and the root survives. The same reasoning applies to a private PKI: an organisation whose issuing CA signs directly from an online root has no recovery path short of reinstalling trust everywhere.

What the Client Checks

Path validation is specified in RFC 5280, and every step can fail independently:

  1. The signature on each certificate verifies against the public key of the certificate above it.
  2. Each certificate is within its validity period, measured against the client’s clock.
  3. Every issuer above the leaf has basicConstraints set to CA:TRUE, and respects any pathLenConstraint.
  4. Key usage and extended key usage permit the purpose — server authentication, client authentication, or code signing.
  5. Any name constraints on an intermediate are satisfied by the names in the leaf.
  6. Revocation status is checked through CRL or OCSP, where the client bothers to check at all.
  7. The requested hostname matches a subject alternative name. The common name has been ignored for this purpose by modern clients for years.

Only after all of that does the client decide the chain terminates at a trusted root. Note that the root itself is self-signed, so its signature proves nothing; it is trusted because it is in the store, and for no other reason.

Cross-Signing and the Day Android Broke

A new certificate authority faces a bootstrapping problem: its root is not yet in any trust store, and old devices will never receive an update. Cross-signing solves it by having an established root also sign the new CA’s certificate, so the chain can terminate at either anchor.

Let’s Encrypt relied on a cross-signature from IdenTrust’s DST Root CA X3, which expired on 30 September 2021. Devices with current trust stores moved to the ISRG Root X1 path without noticing. Android versions before 7.1.1, OpenSSL 1.0.2, and a long list of appliances did not, and spent that day unable to connect to a sizeable slice of the web. It remains the clearest demonstration that the chain depends on the oldest client in your estate, not the newest.

The Errors You Will Actually See

SymptomUsual cause
Browser fine, curl and Java failThe server does not send the intermediate; browsers fetch it via the AIA extension, most other clients do not
Works on new devices, fails on old onesA cross-signed path that has expired, or a root missing from an outdated trust store
Mobile app fails after a routine renewalCertificate pinning to a leaf or intermediate that changed
Everything fails after midnightAn expired certificate, or a client clock that is badly wrong

The first row is the most common production incident in this area, and it is a one-line fix: configure the server to present the full chain, leaf first, excluding the root. Testing with a browser alone will not reveal it.

Trust Stores Are a Control You Own

In a managed estate the trust store is an asset worth inventorying. Decommissioned internal roots, test CAs installed during a project, and roots added by a proxy or an interception appliance all grant the ability to impersonate any site to that machine. Attackers know this: installing a root certificate is a recognised persistence technique (MITRE ATT&CK T1553.004). Reviewing what is actually trusted on servers, build agents, and laptops is part of our cyber risk analysis services, and it regularly turns up anchors nobody could account for.

FAQ – Frequently Asked Questions

Should My Server Send the Root Certificate?

No. The client either already has the root in its trust store, in which case sending it wastes handshake bytes, or it does not, in which case receiving it changes nothing because an untrusted root cannot bootstrap trust. Send the leaf and every intermediate, in order, and stop there.

What Is the Difference Between a Root and an Intermediate CA?

A root is self-signed and distributed in operating system and browser trust stores; its key is kept offline because replacing it is nearly impossible. An intermediate is signed by the root or by another intermediate and does the day-to-day issuing. If an intermediate is compromised it can be revoked and replaced without disturbing the root.

Why Does a Certificate Work in Chrome but Fail in My Application?

Browsers compensate for incomplete chains by downloading missing intermediates using the Authority Information Access extension, and they ship their own trust stores. Command line tools, Java, and many SDKs do neither. Test with openssl s_client -showcerts or an external checker rather than assuming a working browser means a correct configuration.

How Do Name Constraints Limit a Private CA?

A name constraint extension on an intermediate restricts the names it may sign, for example only hosts under example.co.uk. A compliant client rejects any certificate from that CA for a name outside the permitted set. It is a cheap way to limit the blast radius of an internal CA or a supplier-operated issuing authority.

Related Terms

You May Be Interested In These

What Is a Cloud Workload Protection Platform?

Cybersecurity Terms

17 November 2026

What Is a Cloud Workload Protection Platform?

Read More
What Is Volume Shadow Copy Analysis?

Cybersecurity Terms

17 November 2026

What Is Volume Shadow Copy Analysis?

Read More
What Are CSIRT and CERT?

Cybersecurity Terms

17 November 2026

What Are CSIRT and CERT?

Read More