---
title: Close a remediation task
description: If you determine that the issue associated with a remediation task can be immediately closed without further analysis, you can use the Close feature. Starting with v23.0 of Vulnerability Response, the Close button has been removed for a remediation task and the closure of a remediation task is driven by the scanner.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/security-management/vulnerability-response/close-vuln-group.html
release: australia
product: Vulnerability Response
classification: vulnerability-response
topic_type: task
last_updated: "2026-03-12"
reading_time_minutes: 1
breadcrumb: [Resolve remediation tasks, Working with unmatched CIs, Vulnerability Response remediation overview, Vulnerability Response, Unified Security Exposure Management, Security Operations]
---

# Close a remediation task

If you determine that the issue associated with a remediation task can be immediately closed without further analysis, you can use the **Close** feature. Starting with v23.0 of Vulnerability Response, the **Close** button has been removed for a remediation task and the closure of a remediation task is driven by the scanner.

## Before you begin

Role required: admin

## About this task

In the Vulnerability Response Workspaces, a remediation task transitions through the same states as a remediation task prior did in previous versions of Vulnerability Response. When all the vulnerable items \(VITs\) in a remediation task are closed, the remediation task transitions to the Inactive state.

**Important:** You can manually move change requests and remediation tasks through the states of their life cycles on their respective records with state synchronization enabled, but when the system registers that a CHG has changed its state, or you add a CHG or remove it from a remediation task, state synchronization potentially can override your manual intervention. However, change request states do not automatically move remediation tasks from the `Closed` or `Deferred` states.

## Procedure

1.  Open the record that you want to request a review for.

2.  Select the **Close/Defer** button.

3.  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>

State

</td><td>

Select a state. Choices are:

 -   Deferred
-   Closed


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

Until

</td><td>

Only available in the **Defer** state pop-up.

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

 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 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 closing the issue.

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

Additional information

</td><td>

Enter any other relevant information.

</td></tr></tbody>
</table>4.  Select **Submit**.

    The remediation task is marked **Closed**.


**Parent Topic:**[Resolve remediation tasks](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/remediate-vuln-groups.md)