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


---

# Turn on Code Signing

# Turn on Code Signing {#ariaid-title1}

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

Turn on Code Signing in your trusted non-production instance to identify the trusted instances linking to your production instance.

## Vorbereitungen

Roles required: security_admin, and either sn_kmf.crypto_manager or sn_kmf.admin

As a customer administrator, you can access and install the Code Signing \[com.glide.code_signing_enterprise\] plugin from the ServiceNow Plugin portal. To learn more about the use cases of Code Signing, see [Exploring Code Signing](https://servicenow-prod.fluidtopics.net/uJZNKinevD7L_0wL3Wck3g "Code Signing provides cryptographic verification to ensure that only authorized scripts can execute on MID Servers. Code Signing prevents unauthorized or tampered External Communication Channel(ECC) queue records from being processed by MID Servers, maintaining the integrity of integrations between ServiceNow and external systems.").

## Warum und wann dieser Vorgang ausgeführt wird

Code Signing jobs with signed update sets are used to turn the Code Signing feature on or off. There's no other method for this functionality. This process includes the following:

* Create two Code Signing jobs in the trusted instance, one to turn on Code Signing and one to turn off Code Signing.
  * The Turn On scheduled job starts the process of MID Server validation of signed code.
  * The Turn Off scheduled job stops the MID Server validation of signed code.

  {#enable-codesiging__ul_zwm_nx1_fwb}

  By default, Code Signing applies to all MID servers. However, if you need to
  restrict Code Signing to a specific subset of MID servers, you can achieve this by
  using the ECC firewall.  
  Hinweis:  
  When turning off Code Signing, the system property is marked to false, but the Code Signing trusted friends list is still available.
* Put the Turn on Code Signing Property job into an update set.
* Bring the job into production.
* Use the Turn on Code Signing Property job in production if the signature is verified to originate from a trusted instance.
{#enable-codesiging__ul_npk_3my_spb}

## Prozedur

1. In your trusted instance, navigate to AllSystem DefinitionScheduled Jobs.
2. Search for "\*Turn" in the name field.
3. Select Turn on Code Signing Property.  
   The Scheduled Script Execution form load. This form contains information to enable the Code Signing property. The jobs create update sets that contain the jobs and validated signatures through the Code Signing process.  
4. To execute the script immediately, sign the certificate, create the update set, and select Export signed job to production.  
   You can also configure the script to run on a designated schedule.
5. Navigate to System Update SetsLocal Update Sets.
6. Open each of the Code Signing property update sets and select Export to XML.
7. Log in to the production instance.
8. Navigate to System Update SetsRetrieved Update Sets.
9. Select the Import Update Set from XML button, and select the Code Signing property update set.
10. Select Choose File and upload and commit the update sets.
11. Return to the scheduled jobs list by navigating to AllSystem DefinitionScheduled Jobs.
12. Open the Turn on Code Signing Property job record.
13. Select the Prerequisite Check button at the top of the form.  
14. Select the Execute Now button after the prerequisite check is complete.  
    The Turn on Code Signing Property scheduled job starts the process of MID Server validation of signed code.
15. In the navigator, enter <kbd class="ph userinput">sn_kmf_record_signature.list</kbd> to open the KMF Signature Records list, and filter for records where the KMF Signature Purpose is <kbd class="ph userinput">Circle of Trust</kbd>.  
    The trust relationship has moved the jobs over and when the jobs are used the signature verification process executes. If the jobs, signatures, and certificates are all part of the Circle of Trust, then Code Signing with Circle of Trust can be turned on.
16. In the navigator, enter <kbd class="ph userinput">sys_properties.list</kbd> to open the system properties list.
17. Search for com_snc_kmf_signature.validation.flag and ensure that the value is set to true.
18. Verify that a new property com_snc_kmf_signature.validation.certificate is listed in the table.  
    Abbildung : 1. System Properties

    Use the Circle of Trust job in production to verify the trust relationship. No direct job can be executed in production that attempts to sign code. See [Configuring Code Signing](https://servicenow-prod.fluidtopics.net/bar5xF5UMDW_5By9WiBx3Q "Activate and configure Code Signing to verify the authenticity and integrity of your data.") for details on configuration options.