TL;DR: Different public PKIs serve different trust communities, so certificate governance has to match the use case rather than one shared policy model, according to Red Sift. Certificate lifecycle rules, validation, and revocation need separate ownership across web, email, code signing, and device trust domains.
Editorial analysis by NHI Mgmt Group, based on content published by Red Sift: “How many public PKIs are there?”.
Key questions
Q: Why is PKI more than a cryptography problem?
A: PKI is more than cryptography because trust depends on policy, operating context, and lifecycle control as much as on key pairs and signatures.
Q: What goes wrong when certificate trust is managed as one shared model?
A: The main failure is scope confusion.
Q: How should security teams govern certificates across multiple PKI ecosystems?
A: Security teams should segment certificate governance by trust domain, because web, code signing, email, and device PKIs do not follow the same policy or assurance model.
Practitioner guidance
- Map each PKI use case to its trust domain Separate website, code signing, email, and device certificates into distinct governance domains so policy matches the trust model and lifecycle requirements.
- Assign clear lifecycle owners for certificates Define who issues, validates, renews, revokes, and audits certificates in each PKI context before automation expands the estate.
- Review trust assumptions by ecosystem Check whether browser-governed, vendor-governed, or specialised PKIs apply to the systems you operate, then adjust validation and monitoring accordingly.
Bottom line: PKI is best understood as governance plus cryptography, because policy determines how trust is created and enforced.
Glossary terms: Public Key Infrastructure, Certificates, Private Key, Trust Domain
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
PKI is an identity governance system, not a cryptography footnote. The article makes clear that a certificate only becomes useful when policy defines how trust is established, consumed, and limited. That means machine identity programmes should treat issuance rules, validation scope, and revocation authority as governance decisions, not implementation details. Practitioners should review PKI as an operating model, not just a certificate format.
A few things that frame the scale:
- 48% of organisations cite cloud-based services as a driver for PKI deployment, according to the 2023 State of Machine Identity Management report.
A question worth separating out:
Q: When should organisations use a specialised PKI instead of Web PKI?
A: Use a specialised PKI when the trust community, device class, or operational purpose is narrower than the public web. Matter, code signing, and S/MIME each have different trust rules and lifecycle expectations, so the right choice is the one whose governance model matches the use case, not the one that seems most familiar.
👉 Read our full editorial: PKI governance depends on policy, not just public keys