---
sourceDocument: Australia Security Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/security-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# Remediation task form fields

# Remediation task form fields {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read

Using remediation tasks, the analyst can monitor progress and drive the mediation
process more efficiently.
These fields are found on records listed in the Remediation Task \[sn_vul_vulnerability\] table.

To view imported data in the fields listed in the following tables, you must have, at a minimum, the sn_vul.read_all role.
{#vulnerability-group-fields__table_t4d_4bd_5s__entry__2}

| Field | Description |
|-|-|
| Number | The automatically generated vulnerable item (VI) number for this record. |
| Risk rating | Rollup of vulnerable item risk scores separated into ranges: Critical, High, Medium, Low and None. For more information on risk ratings see, [Vulnerability Response calculators and vulnerability calculator rules](https://servicenow-prod.fluidtopics.net/3Hl03aogPFrru7chhJttaQ "Vulnerability calculators automate calculating initial values for the fields on vulnerable items. The condition for each calculator is evaluated in order, and the first matching calculator is used."). Note: This base Risk rating is not the same as the Solution record Risk rating. |
| Risk score | Rollup of the risk scores of all of the vulnerable items associated with this remediation task. Amount of risk the vulnerable items, collectively, pose to your environment. Note: This base Risk score is not the same as the Solution record Risk score. |
| Remediation target | Date by which the vulnerable items should be remediated, since first identified. For more information on remediation targets see [Vulnerability Response remediation target rules](https://servicenow-prod.fluidtopics.net/Rk0nNjDmu1fZ7GxcJJ20Jg "Remediation target rules define the expected time frame for remediating vulnerable items (VI), much like SLAs provide a time frame for remediating the vulnerability itself. For example, if an asset contains PCI data (credit card data) then the vulnerability on that item must be fixed within 30 days according to PCI DSS."). |
| Remediation status | Status of the remediation for the task. It is determined by the vulnerable item with the nearest due date. For open groups states include: * In-flight * Approaching Target * Target Missed {#vulnerability-group-fields__ul_d14_gzp_2fb} For closed groups states include: * No Target * Target Met * Target Missed {#vulnerability-group-fields__ul_tj4_rn4_3gb} For calculated remediation target dates, if the task is closed, the overall remediation status of all of the closed vulnerable items is shown in the task. Those determine whether the task met its date or not. A closed task's remediation Status is No Target if none of its closed items had a remediation target date. It is Target Missed if any of its closed items missed their target date. It is Target Met if at least one closed VI met its target and none of the others missed it. |
| State | Progress status of the task. States include: * Open * Under Investigation * Awaiting Implementation * Deferred * In Review * Resolved * Closed {#vulnerability-group-fields__ul_xbk_rzp_2fb} For more information on states, see [Vulnerability Response remediation task and vulnerable item states](https://servicenow-prod.fluidtopics.net/WxaJrhnoLTHqOnIz9WpoLA "With the Vulnerability Response application, you can use the state model to see the status of a remediation task, at any given time. Knowing how each state relates to and affects each other helps you to determine when and how to remediate your vulnerable items (VIs)."). |
| Until date for Risk reduction | Date on which compensatory controls applied to the remediation task expire. Note: This field appears only when the value is available. |
| Assignment group | Group selected to work on this remediation task. |
| Assigned to | Individual from the selected assignment group that works on this vulnerability. |
| Created | Date this remediation task was created. |
| Updated | Date this remediation task was last updated. |
| Vulnerability | Vulnerability applicable to the task. (Visible when the group is formed based on a single vulnerability.) |
| Short description | Brief description of this remediation task. |
| In Review (visible when the RT is in the In Review state) ||
| Requested by | Individual who requested the deferral. |
| Desired reason | Reason for deferral. |
| Desired state | The state requested from the approver. |
| Desired substate | The reason requested from the approver. |
| Deferral(visible when the task is in the Deferred state) ||
| Deferred by | Individual who deferred the task. |
| Defer expiration | Date the deferral expires. |
| Reason to defer | Reason for the deferral. |
| Resolution (visible when the RT is in the Resolved state) ||
| Resolved by | Individual who resolved the remediation task. |
| Resolution date | Date the remediation task was resolved. |
| Resolution notes | Additional information. |
| Close (visible when the RT is in the Closed state) ||
| Closed by | Individual who resolved the remediation task. |
| Closed | Date the remediation task was closed. |
| Close notes | Additional information. |
| Group Configuration (visible in all states) ||
| Filter type | Type of filtering used to select vulnerabilities for the group: Condition : Note: Refreshes once an hour. Filter group : Note: Refreshes once an hour. Manual : |
| Remediation Status ||
| Excludes Deferred ||
| Vulnerable items | Number of active vulnerable items within this task. This count excludes deferred vulnerable items. |
| Total VIs | Total number of vulnerable items within this task. This count excludes deferred vulnerable items. |
| %VIs remediated | Percent complete for remediation of vulnerable items within this task. This count excludes deferred vulnerable items. |
| Includes Deferred ||
| Vulnerable items | Number of active vulnerable items within this task. |
| Total VIs | Total number of vulnerable items within this task. |
| %VIs remediated | Percent complete for remediation of vulnerable items within this task. |
| Notes (visible in all states) ||
| Description | Description of the group or remediation actions. |
| Additional comments | Additional information. |
| Activities | System notes. |
| Related Links ||
| Re-scan vulnerable items | Triggers a re-scan of the vulnerable items to determine if they are fixed. |
| Update Status | Displays date and time of the last update. Rolls up the following from the VIs in the task: * Remediation task state * Risk scores and risk ratings * Remediation target date and status (if applicable) * Metrics such as Active VIs, Total VIs from the Remediation Status section {#vulnerability-group-fields__ul_zmr_fwj_5kb} |
| Related Lists ||
| Vulnerable items | Vulnerable items in this task. |
| Task SLAs | Platform SLAs associated with this task. |
| Preferred Solutions | Preferred solutions of the vulnerable items in this task. |
| Change Requests | Change requests associated with this task. |
| Requested Approvals | (Visible when the task is in the In Review state.) List of approvers. Once the deferral is approved, the remediation task moves to the Deferred state. |
[Table 1. Remediation task fields]

{#vulnerability-group-fields__table_t4d_4bd_5s}