---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Data Discovery jobs

# Data Discovery jobs {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Data Discovery reviews your targeted information using user-defined data patterns and target tables.
Data Discovery works by first scheduling a job in the Data Discovery Job section. When a scheduled job runs, all active data patterns are searched for on the current target tables. For more information on creating and configuring a Data Discovery job, see [Configure a Data Discovery job](https://servicenow-prod.fluidtopics.net/GW429iTIUN0u5V9C6CyS~g "Configure a Data Discovery job and review the status of ongoing jobs. A Data Discovery job defines when a pattern is executed on a target table.").  
Hinweis:  
Sample Scan jobs scan up to 10,000 records are scanned per table per pattern.  
Warnung:  
If a job is executed twice in a small amount of time, the number of scanned rows may return 0 for second run.

## Data Discovery data patterns {#data-discovery-jobs__section_yqm_2jl_gxb}

The Data Patterns section shows all current data patterns, both active and inactive. A data pattern is a regular expression used to match sensitive data. For more information on how to access and configure
data patterns, see [Configure Data Discovery patterns](https://servicenow-prod.fluidtopics.net/hXtRWb_tFuo_aR7pQD9zjQ "Configure a Data Discovery pattern and review current patterns. A Data Discovery pattern defines the regular expression used to match data against a target table."). The Active Data Patterns section shows only active patterns. Inactive patterns don't appear.

## Target tables {#data-discovery-jobs__section_zv4_xhl_gxb}

The Target Tables section lists all tables that can be processed for a job. To access the target tables, select Target Tables.  
The following tables aren't supported:

* sr
* sysx
* v
* sh$
* syslog
* ua
* usageanalytics
* ecc
* clone
* jrobin
* pa
* sla_repair_log
* scan
* gcf
* fm_log
* log
* np$
* sn_data_discovery
* dp_configuration
* dp_federated_job
* dp_field_technique
* dp_job
* dp_job_summary
* dp_primary_reference
* dp_technique
* data_classification
* m2m_dictionary_dataclass
{#data-discovery-jobs__ul_otf_p2s_3xb}

## Granular Configuration {#data-discovery-jobs__section_xzy_t4t_dcc}

The [Granular Configuration](https://servicenow-prod.fluidtopics.net/sRxtoxRCXrjHADTPX9H55A "Granular scan can be used to scan specific table columns for discovery. Traditional Data Discovery jobs scan the entire table to discover data, whereas granular scan targets specific columns of the table thereby offers more control over the discovery process") tool enables more specific and fine tuned controls for discovering sensitive data in a table. However there are key differences in its operation compared to a
traditional data discovery job. A granular configuration scans only specified columns of a table for discovery, reporting its findings by the record. Findings from the scan of Granular Configurations, called Granular Findings have
their actions specified per record, and require the data_privacy_admin role to be anonymized.