Issue
Create certificates through the platform, API, or private ACME server.
From issuance to retirement
Manage the complete certificate lifecycle in one place.
SecuriTLS tracks certificates from initial issuance through renewal, rekey, reissue, revocation, expiration, replacement, and deployment validation.
Replace scattered scripts and spreadsheets with lifecycle records that show what changed, why it changed, and which certificate replaced which.
Teams using infrastructure as code can manage certificate resources and explicit renew, rekey, and reissue triggers with the SecuriTLS Terraform provider.
IssueCreate
RotateRenew or rekey
RetireRevoke or expire
The automation deadline is approaching
47-day public TLS certificates make manual certificate management harder to justify.
The CA/Browser Forum maximum validity schedule moved publicly trusted TLS certificates to 200 days in 2026, drops to 100 days on March 15, 2027, and reaches 47 days on March 15, 2029. That schedule does not apply to private PKI certificates, but it makes the operational direction clear: certificate rotation is becoming continuous infrastructure work.
SecuriTLS is built to automate the lifecycle around certificates it manages: renewal, replacement tracking, deployment, validation, alerts, and audit history.
See the 47-day TLS automation timeline →Lifecycle operations
Handle the changes certificates go through in production.
Renew
Replace an expiring certificate while preserving the relationship between the old and new records.
Rekey
Issue a replacement certificate with new key material when key rotation is required.
Reissue
Replace a certificate when identity details, SANs, or other certificate properties change.
Revoke
Mark certificates revoked and connect revocation state to CRL and ACME workflows.
Expire
Surface expiring and expired certificates before they become forgotten infrastructure debt.
Operational continuity
Preserve certificate relationships during replacement.
SecuriTLS records replacement links so renewed, rekeyed, and reissued certificates do not lose their operational context.
1
Identify the current certificate
Review issuer, validity, deployment, and existing lifecycle state.
2
Create the replacement
Renew, rekey, or reissue based on the reason for rotation.
3
Update deployment references
Move device and service attachments to the replacement certificate.
Explore deployment automation →4
Validate the live result
Confirm that the expected certificate is deployed and serving.
Explore validation →Visibility and control
Know what is active, what changed, and what needs attention.
Status and alerts
Surface valid, expiring, expired, renewed, reissued, rekeyed, and revoked states.
Audit history
Record lifecycle actions for troubleshooting, accountability, and review.
Automation paths
Use the platform, API, ACME, scheduled workflows, and deployment automation according to your plan.
Get started
Bring your certificate workflows into one place.
Start with a private CA and a few certificates, then expand into automation, deployment validation, audit history, and satellite workflows.