| Module name |
Displays the module name prepended with the application scope name to avoid conflict with other scoped applications. For example, if you create a module with the name my_crypto_module in the global
application scope, the name is saved as global.my_crypto_module. Choose a name for the module. This name is referenced when running scripts. |
| Module lifecycle state |
The term “lifecycle” refers to the creation, use, and deactivation of a cryptographic module. Set this value to Draft initially during configuration. Set it to
Published for active use.Note: The default template is automatically set to Published. |
| Application scope |
The application scope for this module. This field is automatically populated with the current application. |
| Cryptographic 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/Data. |
| Crypto Spec Template |
Automatically populated with Default template. This template is used to create the cryptographic module that contains mappings of many cryptographic purposes to cryptographic
specifications and recommended algorithms. |
| Algorithm |
Defines which encryption scheme will be used to encrypt fields associated with the module. |