---
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


---

# Configure application scanning properties

# Configure application scanning properties {#ariaid-title1}

* Release version: Australia
* 
* Updated August 11, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

The Scan Engine provides options to configure application scanning and enhance
governance over Team Dev push approval. Configure which applications are scanned, the
parameters applications must have to satisfy Team Dev approval, and whether developers can
use Suite Scans for faster, focused validation.

## Before you begin

Applications are scanned in Team Dev workflows during the following scenarios:

* On-demand scan before push approval
* Team Dev review process with automatic scanning
* Application validation for governance rules

Role required: scan_engine_admin

## About this task

Set filter conditions that
align with your Team Dev governance requirements. Different applications may require
different criteria based on their risk profile and deployment targets.{#configure-application-scanning-properties__configure-application-scanning-properties-context-1}

## Procedure

1. Navigate to ALLImpactConfigurationScan Engine Properties.
2. Select the Dev Team tab.
3. In the Table for application scanning condition field, verify the table reference.  
   This field specifies which table the scan condition builder references. By
   default, this is the Custom Applications \[x_snc_sys_app_app\] table and is
   typically not changed.
4. Configure the application scanning condition using the condition builder.  
   The Scan Engine uses these defined conditions to determine which applications
   to include in scans. By default, conditions are set to filter out system
   applications and include only active, custom applications.

   You can add and configure additional filter conditions by selecting
   Add filter condition. You can also add and
   configure OR clauses by selecting Add OR clause.  
   Tip:  
   You can append filter conditions and OR clauses to existing conditions by selecting the AND or OR options next to them.
5. Select the Enable Team Dev push approval enforcement check box to require applications to meet approval conditions before push.  
   When enabled, applications must meet the conditions specified in the
   Conditions for Team Dev push approval field.  
   Warning:  
   Team Dev reviewers may be blocked from approving pushes until scanning validation is satisfied.
6. Configure the conditions for Team Dev push approval using the condition builder.  
   Typical criteria include:
   * Finding severity limits
   * Restricted module rules
   * Definition suite alignment
   * Custom governance conditions
7. **Optional:** Configure additional application scanning options.  
   {#configure-application-scanning-properties__entry__2}

   | Field | Description |
   |-|-|
   | Enforce completion criteria for application scans | * When selected, applications must meet the conditions specified in the Conditions for completing application scans field. * Distinct from Team Dev push approval enforcement. * Allows different completion criteria from approval criteria for flexible governance. |
   | Conditions for completing application scans | * Conditions used to determine if an application scan is complete or resolved for internal tracking. * Typically used to mark an application as scanned and passed for compliance or tracking purposes. * Separate from Team Dev approval. |
   | Allow Suite Scan for applications | * Suite Scan runs only selected definitions for faster validation. * Full Scan runs all active definitions for comprehensive validation. * When selected, developers can choose between Full scan and Suite scan. * When cleared, only Full scans are available. * Enable for faster, focused validation. Clear for comprehensive validation. |
   [Table 1. Additional application scanning options]

8. Select Save.
**Related tasks**   

* [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.")
* [Initiate application scans](https://servicenow-prod.fluidtopics.net/~yH6~4JUnHte62OJvwjDwQ "Scan applications to identify definition findings before publishing to the application repository. Application scans give insight into health scores, the number of findings, and the total impact of findings within your custom applications. When Suite Scan is enabled, choose between scanning all active definitions or a curated suite.")
* [Configure update set scanning properties](https://servicenow-prod.fluidtopics.net/1ScAsbBdkKQ2Ed~Ybs6lqg "The Scan Engine provides several options to further configure update set scanning and enhance the governance over update set management. Update set scanning occurs during scheduled instance scans and when developers attempt to mark update sets complete.")

*[\>]: and then