---
title: "The Certificate Authority Trust Stack: Who Signs, Who Trusts, Who Must Patch"
description: "A layered map of how a certificate authority earns trust: root programs, offline roots, online intermediates, leaf certificates, and the trust stores that decide whether verification actually happens."
---

# The Certificate Authority Trust Stack: Who Signs, Who Trusts, Who Must Patch

**Type:** [Architecture](https://yomu.fyi/visual-explainers/category/architecture.md)

![Layered architecture diagram of certificate authority trust: root programs and trust stores at top, then an offline root CA, online intermediate CAs, leaf certificates, and relying parties, with signing arrows downward and revocation and transparency signals flowing back up.](https://yomufyi.s3.us-east-1.amazonaws.com/visual-explainers/389737d3-2705-4d8b-8ef9-7296765323af/image-2fe07f02-cc07-4cff-8f96-e2e59b7657b6.webp)

> A layered map of how a certificate authority earns trust: root programs, offline roots, online intermediates, leaf certificates, and the trust stores that decide whether verification actually happens.

## Explanation

A certificate authority is not one server; it is a chain of trust with different lifetimes and different blast radii at each layer. Root programs decide which roots browsers and operating systems accept, an offline root signs online intermediates, and intermediates issue the leaf certificates that terminate TLS. When an intermediate's private keys are compromised, attackers can forge certificates for any domain, so the real work is remediation: updating trust stores, base images, and every background service that verifies TLS rather than only the browser in front of you.

## FAQ

### Why would a new CA acquire an old root instead of building a fresh one?

A freshly created root is not trusted by older clients and would never reach the long tail of devices, causing avoidable breakage. Acquiring an established root preserves compatibility with those clients while the new CA builds out issuance. Cloudflare took that route, pairing the acquired root with an ACME-first issuance model and Merkle Tree Certificates for post-quantum readiness.

**Tags:** [Certificate Authority](https://yomu.fyi/topic/certificate-authority.md), [Certificate Transparency](https://yomu.fyi/topic/certificate-transparency.md), [Cryptography](https://yomu.fyi/topic/cryptography.md), [Security](https://yomu.fyi/topic/security.md), [TLS](https://yomu.fyi/topic/tls.md), [Trust](https://yomu.fyi/topic/trust.md)

## Related reading

### [How Anchorage Digital and Turnkey verify code with AWS Nitro Enclaves](https://yomu.fyi/post/how-anchorage-digital-and-turnkey-verify-code-with-aws-nitro-enclaves.md)
- Company: [AWS](https://yomu.fyi/company/aws.md)
- Author: Alexander Qin
- Published: Oct 27, 2026
- Type: Problem & solution

Cryptocurrency wallets face phishing attacks due to blind signing, where transactions are approved without full semantic understanding. Anchorage Digital and Turnkey built VisualSign, an open source Rust transaction parser that runs inside AWS Nitro Enclaves. The enclave communicates only over a local vsock channel with no persistent storage or network, and produces signed attestation documents containing Platform Configuration Registers (PCRs) that prove which exact code executed. Reproducible builds ensure byte-identical binaries, so PCR values are deterministic and verification policies never require updates. This architecture pattern of reproducible builds, enclave-hosted computation, and attestation-gated access extends beyond blockchain as a general-purpose verifiable compute building block.


### [PrivacyLib: Privacy Controls at the Data Access Boundary](https://yomu.fyi/post/privacylib-privacy-controls-at-the-data-access-boundary.md)
- Company: [Meta](https://yomu.fyi/company/meta.md)
- Author: By Sai Nagabhairava, Hannes Roth, Na Chen, Peter Prelich, Jonathan Bergeron
- Published: Oct 27, 2026
- Type: Explainer

PrivacyLib is a common library that runs inside clients of Meta’s data and processing systems at the data access boundary, replacing separate privacy enforcement implementations across systems. Systems integrate with PrivacyLib once, and new privacy capabilities are added as modules that reuse that integration, performing billions of checks per second. PrivacyLib addresses three engineering challenges: coverage by integrating at typed client libraries and network boundaries, scale by compiling requirements at build time and using in-process caches, and reliability by deploying enforcement changes through each service’s own pipeline. For internal AI agents, tool calls carry agent context that PrivacyLib uses to observe data access and block disallowed operations. Meta learned that designing for evolving systems, prioritizing reliability to earn adoption, and ensuring coverage includes deployment are critical for operating PrivacyLib at scale.


### [8 eMudhra certificates are compromised. Here's what you need to know](https://yomu.fyi/post/8-emudhra-certificates-are-compromised-here-s-what-you-need-to-know.md)
- Company: [Cloudflare](https://yomu.fyi/company/cloudflare.md)
- Author: Jeremy Hartman
- Published: Oct 20, 2026
- Type: Incident / postmortem

On October 19, 2026, Cloudflare learned that private keys for eight eMudhra intermediate certificates were compromised due to weak keys, allowing attackers to forge certificates for any domain and intercept or modify traffic. Cloudflare immediately patched critical services, updated shared trust stores and base images, released updates for Cloudflare One Clients and Cloudflare Tunnel, and deployed mitigations across CDN, Developer, and Zero Trust products. The security review found no active exploitation on Cloudflare services, but customers using mutual TLS or custom origin certificates must update trust stores and server configurations, and Cloudflare is updating Automatic SSL/TLS to notify affected users. Developers should update dependencies and verify the actual TLS verification path used by their applications, as a browser test does not prove a background service is protected. Browsers remediated quickly with CRLSets, and Cloudflare is working on further remediation while advocating for dynamic trust stores that can incorporate revocation information.


### [Building a certificate authority for the whole Internet](https://yomu.fyi/post/building-a-certificate-authority-for-the-whole-internet.md)
- Company: [Cloudflare](https://yomu.fyi/company/cloudflare.md)
- Author: Steve Goldsmith
- Published: Sep 29, 2026
- Type: Announcement

Cloudflare, which terminates TLS for millions of domains and sits in front of over 20% of global Internet request traffic, announced its intent to become a public certificate authority (CA) during Birthday Week 2026. The company has applied for inclusion in the Chrome, Apple, Microsoft, and Mozilla root programs and signed a definitive agreement to acquire an established root from GlobalSign. This acquisition ensures certificate compatibility with older clients that a fresh root would never reach, addressing the long tail of devices where avoidable breakage occurs. Cloudflare plans to be among the first CAs to issue production Merkle Tree Certificates (MTCs) in early 2027, targeting post-quantum readiness as part of Chrome’s Quantum-resistant Root Program. The CA will be ACME-first, require ACME Renewal Information (ARI) support for issuance, and operate transparently with reproducible builds of signing software and a public dashboard.
