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


---

# Module access policy debugger

# Module access policy debugger {#ariaid-title1}

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

Use the module access policy debugger to review logging information and understand why your users are or aren't granted access to an encryption context.
Module access policies (MAPs) define instance-level controls for access to cryptographic modules. Callers (for example, a user or script) require explicit access to use a cryptographic module for encryption
and decryption. Use the debugger to see which policies are evaluated when a caller attempts to access a cryptographic module. You can also use the debugger and learn why access is or isn't being granted.

This flowchart shows
how your instance evaluates requests for access to a cryptographic module.

## Control access to the debug logs {#map-debugger__section_vxd_1cp_qxb}

Access to the module access debug logs is determined by role. Users with the sn_kmf.admin and sn_kmf.cryptographic_manager roles have access to the debugger. Grant access to other roles using
the glide.kmf.module_access_policies.debugger.authorized.roles system property. The value of this property is a comma-separated list of roles that access the debug logs.

## Enable or disable the debugger {#map-debugger__section_r2w_bcp_qxb}

To enable debug logging messages for module access policies, navigate to AllDiagnosticsSession DebugDebug Module Access Policies.

When you're finished debugging, you can disable the logging messages by navigating to AllDiagnosticsSession DebugDisable All.

## Access the logs {#map-debugger__section_mts_ccp_qxb}

After enabling debugging, navigate to a page that triggers a MAP evaluation to view the MAP debug logs. Debug messages appear at the bottom of the page.  
Tipp:  
You can use impersonation to troubleshoot access for other users. For details on impersonation, see [Impersonating users](https://www.servicenow.com/docs/access?context=c_ImpersonateAUser&version=australia&pubname=australia-platform-administration&ft:locale=en-US). To view the debug logs from the perspective of another user, make sure that your module access policies with the role type have the Impersonation field set as true.

In this example, a caller invokes two access requests to the `global.fuji` cryptographic module. A symmetric encryption, which is granted, and a symmetric decryption, which was denied.

## Understanding log entries {#map-debugger__section_tvd_2cp_qxb}

Debugging information is structured using this format.

1. This first line displays the cryptographic module receiving the access request.
2. The lines between the first and last line displays the evaluated MAPs in the order that they were evaluated, and includes their name, type, target, granular operation, and result.
3. The last line displays the Policy Decision (if applicable) and the net access result for the caller (whether the caller is granted access).

{#map-debugger__ol_h44_zmp_qxb}

Each line starts with an icon that indicates its message type.
{#map-debugger__table_ixp_fd5_qxb__entry__2}

| Icon | Message type |
|-|-|
| ![Informational icon]() | Informational message |
| ![MAP grant access icon]() | Module access policy grants access |
| ![MAP deny access icon]() | Module access policy denies access |
| ![Caller grant access icon]() | Caller is granted access |
| ![Caller deny access icon]() | Caller is denied access |
| ![No MAP icon]() | No module access policy to evaluate |
[Tabelle : 1. Message icons]

{#map-debugger__table_ixp_fd5_qxb}

## Debug log examples {#map-debugger__section_kz1_bj5_qxb}

Access granted message
:

Access denied message
:

Access denied (No module access policies to evaluate
:

Access denied (insufficient privileges)
:
**Zugehörige Konzepte**   

* [Module access policy visualization](https://servicenow-prod.fluidtopics.net/N2rg64YSDVbQ8pm~npdDmA "Use module access policy visualization to view all relevant cryptographic module information on a single UI page.")
* [Encryption and Key Management subscription bundle](https://servicenow-prod.fluidtopics.net/1ecP56AMSSFdlBEyW4Jngg "With Key Management, Field Encryption is upgraded at no additional charge to include highly configurable encryption modules. You can also optionally upgrade to the unlimited-use license. Subscribe to the new encryption entitlement bundle, Platform Encryption, which includes Field Encryption Enterprise and Cloud Encryption.")  
**Zugehörige Verweise**   

* [Key Management Framework key life-cycle states](https://servicenow-prod.fluidtopics.net/v7eh_8MY0E4_eMEkF30zaw "KMF supports several cryptographic key life-cycle states through the enforcement of specific allowable actions. For example, only keys that are in the active state can be used fully for their intended cryptographic purpose. The following table provides further detail on the varying key life-cycle states.")
* [Roles installed with Key Management Framework](https://servicenow-prod.fluidtopics.net/aruIC5O_pblgIxuOxBeY2A#kmf-roles "The Key Management Framework (KMF) introduces specific roles for cryptographic module and key management-related configurations.")