{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":46198,"path":"security-management/vulnerability-response/vr-rt-states.md","title":"Vulnerability Response remediation task states","bundle":null,"doc_type":null,"release":"australia","body":"\n# Vulnerability Response remediation task states\n\nThird-party integrations import vulnerable item detection data that create new vulnerability items \\(VITs\\) or update existing VITs. Detection states update VIT states in so far as they’re Open or Closed.\n\nFor more information on how a detection's state affects a VIT's state, see the [Detections, remediation tasks, and vulnerable item states](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vr-detections-rt-vi-states.md).\n\nWith [Change management for Vulnerability Response](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vuln-change_mgmnt_ovrvw.md), there’s a synchronized relationship between the state fields of the remediation tasks and the state fields of the change requests \\(CHG\\) in the Vulnerability Response product. As a change request moves through its life cycle, it also moves the state of any related remediation tasks automatically. After a change request is implemented, the remediation task is automatically resolved. See [State synchronization between change requests and remediation tasks](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vuln_change_mgmnt_state_synch.md) for more information.\n\n**Note:** Starting with v23.0 of Vulnerability Response:\n\n- the **Remediation Task State Approval** workflow is deprecated and replaced by flow Remediation Task State Approval in the flow designer.\n- the **Close** button has been removed for a remediation task and the closure of a remediation task is driven by the scanner.\n\nThe following table lists the remediation task states and the actions that you can perform on a remediation task at the respective state:\n\n\n
\n\nState\n\n\n\nDescription\n\n
\n\nOpen\n\n\n\nState upon creation. From this state you can:- **Show Duplicate VIs**\n\nIdentify duplicate VITs reported by multiple scanners in the system. You can mark the duplicate VIT as Resolved or Closed. Duplicate entries are only shown when the combination of vulnerabilities is created using Common Vulnerabilities and Exposures \\(CVE\\). For more information, see [Vulnerability Response remediation task and vulnerable item states](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vulnerabillity-states.md).\n\n- **Start Investigation**\n\nAssign this remediation task to a person or group to start investigating.\n\n- **Mark as false positive**\n\nMark an item or group as false positive if the scanner reports that a vulnerability exists in the system, but in reality there’s no vulnerability.\n\n- **Request exception**\n\nRequest an exception, a reopen \\(Until\\) date, a reason, and optionally, provide additional information. Defers the remediation of the item or group until the date that an exception is requested.\n\n- **Resolve**\n\nMark as Resolved to move the item or group to a resolved state.\n\n- **Create Change**\n\nCreate a change request or associate a remediation task to an existing change request. For more information, see [Create a change request from a remediation task](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vuln-change_mgmnt_create_change.md) and [Associate a remediation task to an existing change request](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vuln_change_mgmnt_associate_chng.md).\n\n- **Split Remediation task**\n\nFor a remediation task with more than one vulnerable item, use a set of conditions to filter out a subset of vulnerable items and split a remediation task. The items that you select are automatically moved to a new remediation task. For more information, see [Split a remediation task in the IT Remediation Workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/it-remediation-workspace/vr-ws-split-task.md).\n\n- **Defer**\n\nSelect the Deferred state, a reopen date, a reason and, optionally, provide addition information. Defers the remediation task state until the reopen date.\n\n- **Delete**\n\nConfirm the deletion. Removes the group.\n\n\n
\n\nUnder Investigation\n\n\n\nTriggered by the **Start Investigation** button. From this state, you can:- **Create a Security Incident**\n\nFor more information, see [Create a security incident](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/security-incident-response/t_ManuallyCreateSecurityIncident.md).\n\n- **Create Change**\n\nCreate a change request or associate a remediation task to an existing change request. For more information, see [Create a change request from a remediation task](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vuln-change_mgmnt_create_change.md) and [Associate a remediation task to an existing change request](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vuln_change_mgmnt_associate_chng.md).\n\n- **Split Task**\n\nFor a remediation task with more than one vulnerable item, use a set of conditions to filter out a subset of vulnerable items and split a remediation task. The items that you select are automatically moved to a new remediation task. For more information, see [Split a remediation task](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vuln_change_mgmnt_split.md).\n\n- **Create a Change Request**\n\nFor more information, see [Create a change request from a remediation task](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vuln-change_mgmnt_create_change.md).\n\n- **Awaiting Implementation**\n\nChanges state to Awaiting Implementation. This state indicates that remediation tasks have been referred outside a Vulnerability Response.\n\n- **Defer**\n\nSelect the Deferred state, a reopen date, a reason and, optionally, provide additional information. Defers the remediation task state until the reopen date.\n\n- **Delete**\n\nConfirm the deletion. Removes the remediation task.\n\n\n
\n\nDeferred\n\n\n\nTriggered by the **Request Exception** button. As part of the approval workflow, the Deferred state is In Review and can't be closed until approved. From this state, you can:\n\n - **Create Change**\n\nCreate a change request or associate a remediation task to an existing change request. For more information, see [Create a change request from a remediation task](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vuln-change_mgmnt_create_change.md) and [Associate a remediation task to an existing change request](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vuln_change_mgmnt_associate_chng.md).\n\n- **Split Task**\n\nFor a remediation task with more than one vulnerable item, use a set of conditions to filter out a subset of vulnerable items and split a remediation task. The items that you select are automatically moved to a new VG. See [Split a remediation task](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vuln_change_mgmnt_split.md).\n\n- **Create a Security Incident**\n\nFor more information, see [Create a security incident](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/security-incident-response/t_ManuallyCreateSecurityIncident.md).\n\n- **Reopen**\n\nTransition back to an Open state.\n\n- **Delete**\n\nConfirm the deletion. Removes the remediation task.\n\n\n Deferment information appears under the **Close/Defer** tab. On the defer date, the group reopens for remediation.\n\n
\n\nAwaiting Implementation\n\n\n\nTriggered by the **Awaiting Implementation** button. From this state, you can:- **Create a Security Incident**\n\nFor more information, see [Create a security incident](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/security-incident-response/t_ManuallyCreateSecurityIncident.md).\n\n- **Create Change**\n\nCreate a change request or associate a remediation task to an existing change request. For more information, see [Create a change request from a remediation task](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vuln-change_mgmnt_create_change.md) and [Associate a remediation task to an existing change request](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vuln_change_mgmnt_associate_chng.md).\n\n- **Split Task**\n\nFor a remediation task with more than one vulnerable item, use a set of conditions to filter out a subset of vulnerable items and split a remediation task. The items that you select are automatically moved to a new remediation task. For more information, see [Split a remediation task](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vuln_change_mgmnt_split.md).\n\n- **Create a Change Request**\n\nFor more information, see [Create a change request from a remediation task](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vuln-change_mgmnt_create_change.md).\n\n- **Defer**\n\nSelect the Deferred state, a reopen date, a reason and, optionally, provide addition information. Defers the remediation task state until the reopen date.\n\n- **Resolve**\n\nAdd notes. The state becomes Resolved. Notes appear under the **Resolution** tab.\n\n- **Delete**\n\nConfirm the deletion. Removes the remediation task.\n\n\n
\n\nResolved\n\n\n\nTriggered from the **Resolve** button. From this state you can:- **Create a Security Incident**\n\nFor more information, see [Create a security incident](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/security-incident-response/t_ManuallyCreateSecurityIncident.md).\n\n- **Create Change**\n\nCreate a change request or associate a remediation task to an existing change request. For more information, see [Create a change request from a remediation task](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vuln-change_mgmnt_create_change.md) and [Associate a remediation task to an existing change request](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vuln_change_mgmnt_associate_chng.md).\n\n- **Reopen**\n\nTransition back to an Open state.\n\n- **Delete**\n\nConfirm the deletion. Removes the remediation task.\n\n\n Notes appear under the **Notes** tab. Resolution information appears under the **Resolution** tab.\n\n
\n\nClosed\n\n\n\nTriggered by the scanner. From this state, you can:- **Create a Security Incident**\n\nFor more information, see [Create a security incident](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/security-incident-response/t_ManuallyCreateSecurityIncident.md).\n\n- **Reopen**\n\nTransition back to an Open state.\n\n- **Delete**\n\nConfirm the deletion. Removes the remediation task.\n\n\n Closure information appears under the **Close/Defer** tab.\n\n
- The remediation owner can only mark a vulnerable item or remediation task as resolved. Based on the confirmation from the scanner, this resolved item or remediation task can be marked as Closed or reopened.\n- The **Delete** button is available for the administrator when there are multiple vulnerable items created manually, and these need to be closed or deleted.\n- If you determine that the items are a low risk, waiting for a change window, or a patch, you can change their remediation task to the Deferred state for a defined amount of time. You can request an exception using the **Request Exception** option.\n\n **Note:** When remediation tasks are deferred or closed, you can specify resolutions to further define the reasons for doing so.\n\n- When a VIT is reopened, either manually or automatically, the following happens:\n\n - The VIT state changes to Open. The original remediation task state doesn't update.\n - The VIT is reevaluated and put into a new or existing remediation task that is based on the active Remediation Task Rules.\n This preserves its history while enabling further remediation.\n\n- When a remediation task is created \\(automatically or manually\\), or split, then its **State**, **Reason**, and **Until** fields are evaluated. In case of the split action, these fields are evaluated for both the old and new remediation tasks. When a VIT is updated, then the **State**, **Reason**, and **Until** fields of all its associated remediation tasks are evaluated.\n\n - If all the VITs in a remediation task are deferred and have the same reason, then the remediation task's state changes to **Deferred** and the VITs' reason is assigned to the remediation task. If the VITs differ in reason, then the remediation task's reason changes to **None**.\n - The closest **Until** date of all the VITs is updated in the **Until** field of the remediation task.\n - If you reopen any VIT, then the state of the remediation task changes to **Open**.\n This evaluation is done by the **Rollup vulnerability item values to vulnerability and group** scheduled job, which runs every 15 minutes.\n\n\n"}}