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


---

# Script access for cryptographic modules

# Script access for cryptographic modules {#ariaid-title1}

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

Scripts can be run to access a cryptographic module policy for a cryptographic
purpose.

For Key Management Framework, policies can be based scripts. When an access
policy is triggered for script access, the backend script can execute the module policy actions
from the script.

Cryptographic modules can support one or more encryption purposes, such as Asymmetric Data
Decryption and Symmetric Data Decryption. Each cryptographic purpose requires the generation of
an encryption key and defined cryptographic purpose.

Consider the following when executing an encryption script request:  
* The referenced cryptographic purpose must be defined in the cryptographic module.
* An active generated key must exist for the cryptographic module.
* The Module Access Policy type must be set to script.
{#script-map__ul_owr_lb4_ynb}

## Check script version {#script-map__section_ggj_1z1_yrb}

When creating a module access policy that is set to the script type, there is an option available to validate the integrity of the script version being accessed. Only the assigned version of the script is allowed access to the encryption modules. When the Check script version check box is selected in the module access policy, anytime the script is run, the system performs a version comparison. If the script has been changed, the user is notified.Abbildung : 1. Check script version check box

## Configure script access to encrypted data {#script-map__section_t1l_sss_m3c}

Execute a script to run the cryptographic module policy for a cryptographic purpose. Specific read (decrypt/unwrap) or write (encrypt, wrap) access can be defined based on the module access policy operation granularity. See [Configure script access to encrypted data](https://servicenow-prod.fluidtopics.net/X~uqNyCaXo_Y7XkqppT~1A "Execute a script to run the cryptographic module policy for a cryptographic purpose. Specific read (decrypt/unwrap) or write (encrypt, wrap) access can be defined based on the module access policy operation granularity.").
* **[Configure script access to encrypted data](https://servicenow-prod.fluidtopics.net/X~uqNyCaXo_Y7XkqppT~1A)**   
  Execute a script to run the cryptographic module policy for a cryptographic purpose. Specific read (decrypt/unwrap) or write (encrypt, wrap) access can be defined based on the module access policy operation granularity.