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


---

# Trusted Instance Setup

# Configure Code Signing Enterprise on your trusted instance {#ariaid-title1}

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

Turn on and configure Code Signing on your trusted instance.

## Vorbereitungen

Roles required:

* admin
* security_admin
* codesigning_admin  
  Hinweis:  
  The codesigning_admin role can be assigned using the process detailed in [Assign the Code Signing Administrator Role](https://servicenow-prod.fluidtopics.net/UvJWRFiZoD6UpHEgeQqEkg "Assign the Code Signing Administrator role to a user to access the Code Signing configuration experience.").
* sn_kmf.cryptographic_manager
{#cse-turn-on-cse__ul_ivn_mf1_jbc}

You must have at least one cryptographic key pair and certificate (p12 file extension) for customer signing and Circle of Trust (COT) administration. For improved security, consider using separate cryptographic key pairs for
customer signing and COT administration.  
Warnung:  
After completing this process, you will have downloaded a configuration file that must be installed on your protected instance within an hour. Verify that you have time available after this process to upload the configuration file to your protected instance. For details on that process, see [Upload your Code Signing configuration file to your protected instance](https://servicenow-prod.fluidtopics.net/o60PLWkAF~SWQwPD_kbvJA "Upload the configuration file generated on your trusted instance.").

## 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 Code Signing.
5. 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.
6. In the Password field, enter the password for the uploaded key pair.
7. Select Import.
8. Select Continue to move to the next section.
9. 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.
10. In the Password field, enter the password for the uploaded key pair.
11. Select Import.
12. Select Continue to move to the next section.
13. 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 details 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.").  
    Hinweis:  
    Code Signing enforces limits on large update sets to improve the user experience. The maximum size for an update set is 10,000 records.