Order an EV Code Signing certificate
Important
RSA 3072-bit key minimum for EV code signing certificates
To comply with new industry requirements, DigiCert made the following changes to our EV code signing certificate process.
Only issues RSA 3072-bit key or larger EV code signing certificates.*
Uses new intermediate CA and root certificates to issue our EV code signing certificates: RSA and ECC.
eToken and HSM changes
DigiCert supports the following eTokens:
SafeNet eToken 5110 CC for RSA 4096-bit and ECC P-256-bit 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 key certificates.
HSM must:
Support RSA 3072-bit or ECC P-256-bit keys sizes or larger.
Be FIPS 140-2 Level 2+ or Common Criteria EAL4+ compliant devices.
*Note: All existing 2048-bit key code signing certificates issued before June 1, 2021, will remain active. You can continue to use these certificates to sign code until they expire.
Learn more about the change to 3072-bit key code signing certificates.
Before you begin
Organization validation
Make sure the organization with which you want to associate your EV Code Signing (CS) certificate has been validated for EV CS – Code Signing Organization Extended Validation. See Submit an organization for prevalidation.
Hardware security module (HSM)
Are you installing your EV 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.
Order your EV Code Signing certificate
In the left main menu, hover over Request a Certificate. Under Code Signing Certificates, select EV Code Signing.
On the Request EV Code Signing Certificate page, in the For dropdown, select the division to manage the certificate.
The For dropdown only appears if your account uses Divisions.
Certificate Settings
Validity period
Select a validity period for the certificate: 1 year, 2 years, or 3 years.
If needed, you can customize the expiration date or certificate length. However, you cannot exceed the 39-month maximum EV code signing certificate validity.
Auto-renew
To set up automatic renewal for this EV code signing certificate, check Auto-renew order 30 days before expiration.
With auto-renew enabled, DigiCert automatically submits a request to renew the EV Code Signing order thirty days before it expires. Auto-renew is not available with credit card payments.
Important
If your certificate still has time remaining before it expires, DigiCert adds the remaining time from your current certificate to your new certificate (up to 39 months).
Organization
Add an organization
Select Add organization. The organization name will appear on the EV code signing certificate.
You can add an existing organization from your account or a new organization. The new organization will be added to your account. Before we can issue your certificate, DigiCert must complete the EV code signing validation for the selected or new organization.
In the Add organization window, do one of the following:
Add an existing organization.
Select An existing organization.
In the dropdown, select the organization and then select Add.
If you choose an organization not validated for EV Code Signing certificates or if the organization's EV code signing validation has expired, DigiCert must validate the organization for EV code signing validation before we can issue your certificate.
Organization and technical contacts.
DigiCert automatically adds the contacts assigned to the organization to the request form. To see the organization and technical contacts, select Show organization contacts.
Verified contacts.
DigiCert automatically adds the assigned contacts to the request form if the organization has EV code signing verified contacts. To view, change selections, or add verified contacts, expand Verified contacts.
The Add contacts popup window opens if the organization has not assigned EV code signing verified contacts. In this window, you can add yourself, a user in your account, or a new contact as a verified contact. See Verified contacts below.
Add a new organization.
Select A new organization and select Next.
Under Organization address details, enter your organization's legal name, assumed name (optional), address, and phone number.
DigiCert must validate the organization for EV code signing validation before we can issue your certificate.
When ready, select Add.
Add an organization contact.
In the Add organization window, add yourself or someone else from your account, or create a new organization contact.
Important
The organization contact is whom we contact when validating the organization and verifying your authority to order a DigiCert certificate for the organization.
They may also receive the following notifications:
Order status updates for certificates requested for their organization.
Domain status updates for domains associated with their organization.
Add yourself as the organization contact.
Select Add me as the organization contact and then select Add or Next.
If we have all your information, you will select Add.
If we need more information, you will select Next, enter the missing information, and then select Add.
Add someone else as the organization contact.
Select Add someone else as the organization contact. Then in the Add contact dropdown, select the contact or user and then select Add or Next.
If we have the needed user information, you will select Add.
If we need more user information, you will select Next, enter the missing information, and then select Add.
Create new contact.
Select Add someone else as the organization contact.
In the Add contact dropdown, select Create new contact and then select Next.
Enter the needed user information and then select Add.
Technical contact for the organization (optional)
We may contact a technical contact for inquiries regarding certificate orders for the organization. They may receive the certificate lifecycle-related emails: certificate issued, reissued, and expiring.
Add yourself as the technical contact.
Select Add me as the technical contact for the organization and then select Add or Next.
If we have all your information, you will select Add.
If we need more information, you will select Next, enter the missing information, and then select Add.
Add someone else as the technical contact.
Select Add someone else as the technical contact for the organization. Then in the Add contact dropdown, select the contact or user and then select Add or Next.
If we have the needed user information, you will select Add.
If we need more user information, you will select Next, enter the missing information, and then select Add.
Create new contact.
Select Add someone else as the technical contact for the organization.
In the Add contact dropdown, select Create new contact and then select Next.
Enter the needed user information and then select Add.
Verified contacts
A verified contact must represent the organization included in your certificate request. At least one EV code signing verified contact is required.
To view, change selections, or add verified contacts, expand Verified contacts.
Select verified contacts.
If the organization has multiple EV code signing verified contacts, you can select who receives the EV code signing order approval email.
DigiCert sends the approval email to all selected, verified contacts, but only one needs to approve your order. Once the order is approved, DigiCert can issue your certificate. Selecting multiple verified contacts increases the likelihood of your order being approved quickly.
Add a verified contact.
When adding a new verified contact, we will contact the organization directly to verify the individual's name, email, phone number, job title, and authority. Only after DigiCert validates a verified contact can they approve EV code signing orders for the organization.
Add yourself as the verified contact.
Select Add me as a verified contact for the organization and then select Add or Next.
If we have all your information, you will select Add.
If we need more information, you will select Next, enter the missing information, and then select Add.
Add someone else as the verified contact.
Select Add someone else as the verified contact for the organization. Then in the Add contact dropdown, select the contact or user and then select Add or Next.
If we have the needed user information, you will select Add.
If we need more user information, you will select Next, enter the missing information, and then select Add.
Create new contact.
Select Add someone else as the verified contact for the organization.
In the Add contact dropdown, select Create new contact and then select Next.
Enter the needed information and then select Add.
Additional emails (optional)
Enter the email addresses (comma separated) you want to receive the certificate notification emails, such as certificate issuance and expiring certificate notifications.
Depending on your account settings, your administrator may require you to include at least one additional email.
Additional certificate options
The information below is optional. None of it is required to issue your EV code signing certificate.
Organization unit (optional)
Enter the organization unit (OU) with which you want to associate the certificate and signatures. If you include an OU in your order, DigiCert must validate it before we can issue your certificate with the OU field.
An OU is not required to issue your certificate. You can leave this box empty. When the box is empty, the issued certificate will not have an OU value.
Order Settings
Provisioning options
The provisioning method refers to where you will store the private key and certificate. For the security of your EV Code Signing certificate, the certificate must be installed on and used from an approved device.
Select the storage device for your EV Code Signing certificate and its' private key.
DigiCert-provided hardware token
DigiCert ships 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 EV code signing certificate, install the certificate on your token.
In the Platform dropdown, select the type of hardware token on which you plan to install your EV Code Signing certificate:
SafeNet eToken 5110 CC 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.
Important
You must have a FIPS 140-2 Level 2 or Common Criteria EAL4+ compliant device. See Currently Supported eTokens. 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 EV code signing 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 ensures the private key is stored on an HSM certified as FIPS 140 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 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 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.
Additional order options
The information below is optional. None of it is required to issue your certificate.
Comments to Administrator (optional)
Enter any information your administrator might need for approving your request, about the purpose of the certificate, etc.
Additional Renewal Message (optional)
To create a renewal message for this certificate, add a message with information relevant to the certificate's renewal.
Payment Information
Select Payment Method
Under Payment Information, select a payment method to pay for the certificate:
Bill to Credit Card
Don't have a contract or don't want to use the contract to pay for this certificate? Use a credit card to pay for the certificate.
We authorize the card when the request is made. However, we only complete the transaction once we issue your certificate.
If you have a contract enabled, check Exclude from contract terms.
Bill to Account Balance
Don't have a contract or don't want to use the contract to pay for this certificate? Bill the cost to your account balance.
To deposit funds, select the Deposit link. This link takes you to another page inside your CertCentral account. Any information entered in the request form will not be saved.
If you have a contract enabled, check Exclude from contract terms.
Pay with Contract Terms
Have a contract and want to use it to pay for the certificate? When you have a contract, it is the default payment method.
Master Services Agreement
Select the Master Services Agreement link to read through the agreement.
Select Submit Certificate Request.
Selecting Submit Certificate Request also means you agree to all the terms and conditions in the Master Services Agreement.
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.