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


---

# Configure field encryption settings to select key type

# Configure field encryption settings to select key type {#ariaid-title1}

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

Configure your field encryption settings to use ServiceNow supplied keys or your own customer-supplied keys (CSK) for encryption on the ServiceNow AI Platform.

## Vorbereitungen

Customer-supplied keys are only supported with Field Encryption Enterprise.

Role required: sn_kmf.cryptographic_manager and security_admin

## Prozedur

1. Navigate to AllSystem SecurityField Encryption Settings.
2. From the Field Encryption Settings, select either ServiceNow Generated Keys or Customer Supplied Keys from the Key Source list.  
   Abbildung : 1. Key source selection  
   This option changes the
   `com.glide.encryption.cle_kmf.key_source` property to
   either ServiceNow Generated Keys or
   Customer Supplied Keys.
3. Select Save.

## Nächste Maßnahme

* If you're using your own customer-supplied keys, see [Using customer-supplied keys with Field Encryption Enterprise](https://servicenow-prod.fluidtopics.net/SsfTkqJbTuooJebc15p4Zg "You can use your own customer-supplied key instead of using the ServiceNow system-generated keys.").
* If you're using ServiceNow supplied keys, start creating your cryptographic module. See [Create a cryptographic module](https://servicenow-prod.fluidtopics.net/Jy8yosmnoD7W9psp60zV_A "Create a cryptographic module to define the mechanisms used for cryptographic operations. After you create the module, you create a cryptographic specification, where you define an algorithm for encryption and generates a key.").
{#configure-field-encryption-settings__ul_n4d_hqw_b4b}