---
sourceDocument: Australia Telecommunications Service Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/telecom-service-ops

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Telecommunications Service Operations Management

ft:clusterId :

    - tsom

bundleId :

    - tsom

workflow :

    - Customer and Industry


---

# Configure filter for audit

# Configure filter for audit {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

Define filtering conditions to control the scope of Telecom Discrepancy audits. These filters ensure that audits run only on the desired set of CIs, improving performance and targeting accuracy.

## Antes de Iniciar

Role required: admin

## Por Que e Quando Desempenhar Esta Tarefa

Understanding Filtering Conditions in Telecom Discrepancy Audits

* Audits use filtering conditions to narrow the scope of CIs being evaluated.
* Filtering conditions are essential for narrowing down audit targets.
* You can define and modify conditions per audit instance to meet specific audit requirements.
* Filtering by `discovery_source` is a common condition to filter records associated with particular integration sources (e.g., TSOM and Altiplano). Additionally, you can customize the filter according to the audit requirements.
* Each version of the audit can have a different filtering condition.
{#configure-certification-filter-for-audit__ul_sz3_z3d_zfc}  
The following are the audit filters:

1. Telecom Logical Connections Discrepancy Audit: This audit runs at the logical connection table. The default filter condition is defined as `discovery_source` like TSOM. This condition is applied on each CI in the logical connection table.
2. Telecom Network Topology Discrepancy Audit: This audit runs at the network topology table. The default filter condition is defined as `discovery_source` like TSOM. This condition is applied on each CI in the network topology table.
3. Telecom Discrepancy Audit: This audit runs at the relationships table. The default filter condition is defined as `discovery_source` like TSOM. This condition is applied on each CI at the equipment level.
{#configure-certification-filter-for-audit__ol_bvh_kjd_zfc}

The following screenshot helps to understand the user interface of the certification filter .

## Procedimento

1. Navigate to AllCertificationFilters.
2. Select New.  
   The certification filter interface appears.
3. Fill in the fields.  
   For more guidance, see [Create a filter](https://www.servicenow.com/docs/access?context=t_CreatingFilters&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US).
4. Add the filter conditions.  
   For example, Discovery source contains TSOM.
5. Select Submit.  
   The filter is created.

## Resultado

You can use the filter in the logical connection audit.
**Conceitos relacionados**   

* [System components installed with Telecom Discrepancy Identification \& Reconciliation](https://servicenow-prod.fluidtopics.net/YVXtqgVjk9AaeaTdp6tVLg "The system properties are part of the TSOM Visibility plugin (sn_tsom_core) and control the Telecom Discrepancy Identification & Reconciliation log (TSOM CMDB Audit). The TSOM Visibility plugin serves as an enabler for the TSOM Visibility applications, containing logic that is shared across the Telecom Discovery and Telecom Discrepancy Identification & Reconciliation solution.")  
**Tarefas relacionadas**   

* [Run Telecom Discrepancy audit](https://servicenow-prod.fluidtopics.net/5mRM0tcwRVFc4Tgjl1B_aA#run-audits "The Telecom Discrepancy Audit validates the integrity of configuration items (CIs) and relationships across your telecom inventory using the CMDB Compliance framework.")
* [Example for Telecom Discrepancy Audit and Remediation](https://servicenow-prod.fluidtopics.net/5mRM0tcwRVFc4Tgjl1B_aA#example-for-telecom-discrepancy-and-reconciliation "The following example illustrates how the audit works in a scenario.")
* [Configure attribute value discrepancy in CMDB 360](https://servicenow-prod.fluidtopics.net/3tUL229ZCdQS11xxzb9TYQ "Configure attribute comparison settings in CMDB 360 to detect data inconsistencies across multiple discovery sources.")
* [Control CI attribute updates using Reconciliation rules](https://servicenow-prod.fluidtopics.net/WBroU3wALwNONjdclpxhwA "To prevent specific attributes of a Configuration Item (CI) from being overwritten by Discovery or other data sources, use Reconciliation Rules. These rules define which data source is trusted to update a particular attribute when multiple sources provide values.")