Topic starter
25/06/2026 10:35 pm
TL;DR: Google’s decision to require Certificate Transparency for publicly trusted SSL/TLS certificates issued from April 2018 affects DV, OV, and EV certificates alike, improving early detection of misissued certificates while forcing certificate teams to adapt workflows, according to DigiCert. The shift makes certificate visibility and lifecycle controls a governance issue, not just a PKI operational detail.
Editorial analysis by NHI Mgmt Group, based on content published by DigiCert: “Google CT to Expand to All Certificates Types”.
Key questions
Q: What changes when Certificate Transparency applies to all publicly trusted certificates?
A: The main change is that trust visibility stops being limited to EV certificates and extends to DV and OV as well.
Q: Why does certificate transparency create governance risk for certificate teams?
A: Because CT turns certificate issuance into an observable event that must be explained, logged, and reviewed consistently.
Q: What breaks when certificate subject names expose internal details?
A: The problem is that trust logging can surface more information than the organisation intended, including project names, internal structure, or staff data.
Practitioner guidance
- Inventory all publicly trusted certificates Build a complete register of DV, OV, and EV certificates so the team can see which assets fall under CT expectations and where logging obligations may differ by certificate class.
- Test CT logging before the deadline Use non-critical certificates to confirm that issuance, submission, and visibility behave as expected before compliance becomes mandatory across more certificate types.
- Review certificate subject naming Check whether certificate names reveal internal structure, project codenames, or personal information that should be redacted or reworked before public trust logging.
Bottom line: Google’s CT expansion broadens the governance surface for publicly trusted certificates by extending visibility expectations beyond EV.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
25/06/2026 11:11 pm
Certificate transparency has become a governance control, not a browser footnote. Once CT applies to DV and OV certificates as well as EV, certificate teams can no longer treat trust visibility as an edge case. The control now influences how organisations inventory certificates, monitor issuance, and explain trust state to auditors and security teams. Practitioners should treat CT as part of the certificate lifecycle, not as an afterthought attached to browser compatibility.
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: Should teams treat certificate transparency as a PKI task or an identity governance task?
A: Treat it as both, but govern it like an identity lifecycle issue because issuance, visibility, and revocation all affect trust state. PKI handles the mechanics, while identity governance provides the inventory, ownership, and review discipline needed to keep certificate controls consistent.
👉 Read our full editorial: Google CT expansion raises the bar for certificate governance