--- sourceDocument: Australia Impact sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/impact Release : - australia ft:locale : - en-US ft:publication_title : - Australia Impact ft:clusterId : - ipact bundleId : - ipact --- # Customize Scan Engine definitions # Customize Scan Engine definitions {#ariaid-title1} * Release version: Australia * * Updated July 27, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read You can toggle the Active status of a definition or modify an existing definition to further customize and refine its scanning criteria. ## Before you begin For the complete list of Scan Engine definitions, see [Scan Engine definitions](https://servicenow-prod.fluidtopics.net/KYuMN2XXHsANH1ZwH_MQpw "The Scan Engine uses a large set of definitions to correct coding and workflow findings in real-time and perform scans across your entire instance to detect existing findings."). Role required: Scan Engine admin (`sn_se.scan_engine_admin`). Scan Engine admins can toggle the Active field on any definition without using the override function. To modify other definition properties, you must use the Override Definition option. Any user with the Scan Engine user role can view definitions. ## Procedure 1. Navigate to ALLImpactPlatform HealthDefinitions. 2. Select a definition number to open its details. 3. To deactivate a definition without overriding, uncheck the Active checkbox. The Active field is editable without requiring an override. Unchecking this field deactivates the definition so it will no longer run in any scan type. No other changes to the definition are needed. 4. To modify other definition properties, select Override Definition. When a definition is overridden, the base system definition will no longer be used in any scan type (real-time, scheduled, update set, application, or on demand). All fields in the overridden definition become editable. You can then modify the required and optional fields. Refer to [Create custom Scan Engine definitions](https://servicenow-prod.fluidtopics.net/dW24Rs1_RuNlNKDYORo60g#create-scan-engine-definitions "The Scan Engine contains preexisting base system definitions. In addition to these definitions, you can create your own.") for complete field details. 5. When updating an overridden definition, review the override field information. * The Override field is only visible if a base definition has been overridden using Override Definition. * Deleting an overridden definition re-enables the base system definition. * Overridden definitions are considered custom definitions. As a result, they are included in the count of 10 active custom definitions limit for Guided customers. {#view-modify-scan-engine-properties__ul_eq3_d1c_jhc} 6. Select Update. Related lists appear at the bottom of the definition screen. | Option | Description | | Applicable Tables | Displays all tables scanned by the definition, as well as the conditions table records must match to be scanned. To add a table to the list: 1. Select New. 2. In the New Applicable Table form, define the potential tables to scan: * Definition: The definition that applies to this record. For the table defined in this record, if the condition matches, the definition in this field will record a finding. * Table: Specific table that the definition runs against. * Configuration tables: Definitions run against tables that extend the application file (sys_metadata). Scans of these tables can be monitored in real time. * Non-configuration tables: Definitions run against all other tables. Scans of these tables cannot be monitored in real time and will only be seen in the results of an update set, application, or other on-demand scan. {#view-modify-scan-engine-properties__ul_psw_ykx_2hc} * Global Scope: Some global tables have a type of restricted access, called Caller Restriction. Special handling is required to access these tables from the Scan Engine scope. See [Restricted Caller Access](https://www.servicenow.com/docs/access?context=restricted-caller-access-privilege) for more information. * Conditions: Defines the conditions that table records must meet in order to be scanned. {#view-modify-scan-engine-properties__ul_rxz_5kx_2hc} {#view-modify-scan-engine-properties__ol_rtp_rkx_2hc} | | Findings For This Definition | Displays any findings, as established by the definition, found during on-demand or scheduled scans. | | Resolved Finding Histories | Shows findings that were resolved for this definition. | | Scan Engine Suites | Displays all suites assigned to the definition, which allows for scanning entire suites of definitions. Suites are also used in reporting within the Analytics Dashboard. For more information, see [Customize Scan Engine definition suites](https://servicenow-prod.fluidtopics.net/pKXcsp_Hre6e43l_VSMZ9A#create-scan-engine-definition-suites "Follow these steps to create or modify Scan Engine definition suites."). To assign suites to a definition: 1. Select Edit. 2. In the Edit Members form, assign one or more suites to a definition: * Collection: List of available suites that can be assigned to a definition. * Scan Engine Suites List: Assigned suites for the current definition. {#view-modify-scan-engine-properties__ul_e24_jmx_2hc} {#view-modify-scan-engine-properties__ol_wvw_gmx_2hc} | |-|-| {#view-modify-scan-engine-properties__choicetable_fkk_pkx_2hc} * **[Create custom Scan Engine definitions](https://servicenow-prod.fluidtopics.net/dW24Rs1_RuNlNKDYORo60g#create-scan-engine-definitions)** The Scan Engine contains preexisting base system definitions. In addition to these definitions, you can create your own. * **[Customize Scan Engine definition suites](https://servicenow-prod.fluidtopics.net/pKXcsp_Hre6e43l_VSMZ9A#create-scan-engine-definition-suites)** Follow these steps to create or modify Scan Engine definition suites. * **[Create policies for Scan Engine](https://servicenow-prod.fluidtopics.net/JeRkbWDgbs7kFJ6n35xIAQ)** Policies let you determine how specific definition findings appear on analytics dashboards; you can ignore them completely or place them in a prioritized view. *[\>]: and then