--- title: Set up Module Access Policies description: Configure module access policies in External Key Management Service \(EKMS\) to control who can view encrypted data in clear text. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/platform-security/ekms-set-up-maps.html release: australia topic_type: task last_updated: "2026-04-02" reading_time_minutes: 2 breadcrumb: [Configuring External Key Management Service, External Key Management Service, Field Encryption, Encryption] --- # Set up Module Access Policies Configure module access policies in External Key Management Service \(EKMS\) to control who can view encrypted data in clear text. ## Before you begin Role required: sn\_kmf.admin or sn\_kmf.cryptographic\_manager Confirm that you have: - [Created a cryptographic module with external key wrapping enabled](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/ekms-configure-external-key-definition.md) - [Created an Encrypted Field Configuration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/ekms-create-encrypted-field-config.md) ## Procedure 1. Navigate to **All** > **System Security** > **Field Encryption** > **Field Encryption Experience** > **Configurations** > **Access Policies**. **Note:** For additional information, refer to [Configure module access policies for Field Encryption](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/platform-encryption/create-module-access-policy.md). 2. Select **Create New**. 3. Select **Configure**. 4. Complete the Module Access Policy \(MAP\) form.
Field Description
Policy name Enter a name for the policy.
Type Decide who or what should have access to this MAP to encrypt or decrypt data.- Scope- Anything within the specified Application Scope has access to this MAP. - Role- Only users with the specific role can access this MAP. - Script- Ensure a specified script can access this MAP. - System Access- Allows processes running in “System Context” access to this MAP. - Resource Exchange- Allows for the Resource Exchange feature access to this MAP. For more information on how these different types of MAP work, see [Exploring Field Encryption](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/exploring-fe.md).
Target scope Field is visible as an identifier for the Scope type. Refers to the functionality of the policy. Select the applications from the search menu.
Specify purpose Optional.  Enable  to  display  the  Crypto  Spec  field  on  the  form.  Enable this option to configure granular operations, such as some users being able to encrypt, but not decrypt. 
Application The  Application scope  is  auto-populated  by  your  current scope. 
Active Select to activate the policy.
Result Select one of the following:- **StrictReject** rejects access under all circumstances. - **Reject** rejects users with the **Target Role** or **Target Scope** from accessing this cryptographic module unless another policy grants them access. - **Track** to permit access and monitor use of the module.
\[Omitted image "ekms-create-map-track-ui.png"\] Alt text: Example of completed MAP form. ## Result The Module Access Policy for the script is available in the system. Next steps: - [Test an external key definition](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/ekms-test-external-key-definition.md) - [Learn how to change the status of an AWS KMS Key](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/ekms-change-status-aws-kms-key.md) **Parent Topic:**[Configuring External Key Management Service](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/ekms-configuring-external-key-management.md)