---
title: Defer a container vulnerable item in Container Vulnerability Response
description: If you determine that the issue associated with a container vulnerable item \(CVIT\) is of low risk and can be immediately deferred without further analysis, you can use the Defer feature.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/security-management/container-vulnerability-response/defer-vul-item-cvr.html
release: australia
product: Container Vulnerability Response
classification: container-vulnerability-response
topic_type: task
last_updated: "2026-03-12"
reading_time_minutes: 3
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]
---

# Defer a container vulnerable item in Container Vulnerability Response

If you determine that the issue associated with a container vulnerable item \(CVIT\) is of low risk and can be immediately deferred without further analysis, you can use the **Defer** feature.

## Before you begin

Role required: sn\_vul.vulnerability\_admin or sn\_vul.admin \(deprecated\)

Persona and granular roles are available to help you manage what users and groups can see and do in the Vulnerability Response application. For an initial assignment of the persona roles in Setup Assistant, see [Assign the Vulnerability Response persona roles using Setup Assistant](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vr-assign-personas_SA.md). For more information about managing granular roles, see [Manage persona and granular roles for Vulnerability Response](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vr_manage_granular-roles.md).

## About this task

A scheduled job runs every day checking for deferred vulnerable items that have reached their reopen date. On the day the CVIT's deferral is set to expire, the record is reopened.

## Procedure

1.  Navigate to **All** > **Container Vulnerability Response** > **Container Vulnerable Items**.

2.  Open a vulnerable item.

3.  Click **Request Exception**.

4.  Fill in the fields on the form, as appropriate.

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

Field

</th><th>

Description

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

Until

</td><td>

Select the date when the Deferred state expires and the remediation task is reactivated.

 **Note:** Starting with version 18.0 of Container Vulnerability Response, if a deferred container vulnerable item \(CVIT\) is closed and reopened by a scanner before the exception window expires, the state of the CVIT reverts to deferred state honouring the active exception window. To enable this functionality, set the value of the system property **sn\_vul\_container.auto\_defer\_cvit\_in\_active\_exception\_window**to true. Additionally, the deferred Until date persists even after the vulnerable item gets closed or the exception expires. The role required is sn\_vul\_container.manage\_exception\_configuration for both read and write.

 After the record is submitted, if [email notifications](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/t_DefineEmailNotifications.md) are defined, members of the Container Vulnerability Response group receive an email when the expiration date is within one week. When the defer date expires, the vulnerable item is set back to Open and a second email notification is sent out.

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

Reason

</td><td>

Enter the reason for deferring the issue. Choices include:

-   Awaiting maintenance window
-   False positive
-   Fix unavailable
-   Risk accepted
-   Mitigating control in place
-   Other


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

Additional information

</td><td>

Enter any other relevant information.

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

    The group is marked **In Review**. A **Reopen** related link appears. The reopen date and reason appear in work notes under the **State Change Approvals** tab.

    Starting with Container Vulnerability Response v2.3, you can add relevant information in the Work Notes field in the Notes section for a deferred container vulnerable item.


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