---
sourceDocument: Australia Impact
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/impact

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Configure Scan Engine instance integration settings

# Configure Scan Engine instance integration settings {#ariaid-title1}

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

You can view and configure a variety of information, formatted into lists, that the Scan Engine uses to implement its various scanning types.

Role required: Scan Engine admin and Impact admin.

## System properties {#add-view-scan-engine-related-lists__section_wr2_nx4_ghc}

These are the properties specifically created by the Scan Engine application upon installation. Modification of these properties is performed using standard procedures in ServiceNow.

## My SN Instances {#add-view-scan-engine-related-lists__section_djg_qx4_ghc}

Each record indicates an instance connected to the current instance through API integrations.  
Hinweis:  
You must configure this to take advantage of exception processing, definition syncing, and user story tracking in Production.

1. To add an instance to the list, select New.
2. Configure the following fields and settings. {#add-view-scan-engine-related-lists__table_aj5_vx4_ghc__entry__2}

   | Field/Setting | Description |
   |-|-|
   | Instance Name | The name of the instance. |
   | Instance URL | The URL of the instance. |
   | Environment | The instance environment: * Development * Production * Test {#add-view-scan-engine-related-lists__ul_bj5_vx4_ghc} Wichtig: Only one instance can be listed as Production. Otherwise, the integration will fail. |
   | Validated | * Indicates whether the instance has been successfully validated using the UI Action provided in the configuration interface. * You can use the Validate Connection action available on the instance configuration form to attempt a live connection to the target instance using the defined credentials and connection parameters. If successful, the instance is flagged as Validated = true. {#add-view-scan-engine-related-lists__ul_ej5_vx4_ghc} |
   | Connection Status | * Represents the current state of connectivity between local and remote instances. * This field is automatically updated based on the results of the validation process. It reflects the outcome of the live connection test and cannot be edited. * The following values are supported: * Approvals not configured in production * Authentication method is not configured * Connection Valid * Connection Invalid * API User is missing role * User not setup on target instance {#add-view-scan-engine-related-lists__ul_jj5_vx4_ghc} These values help diagnose integration issues, as well as help with corrective actions. {#add-view-scan-engine-related-lists__ul_gj5_vx4_ghc} |
   | Authentication Type | The instance's authentication type: * Basic * OAuth {#add-view-scan-engine-related-lists__ul_pj5_vx4_ghc} |
   | API Credential Config | * This field references the credential record used for authentication when Basic is selected as the Authentication Type. * It typically points to a Basic Auth credential stored securely in the system. {#add-view-scan-engine-related-lists__ul_rj5_vx4_ghc} |
   | OAuth Application Registry | * The OAuth application registry used for cross-instance integrations. * This field is only available if OAuth was selected as the Authentication Type. {#add-view-scan-engine-related-lists__ul_tj5_vx4_ghc} |
   | OAuth User Profile | The OAuth user profile used for cross-instance integrations. |
   [ ]

   {#add-view-scan-engine-related-lists__table_aj5_vx4_ghc}

{#add-view-scan-engine-related-lists__ol_iv4_rx4_ghc}  
Hinweis:  
See [Scan Engine integrations](https://servicenow-prod.fluidtopics.net/W3PbMYso1e7JqJntFddSGQ "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.") for details on integration setup.