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


---

# Create cryptographic module for Column Level Encryption

# Create cryptographic module for Column Level Encryption {#ariaid-title1}

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

Create a Field Encryption cryptographic module to define the mechanisms used for cryptographic operations.

## Vorbereitungen

Role required: sn_kmf.cryptographic_manager or sn_kmf_admin, security_admin, admin

## Warum und wann dieser Vorgang ausgeführt wird

This procedure describes options that are available with Column Level Encryption with the base system and additional configuration options that become available with Column Level Encryption Enterprise functionality. Column Level Encryption Enterprise is available with a paid subscription. Refer to [Encryption and Key Management subscription bundle](https://servicenow-prod.fluidtopics.net/1ecP56AMSSFdlBEyW4Jngg "With Key Management, Field Encryption is upgraded at no additional charge to include highly configurable encryption modules. You can also optionally upgrade to the unlimited-use license. Subscribe to the new encryption entitlement bundle, Platform Encryption, which includes Field Encryption Enterprise and Cloud Encryption.") for supported features and options available with each offering. See [Activate Column Level Encryption Enterprise](https://servicenow-prod.fluidtopics.net/bd5xKPL4HnumiOslxPYuVw "With subscription to Column Level Encryption Enterprise, an admin can activate the com.glide.now.platform.encryption plugin.") for more information on obtaining Column Level Encryption Enterprise.

## Prozedur

1. Navigate to AllSystem SecurityField Encryption ModulesNew.  
2. On the form, fill in the fields.  
   {#create-PE-cryptographic-module-2__table_rwf_tpw_d3c__entry__2}

   | Field | Description |
   |-|-|
   | Module name | Alphanumeric string to be referenced when running scripts. |
   | Crypto spec template | Default template used to create the cryptographic module that contains mappings of many crypto purposes to crypto specifications and recommended algorithms. |
   | Application | The selected application scope. |
   | Name | Encryption module name is prepended with application scope name to avoid conflict with other scoped applications on module creation. For example, if you created a module with the name <kbd class="ph userinput">my_crypto_module</kbd> in the global application scope, the name is saved as <kbd class="ph userinput">global.my_crypto_module</kbd>. |
   | Crypto module lifecycle state | The term lifecycle refers to the creation, use, and deactivation of a cryptographic module. Set to Draft initially during configuration. When using the module, set to Published. The Default template is automatically set to Published. |
   | Parent crypto module | The parent is populated automatically as column_level_encryption. |
   [Tabelle : 1. Cryptographic Module form]

   {#create-PE-cryptographic-module-2__table_rwf_tpw_d3c}
3. Click Submit.  
   After submitting successfully, your cryptographic module is listed in the Cryptographic Modules table.  
   Warnung:  

   For legacy encryption support users:
   :   If you're using the non-enterprise version of Column Level Encryption, you're limited to five fields. If you've exceeded this limit, you receive the following warning:
   : This insertion exceeds the number of published fields limit for Column Level Encryption  entitled with the Subscription Product. The Enterprise subscription for Column Level Encryption is required for additional fields. Please reach out to your Account team.  
   A default cryptographic specification is created with the crypto purpose set to Symmetric Data Encryption/Decryption and the algorithm as AES 256 CBC. Select the algorithm for updates.
4. To open the configuration options, click the newly created cryptographic module.  
   Hinweis:  
   A maximum of five Column Level Encryption fields are allowed before upgrading to Column Level Encryption Enterprise. An error message displays and you are prevented from adding additional cryptographic modules.
{#create-PE-cryptographic-module-2__steps_qwf_tpw_d3c}

## Nächste Maßnahme

[Create a cryptographic specification for Column Level Encryption](https://servicenow-prod.fluidtopics.net/7hMGg6QJoweggtnNInbXuw "After you create a cryptographic module, access the corresponding cryptographic specification to define the algorithm.").