Certificate and private key managementInternal research

The 47-day clock has already started.

With public certificates at 47 days by 2029, we find yours and match a platform that renews them.

Free. No fit, no obligation.

The problem

Renewal stopped being a once-a-year job.

The CA/Browser Forum's schedule cuts the maximum life of a public TLS certificate from about 398 days to 200, then 100, then 47 days by 2029. Domain-validation reuse drops to 10 days. A once-a-year task becomes close to monthly, for every certificate you own.

The Australian Signals Directorate (ASD) adds a second deadline: off today's public-key cryptography by the end of 2030, with a transition plan by the end of 2026. Both are published, and they set the work whether or not a certificate has ever caused you trouble.

47 daysthe maximum life of a public TLS certificate by 2029, down from about 398.

Architecture

Four problems the schedule creates.

What was a calendar reminder is now four distinct problems at once.

  1. 01

    Seeing what you have

    Most teams track certificates in a spreadsheet and memory. Industry surveys suggest only about a third have a complete, current view.

  2. 02

    Renewing before they expire

    At 47 days, manual renewal doesn’t scale. One missed certificate takes down a website, API or internal service without warning.

  3. 03

    Every authority, not one

    Several authorities means several consoles. When one loses trust, as Entrust did in 2024, every certificate it issued needs replacing at once.

  4. 04

    The clock on quantum

    Data captured today can be decrypted once a capable quantum computer exists, and the ASD deadline to move off today’s cryptography is fixed.

Certificate and private key management

You can’t automate what you can’t see.

Every vendor demonstrates automated renewal, and it only works on certificates you know about. Outages come from the ones you don't: a certificate set up two years ago, on an appliance nobody owns now.

So the first job is discovery: a live inventory of every certificate across your estate, public and private. Get it right and renewal, governance, and the quantum transition have something real to work from.

What you get

What good certificate management gives you.

What good looks like once the schedule is against you.

What to look for

What can the top platforms do?

These capabilities separate a platform that governs every certificate from a console that only sells them.

  • Continuous discovery across the estate

    Finding certificates on your network, in the cloud, and on appliances, beyond the ones already listed. A "scan the internet" feature is usually Certificate Transparency log monitoring, which is public and free: table stakes.

  • Authority-agnostic lifecycle

    Managing certificates from every public and private authority in one place, so a trust event at one authority becomes a bulk re-issue rather than an emergency.

  • Automated enrolment and renewal

    Open standards like ACME and SCEP doing the renewal work, so a 47-day cycle runs without a person in the loop.

  • Policy and governance

    Central rules for who can issue what, and from where, so certificate sprawl does not quietly rebuild itself.

  • Expiry monitoring and alerting

    A warning well before a certificate lapses, tied to a named owner, so the renewal has somewhere to land.

  • A private certificate authority as a service

    Issuing internal and machine certificates without standing up and maintaining your own PKI, described as what it is: a delivery model, not magic.

  • A crypto-agility inventory

    Knowing which algorithms sit where across your estate, so the transition off today's cryptography before 2030 is planned from evidence.

Maturity

Where most teams sit today.

Certificate management maturity, tier by tier.

  1. Focused

    Spreadsheet tracking and manual renewal, with gaps found when something breaks, which won’t hold at 47 days. Many mid-market teams sit here.

    Typical features

    • Certificates tracked in a spreadsheet
    • Renewal done by hand
    • Expiry found when something breaks
    • No single owner
  2. Broad

    A complete, live inventory, renewal automated from any authority through open standards, and expiry tied to a named owner.

    Typical features

    • A complete, live inventory
    • Discovery across every authority
    • Renewal automated through ACME and open standards
    • Expiry tied to a named owner
    • Alerts well before the deadline
  3. Ready for post-quantum

    Comprehensive

    Everything Broad does, plus central policy, a hosted private authority and a post-quantum crypto-agility inventory. Start here if you issue internal certificates or answer to APRA.

    Everything in Broad, plus

    • Policy enforced centrally
    • A private authority run as a service
    • A crypto-agility inventory
    • Re-issue at scale when an algorithm changes
    • A post-quantum transition plan

Tekspace Research

We research the certificate and private key management field.

Internal research

Certificate and Machine Identity Management

Finds every certificate you own and renews it before an expiry causes an outage.

Vendors assessed6 vendors assessed

  • AppViewX
  • CyberArk Venafi
  • DigiCert
  • GlobalSign
  • Keyfactor
  • Sectigo

Examples of what we test

  • Discovery across every CA
  • Automated renewal (ACME)
  • Crypto-agility for post-quantum

Same tests on every product. The scores publish with the benchmark.

Questions we hear most.