---
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 a cryptographic specification

# Create a cryptographic specification {#ariaid-title1}

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

After you create a cryptographic module, create a cryptographic specification to
define the module algorithms.

## Vorbereitungen

Role required: sn_kmf.cryptographic_manager

## Prozedur

1. Navigate to Key ManagementCryptographic ModulesAll.
2. Select the cryptographic module for definition to open the configuration options.
3. On the Crypto Specifications tab, select New.  
4. Complete the Algorithm Definition form.  
   See [Cryptographic specification overview](https://servicenow-prod.fluidtopics.net/9DHKEp9EL2VYGfVuKxn5xQ "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.  

   The algorithm definition screen opens. Select options for the key generation. Repeat this step to generate multiple keys for the selected crypto module.  
   {#create-crypto-spec__table_bbk_5v4_kqb__entry__2}

   | Field |   |
   |-|-|
   | Crypto module | Read only. Name of the selected cryptographic module displays. |
   | Crypto purpose | Select the purpose of this module. For example, you might use it for data encryption, signature generation, or key wrapping. The available algorithms adjust based on the selected crypto purpose. See [Cryptographic specification overview](https://servicenow-prod.fluidtopics.net/9DHKEp9EL2VYGfVuKxn5xQ "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. |
   | Algorithm | Type of algorithm used to accomplish the crypto purpose. The algorithm also controls the key origin. Adjusts automatically based on the selected crypto purpose. [Cryptographic specification overview](https://servicenow-prod.fluidtopics.net/9DHKEp9EL2VYGfVuKxn5xQ "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. |
   | Operation mode | This field may display based on the selected crypto purpose. |
   | Size | Select the bit size. |
   | Hash | This field becomes available based on the algorithm selected. |
   | Equality preserving | Enables non-deterministic encryption. This option appears when you select Symmetric Data Encryption/Decryption with AES and in Cipher Block Chaining (CBC) mode. Selecting this option means that if the same data is encrypted again the encoded data is the same each time. Non-deterministic encryption doesn't support filtering a list of encrypted data using equality comparison operators. |
   | Integrity | GCM operation mode provides Integrity. |
   [Tabelle : 1. Algorithm Definition fields]

   {#create-crypto-spec__table_bbk_5v4_kqb}
5. Select Next.  
   The crypto specification is listed on the Key Lifecycle table based on the algorithms selected.

## Nächste Maßnahme

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://servicenow-prod.fluidtopics.net/NVIDPtYNGu5nP4Wd3oW4Tw "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://servicenow-prod.fluidtopics.net/24qBq00hyoT4pc0kGA7nTw "Follow this procedure to upload and configure a ServiceNow cryptographic key to encrypt sensitive data.").
  * [Configure properties for customer-supplied keys](https://servicenow-prod.fluidtopics.net/Wg7gwmbhwjqas7ygpSOHmQ "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://servicenow-prod.fluidtopics.net/LJgZg8VNdUMfFPJrzbTVog#import-key-webservice "Configure Key Management Framework import settings before importing a key.").
  {#create-crypto-spec__ul_s4y_kqx_kqb}
{#create-crypto-spec__ul_r4y_kqx_kqb}