Contact us

BOOK A PRESENTATION

You can't automate what you can't find: how Certiligent Agent brings existing TLS certificates under automated renewal

November 20, 2026
Category:
NO NAME
An automation platform can only renew the TLS certificates it knows about. Before automated renewal can start, every certificate already running in production has to be found, identified and handed over to the platform. In most organizations, that hand-over is where certificate automation projects slow down.

The Certiligent Agent covers exactly this step. It runs on your servers, finds the certificates that are already there, maps each one to the service that uses it, and, once you approve, puts it on automated renewal.

Think of a facility manager who takes over a large office building. The service contract is signed and the maintenance schedule is ready. Then the previous tenant hands over a box of unlabelled keys. Nobody is quite sure which door each key opens, and some doors are not on the floor plan at all. The schedule is useless until someone walks the building, door by door.

TLS certificates work the same way. The renewal engine is rarely the issue. The challenge is the walk through the building.

Where certificates actually live

Most certificate-related outages are not due to the certificates a team tracks. They come from the ones nobody tracks. A typical environment holds certificates that sit in one or more of these blind spots:

Outside the inventory. Issued years ago, never added to the spreadsheet or CMDB.

Without an owner. The person who installed them changed teams or left the company.

Embedded in scripts and applications. Bundled into a config file or an application package, invisible from the outside.

On network and security equipment. Load balancers, VPN gateways and appliances that rarely appear in a server list.

Issued without documentation. Requested in a hurry, installed, and forgotten.

Copied across servers. One wildcard certificate, deployed to many machines, each copy expiring on the same day.

Spreadsheets and CMDBs describe the environment as planned. Production is the environment as it actually is. The gap between the two is where the risk sits, and it is also what stands between you and automated renewal.

Why manual onboarding stalls

Putting one existing certificate under automated renewal is a small integration project. Done by hand, it usually looks like this:

  1. Find the certificate on the server where it is installed.
  2. Work out which application or service uses it, and who owns that service.
  3. Install and configure an ACME client on that server.
  4. Define what must happen after renewal: reload a web server, restart a service, restart a container.
  5. Test the full cycle without breaking production.

None of these steps is hard on its own. The problem is repetition. An organization with 100 certificates faces 100 of these small projects, spread across different teams, operating systems and maintenance windows. Each one competes with day-to-day work, so onboarding drags on for months.

Wildcard certificates add a twist. One certificate may protect dozens of servers. Renewing it is easy; making sure the new copy lands on every server that uses it is not. Miss one machine and that service fails on the old expiry date, even though the certificate was "renewed".

Until onboarding is finished, the automation platform manages only part of the estate. The rest still depends on calendars, reminders and whoever remembers.

What the Certiligent Agent does

The Certiligent Agent is a component installed on your own servers. It takes over the walk through the building: it discovers the certificates already in place and brings them under automated renewal, without a separate ACME client on every machine.

The process runs in four steps:

  1. Discover. The Agent scans the server and finds the TLS certificates already present on it.
  2. Map. Each certificate is linked to the servers, applications and services that use it. The anonymous key gets a label.
  3. Approve. Your team reviews insights and the actions the Agent plans to take. Nothing changes until you approve it.
  4. Automate. Approved certificates are renewed on time through the Certiligent platform. The Agent installs the new certificate and runs the post-renewal actions, such as restarting services or containers.

Two capabilities matter most for onboarding at scale:

  • Wildcard certificate distribution. With wildcard certificate renewal, the Agent distributes the new copy to every server that uses it.
  • Centralized management. Agent configuration has central management from the platform and changes apply without restarting the Agent.

The result is that onboarding stops being 100 separate projects. It becomes one installation per server, followed by a review and an approval.

Security and control by design

Any software that touches production certificates must earn the security team's trust first. The whole purpose of the Certiligent Agent is to pass that review:

Minimal server privileges. It runs with only the permissions it needs to do its job.

No inbound ports. Nothing new is opened on the server, so the attack surface does not grow.

Digitally signed distribution. The Agent package is signed, so you can verify it has not been tampered with.

Review before execution. Planned actions can be inspected before they run. Your team decides what happens and when.

Installs in minutes. No lengthy deployment project before the first results.

Automation does not mean handing over control. It means the routine work runs on its own, while the decisions stay with your team.

What changes for the team

With the Agent in place, the certificate inventory is built from what is actually running, not from what someone remembered to write down.

 Manual onboardingWith the Certiligent Agent
Finding certificatesServer by server, by handAutomatic discovery on each server
Knowing what uses a certificateAsking around, checking configsCertificates mapped to servers, applications and services
Setting up renewalACME client configured per serverNo separate ACME client needed
After renewalManual reloads and restartsPost-renewal actions run automatically
Wildcard certificatesCopied to each server by handDistributed to every server that uses them
InventorySpreadsheet or CMDB, often outdatedCentral, live view in Certiligent

Once certificates are on the platform, Certiligent handles the rest of the lifecycle: monitoring, alerts for upcoming expirations or failed renewals, and an audit trail of every operation for NIS2, DORA or internal audit.

From a box of keys to a building that runs itself

Back to the facility manager. The maintenance contract was never the hard part. The hard part was knowing which key opens which door, and finding the doors that were not on the plan.

The Certiligent Agent does that walk for you. It finds the certificates already in production, tells you where each one is used, and moves them onto automated renewal once you say yes. From then on, renewals happen on schedule, on every server that needs them, without tickets or late-night interventions.

Want to see what the Agent finds in your environment?

Register for a free trial or book a presentation with our team

Certiligent Agent FAQ

The Certiligent Agent is a component installed on your own servers. It discovers TLS certificates already present there and, once approved, automates their renewal and post-renewal actions through the Certiligent platform.

An automation platform can only renew certificates it knows about. Certificates outside the inventory, without an owner or copied across servers stay on manual renewal until they are found and onboarded.

No. Once a certificate is approved, the Agent handles renewal and installation, so there is no need to issue certificates manually through a separate ACME client.

Yes. Post-renewal actions, such as restarting services or containers, run automatically after the new certificate installation.

After wildcard certificate renewal, the Certiligent Agent distributes the new copy to every server that uses it.

The Agent runs with minimal server privileges, requires no inbound ports and is distributed with a digital signature. Planned actions can be reviewed before they are executed.

The Certiligent Agent installs on a server within minutes.

Want to learn more about cybersecurity trends and industry news?

SUBSCRIBE TO OUR NEWSLETTER

CyberSecurityhub

chevron-down linkedin facebook pinterest youtube rss twitter instagram facebook-blank rss-blank linkedin-blank pinterest youtube twitter instagram