Ports Used¶
The following ports must be open before deploying Certificate Lifecycle Management. All ports are TCP unless noted. Firewall changes should be approved for every network the platform must reach, including networks that host the systems it scans and the systems that receive certificates.
Core Product Ports¶
| Port name | Source | Destination | Port | Details |
|---|---|---|---|---|
| PostgreSQL database | Primary and secondary application servers | PostgreSQL database server | 5858 | Default database connection |
| Microsoft SQL Server database | Primary and secondary application servers | Microsoft SQL Server | 1433 | Only if Microsoft SQL Server is the database |
| Web console | User machines and the secondary server | Primary application server | 5959 | Can be changed to 443 or another port |
| Web console | User machines | Secondary application server | 5959 | Only with high availability. Can be changed to 443 or another port |
| Database replication | Primary application server | Secondary application server | 5858 | Only with high availability. Replication runs in both directions, so the port must be open on both servers. For automatic failover, the standby server must be in the same subnet as the primary server. |
| Mail (SMTP over TLS) | Application server | Mail server | 587 | Email notifications using TLS |
| Mail (SMTP over SSL) | Application server | Mail server | 465 | Email notifications using SSL |
Directory, Authentication and Integration Ports¶
Required only for the features in use.
| Port name | Source | Destination | Port | Details |
|---|---|---|---|---|
| Proxy server | Primary application server | Proxy server | Your proxy's port | Only if a proxy controls internet traffic |
| Active Directory, secure | Primary application server | Active Directory domain controller | 636 | Default. Used when users sign in with Active Directory over SSL/TLS |
| Active Directory, standard | Primary application server | Active Directory domain controller | 389 | Only if SSL/TLS is not turned on for the directory connection |
| RADIUS | Application servers | RADIUS or MFA server | 1812 | Only if RADIUS-based two-factor authentication is used |
| Microsoft Entra ID | Application servers | Microsoft Entra ID (Microsoft Graph API) | 443 (HTTPS) | Only if Entra ID is used for user sign-in |
| SIEM | Application server | Your SIEM server | Your SIEM's port, for example Syslog | Forwards audit events to your security information and event management (SIEM) platform. |
Certificate Discovery Connections¶
Required only if certificate discovery is used. The platform connects out to the servers and websites it scans on your network.
| Discovery type | Source | Destination | Port |
|---|---|---|---|
| SSL certificate discovery | Primary application server (on-premises); remote connector (SaaS) | Servers and websites being scanned | The ports their certificates are served on, usually 443 |
Certificate Issuance and Deployment Connections¶
Required only when certificates are issued, renewed or deployed through the platform.
| Port name | Source | Destination | Port |
|---|---|---|---|
| Public certificate authorities | Application server | API of each CA you use (GoDaddy, The SSL Store, DigiCert, GlobalSign, Sectigo, Entrust, emSign) | 443 (HTTPS) |
| ACME providers | Application server | ACME service of each provider, for example Let's Encrypt | 443 (HTTPS) |
| ACME domain validation | ACME provider | Application server | 443 (HTTPS) |
| Certificate deployment | Primary application server (on-premises); remote connector (SaaS) | Windows and Linux systems receiving certificates (OpenSSH Server) | 22 (SSH) |
| Certificate revocation list (CRL) | Systems and browsers that check certificates issued by your private CA | Application server | 5961 |
Configuration Notes¶
- The web console port (default 5959) can be changed to 443 or any available port.
- The Active Directory port defaults to 636. Port 389 applies only when SSL/TLS is not turned on for the directory connection.
SaaS Customers¶
Securden manages the core product ports. Certificate discovery, issuance and deployment connections start from Securden's cloud, or from the remote connector for systems inside your network.