A public code signing certificate comes from a publicly trusted CA. Operating systems and platforms trust it by default, so it's used for software distributed to systems you don't control. A private code signing certificate comes from your own CA. It's trusted only on systems where you install your root certificate, so it's used for internal software and devices you manage. Public certificates must follow industry rules on validation, algorithms, validity, and key storage. With private certificates, your organization sets those rules.
Public |
Private |
|
Issued by |
A publicly trusted CA that follows the CA/B Forum Code Signing Baseline Requirements |
Your own CA, or a private CA run as a service |
Trusted by |
Operating systems and platforms by default, through their root programs |
Only systems where you install and trust your root |
Identity checks |
The CA verifies your organization (OV or EV) |
Defined by your internal policy |
Key types |
RSA (3072-bit minimum) or ECDSA |
Set by your policy. Can include other options, such as RSA 2048 or Ed25519, if the verifying systems support them. |
Maximum validity |
Set by your policy |
|
Key storage |
Required: certified hardware (FIPS 140 Level 2, Common Criteria EAL 4+, or equivalent) (DigiCert) |
No industry mandate. Hardware storage is still strongly recommended. |
Revocation and timestamping |
Provided by the CA |
Provided by your CA or service, or a public timestamp service |
Use a public certificate when the software runs on systems you don't control. Examples:
Without a public certificate, users see "unknown publisher" warnings or the software is blocked.
Use a private certificate when you control the systems that verify the signature. Examples:
Private certificates give you control over algorithms, validity periods, and naming. Private CAs also avoid the public certificate volume and cost.
No. Neither type encrypts code. Both create signatures that prove who published the software and that it hasn't changed. The differences are in which algorithms and key sizes are allowed, and who decides.
They aren't required to be in hardware, but they should be. A stolen private key can sign malware that your own systems will trust. Apply the same controls you use for public keys:
They fit neither category. Apple issues its own developer certificates. Android apps are signed with keys the developer manages. See Types of code signing certificates.
How DigiCert helps: DigiCert issues public OV and EV code signing certificates and offers private certificates through (PKI as a Service) Private CA. Software Trust Manager manages both public and private code signing certificates with the same public-level HSM storage, access control, and logging.