コードサイニング証明書を更新する

デジサートコードサイニング証明書を更新する必要がある場合は、以下のステップを実行して証明書を更新します。

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 must be stored on hardware certified as Federal Information Processing Standards (FIPS) 140-2 Level 2, Common Criteria EAL 4+, or equivalent.

For more information, see our knowledge base articles:

ステップ1：新しいCSRを生成する（オプション）

Organization validation
- Code signing certificate renewals: Ensure the organization with which you associate your code signing (CS) certificate has been validated for CS-Code Signing Organization Validation.
- EV code signing certificate renewals: Ensure the organization with which you associate your EV code signing certificate is validated for EV CS-Code Signing Organization Extended Validation.
Domain validation for code signing certificate renewals
When adding an email address as the subject of your certificate, the email must include a validated domain assigned to the organization in your order. 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 out domain prevalidation instructions.
Hardware security module (HSM)
Are you installing your code signing certificate on an HSM device?
必須：CSRの送信が必要となるプラットフォームは、Sun Javaプラットフォームのみです。

ステップ3：更新フォームに記入する

左側にあるメインメニューで、［証明書］＞［有効期限間近の証明書］の順にクリックします。
1. In the left menu, go to Certificates > Orders.
2. ［有効期限間近の証明書］ページで、更新する必要がある証明書の横にある［今すぐ更新する］をクリックします。
3. For CertCentral Subscription accounts:
  1. In the left menu, go to My Digital Trust Products > Certificates.
  2. On the Certificates page, select the Order # of the code signing or EV code signing certificate you want to renew.
On the Order details page, in the Certificate actions menu, select Renew.
On the Renew EV Code Signing/Code Signing Order page, update the renewal form as needed, including selecting a new provisioning method.
Provisioning options
The provisioning method refers to where you 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 sends you a secure token with instructions for installing the certificate on your token.
  Then, under Shipping address, add your mailing information: your name and the address where you want us to send the hardware token.
- Use existing token
  When DigiCert issues your code signing certificate, install the certificate on your token.
  In the Platform menu, 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 key certificates.
  - SafeNet eToken 5110 FIPS for ECC P-256-bit key certificates.
  - SafeNet eToken 5110+ FIPS for RSA 4096-bit and ECC P-256-bit key certificates.
  - SafeNet eToken 5110+ CC (940B) for ECC P-256-bit key certificates.
  - SafeNet eToken 5110+ CC (940C) for RSA 4096-bit and ECC P-256-bit key certificates.
  注記
  You must have a DigiCert-supported FIPS 140-2 Level 2 or Common Criteria EAL4+ compliant device. You can’t install the certificate on any device not on the list.
  Need an approved token?
  Select DigiCert-provided hardware token to have DigiCert send a token to you. If you have questions, contact DigiCert Support.
- Install on HSM
  When DigiCert issues your code signing certificate, install it on the HSM where you generated the private key and certificate signing request (CSR).
  1. Select Yes under Was the private key generated by a Common Criteria EAL4+ standard or FIPS 140-2 level 2 HSM?
  2. In the Add your CSR box, upload or enter your CSR.
    Code signing certificates must use an RSA key a minimum of 3072 bits in length to remain secure.
    Your CSR must include the -----BEGIN NEW CERTIFICATE REQUEST----- and -----END NEW CERTIFICATE REQUEST----- tags.
  DigiCert send the certificate requester 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 can't issue the certificate unless the requester agrees to the private key protection requirement.
  注記
  You must have a FIPS 140-2 Level 2 or Common Criteria EAL4+, or equivalent hardware security module (HSM) that supports at least 3072-bit keys.
  Don't have a compatible HSM?
  Select a different provisioning method. If you have any questions contact DigiCert Support.
- DigiCert® KeyLocker (Cloud HSM)
  KeyLocker is an automated cloud storage service where you can store your private keys and code signing certificates. Access your certificates anytime from anywhere to sign your code. Learn more.
  DigiCert also offers DigiCert® Software Trust Manager, an enterprise-level code signing solution. Contact your account representative to determine if your organization could benefit from Software Trust ManagerSoftware Trust Manager. Learn more.
When ready, select Submit request.

ステップ4：デジサートがコードサイニング証明書を発行する

CSRが送信されている場合は、更新された証明書が証明書の連絡先にEメールで送信されます。CertCentralアカウントで更新された証明書をダウンロードすることもできます。

Complete organization validation

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

Human Resources
Manager
Technical contact

To provide organization consent for your certificate order:

Answer the organization/validation phone call (preferred method).*
Ensure the organization contact, technical contact, and company receptionist know you've ordered a code signing certificate. Tell them DigiCert must call a verified phone number to speak with one of them to make sure you have permission to request this certificate. This call usually occurs within 24 hours of the certificate order being placed.
Respond to the organization's consent message.
If the DigiCert validation agent can't reach someone representing you at the verified phone number, they leave a message. The message includes a callback phone number and a verification code. Make sure that organization or technical contact responds to the message and provides the verification code.
Schedule a time for a call back through the verified phone number.
If the DigiCert validation agent can't reach someone who represents you at the verified phone number, they may email you. The email asks you to schedule a time for us to call back to finish the verification.

Order approval

When DigiCert finishes process your order, we send an email with information to approve the certificate request to the verified contacts included in the renewal. We can finish processing your order when a verified contact approves your request.

Certificate issuance

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

DigiCert-provided hardware token (nonrefundable)
If you opted to have DigiCert send you a secure token, we send your token with instructions for installing the certificate on your token. See our knowledge base article for Installing your code signing certificate onto a secure token.
Your own supported hardware token
If you opted to use your own supported secure token, see our knowledge base article for Installing your code signing certificate onto a secure token.
Supported HSM device
If you opted to install your code signing certificate on a supported HSM, download the certificate from CertCentral to install it on the HSM. See Download a code signing certificate from your account.
DigiCert KeyLocker
If you opted to store your private key and code signing certificate on DigiCert KeyLocker, see KeyLocker access.

このセクションの内容: