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


---

# Circle of Trust

# Prepare Circle of Trust certificates {#ariaid-title1}

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

Create an update set in the trusted environment to export the trusted certificate to the production environment.

## Vorbereitungen

Roles required: admin, security_admin

## Vorbereitungen

Trusted instance

## Prozedur

1. In the trusted environment, navigate to sys_certificate.list.  
2. Open the most recently created X.509 Certificate that was generated with the type Trust Store Cert.  
   You may need to add the Created field to the list to find the most recent record. See [Personal
   lists](https://www.servicenow.com/docs/access?context=c_PersonalLists&version=australia&pubname=australia-platform-user-interface&ft:locale=en-US).
3. Select Export certificate to production.  
   A signature is created along with the certificate.
4. Navigate to System Update SetsLocal Update Sets.
5. Find and open the code signing update.  
   This update starts with the text `code_signing_key_publicsigver`.

   A new code signing update set record has been created by the previous steps. To find this record, sort the list using the Created by field and look for records with in the Name
   field.
6. View the relevant Signature Records and the X.509 Certificate.  
   The update set includes the attachment for the signature record along with the entry of the signature in the table and the certificate.  
7. Select the Export to XML related link.  
8. Retrieve the update set in production.  
   See [Retrieve an update set](https://www.servicenow.com/docs/access?context=t_RetrieveAnUpdateSet&version=australia&pubname=australia-application-development&ft:locale=en-US) for details.  
   Wichtig:  
   Repeat these steps for your second key pair. Remember that there's a key for both the cm_code_attest and cm_code_signing cryptographic modules.

