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


---

# Cryptographic specifications for Field Encryption

# Cryptographic specifications for Field Encryption {#ariaid-title1}

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

Use cryptographic specifications to define the purpose, algorithm, key length, mode, and origin of your encryption key.

## Vorbereitungen

Role required: security_admin and sn_kmf.cryptographic_manager or sn_kmf.admin

## Warum und wann dieser Vorgang ausgeführt wird

This procedure shows how to configure generated keys. A data encryption key (known as a Module Key) is automatically populated once you have configured the Crypto Specifications.

For customer-supplied key configuration, see [Configure Customer-supplied keys for Field Encryption Enterprise](https://servicenow-prod.fluidtopics.net/GY0Ufu_m8ZsV2CFOha7sJQ "Bring your own data encryption key to the platform instead of using the one that ServiceNow generates.").

## Prozedur

1. Navigate to AllSystem SecurityField EncryptionField Encryption Experience.
2. Select View module details from the Field Encryption modules overview to open the module record you want to configure.  
   Hinweis:  
   The names displayed in the list are appended with the scope, for example, <kbd class="ph userinput">global.[your Field Encryption Module name]</kbd>.
3. In the Cryptographic Specifications section, select Manage Specification Settings.  
4. In the Crypto Specifications form, fill out the fields as needed.  
   Hinweis:  
   The fields are divided into sections. Select the Next or Back buttons to navigate between sections.
   {#configure-fe-crypto-specs__table_xfy_lsd_f2c__entry__3}

   | Section | Field | Description |
   |-|-|-|
   | Algorithm Definition | Crypto module | Displays the name of the selected cryptographic module. |
   | Algorithm Definition | Crypto purpose | The purpose of the selected algorithm, key, length, and mode. For Field Encryption, this field is read only and has a value of Symmetric Data Encryption/Decryption. |
   | Algorithm Definition | Algorithm | Select a type of algorithm used to accomplish the cryptographic purpose. The options available are filtered to align to the selected cryptographic purpose. |
   | Lifecycle Definition | Applies to | Displays the selected key that the lifecycle applies to. |
   | Lifecycle Definition | For field | Select the type of control for the key that you want to apply for the lifecycle. * Expiration date * Future activation date * Future destruction date * Future renewal date * Future rotation date {#configure-fe-crypto-specs__ul_a4t_dwd_f2c} |
   | Lifecycle Definition | Key type |   |
   | Lifecycle Definition | Lifecycle default |   |
   | Lifecycle Definition | Order | Order in which to process the key lifecycle state for the crypto specification. Lower values execute before higher values. |
   | Lifecycle Definition | Relative duration | Number of years, months, or days the key is valid. |
   | Lifecycle Definition | Relative duration type | Duration type of the lifecycle. Select from Years, Months, or Days. |
   | Lifecycle Definition | Relative operation | Choose Before or After. |
   | Lifecycle Definition | Relative to | Select a field that the duration is relative to. * Activation date * Compromise date * Deactivation date * Destruction date * Expiration date * Generation date * Last renewal date * Last rotated date * Revocation date {#configure-fe-crypto-specs__ul_w4v_sxd_f2c} Hinweis: This field works together with the value selected in the Relative operation field. |
   | Lifecycle Definition | Type | Select if the value for the key lifecycle is relative or absolute. Relative :   Enter a value that depends on other data entries in the system, such as key generation, activation, and deactivation. Absolute :   Enter an exact value, such as a date. |
   | Key Origin | Crypto module | Displays the Name of the selected cryptographic module. |
   | Key Origin | Origin | Whether the key originated from or is supplied by the customer. * For starter, select Servicenow * For Enterprise, select Servicenow or Customer Supplied {#configure-fe-crypto-specs__ul_k1c_fyd_f2c} |
   | Key Origin | Key alias | Name of the cryptographic module with the scope appended to the front of the name. |
   | Key Origin | Crypto purpose | Displays the purpose of the selected algorithm, key, length, and mode. For Field Encryption, this field is read only and has a value of Symmetric Data Encryption/Decryption. |
   | Key Origin | Algorithm | Displays the algorithm used to accomplish the crypto purpose. |
   | Key Creation | Crypto module | Displays the name of the selected cryptographic module. |
   | Key Creation | Key alias | Displays the name of the cryptographic module with the scope appended to the front of the name. |
   | Key Creation | Generate Key | Select this link to generate your data encryption key if you're using a generated key, and not a customer supplied key. |
   | Key Creation | Auto generate key | If you don't select the Generate key link, a data encryption key is automatically generated during the first time data must be encrypted using the cryptographic module. |
   | Key Creation | Crypto purpose | Displays the purpose of the selected algorithm, key, length, and mode. For Field Encryption, this field is read only and has a value of Symmetric Data Encryption/Decryption. |
   | Key Creation | Origin | Displays the value that was selected during the Key Origin section. |
   | Key Creation | Algorithm | Displays the algorithm used to accomplish the crypto purpose. |
   [ ]

   {#configure-fe-crypto-specs__table_xfy_lsd_f2c}
5. Select Go To Crypto Module to return to your Module record.  
   In the Module record, there's now an entry in the Module Keys related list. The Key alias field in the Crypto Specifications related list is now empty, since the key alias has moved to the new module key.

## Nächste Maßnahme

For information on using a customer supplied key, see [Configure Customer-supplied keys for Field Encryption Enterprise](https://servicenow-prod.fluidtopics.net/GY0Ufu_m8ZsV2CFOha7sJQ "Bring your own data encryption key to the platform instead of using the one that ServiceNow generates.").