Skip to main content

코드 서명 인증서 갱신

DigiCert 코드 서명 인증서를 갱신해야 합니까? 아래의 단계를 따라서 인증서를 갱신합니다.

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 Level 2, Common Criteria EAL 4+, or equivalent.

For more information, see our knowledge base articles:

단계 1: 새 CSR 생성(옵션)

중요

업계는 코드 서명 인증서에 대해 최소 RSA 3072비트 키로 전환

업계 변경 사항을 준수하기 위해 DigiCert는 코드 서명 인증서 절차에 대해 다음을 변경했습니다:

  • RSA 3072비트 이상 코드 서명 인증서만 발급*

  • 코드 서명 및 EV 코드 서명 인증서를 발급하기 위해 새 중간 CA 및 루트 인증서를 사용: RSA 및 ECC

3072비트 코드 서명 인증서로 변경에 대해 자세히 알아보세요.

  • 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?

    필수: Sun Java Platform이 CSR을 제출해야 하는 유일한 플랫폼입니다.

단계 3: 갱신 양식을 입력합니다.

  1. 왼쪽 메인 메뉴에서 인증서 > 만료되는 인증서를 클릭합니다.

  2. 만료되는 인증서 페이지에서 갱신해야 하는 인증서 옆에서 지금 갱신을 클릭합니다.

  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.

      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.

      중요

      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 any 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.

      중요

      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.

단계 4: DigiCert에서 코드 서명 인증서를 발급

CSR을 제출한 경우, 갱신된 인증서를 이메일의 인증서 연락처로 보냅니다. 또한 CertCentral 계정에서 갱신 인증서를 다운로드할 수도 있습니다.

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.

이 섹션의 내용: