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


---

# Recurring Key Exchange walkthrough

# Recurring Key Exchange walkthrough {#ariaid-title1}

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

Use this walkthrough to set up a recurring key exchange in your instance using and Resource Exchange.

## Vorbereitungen

Roles required: sn_kmf.cryptographic_manager

## Warum und wann dieser Vorgang ausgeführt wird

This example shows you how a target instance requests keys from a host instance.

* Before you can perform this procedure, you must clone an instance. See System clone for more information.
* Automatic Key Exchange: The base system property glide_encryption.auto_key_exchange.enabled is true by default, meaning that automatic is activated when cloning an instance. The property is cloned over to the target instance.
* Turn off automatic by setting the property to false.
{#key-exchange-walkthrough__ul_cxc_c1c_bqb}

## Prozedur

1. On the source instance, create a crypto module or access an existing crypto module using column_level_encryption and set up the encrypted field configurations for the ciphertext encryption for Key Exchange.  
   See and for details.
   1. Ensure that keys have been generated in the crypto module.

   Hinweis:  
   Your instance automatically creates a module access policy on the execution of the clone request.
2. From the cloned instance, navigate to Key ManagementResource Exchange RequestsNew.
3. Complete the form and select Recurring Clone as the Exchange Frequency.
4. From the target instance of the clone, navigate to Key ManagementResource Exchange Requests.  
   The request from the host instance is displayed in the table.  
   Wichtig:  
   For both one-time and recurring clone requests, your instance creates a module access policy automatically. You don't need to configure a policy manually. At clone time, this policy on the source instance is invoked to auto-approve the request and send keys to the newly cloned target.  
   In the Requests form, the status updates to Request Approved and the Imported Key Count field appears on the record.
5. Return to the host instance.
6. View the Request record to see the number of exported keys.
7. View the Module Access Policy record to see that the Type is Resource Exchange.  
   Hinweis:  
   Resource Exchange also supports rekeying of ciphertext on the target instance. See for details.

## Ergebnisse

After a key exchange is attempted, your non-production instance updates the protected.script.values.kmf.rekeyed system property. This property is visible in the System Properties \[sys_properties\] table. If
the encryption using the exchanged key is successful, this property has a value of true. Otherwise, the property has a value of false. If the value is false, your instance will
attempt to encrypt again the next day.