---
sourceDocument: Zurich Impact
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/impact

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Scan Engine integrations

# Scan Engine integrations {#ariaid-title1}

* Release version: Zurich
* 
* Updated October 20, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

You can integrate the Scan Engine into a variety of processes, such as the syncing of definitions or exception reasons, as well as integrating with your existing agile project management systems.

Scan Engine has the ability to integrate with your other environments running Impact so that you can:

* Compare technical debt across instances
* Sync custom definitions across instances
* Enable approvals for finding exceptions in production
* Create user stories from findings

The following integrations are available for the Scan Engine.
{#instance-integration-scan-engine__table_i33_xr5_3hc__entry__2}

| Integration | Description |
|-|-|
| [Definitions integration](https://www.servicenow.com/docs/madBrtKnaiRy8~noxmYKjA "You can push changes made to definitions, or new definitions between development and production environments to synchronize the definition ruleset.") | Allows users to synchronize definition overrides and custom definitions between sub-production and production instances. Ensuring a consistent ruleset is being applied throughout the instance stack. |
| [Exception reason integration](https://www.servicenow.com/docs/BovPxJI4M4PRSRN7gwQQrQ "You can synchronize exception reasons from sub-production to Production instances once a record is created or updated.") | * Synchronizes exception reasons between sub-production and production instances. * Facilitates the approval or rejection of exception reasons in the production environment. {#instance-integration-scan-engine__ul_j33_xr5_3hc} |
| [User story integration](https://www.servicenow.com/docs/fkN1M_M~uRf~Bw9W_Hv9Pg "With Scan Engine, you can create agile tasks and stories directly from finding records using the multiple integration options.") | Creates tasks for findings from a ServiceNow instance to: * ServiceNow production Instance * Jira * Azure DevOps * Others {#instance-integration-scan-engine__ul_l33_xr5_3hc} |
| [Update set integration](https://www.servicenow.com/docs/pIydY_DffBOSW93aposKLQ "Scans performed on update sets automatically sync from Developer to Production instances defined in My SN Instances once the update set scan is marked complete.") | Synchronizes update set summary scans to the production instance from instances where this integration is enabled. |
| [AES/AEMC integration properties](https://www.servicenow.com/docs/4EuGyneHzK7uJYyn1QMd1A "The AES/AEMC integration provides automated governance for custom application deployments by validating the scoped applications against admin-defined conditions before approval. When a developer submits a deployment request from App Engine Studio or ServiceNow Studio, the system automatically runs compliance checks using the Scan Engine to ensure all required rules are met. If the are not, it blocks the deployment.") | Provides automated governance for custom app deployments by validating deployment requests against admin-defined conditions before approval. When a developer submits a deployment request, the system automatically runs compliance checks to ensure all required rules are met, blocking deployment if conditions fail. |
[Table 1. Scan Engine integrations]

{#instance-integration-scan-engine__table_i33_xr5_3hc}  
Note:  
Except for Jira, Azure DevOps and AES/AEMC integration types, you must first register your instances as part of My SN Instances. You will then need to configure either your basic or OAuth authentication methods for your instances to enable synchronization.