Private Keys and CSRs: The SSL Security Rules You Cannot Ignore
Generate keys safely, decode a CSR, choose modern algorithms and respond correctly when a private key is exposed.

The certificate is public. The private key is the secret that proves your server owns it. If someone obtains that key, they may be able to impersonate the service under the right network conditions.
Generate the key where it will live
Create the key on the server, hardware module or managed load balancer whenever possible. Do not ask a third party to generate and email it. Restrict filesystem permissions and exclude keys from source control and ordinary backups.
Check the CSR
A Certificate Signing Request contains the public key and requested identity. Double-check the common name, SANs, organisation and algorithm before you submit it β our CSR generator lets you enter each field deliberately, and the CSR matcher confirms the issued certificate matches. A typo means reissuing.
If the key is exposed
Generate a new key and CSR, request a free reissue, deploy it everywhere, then revoke the old certificate. Copying the old certificate onto a new key does not work; they are cryptographically paired.
Modern defaults
RSA 2048 remains broadly compatible; ECDSA offers smaller keys and efficient handshakes where your platform and clients support it. Follow the CA and server documentation rather than inventing parameters.
Share this article
Was this article helpful?
Your vote helps us write better guides.
