Overview
The CyberSift Certificate Manager issues, renews and keeps track of every TLS certificate your organisation uses, on a server you control.
In short: install one container, follow the setup guide, issue your first certificate. Renewals and alerts look after themselves from then on.
What it does for you
- Issues and renews automatically. Public and internal host names, wildcards and multi-name certificates. Nobody has to remember an expiry date again.
- Keeps one inventory. Every certificate, issued here or uploaded from a vendor, with its expiry, issuer, key strength and any problems.
- Warns you early. E-mail, Microsoft Teams or Slack, at the thresholds you choose.
- Hands certificates out. Your servers fetch them through the API, a download link or a small pull script. Nothing is pushed onto your servers.
- Checks the hand-over. It records which systems picked up each certificate, and can check what a host is actually serving, so a missed renewal is caught early.
- Watches what it did not issue. Appliance and vendor certificates can be uploaded or tracked by their live endpoint.
How it fits in
| Topic | In short |
|---|---|
| Where it runs | One container on your own server, on-premises or in your cloud |
| Who uses it | Your IT and security teams, through the browser or the API |
| Sign-in | Microsoft Entra ID, OIDC or LDAP, plus a built-in administrator |
| What you configure | Everything in the web interface. The server only needs a port and a key |
Licensing in one line
Licences count certificates, not users: add as many people and teams as you like. See Licensing.