Implementation Checklist
Refer to the implementation checklist below to deploy and get started with Certificate Lifecycle Management in your production environment. Setup starts with the database and basic settings, then user access, then bringing in your existing certificates and setting up issuance, renewal and deployment.
Base Setup
| No. |
Step |
Notes |
|
Database |
|
| 1 |
Choose the database |
Use the bundled PostgreSQL database or Microsoft SQL Server. Both scale well. Decide before moving to production: switching later is not supported because data cannot be migrated. |
|
Mandatory settings |
|
| 2 |
Apply the licence |
Apply the registered licence key for Certificate Lifecycle Management. It then appears under Admin >> Certificate Management >> Manage & Govern Certificates. |
| 3 |
Move the installation encryption key |
When you apply the licence, you are prompted to move the installation encryption key out of the installation folder, so the key and the encrypted data are not stored together. Follow the steps on screen. |
| 4 |
Mail server settings |
Enter your SMTP server details so the platform can send email notifications, such as certificate expiry alerts. Go to Admin >> General >> Mail Server Settings. |
| 5 |
Proxy server settings |
If a proxy server controls internet traffic, enter its details. The platform needs internet access to reach certificate authorities and ACME providers. Go to Admin >> General >> Proxy Server Settings. |
| 6 |
Server connectivity settings |
Set the name and address that user machines use to reach the web console. Go to Admin >> General >> Securden Server Connectivity. |
User Onboarding
| No. |
Step |
Notes |
| 7 |
Connect your directory |
Import users and groups from Active Directory, Microsoft Entra ID or LDAP, keep them in sync, and let users sign in with their directory accounts. Go to Users >> Add. |
| 8 |
Assign roles |
Assign a predefined or custom role to each user. Create custom roles from Admin >> Customization >> Custom User Roles. Create one or two super administrators, then turn off further creation from Admin >> Customization >> Configurations. |
| 9 |
Delete the default administrator account |
The product ships with a local administrator account. Delete it. You may keep one other local account for emergencies, such as when the directory is down. |
| 10 |
Enforce two-factor authentication |
Require a second sign-in step for all users. Go to Admin >> Authentication >> Two Factor Authentication. |
| 11 |
Set up single sign-on (SSO) |
Connect a SAML identity provider such as Okta, Microsoft Entra ID, ADFS, OneLogin, PingIdentity or Google Workspace. Go to Admin >> Integrations >> SAML SSO. |
Certificate Lifecycle Management
All paths below are under Admin >> Certificate Management >> Manage & Govern Certificates.
| No. |
Step |
Notes |
|
Set up issuance |
|
| 12 |
Set up certificate authorities |
Create a private root CA for internally signed certificates, connect the public CAs you buy from, and add ACME providers for automatic issuance and renewal. Go to Authorities. |
| 13 |
Create CSR templates |
Save reusable templates for certificate signing requests (CSRs), holding common details such as organisation, organisational unit and locality. Go to Certificate Signing Requests. |
|
Bring in existing certificates |
|
| 14 |
Discover certificates |
Scan servers and websites on your network for the SSL/TLS certificates they use. Start with a small range to check results before scanning the rest. Go to SSL/TLS Certificates >> Add Certificate >> Discover Certificates >> SSL Certificate Discovery. |
| 15 |
Add certificates manually |
Add any certificates that discovery does not reach, so the inventory and expiry tracking are complete. Go to SSL/TLS Certificates >> Add Certificate >> Add Manually. |
|
Issue, renew and deploy |
|
| 16 |
Issue and renew certificates |
Create a CSR and either self-sign it or submit it to a certificate authority. When you renew an expiring certificate, the platform creates a new CSR and sends it to the CA for you. Certificates issued through ACME renew automatically. Certificates can also be revoked. |
| 17 |
Deploy certificates |
Push certificates to Windows and Linux systems and the Microsoft Certificate Store. OpenSSH Server must be enabled on each target system. Go to SSL/TLS Certificates and choose Deploy Certificate. |
Monitoring, High Availability and Maintenance
| No. |
Step |
Notes |
|
Monitoring |
|
| 18 |
Review the audit trail |
The Certificate Management tab of the audit trail records each action, with the user, IP address, time and stated reason. Go to Audits and Administration >> Audit. |
| 19 |
Use the reports |
Available reports: Expiring Certificates, Expired Certificates and Self-Signed Certificates. Export any report as PDF, CSV or XLSX. Go to Audits and Administration >> Reports. |
| 20 |
Configure notifications |
Choose which events send email notifications, such as certificate expiry alerts. Go to Admin >> Notifications >> Event Notifications. |
| 21 |
Connect your SIEM |
Forward audit events to your SIEM platform. Go to Admin >> Integrations. |
|
Security, high availability and maintenance |
|
| 22 |
Restrict console access by IP address |
Allow access to the web console only from specific IP addresses, and review the other security settings. Go to Admin >> Security. |
| 23 |
Configure high availability |
Deploy a secondary application server that takes over if the primary fails. You can add more application servers in other locations. With Microsoft SQL Server, you can use SQL Server clusters. Go to Admin >> High Availability. |
| 24 |
Replace the self-signed certificate |
The product ships with a self-signed certificate. Replace it with your CA-signed certificate and its private key. |
| 25 |
Schedule database backups |
Back up the full database to a remote network path, as often as every hour, and choose how many past copies to keep. Go to Admin >> High Availability >> Database Backup. |
| 26 |
Keep the product up to date |
Check for new releases and upgrade from Admin >> Product Upgrades. |