Two-Tier Encrypted Offline Root PKI in Azure Key Vault & Managed HSM
Most enterprise PKI modernisations stall for the same reason: teams lift legacy Active Directory Certificate Services (AD CS) straight into cloud VMs, leave root keys reachable over the network, and store static service credentials in CI/CD pipelines. In regulated banking and defence environments, that fails audit before day one.
1. The Two-Tier Trust Boundary
A production-grade cloud PKI separates the root of trust from daily certificate issuance:
- Tier 1 — Air-Gapped Encrypted Offline Root CA: Generated and stored offline on encrypted media or dedicated FIPS 140-3 HSM hardware. Brought online only for scheduled CRL publication and Subordinate CA signing ceremonies under dual control.
- Tier 2 — HSM-Backed Issuing CA (Azure Key Vault Premium / Managed HSM / Thales Luna): Private keys never leave the HSM boundary. Issuing workloads authenticate strictly via Azure Managed Identity — zero stored client secrets, zero static PFX files on disk.
[Tier 1: Air-Gapped Offline Root CA] -- (Dual-control ceremony) --> [CRL / AIA Static Store]
|
(Signs Sub-CA Cert)
v
[Tier 2: HSM-Backed Issuing CA (Azure Managed HSM / Thales)]
|
(Managed Identity · Zero Secrets)
v
[ACME / EST / SCEP Automation] --> Workloads, Devices, mTLS, Entra ID
2. Prove Recovery Before Production: 36 Automated Acceptance Tests
A PKI design on slides is worthless until you prove it survives renewal, rollback, and CA loss. My 4-module PKI modernisation lab validates every build against 36 automated acceptance tests before sign-off:
- Module 1 — Root & Sub-CA Ceremony Controls: Key generation, offline storage encryption, AIA/CDP reachability, and OCSP/CRL freshness windows.
- Module 2 — Zero-Secret Issuance: Managed Identity token binding, RBAC least privilege, and negative tests proving stolen pipeline variables cannot sign certificates.
- Module 3 — Lifecycle & 47-Day Automation: Automated ACME/EST enrollment, short-lived renewal, revocation propagation, and emergency rollback.
- Module 4 — Disaster Recovery & Post-Quantum Readiness: Full Issuing CA rebuild from HSM backup, crypto-agility algorithm profile swaps, and hybrid PQC test chains.
Need this architecture reviewed or built for Q1 2027?
Available from January 2027 for Principal PKI/DPKI architecture contracts (B2B Ltd / Outside IR35) or 5–10 day fixed-scope readiness sprints. View my 2026 CV (PDF) or request access to the Controlled DPKI Briefing.
Available from January 2027 for Principal PKI/DPKI architecture contracts (B2B Ltd / Outside IR35) or 5–10 day fixed-scope readiness sprints. View my 2026 CV (PDF) or request access to the Controlled DPKI Briefing.