---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Enable Certificate Validation

# Turn on certificate validation {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Protect your instance with certificate based validation.

## Vorbereitungen

Role required:

* codesigning_admin
* security_admin
* sn_kmf.cryptographic_manager
{#cse-turn-on-cert-validation__ul_u2w_ztt_pbc}

## Prozedur

1. On your trusted instance, navigate to AllCode SigningConfigurationGuided Setup to open the Code Signing configuration page.
2. In the Instance type field, select trusted instance.
3. Select the Next button.
4. In the Action field under Select the action you'd like to accomplish, select Turn on Cert Validation.
5. Select the Next button.
6. Next to Attachments in the Customer signing key pair and certificate section select +Add File to upload a cryptographic key pair (p12 file extension) to use for customer signing.  
   Tipp:  
   If the +Add File option is not available, verify that you are in the Global scope, and that you have the sn_kmf.cryptographic_manager role.
7. In the Password field, enter the password for the uploaded key pair.
8. Select Import.
9. Select Continue to move to the next section.
10. Next to Attachments in the COT administration key pair and certificate section select +Add File to upload a cryptographic key pair (p12 file extension) to use for customer signing.
11. In the Password field, enter the password for the uploaded key pair.
12. Select Import.
13. Select Continue to move to the next section.
14. In the Perform trusted instance tasks section, wait for all tasks to be completed.  
    Your instance generates and executes these tasks automatically. If you used
    Code Signing prior to the Vancouver release, tasks are
    created and executed to update your signatures.

    In some cases, no tasks are needed. No tasks needed
    displays on this page.
15. Select Continue to move to the next section.
16. On the Export Configuration file page, select Export to create and download a configuration file used to turn on Code Signing on your protected instance.  
    The export process downloads an XML file to your local machine for use in the steps detailed in [Configure Code Signing Enterprise on your protected instance](https://servicenow-prod.fluidtopics.net/yskylTZibHsVPIFJNIHMlg "Turn on and configure Code Signing on your protected instance.").
17. On your protected instance, navigate to AllSystem Update SetsRetrieved Update Sets.
18. Select Import Update Set from XML at the bottom of the Retrieved Update Sets list.
19. Select Choose File, and select your configuration file (xml file extension).
20. Select Upload.
21. Return to the code signing configuration page at AllCode SigningCode Signing Configuration.
22. Use the wizard to complete your configuration, selecting the options for completing certificate validation activation.