--- sourceDocument: Brazil Security Management sourceDocumentLink: https://www.servicenow.com/docs/r/security-management Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Security Management ft:clusterId : - security bundleId : - security workflow : - Technology --- # Life cycles of remediation efforts, remediation tasks, and records in the Vulnerability Response Workspaces # Life cycles of remediation efforts, remediation tasks, and records in the Vulnerability Response Workspaces {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Life cycles of remediation efforts, remediation tasks, and records in the Vulnerability Response Workspaces This content explains how remediation efforts, remediation tasks, and their associated records behave and evolve within the Vulnerability Response Workspaces, specifically in the Brazil release. It covers how actions like deferring, resolving, reopening, and transferring affect the states of these items. The guidance is targeted at users with roles such as vulnerability analysts, administrators, and managers across different vulnerable item types including hosts, applications, containers, and configuration test results. Show full answer Show less ## Creating Remediation Efforts Remediation efforts can be initiated directly from a watch topic via options to create a single remediation effort or a recurring remediation effort. Only one recurring remediation effort can exist per watch topic, which automates subsequent efforts based on defined criteria. Key points include: * Only **Active** records are included in remediation efforts. * All records in a new remediation effort are assigned to new remediation tasks. * Records may appear in multiple remediation tasks but are linked to only one remediation effort. * A remediation effort is automatically deactivated when it contains no active records. ## Transferring and Carrying Over Records Records can be transferred from one remediation effort to another during the creation of a remediation effort by selecting the appropriate option. Transfer behaviors depend on whether the new remediation effort is within the same watch topic or a different one: * **Within the same watch topic:** All remediation tasks move to the new effort, new remediation tasks are created for previously unassigned records, and the old effort is deactivated. * **Across different watch topics:** All records move to the new effort with remediation tasks created accordingly. If all records from old remediation tasks transfer, those tasks are closed-canceled; if only some records transfer, tasks are split and remain active. Closed tasks remain unaffected. **Important limitations:** * Records cannot be transferred from recurring remediation efforts to new remediation efforts. * Records can be transferred only from existing, non-recurring remediation efforts. These lifecycle behaviors and transfer rules help maintain data integrity and streamline remediation workflows within ServiceNow's Vulnerability Response Workspaces. The states of records and their associated remediation tasks (RTs) are impacted if records are deferred, resolved, reopened, and transferred to other remediation efforts (REs). Roles required: * sn_vul.vulnerability_analyst, or sn_vul.vulnerability_admin for host vulnerable items (VITs) * sn_vul.app_sec_manager for application vulnerable items (AVITs) * sn_vul_container.vulnerability_analyst or sn_vul_container.vulnerability_admin for container vulnerable items (CVITs) * sn_vulc.admin for configuration test results (CTRs) {#vr-ws-re-lifecycle__ul_myz_sdj_hbc} ## Creating remediation efforts {#vr-ws-re-lifecycle__section_qy1_tw2_xrb} How the states and life cycles of remediation efforts, remediation tasks, and records are impacted depends on how a remediation effort is created, when it's created, and if it's deactivated. From the list in the upper right on a watch topic, you can create a remediation effort by clicking Create a Remediation Effort or Create recurring effort. You can create one recurring remediation effort per watch topic. If you create a recurring remediation effort, subsequent remediation efforts for the associated watch topic are created automatically based on the criteria you set. In either case: * To facilitate remediation, only Active records are added to the remediation efforts. * All records in new remediation efforts are placed in new remediation tasks. Records can exist in multiple remediation tasks, but only one record can be associated with a remediation effort. {#vr-ws-re-lifecycle__ul_whm_vw2_xrb} Note: A Remediation Effort is deactivated automatically when there are no active records. ## Transferring records or record carry over {#vr-ws-re-lifecycle__section-wmws-re-transfer-records} You can transfer records from one remediation effort to another when creating a remediation effort by selecting the Transfer matching records from other active remediation efforts check box. For more information on how to transfer the records, see [Transfer records to remediation efforts in the Vulnerability Manager Workspace](https://www.servicenow.com/docs/mTtw9sMU9f73vIFEDcpDmw "You can transfer records from existing remediation efforts into new remediation efforts in the Vulnerability Manager Workspace."). If records are transferred from a remediation effort or carried over into recurring remediation efforts: To a new remediation effort in the same watch topic : * All Remediation Tasks from the old Remediation Effort are moved to the new Remediation Effort. * New Remediation Tasks are created based on the chosen grouping criteria for the records previously not part of any Remediation Task. * The old Remediation Effort is deactivated. {#vr-ws-re-lifecycle__ul_lrs_xjg_q1c} To a new remediation effort in a different watch topic : All the records from the old Remediation Effort are moved to the new Remediation Effort and Remediation Tasks are created based on the chosen grouping criteria. * If all records in the Remediation Tasks associated with the old Remediation Effort are transferred, these Remediation Tasks are closed-canceled. * If only a subset of records are transferred, the Remediation Tasks associated with the old Remediation Effort are split and remain active. {#vr-ws-re-lifecycle__ul_mrs_xjg_q1c} : The closed Remediation Tasks associated with old Remediation Effort are not affected. Note: You can't transfer records from recurring remediation efforts into new remediation efforts. However, you can transfer records from existing, non-recurring remediation efforts into new remediation efforts. See [Transfer records to remediation efforts in the Vulnerability Manager Workspace](https://www.servicenow.com/docs/mTtw9sMU9f73vIFEDcpDmw "You can transfer records from existing remediation efforts into new remediation efforts in the Vulnerability Manager Workspace.") for more information about transferring records.