Filtering within Vulnerability Response

concept brazil Updated Sep 10, 2026 1 min read vr-filtering.md

Remediation Task Rules, Calculators, and Assignment Rules use conditions during import, created using the Condition builder. Changes to their criteria can affect performance since each record is evaluated using these filters.

The rules and calculators shipped with the base system are optimized for performance. Editing or creating rules or calculators takes care and may require both ServiceNow and Vulnerability Response expertise.

Avoid filtering based on subclass fields

Some tables support extension. An example of that is the CMDB CI [cmdb_ci] table. Tables like cmdb_ci_hardware and cmdb_ci_computer extend this table. If you filter based on a field that is not on the parent table, that filter can be expensive to construct and evaluate.

[Omitted image "ConditionFilterDropDown.png"] Alt text: Condition filter drop-down menu example.

For example, filtering on Configuration Item > Cost would not adversely affect performance because Cost is a class field, and not a subclass field, of Configuration Item. [Omitted image "FilteringClass.png"] Alt text: Filtering on class field example

Configuration Item > Computer, however, is a subclass requiring a dot-walk to another field, in this case, Operating System. This process can take many milliseconds which adds up quickly, when millions of vulnerable items are being imported, and affect performance. [Omitted image "FilteringSubClass.png"] Alt text: Filtering on subclass field example.

Note: Using the [contains] condition is like a wild card search and can cause performance impact. Using [is], wherever possible, is more efficient.

Parent Topic:Advanced Vulnerability Response configuration tasks

35 lines · 2.6 KB Wrap lines

---
title: Filtering within Vulnerability Response
description: Remediation Task Rules, Calculators, and Assignment Rules use conditions during import, created using the Condition builder. Changes to their criteria can affect performance since each record is evaluated using these filters.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/security-management/vulnerability-response/vr-filtering.html
release: brazil
product: Vulnerability Response
classification: vulnerability-response
topic_type: concept
last_updated: "2026-09-10"
reading_time_minutes: 1
breadcrumb: [Advanced Vulnerability Response configuration tasks, Vulnerability Response implementation, Vulnerability Response, Unified Security Exposure Management, Security Operations]
---

# Filtering within Vulnerability Response

Remediation Task Rules, Calculators, and Assignment Rules use conditions during import, created using the **Condition builder**. Changes to their criteria can affect performance since each record is evaluated using these filters.

## Avoid filtering based on subclass fields

Some tables support extension. An example of that is the CMDB CI \[cmdb\_ci\] table. Tables like cmdb\_ci\_hardware and cmdb\_ci\_computer extend this table. If you filter based on a field that is not on the parent table, that filter can be expensive to construct and evaluate.

\[Omitted image "ConditionFilterDropDown.png"\] Alt text: Condition filter drop-down menu example.

For example, filtering on **Configuration Item** &gt; **Cost** would not adversely affect performance because **Cost** is a class field, and not a subclass field, of **Configuration Item**. \[Omitted image "FilteringClass.png"\] Alt text: Filtering on class field example

**Configuration Item** &gt; **Computer**, however, is a subclass requiring a dot-walk to another field, in this case, **Operating System**. This process can take many milliseconds which adds up quickly, when millions of vulnerable items are being imported, and affect performance. \[Omitted image "FilteringSubClass.png"\] Alt text: Filtering on subclass field example.

**Note:** Using the \[contains\] condition is like a wild card search and can cause performance impact. Using \[is\], wherever possible, is more efficient.

**Parent Topic:**[Advanced Vulnerability Response configuration tasks](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/security-management/vulnerability-response/setup-tasks-optional.md)