Container Vulnerability Response remediation tasks and task rules overview
Summarize
Summary of Container Vulnerability Response remediation tasks and task rules overview
The Container Vulnerability Response (CVR) remediation tasks and task rules feature in ServiceNow allows analysts and remediation specialists to efficiently organize and manage container vulnerable items (CVITs). Remediation tasks group CVITs based on configurable criteria, enabling bulk analysis, progress tracking, and streamlined remediation processes.
Show less
Key Features
- Automatic grouping and assignment: Remediation task rules define how CVITs are automatically grouped and assigned into remediation tasks using various fields such as configuration item or vulnerability ID. Multiple grouping criteria can be combined (up to six).
- Default and customizable rules: A default “Vulnerability” rule groups CVITs by vulnerability, but customers can create multiple task rules tailored to risk levels, product models, assignment groups, and other fields.
- Assignment management: By default, remediation tasks inherit assignment groups from CVITs based on assignment rules. Starting with version 2.13, users can clear incorrect assignments directly from CVIT or remediation task records.
- Deferral tracking: The system tracks how many times CVITs and remediation tasks have been deferred, displaying counts and listing items deferred multiple times for better prioritization.
- State rollup and rolldown: Changes in remediation task states propagate down to associated CVITs immediately, while CVIT states roll up to the remediation task on a scheduled basis when all CVITs share the same state.
- Reapplying and evaluating rules: Changes to remediation task rules can be reapplied to open tasks, automatically deleting and recreating them as needed. The Vulnerability Manager Workspace offers a more efficient way to evaluate these rules on selected CVITs.
- Auto-close rules: Customers can create rules to automatically close older CVITs based on defined filter conditions, helping maintain focus on current vulnerabilities.
Practical Benefits for ServiceNow Customers
- Efficiency: Automating CVIT grouping reduces manual effort and improves consistency in remediation task creation and assignment.
- Visibility and control: Tracking deferrals and state changes helps identify bottlenecks and ensures remediation progress is accurately reflected.
- Flexibility: Customizable task rules enable targeting different risk levels and organizational structures, aligning vulnerability management with business priorities.
- Improved assignment accuracy: Ability to remove incorrect assignments directly from records minimizes delays and confusion in remediation workflows.
Next Steps
To make the most of these capabilities, customers should configure remediation task rules aligned with their environment and risk posture, use assignment rules to automate task ownership, and leverage the Vulnerability Manager Workspace for streamlined evaluation of task rule impacts. Regularly monitoring deferral counts and using auto-close rules can help maintain an efficient and focused container vulnerability remediation process.
Configure remediation tasks (CVULs) to help analysts and remediation specialists organize container vulnerable items (CVIT) and analyze them in bulk. The criteria by which remediation tasks are formed are configured so that CVITs are automatically assigned into remediation tasks. Using remediation tasks, you can monitor progress and drive the remediation process more efficiently.
Removing assignments from container vulnerable items and remediation tasks
Starting with version 2.13, you can clear the Assigned to and Assignment group fields on container vulnerable items (CVITs) directly from the CVIT and remediation task records that you determine might be incorrectly assigned to you or your groups.
See Removing assignments from container vulnerable items and remediation tasks and Remove assignments from vulnerable items and remediation tasks for more information.
Tracking deferral counts for container vulnerable items and remediation tasks
Track the number of times a vulnerable item, application vulnerable item, container vulnerable item, or remediation task is deferred. The set deferral counts scheduled job runs daily to post counts for the records that are deferred more than once in the Deferral count column. Records are displayed in the Multiple deferrals modules for VR, AVR, and CVR.
Understanding remediation task rules
Remediation task rules enable you to define how container vulnerable items are automatically grouped and assigned. A default rule Vulnerability is included in the base system that gathers CVITs based on their vulnerabilities. However, you can group by any other set of values in columns accessible from the CVIT. These values could include configuration item (CI), vulnerability entry, and the like.
There are task rules for Container Vulnerability Response that are included with the Vulnerability Response application that is available when you activate it.
You can create multiple conditions with the condition builder. In the Group by section, after you set a field pair, another row appears. You can have up to six Group by selections. You can automate group assignment as well.
For example, you can group your container vulnerable items by the configuration item, or by the product model. You can have one task rule for low severity vulnerabilities or low risk CIs. You can have another task rule for critical servers, and vulnerabilities that expose the company to more risk. See Create, edit, and delete Container Vulnerability Response remediation task rules for more information about the options that you have available to you.
A different set of rules can be used for container vulnerable items that expose the company to more risk. The remediation task name is appended to the remediation task rule Group by values to make the short description of the new record.
When a new container vulnerable item is created, imported, or reopened after being closed, the rules are evaluated against it. A CVIT is only evaluated once, automatically, unless it's reopened after being closed or the rules are reapplied manually.
- For each remediation task rule, the CVIT is compared to the remediation task rule filter.
- For each rule where the remediation task rule condition matches, the rule pulls the data from the Group by selections on the CVIT. It builds a group name and field. In this case, High Risk:
QID-32342:Summary of QID-3242 (Name: vulnerability ID: vulnerability summary).Note:The short description field is limited to 160 characters. Longer vulnerability summaries are truncated.
- If the task is found, the CVIT is added to the existing task in the Open State.
- If no task in the Open state is found, the rule creates a High Risk: QID-32342 task, assigns it to the same assignment group as the CVIT, and places the CVIT in the remediation task.
More than one remediation task rule can be defined to group different kinds of vulnerabilities. Since each vulnerability is compared with the remediation task rule conditions before putting it in a remediation task, too many rules might impact performance. Set up your task rules so the conditions help you avoid creating duplicate remediation tasks.
By default, remediation task rules use the assignment group set by the Assignment Rules on the CVIT when grouping the items and assigns the remediation task to match the CVITs.
As part of the default task rule, the assignment of these remediation tasks is controlled by the rules in the Assignment Rules module. For more information on assignment rules, see Vulnerability Response assignment rules overview.
When a task rule is deleted from the form or list view, you have the option to delete all Open tasks created by that rule. Tasks not in the Open State are excluded.
Reapplying remediation task rules
When you want to change a remediation task rule, use the Reapply button on the remediation task rule page to rerun the changed rule on all active Open remediation tasks created by that rule. It deletes and recreates remediation tasks based on the changed rule automatically.
Reapply only checks existing remediation tasks.
After you select Reapply, the following message is displayed: Reapplying this remediation task rule will delete and re-create the remediation tasks for this rule. Remediation tasks that are not in the Open State aren’t deleted.
Remediation task rules and CVIT creation and update
If a CI from a scan is associated with a known vulnerability, a CVIT is created. After it's created, the CVIT is evaluated against the conditions of remediation task rules for a match. If there’s a match to an existing remediation task, the CVIT is added. If a matching remediation task isn’t found, one is created for the CVIT.
If any property that is captured in the remediation task filtering conditions is updated or changed on a CVIT, the updated AVI is also evaluated against the remediation task rules for a match. If there’s a match to an existing remediation task, the CVIT is added. If a matching remediation task isn't found, one is created for the CVIT.
State rollup and rolldown
If you update a remediation task to Open, or from Open to Under Investigation, the new state rolls down to all associated CVITs. State roll down occurs immediately after you change the State.
State rollup from CVITs to the remediation task only occurs if all the CVITs on the task are in Deferred or Closed- fixed states. Rollup is done with the Rollup container vulnerable item values to vulnerability and a group-scheduled job, which runs every 15 minutes. The state is not rolled up until the job runs. For a State to roll up to occur from the CVITs to the remediation task, all the CVITs must be in the same State.