Deployment Prerequisites¶
The following items must be in place before installing Certificate Lifecycle Management. They apply to on-premises and private cloud deployments. SaaS deployments require only the items listed under SaaS customers.
Licence, Servers and Infrastructure¶
| Item | What you need |
|---|---|
| Installation package and licence | The Securden Unified PAM installation package and a licence key for Certificate Lifecycle Management. |
| Servers | Servers that meet the specifications on the System Configuration page, each with a Windows Server licence. |
| Local admin rights | Local administrator rights on the application server to run the installation. |
| Firewall changes | Firewall rules approved before deployment. See the Ports Used page for the full list. |
| SSL certificate | A publicly trusted SSL certificate with its private key and the intermediate certificate authority (CA) bundle. It secures connections between users' browsers and the server. |
| DNS records | DNS records for the primary and secondary application servers, so users reach the console by name. |
| Load balancer or virtual IP (VIP) | Needed only if you run a secondary server for high availability. |
| Encryption key storage | A separate, access-controlled network location with a dedicated service account, or a hardware security module (HSM). The encryption key is kept away from the encrypted data. |
| Backup storage | A network path the server can write to, for encrypted database backups. |
| Mail server (SMTP) | SMTP server details so the platform can send email notifications, such as certificate expiry alerts. |
| Internet access | Outbound internet access from the application server to reach public certificate authorities and ACME providers. If a proxy server controls internet traffic, have its address, port and credentials ready. |
| User directory (optional) | Connection details for Active Directory, Microsoft Entra ID or LDAP if users will sign in with their directory accounts, and for your single sign-on (SSO) or multi-factor authentication (MFA) provider if you use one. |
Certificate Discovery Access¶
To discover existing certificates, prepare the host names or IP ranges to scan. The application server needs network access to them on the ports their certificates are served on.
Certificate Issuance and Deployment¶
Required only when certificates are issued, renewed or deployed through the platform.
| Item | What you need |
|---|---|
| Public certificate authority | An account with the CA you buy certificates from (GoDaddy, The SSL Store, DigiCert, GlobalSign, Sectigo, Entrust or emSign) and its API credentials. |
| ACME provider | An account with an ACME provider (Let's Encrypt, Buypass Go SSL, ZeroSSL, Telia or any ACME-compatible provider) and a contact email. Some providers, such as ZeroSSL, also issue External Account Binding (EAB) keys that must be entered. ACME (Automatic Certificate Management Environment) is the protocol that issues and renews certificates automatically. |
| Domain validation | ACME providers check that you control each domain before issuing a certificate, usually through a web (HTTP) or DNS check. |
| Private certificate authority | A decision on whether to create a private root CA in Securden for internal certificates. |
| Certificate deployment targets | OpenSSH Server enabled on each Windows or Linux system that will receive certificates, and an account the platform can use to connect to it. |
SaaS Customers¶
Securden hosts the servers, database, SSL certificate, backups and encryption keys. SaaS customers provide:
- Network access to the servers and websites to be scanned, if certificate discovery is used.
- Certificate authority and ACME provider accounts, if certificates are issued or renewed through the platform.
- User directory, SSO or MFA details, if users sign in through them.