Create a secret group cryptographic module

task australia Updated Sep 10, 2026 1 min read create-sm-crypto-module.md

Raw file servicenow.com

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

Before you begin

Role required:

admin
sn_secrets.admin
sn_secrets.secret_manager
sn_kmf.cryptographic_manager
sn_kmf.admin

Procedure

Navigate to All > Secrets Management > Create Secret Group Crypto Module.

Select the type of group crypto module you would like to create.

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

In the Cryptographic Module form, fill in the fields.

[Omitted image "crypto-module-form.png"] Alt text: Cryptographic module form

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

4. Select **Submit**.

Parent Topic:Secrets Management dashboard

123 lines · 2.7 KB Wrap lines

---
title: Create a secret group cryptographic module
description: Create a secret group cryptographic module to perform encryption and decryption.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/platform-security/create-sm-crypto-module.html
release: australia
topic_type: task
last_updated: "2026-09-10"
reading_time_minutes: 1
breadcrumb: [Secrets Management dashboard, Secrets Management, Platform Security]
---

# Create a secret group cryptographic module

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

## Before you begin

Role required:

-   admin
-   sn\_secrets.admin
-   sn\_secrets.secret\_manager
-   sn\_kmf.cryptographic\_manager
-   sn\_kmf.admin

## Procedure

1.  Navigate to **All** &gt; **Secrets Management** &gt; **Create Secret Group Crypto Module**.

2.  Select the type of group crypto module you would like to create.

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

3.  In the **Cryptographic Module** form, fill in the fields.

    \[Omitted image "crypto-module-form.png"\] Alt text: Cryptographic module form

<table id="table_hrr_lnm_ltb"><thead><tr><th>

Field

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Module name

</td><td>

Descriptive name for your module

</td></tr><tr><td>

Application

</td><td>

The application scope that contains your module. This field is automatically populated with the current module.

</td></tr><tr><td>

Crypto spec template

</td><td>

**Default Template** is selected by default.

</td></tr><tr><td>

Name

</td><td>

Name of the module. This name is automatically generated by based on the application and module name.

</td></tr><tr><td>

Default module access policy value

</td><td>

-   Rely on system default
-   Reject
-   Track


</td></tr><tr><td>

Crypto module lifecycle state

</td><td>

Whether the module is in a **Draft** or **Published** state.

</td></tr><tr><td>

Actual module access policy result

</td><td>

This field is for information purposes, and is read-only.

</td></tr><tr><td>

Parent crypto module

</td><td>

The parent cryptographic module, which is determined by the cryptographic module type you selected in the previous step. This field is read-only.

</td></tr></tbody>
</table>4.  Select **Submit**.


**Parent Topic:**[Secrets Management dashboard](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/secrets-dashboard.md)