---
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 advanced algorithms for Column Level Encryption Enterprise

# Configure advanced algorithms for Column Level Encryption Enterprise {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Create a cryptographic specification to define the algorithm for a cryptographic module. Customize the encryption specifications with advanced options that are available for Column Level Encryption Enterprise.

## Before you begin

Role required: admin

## Procedure

1. On the Crypto Specifications (#) tab, click New.  
2. On the form, fill in the fields.  
   {#adv-algorithm-cleent-2__table_ff2_jwq_fqb__entry__2}

   | Field | Description |
   |-|-|
   | Crypto module | Name of the selected cryptographic module populates. |
   | Crypto purpose | The value is Symmetric Data Encryption/Decryption for Column Level Encryption Enterprise. |
   | Algorithm | The value is AES for Column Level Encryption Enterprise. |
   | Operation mode | The value is CBC for Column Level Encryption Enterprise. |
   | Size | Possible values are 256 and 128. Note: 256-bit size is most secure for encryption and is used for Symmetric Data Encryption/Decryption for Column Level Encryption Enterprise. |
   | Equality preserving | Option to enable deterministic encryption. Note: Selecting this option means that the encrypted value of a field should be the same when the field value remains the same. Option to enable Symmetric Data Encryption/Decryption with AES in Cipher Block Chaining (CBC) mode. |
   | Integrity | Option to provide Integrity in GCM operation and does not apply for Column Level Encryption Enterprise functionality. |
   [Table 1. Algorithm Definition form]

   {#adv-algorithm-cleent-2__table_ff2_jwq_fqb}
3. Click Submit.  
   The following example shows AES CBC-256 encryption. When Column Level Encryption Enterprise is active and the parent module is column_level_encryption, only Symmetric Data Encryption/Decryption AES CBC-256 applies as the crypto purpose. See [Cryptographic specification overview](https://www.servicenow.com/docs/9HlQjGW42wvB2rSuyke4lA "The Cryptographic specification is the component that defines aspects of your cryptographic module, including its cryptographic purpose and which encryption algorithm to use.") for details.  
{#adv-algorithm-cleent-2__steps_y3f_zqw_d3c}

## What to do next

Perform one of the following operations:

* Select an entry in the Key Lifecycle table to define key lifecycle behavior. See [Configure key lifecycle states](https://www.servicenow.com/docs/RZ3vt3hx4jJO8iyk~aKi0w "After you have created a cryptographic specification, you can configure the lifecycle actions for the keys in your instance.") for details to complete the lifecycle definition for the key.
* Select Next to create a cryptographic key. See one of the following tasks for key generation:
  * [Generate a ServiceNow cryptographic key](https://www.servicenow.com/docs/jv6sHp92l9QZ00uTGNMzaA "Follow this procedure to upload and configure a ServiceNow cryptographic key to encrypt sensitive data.").
  * [Configure properties for customer-supplied keys](https://www.servicenow.com/docs/gg2qe_D6YQ9IoxRQBKd93g "If the Field Encryption Enterprise plugin is enabled, you can use system properties to define key padding, ephemeral key pair size, and a key validity period of your customer-supplied keys.").
  * [Import the wrapping / unwrapping key pair](https://www.servicenow.com/docs/ExYjM2ykgQrD_rECvOmHHA#import-key-webservice "Configure Key Management Framework import settings before importing a key.").
  {#adv-algorithm-cleent-2__ul_sjf_4rw_kqb}
{#adv-algorithm-cleent-2__ul_yjj_crw_kqb}