Skip to main content

Renew your code signing certificate

Learn how to renew your Code Signing and EV Code Signing certificates.

New private key storage requirements

On May 30, 2023, DigiCert updated our private key storage requirements for code signing certificate private keys, per industry standards. All private keys for code signing certificates must be stored on hardware certified as FIPS 140-2 Level 2, Common Criteria EAL 4+, or equivalent.

For more information, see our knowledge base articles:

Before you begin

Important

RSA 3072-bit key minimum for code signing certificates

On May 28, 2021, DigiCert made the following changes to our code signing certificate process to comply with industry changes:

  • Only issue RSA 3072-bit key or larger code signing certificates.

  • Use new intermediate CA and root certificates to issue our code signing and EV code signing certificates: RSA and ECC.

Learn more about the change to 3072-bit key code signing certificates.

  • Organization validation

    • Code Signing certificate renewals: Make sure the organization with which you want to associate your Code Signing (CS) certificate has been validated for CS – Code Signing Organization Validation.

    • EV Code Signing certificate renewals: Make sure the organization with which you want to associate your EV Code Signing certificate has been validated for EV CS – Code Signing Organization Extended Validation.

  • Domain validation (Code Signing certificate renewals only)

    When adding an email address as the subject of a code signing certificate, the email address must include a validated domain associated with the organization included in your order. Only validated domains appear on the order form.

    For example, if you want to add john.doe@example.com, make sure example.com has been validated. See Domain prevalidation.

  • Hardware security module (HSM)

    Are you installing your code signing certificate on an HSM device?

    Then you must submit a certificate signing request (CSR) with your order. The CSR and private key must be generated by the Common Criteria EAL4+ standard or FIPS 140-2 level 2 HSM on which you plan to install the certificate. To remain secure, certificates must use an RSA 3072-bit or ECC P-256-bit key size or larger. Refer to your HSM manufacturer's instructions.

Renew your code signing certificate

  1. In your CertCentral account, in the left main menu, go to Certificates > Orders.

  2. On the Orders page, select the Order # of the code signing or EV code signing certificate you want to renew.

  3. On the Order details page, in the Certificate actions dropdown, select Renew.

  4. On the Renew EV Code Signing/Code Signing Order page, update the renewal form as needed, including selecting a new provisioning method.

  5. Provisioning options

    The provisioning method refers to where you will store the private key and certificate. For the security of your code signing certificate, the certificate must be installed on and used from an approved device.

    Select the storage device for your certificate and its' private key.

    • DigiCert-provided hardware token (nonrefundable)

      DigiCert ships you a secure token with instructions for installing the certificate on your token, so you can start signing code.

      Then, under Shipping address, add your shipping information: your name and the address where you want us to send the hardware token.

    • Use existing token

      After DigiCert issues your certificate, you must install it on your token.

      In the Platform dropdown, select the type of hardware token on which you plan to install your Code Signing certificate:

      • SafeNet eToken 5110 CC (940) for RSA 4096-bit and ECC P-256-bit or higher key certificates.

      • SafeNet eToken 5110 FIPS for ECC P-256 and P-384-bit key certificates.

      • SafeNet eToken 5110+ FIPS for RSA 4096-bit and ECC P-256-bit or higher key certificates.

      • SafeNet eToken 5110+ CC (940B) for ECC P-256-bit key certificates.

      Important

      You must have a FIPS 140-2 Level 2 or Common Criteria EAL4+ compliant device listed above. You cannot install the certificate on any device not on the list.

      Need an approved token?

      Please select DigiCert-provided hardware token to have a token shipped to you. If you have questions, please contact DigiCert Support.

    • Install on HSM

      After DigiCert issues your certificate, install it on the HSM where you generated the private key and CSR.

      Select Yes under Was the private key generated by a Common Criteria EAL4+ standard or FIPS 140-2 level 2 HSM?

      Note that we will send the certificate requestor an agreement email. This email is to ensure that a private key is stored on an HSM that is certified as FIPS 140-2 Level 2, Common Criteria EAL 4+, or equivalent. DigiCert will only issue the certificate after the requester agrees to the private key protection requirement.

      Important

      You must have a FIPS 140-2 Level 2, Common Criteria EAL 4+, or equivalent hardware security module (HSM) that supports at least 3072-bit keys.

      Don't have a compatible HSM?

      Please select a different provisioning method. If you have any questions, please contact DigiCert Support.

    • DigiCert KeyLocker (Cloud HSM)

      KeyLocker is an automated cloud storage service where you can store your private key and code signing certificate. Access them anytime from anywhere to sign your code. Learn more.

      DigiCert also offers Software Trust Manager, an enterprise-level code signing solution. Contact your account representative to determine if your organization could benefit from Software Trust Manager. Learn more.

  6. When ready, select Submit request.

What's next

DigiCert recommends that developers take precautions with the code signing process and protect the private key associated with their signing certificate. See Protect private keys: Code signing best practices.

Complete organization validation

Before DigiCert can issue your certificate, we need to validate your authority to order a certificate for the organization on your code signing certificate. A validation agent will call a verified phone number to speak with someone who represents you (the certificate requestor) and can confirm your authority:

  • Human resources

  • Manager

  • Technical contact

Order approval

After DigiCert completes the required validation for your order, we send an email with information about how to approve the certificate request to the verified contacts included in the renewal. We can finish processing your order only after a verified contact approves your request.

Certificate issuance

Once the validation is complete and the order is verified-contact approved, we will issue your certificate.

In this section: