FAQ Hero
Code Signing Trust

What's the difference between public and private code signing certificates?

What's the difference between a public and private code signing certificate?

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.

How do public and private code signing certificates compare?

 

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

460 days

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

 

When should I use a public code signing certificate?

Use a public certificate when the software runs on systems you don't control. Examples:

  • Commercial applications and installers
  • Downloadable tools
  • Windows drivers
  • Java applications
  • Updates delivered to customers

Without a public certificate, users see "unknown publisher" warnings or the software is blocked.

When should I use a private code signing certificate?

Use a private certificate when you control the systems that verify the signature. Examples:

  • Test certificates for development, QA, and pre-release builds. Teams can sign test builds as often as they need without touching production keys. Test-signed builds are trusted only inside your organization, so a leaked build or test key can't pass as your released software.
  • Internal applications and scripts on managed devices
  • Firmware for devices that ship with your root built in
  • Internal containers and packages

Private certificates give you control over algorithms, validity periods, and naming. Private CAs also avoid the public certificate volume and cost.

Does either type encrypt software?

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.

Do private signing keys still need hardware protection?

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:

  • Keep keys in an HSM
  • Use role-based access
  • Keep signing logs
  • Never share keys

What about Apple and Android?

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.

Related questions