Topic starter
24/06/2026 11:56 pm
TL;DR: Digital trust will depend on automation, because compressed certificate lifecycles and AI systems acting in production outgrow manual review, Keyfactor says. Certificate estates need continuous policy enforcement, or expired, weak, and orphaned assets can slip through before anyone can react.
Editorial analysis by NHI Mgmt Group, based on content published by Keyfactor: “Keyfactor 2026 Trends & Predictions”.
By the numbers:
- The CA/Browser Forum will reduce public TLS certificate lifecycles from 398 days to 47 days by 2029.
- Only 42% of enterprises are actively addressing the quantum cybersecurity threat today, according to Keyfactor.
- Just 17% of organisations have real-time visibility across their certificate landscape.
Key questions
Q: Why do quantum-readiness programmes fail when cryptographic inventory is incomplete?
A: Because migration planning depends on knowing which systems, algorithms, and dependencies must change.
Q: How should security teams govern AI agents that browse and transact on behalf of users?
A: Security teams should govern AI agents as delegated actors with narrow, task-scoped permissions, not as enhanced browsers.
Q: What breaks when certificate discovery is not tied to lifecycle automation?
A: Discovery alone creates a report, not control.
Practitioner guidance
- Build a unified cryptographic inventory Map certificates, algorithms, keys, and dependencies across public and private trust domains so ownership and expiry can be governed from one view.
- Automate certificate issuance and renewal Eliminate manual renewal paths for public and private certificates and tie issuance, rotation, and revocation to authoritative lifecycle workflows.
- Assign cryptographic identity to AI agents Issue certificates or equivalent identity proofs to AI systems that initiate transactions, and enforce mTLS and least privilege on their communication paths.
Bottom line: Digital trust is shifting from periodic checks to continuous validation as certificate lifecycles compress and AI systems begin to act directly in production environments.
Glossary terms: Digital Trust, Crypto-Agility, Agentic AI Identity, Certificate Lifecycle Management
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 1 day ago by NHI Mgmt Group
25/06/2026 8:43 am
Continuous digital trust has become the operational baseline, not an advanced maturity target. The article shows that certificate lifecycles, quantum preparation, and AI identity governance are converging into one trust problem. In practice, that means organisations can no longer separate PKI operations from broader identity governance and risk programmes. The practitioner conclusion is simple: trust now has to be proven continuously across every identity class.
A question worth separating out:
Q: What is the difference between static trust and crypto-agile trust?
A: Static trust assumes the cryptographic stack will remain stable long enough to be managed episodically. Crypto-agile trust assumes algorithms, certificates, and dependencies may need to change quickly, so the governance model must support rapid transition without losing control.
👉 Read our full editorial: Digital trust in 2026 depends on automation and AI identity