Define a policy reason mapping

task brazil Updated Sep 10, 2026 1 min read define-policy-exception-reason-choices.md

Raw file servicenow.com

Define reason choices to be available to any user who requests an exception.

Before you begin

Role required: sn_vul.compliance.manager and sn_vul_container.manage_exception_configuration

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 Container Vulnerability Response - CVIT integration registry.
In the Reason Choices list, click New.
Click the magnifying glass icon.

Add an existing reason choice to create a new one.

If you want to add an existing reason choice, then select a reason.

If you want to add new reason choice to the Reason Choices table, then click New and fill in the fields on the form.

Field	Description
Label	Unique label for this choice.
Value	Unique value for this choice. This value is mapped in the Policy Reason Mapping 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.

Click Submit.

Result

The reason choice is added. The reason choice will be available in the Reason field of the policy exception request form for the selected application.

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

57 lines · 2.8 KB Wrap lines

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

# Define a policy reason mapping

Define reason choices to be available to any user who requests an exception.

## Before you begin

Role required: sn\_vul.compliance.manager and sn\_vul\_container.manage\_exception\_configuration

## 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 Container Vulnerability Response - CVIT integration registry.

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

4. Click the magnifying glass icon.

5. Add an existing reason choice to create a new one.

- If you want to add an existing reason choice, then select a reason.
- If you want to add new reason choice to the Reason Choices table, then click **New** and fill in the fields on the form.

|Field|Description|
|-----|-----------|
|Label|Unique label for this choice.|
|Value|Unique value for this choice. This value is mapped in the Policy Reason Mapping 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.|

6. Click **Submit**.

## Result

The reason choice is added. The reason choice will be available in the **Reason** field of the policy exception request form for the selected application.

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