---
sourceDocument: Australia Platform security
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/platform-security

 Release :

    - australia

ft:locale :

    - en-US

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}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Configure your field encryption settings to use ServiceNow supplied keys or your own customer-supplied keys (CSK) for encryption on the ServiceNow AI Platform.

## Before you begin

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

Role required: sn_kmf.cryptographic_manager and security_admin

## Procedure

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

## What to do next

* If you're using your own customer-supplied keys, see [Using customer-supplied keys with Field Encryption Enterprise](https://www.servicenow.com/docs/mZTLLn26xFPdxTVnntck6A "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://www.servicenow.com/docs/c2M~jmt1xxwHi5RBTn8xXQ "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}

*[\>]: and then