Define policy reason mapping

task australia Updated Sep 10, 2026 1 min read define-policy-reason-mapping.md

You can define the reason choices to be available to any user who requests an exception.

Before you begin

You must have the GRC: Policy and Compliance Management application installed. This application is available from the ServiceNow® Store with a separate subscription.

For details on system requirements and family compatibility, view the application listing on the ServiceNow Store website.

Role required: sn_vul.compliance.manager and sn_vul.vulnerability_admin

Procedure

Navigate to All > Policy and Compliance > Policy Exceptions > Integration Registry.

Note: You can either select a reason from the reason choices available in the Reason Choices table or add a new reason.
Click the integration registry for your application, for example, Application Vulnerability Response, Vulnerability Response, and so on.
To add an existing reason choice, perform the following steps:
1. In the Reason Choices list, click New.
2. Click the magnifying glass icon to select a reason.
To add new reason choices to the Reason Choices table, perform the following steps:
1. In the Reason Choices list, click New.
2. Click the magnifying glass icon.
3. Click New.
4. On the form, fill in the fields.

Field	Description
Label	Unique label for this choice.
Value	Unique value for this choice. This value is mapped in the Policy Exception Reason Mappings table for the respective applications. To navigate to this table, enter sn_vul_policy_reason_mapping.LIST in the filter navigator.
Order	Order for this choice. Reasons are ordered based on this number.
Default	Option to indicate that this reason choice will be available whenever an on demand policy exception is requested. If the integration registry doesn’t contain any application-specific choices, then all reason choices that have the Default field selected will be available.
Active	Option to display the choice in the list of reason choices.

5. Click **Submit**.

Parent Topic:Requesting and approving an exception in Application Vulnerability Response

107 lines · 3.4 KB Wrap lines

---
title: Define policy reason mapping
description: You can define the reason choices to be available to any user who requests an exception.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/security-management/application-vulnerability-response/define-policy-reason-mapping.html
release: australia
product: Application Vulnerability Response
classification: application-vulnerability-response
topic_type: task
last_updated: "2026-09-10"
reading_time_minutes: 1
breadcrumb: [Requesting and approving an exception in Application Vulnerability Response, Exception Management in Application Vulnerability Response, Configure Application Vulnerability Response, Configure, Application Vulnerability Response, Unified Security Exposure Management, Security Operations]
---

# Define policy reason mapping

You can define the reason choices to be available to any user who requests an exception.

## Before you begin

You must have the GRC: Policy and Compliance Management application installed. This application is available from the ServiceNow® Store with a separate subscription.

For details on system requirements and family compatibility, view the application listing on the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website.

Role required: sn\_vul.compliance.manager and sn\_vul.vulnerability\_admin

## Procedure

1.  Navigate to **All** &gt; **Policy and Compliance** &gt; **Policy Exceptions** &gt; **Integration Registry**.

    **Note:** You can either select a reason from the reason choices available in the Reason Choices table or add a new reason.

2.  Click the integration registry for your application, for example, **Application Vulnerability Response**, **Vulnerability Response**, and so on.

3.  To add an existing reason choice, perform the following steps:

    1.  In the Reason Choices list, click **New**.

    2.  Click the magnifying glass icon to select a reason.

4.  To add new reason choices to the Reason Choices table, perform the following steps:

    1.  In the Reason Choices list, click **New**.

    2.  Click the magnifying glass icon.

    3.  Click **New**.

    4.  On the form, fill in the fields.

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

Field

</th><th>

Description

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

Label

</td><td>

Unique label for this choice.

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

Value

</td><td>

Unique value for this choice.

 This value is mapped in the Policy Exception Reason Mappings table for the respective applications. To navigate to this table, enter sn\_vul\_policy\_reason\_mapping.LIST in the filter navigator.

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

Order

</td><td>

Order for this choice. Reasons are ordered based on this number.

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

Default

</td><td>

Option to indicate that this reason choice will be available whenever an on demand policy exception is requested. If the integration registry doesn’t contain any application-specific choices, then all reason choices that have the **Default** field selected will be available.

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

Active

</td><td>

Option to display the choice in the list of reason choices.

</td></tr></tbody>
</table>5.  Click **Submit**.


**Parent Topic:**[Requesting and approving an exception in Application Vulnerability Response](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/application-vulnerability-response/avr-request-approve-exception.md)