---
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 secret group cryptographic module

# Create a secret group cryptographic module {#ariaid-title1}

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

Create a secret group cryptographic module to perform encryption and decryption.

## Vorbereitungen

Role required:

* admin
* sn_secrets.admin
* sn_secrets.secret_manager
* sn_kmf.cryptographic_manager
* sn_kmf.admin
{#create-sm-crypto-module__ul_xsg_pmm_ltb}

## Prozedur

1. Navigate to AllSecrets ManagementCreate Secret Group Crypto Module.
2. Select the type of group crypto module would you like to create.  
   {#create-sm-crypto-module__table_bp3_wmm_ltb__entry__2}

   | Cryptographic module type | Description |
   |-|-|
   | Create an instance accessible secret crypto module | Create instance accessible secrets that can be decrypted by your instance. |
   | Createn a client accessible secret crypto module | Create client accessible secrets that are encrypted using your own key, which ServiceNow can't access. |
   [ ]

   {#create-sm-crypto-module__table_bp3_wmm_ltb}
3. In the Cryptographic Module form, fill in the fields.  
   {#create-sm-crypto-module__table_hrr_lnm_ltb__entry__2}

   | Field | Description |
   |-|-|
   | Module name | Descriptive name for your module |
   | Application | The application scope that contains your module. This field is automatically populated with the current module. |
   | Crypto spec template | Default Template is selected by default. |
   | Name | Name of the module. This name is automatically generated by based on the application and module name. |
   | Default module access policy value | * Rely on system default * Reject * Track {#create-sm-crypto-module__ul_igv_xnm_ltb} |
   | Crypto module lifecycle state | Whether the module is in a Draft or Published state. |
   | Actual module access policy result | This field is for information purposes, and is read-only. |
   | Parent crypto module | The parent cryptographic module, which is determined by the cryptographic module type you selected in the previous step. This field is read-only. |
   [ ]

   {#create-sm-crypto-module__table_hrr_lnm_ltb}
4. Select Submit.