---
title: Resolve remediation tasks
description: The flexibility inherent in Vulnerability Response allows you to remediate vulnerabilities in whatever way suits your security organization.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/security-management/vulnerability-response/remediate-vuln-groups.html
release: australia
product: Vulnerability Response
classification: vulnerability-response
topic_type: task
last_updated: "2026-03-12"
reading_time_minutes: 4
breadcrumb: [Working with unmatched CIs, Vulnerability Response remediation overview, Vulnerability Response, Unified Security Exposure Management, Security Operations]
---

# Resolve remediation tasks

The flexibility inherent in Vulnerability Response allows you to remediate vulnerabilities in whatever way suits your security organization.

## Before you begin

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

## About this task

Once you are notified that a change request is resolved, move the remediation task state to Resolved and wait for the next scan. Rescans are triggered automatically by the third-party import schedule configured in the Setup Assistant.

**Note:**

If state synchronization is activated, remediation tasks are automatically moved to the Resolved state after a change request associated with a remediation task \(VUL\) is implemented and in the Review state. See [Change management for Vulnerability Response](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vuln-change_mgmnt_ovrvw.md).

## Procedure

1.  Navigate to **All** > **Vulnerability Response** > **Remediation tasks** > **Assigned to me**.

2.  Click a record that is in the Open state.

    The Open state indicates that the record has not yet been worked on. The form displays:

    -   Remediation task information
    -   Group Configuration details
    -   Notes
    -   Associated vulnerable items
    -   Task SLAs
    -   Change Requests
3.  Perform your analysis of the group.

4.  When you are ready to start working on the record, choose any of the following options.

<table id="choicetable_scx_gm5_b2b"><tbody><tr><td id="d415334e131">

**If the vulnerable item poses a risk to your IT environment, create a CHG record and escalate the issue to [Change Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/it-service-management/c_ITILChangeManagement.md) team.**

</td><td>

Assign the group to the appropriate group or individual and click **Create Change**.

</td></tr><tr><td id="d415334e147">

**If the vulnerable item poses a potential security risk to your organization, create a security incident record and escalate the issue to the [Security Incident Response](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/security-incident-response/sir-landing-page.md) team.**

</td><td>

Click **Create Security Incident**. This button is displayed only when Security Incident Response is activated. A business impact calculation is applied, the incident is assigned, and the security incident is created.

</td></tr></tbody>
</table>    After you create a change request, the appropriate record appears in the **Change Requests** related list on the Vulnerability Group form.

5.  If you determine that the issue is of low risk and can be deferred, click **Request Exception**.

    For more information on how to defer a remediation task, see [Defer a Remediation task](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/defer-vuln-group.md).

6.  If you determine that the issue can be immediately closed without further analysis, click **Close**.

    For more information on how to close a remediation task, see [Close a remediation task](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/close-vuln-group.md). Starting with v23.0 of Vulnerability Response, the **Close** button has been removed for a remediation task.

    A third-party integration scheduled job automatically updates and scans records at a set interval. The vulnerable items are scanned at the next scheduled date and time. Alternatively, you can manually initiate a vulnerability scan using the **Scan for Vulnerabilities** related link.

    If the scan again finds the vulnerability on the configuration item and does not mark it Fixed, the vulnerable item returns to the Under Investigation state. Contact IT Operations to reopen the change request.

    If the scan does not find the vulnerability and returns that the vulnerable item has been marked Fixed, the vulnerable item transitions to the Closed-Fixed state and is closed during import.

    Only when all vulnerable items in a task are in the Closed-Fixed state, does the remediation task close automatically. Remediation tasks with vulnerable items in Closed states other than Fixed must be closed manually.


-   **[Defer a Remediation task](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/defer-vuln-group.md)**  
If you determine that the issue associated with a remediation task \(VUL\) is a low priority and can be immediately deferred without further analysis, you can use the **Request Exception** feature.
-   **[Close a remediation task](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/close-vuln-group.md)**  
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.

**Parent Topic:**[Working with unmatched CIs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/working-unmatched-cis.md)

**Related topics**  


[View and reclassify unmatched configuration items]()

[Reconcile unmatched discovered items]()

[Steps to help prevent duplicate or orphaned records after running Vulnerability Response CI lookup rules]()

[De-duplicating existing configuration items]()