Request an exception for a container vulnerable item

task brazil Updated Sep 10, 2026 2 min read cvr-raise-exception.md

Request an exception for a container vulnerable item (CVIT) that can’t be remediated immediately. For example, as a remediation owner, you can request an exception if a patch isn’t available for a machine.

Before you begin

Role required: Developer Group

About this task

You can request an exception for multiple CVITs simultaneously using the Bulk Edit feature in the Vulnerability Manager Workspace. For more information, see Request bulk exception in the Vulnerability Manager Workspace.

Procedure

Navigate to Container Vulnerability Response > Container Vulnerable Items > All.
Select the item that you want to request an exception for.

The selected item must be in Open or Under Investigation state.
On the Container Vulnerable Item form, click Request Exception.
1. On the form, fill in the fields.

Field	Description
Until	Date on which the exception request expires. This date must be within the duration selected in the All > Container Vulnerability Response > Administration > Exception Management screen.When the exception request expires, the group reverts to its Open state. Note: Starting with version 1.2 of Container Vulnerability Response, if a vulnerable item was deferred for remediation by using the exception management feature, then in case it is reopened by the scanner, the deferral date set on the vulnerability will still persist. To enable this functionality, set the value of the system property sn_vul.container.auto_defer_cvit_in_active_exception_window to true. Also, the deferred until date persists even after the CVIT gets closed or the exception expires. The role required is sn_vul_container.manage_exception_configuration for both read and write.
Reason	Reason for the exception. Choices are as follows:- Risk Accepted Awaiting Maintenance Window Fix Unavailable Mitigating Control in Place Other To see how to add new reason choices, see Define a policy reason mapping.
Additional information	Details that are related to the reason why this request is being made. This field is to be updated by the remediation owner.

Field

Description

Until

Date on which the exception request expires. This date must be within the duration selected in the All > Container Vulnerability Response > Administration > Exception Management screen.When the exception request expires, the group reverts to its Open state.

Note: Starting with version 1.2 of Container Vulnerability Response, if a vulnerable item was deferred for remediation by using the exception management feature, then in case it is reopened by the scanner, the deferral date set on the vulnerability will still persist. To enable this functionality, set the value of the system property sn_vul.container.auto_defer_cvit_in_active_exception_window to true. Also, the deferred until date persists even after the CVIT gets closed or the exception expires. The role required is sn_vul_container.manage_exception_configuration for both read and write.

Reason

Reason for the exception. Choices are as follows:- Risk Accepted

Awaiting Maintenance Window
Fix Unavailable
Mitigating Control in Place
Other To see how to add new reason choices, see Define a policy reason mapping.

Additional information

Details that are related to the reason why this request is being made. This field is to be updated by the remediation owner.

2. Submit the exception request by clicking **Request Approval**.

The state of the container vulnerable item changes to In Review. Use the **State Change Approval** tab to track the status of the exception request.

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

86 lines · 4.0 KB Wrap lines

---
title: Request an exception for a container vulnerable item
description: Request an exception for a container vulnerable item \(CVIT\) that can’t be remediated immediately. For example, as a remediation owner, you can request an exception if a patch isn’t available for a machine.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/security-management/container-vulnerability-response/cvr-raise-exception.html
release: brazil
product: Container Vulnerability Response
classification: container-vulnerability-response
topic_type: task
last_updated: "2026-09-10"
reading_time_minutes: 2
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]
---

# Request an exception for a container vulnerable item

Request an exception for a container vulnerable item \(CVIT\) that can’t be remediated immediately. For example, as a remediation owner, you can request an exception if a patch isn’t available for a machine.

## Before you begin

Role required: Developer Group

## About this task

You can request an exception for multiple CVITs simultaneously using the Bulk Edit feature in the Vulnerability Manager Workspace. For more information, see [Request bulk exception in the Vulnerability Manager Workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/security-management/vulnerability-manager-workspace/vmws-bulk-edit-request-exception.md).

## Procedure

1.  Navigate to **Container Vulnerability Response** &gt; **Container Vulnerable Items** &gt; **All**.

2.  Select the item that you want to request an exception for.

    The selected item must be in Open or Under Investigation state.

3.  On the Container Vulnerable Item form, click **Request Exception**.

4.  1.  On the form, fill in the fields.

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

Field

</th><th>

Description

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

Until

</td><td>

Date on which the exception request expires. This date must be within the duration selected in the **All** &gt; **Container Vulnerability Response** &gt; **Administration** &gt; **Exception Management** screen.When the exception request expires, the group reverts to its Open state.

**Note:** Starting with version 1.2 of Container Vulnerability Response, if a vulnerable item was deferred for remediation by using the exception management feature, then in case it is reopened by the scanner, the deferral date set on the vulnerability will still persist. To enable this functionality, set the value of the system property **sn\_vul.container.auto\_defer\_cvit\_in\_active\_exception\_window** to true. Also, the deferred until date persists even after the CVIT gets closed or the exception expires. The role required is sn\_vul\_container.manage\_exception\_configuration for both read and write.

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

Reason

</td><td>

Reason for the exception. Choices are as follows:-   Risk Accepted
-   Awaiting Maintenance Window
-   Fix Unavailable
-   Mitigating Control in Place
-   Other
To see how to add new reason choices, see [Define a policy reason mapping](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/security-management/container-vulnerability-response/define-policy-exception-reason-choices.md).

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

Additional information

</td><td>

Details that are related to the reason why this request is being made. This field is to be updated by the remediation owner.

</td></tr></tbody>
</table>2.  Submit the exception request by clicking **Request Approval**.

    The state of the container vulnerable item changes to In Review. Use the **State Change Approval** tab to track the status of the exception request.


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