Working with an exception rule in Container Vulnerability Response

You can request an exception for container vulnerable items (CVITs) that can't be remediated or deferred immediately. By automating the VI deferral process, you can defer the matching CVITs based on the rule when the system identifies them.

You can perform the following tasks for an exception rule:

Note: Starting from v2.5 of Container Vulnerability Response, you can configure the time frames for approving false positives and exceptions, along with email notifications for both the approver and requester after a set number of days. When a request is raised, the container vulnerable item changes to In-Review status and a state change record is created. If the approver doesn't respond within the configured time frame, the container vulnerable item or remediation task reverts to Open status. The previous state is stored in the backup_state field. For more information, see Configure approval rules for Exception Management.

Create an exception rule in Container Vulnerability Response
Create a rule to automatically request an exception for a specific condition for a group of container vulnerable items (CVITs), such as a rule with a condition that is based on the vulnerability severity of these CVITs. With this rule, you can defer new and existing CVITs automatically if they match the approved rule condition.
Approve an exception rule request in Container Vulnerability Response
Assess exception rule requests from users so that you can approve or reject these requests.
Activating an exception rule in Container Vulnerability Response
A rule is activated on its "Valid from" date. After activation, it automates the exception process for container vulnerable items (CVITs).
Reopen an exception rule in Container Vulnerability Response
Reopen an exception rule that has been rejected, but you want to resubmit. Reopening the rule moves it to the Draft state.
Update an approved exception rule in Container Vulnerability Response
Cancel an approved rule to be able to update it. For example, before you can modify any dates or add a condition to an approved rule, you must cancel it so that the remediation task (VUL) is deleted, and the container vulnerable items (CVITs) move to the Open state.
Delete an exception rule in Container Vulnerability Response
Delete an exception rule that is not required anymore. For example, you can delete a rule if you don't want to defer a container vulnerable item (CVIT) during ingestion.
Request an extension for a deferred remediation task in Container Vulnerability Response
Request an extension for a deferred remediation task (VUL) before it reaches its deferred until due date. As a remediation owner, you’re no longer required to wait until the deferred due date to make this request.
Request an extension for an exception rule in Container Vulnerability Response
Request an extension for a deferred exception rule before it reaches its deferred until due date. As a remediation owner, you’re no longer required to wait until the deferred due date to make this request.

Parent Topic:Exception management in Container Vulnerability Response

title	Working with an exception rule in Container Vulnerability Response
description	You can request an exception for container vulnerable items \(CVITs\) that can't be remediated or deferred immediately. By automating the VI deferral process, you can defer the matching CVITs based on the rule when the system identifies them.
locale	en-US
canonical_url	https://www.servicenow.com/docs/r/security-management/container-vulnerability-response/working-with-exception-rule-cvr.html
release	brazil
product	Container Vulnerability Response
classification	container-vulnerability-response
topic_type	concept
last_updated	2026-09-10
reading_time_minutes	4
breadcrumb	Exception management in Container Vulnerability ResponseUseContainer Vulnerability ResponseUnified Security Exposure ManagementSecurity Operations