--- title: "Certificate provisioning management" slug: "certificateprovisioning-management" updated: 2026-09-17T09:17:45Z published: 2026-09-17T09:17:45Z canonical: "guide.ncloud-docs.com/certificateprovisioning-management" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt > Use this file to discover all available pages before exploring further. # Certificate provisioning management Available in Classic and VPC This section explains how to update, remove, or extend the scope of a provisioned certificate. ## Update certificate To update provisioned certificate: 1. From the NAVER Cloud Platform console, navigate to **Menu** > **All Services** > **Content Delivery** > **Global Edge**. 2. Select the **Certificate Provisioning** menu from the left-hand menu. 3. Select the certificate that needs to be updated from the list of provisioned certificates. 4. Click **[Update certificate]**. 5. In the certificate update popup, select the certificate and click **[OK]**. - Select the newly issued certificate or the externally registered certificate from the Certificate Manager. - Selection is not required as the global exclusive certificates are automatically updated. (Display of the previously used global exclusive certificate name) ![global_edge_certificate_provisioning_update_ko](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/global_edge_certificate_provisioning_update_en.png?sv=2026-02-06&spr=https&st=2026-10-27T16%3A50%3A31Z&se=2026-10-27T17%3A50%3A31Z&sr=c&sp=r&sig=8yKQUUKvfUB166Tq1JgzR07rEfNV%2BoFyW3ehFKp%2FAIM%3D) ## Remove certificate To remove provisioned certificate: Note To remove the certificate, all currently used edges must be returned before the certificate can be removed. 1. From the NAVER Cloud Platform console, navigate to **Menu** > **All Services** > **Content Delivery** > **Global Edge**. 2. Select the **Certificate Provisioning** menu from the left-hand menu. 3. Select the certificate that needs to be removed from the list of provisioned certificates. 4. Click **[Remove certificate]**. 5. Enter the certificate **Slot ID** and click **[OK]** in the certificate removal popup. ## Expand the certificate coverage To add a global certificate for certificates deployed in the service regions of Korea/Japan: 1. From the NAVER Cloud Platform console, navigate to **Menu** > **All Services** > **Content Delivery** > **Global Edge**. 2. Select the **Certificate Provisioning** menu from the left-hand menu. 3. Click **[•••]** on the right side of the provisioned Korea/Japan certificate and then select the expand certificate coverage menu. ![global_edge_certificate_provisioning_expansion_ko](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/global_edge_certificate_provisioning_expansion_en.png?sv=2026-02-06&spr=https&st=2026-10-27T16%3A50%3A31Z&se=2026-10-27T17%3A50%3A31Z&sr=c&sp=r&sig=8yKQUUKvfUB166Tq1JgzR07rEfNV%2BoFyW3ehFKp%2FAIM%3D) 4. Select the **global exclusive certificate** and click **[OK]** in the expand certificate coverage popup. ![global_edge_certificate_provisioning_expansion1_ko](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/global_edge_certificate_provisioning_expansion1_en.png?sv=2026-02-06&spr=https&st=2026-10-27T16%3A50%3A31Z&se=2026-10-27T17%3A50%3A31Z&sr=c&sp=r&sig=8yKQUUKvfUB166Tq1JgzR07rEfNV%2BoFyW3ehFKp%2FAIM%3D) ## Set TLS protocol version It can be configured with various SSL/TLS cipher groups. The list of cipher groups to be used for the TLS handshake is automatically selected when you choose a cipher profile. Once the cipher profile is enabled, NAVER Cloud will not update the existing cipher profile except in the case of a security incident. Customers are recommended to review their registration settings and update to the latest cipher profile if possible. ### Enable cipher profile The cipher profile can be used for all users, all certificates, and all registrations. | Profile | Cipher Suites | | --- | --- | | | - TLS-AES-256-GCM-SHA384 - TLS-CHACHA20-POLY1305-SHA256 - TLS-AES-128-GCM-SHA256 - ECDHE-ECDSA-AES256-GCM-SHA384 - ECDHE-ECDSA-AES128-GCM-SHA256 - ECDHE-RSA-AES256-GCM-SHA384 - ECDHE-RSA-AES128-GCM-SHA256 - ECDHE-ECDSA-CHACHA20-POLY1305 - ECDHE-RSA-CHACHA20-POLY1305 | | | - TLS-AES-256-GCM-SHA384 - TLS-CHACHA20-POLY1305-SHA256 - TLS-AES-128-GCM-SHA256 - TLS-AES-128-CCM-8-SHA256 - TLS-AES-128-CCM-SHA256 - ECDHE-ECDSA-AES256-GCM-SHA384 - ECDHE-ECDSA-AES128-GCM-SHA256 - ECDHE-RSA-AES256-GCM-SHA384 - ECDHE-RSA-AES128-GCM-SHA256 - ECDHE-ECDSA-CHACHA20-POLY1305 - ECDHE-RSA-CHACHA20-POLY1305 - ECDHE-ECDSA-AES256-SHA384 - ECDHE-ECDSA-AES128-SHA256 - ECDHE-RSA-AES256-SHA384 - ECDHE-RSA-AES128-SHA256 - ECDHE-RSA-AES256-SHA - ECDHE-RSA-AES128-SHA | | | - TLS-AES-256-GCM-SHA384 - TLS-CHACHA20-POLY1305-SHA256 - TLS-AES-128-GCM-SHA256 - TLS-AES-128-CCM-8-SHA256 - TLS-AES-128-CCM-SHA256 - ECDHE-ECDSA-AES256-GCM-SHA384 - ECDHE-ECDSA-AES128-GCM-SHA256 - ECDHE-RSA-AES256-GCM-SHA384 - ECDHE-RSA-AES128-GCM-SHA256 - ECDHE-ECDSA-CHACHA20-POLY1305 - ECDHE-RSA-CHACHA20-POLY1305 - ECDHE-ECDSA-AES256-SHA384 - ECDHE-ECDSA-AES128-SHA256 - ECDHE-RSA-AES256-SHA384 - ECDHE-RSA-AES128-SHA256 - ECDHE-RSA-AES256-SHA - ECDHE-RSA-AES128-SHA - AES256-GCM-SHA384 - AES128-GCM-SHA256 - AES256-SHA256 - AES128-SHA256 - AES256-SHA - AES128-SHA |