---
sourceDocument: Brazil Enable AI
sourceDocumentLink: https://www.servicenow.com/docs/r/intelligent-experiences

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Enable AI

ft:clusterId :

    - platai

bundleId :

    - platai

workflow :

    - Platform


---

# Configure Veza access intelligence in the agent map

# Configure Veza access intelligence in the agent map {#ariaid-title1}

Release version: Brazil  
Updated September 8, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Integrate Veza with ServiceNow using OAuth 2.0 to display agent risk scores and severity levels in the agent map.
Veza access intelligence requires a connection between ServiceNow and each hyperscaler that hosts governed AI assets. ServiceNow and Veza each maintain separate connections to hyperscalers to retrieve and correlate AI asset
data. Access intelligence supports governed agents hosted by Amazon Web Services (AWS), Gemini Enterprise Agent Platform, Azure AI Foundry, and Salesforce.

Complete the following in order:

1. In your Veza tenant, configure integrations for all of the supported hyperscalers that you want to connect to. For more information, see [Veza integrations](https://docs.veza.com/4yItIzMvkpAvMVFAamTf/integrations/integrations).
2. In AI Control Tower, navigate to SettingsIntegrationsConnectors to configure integrations for the same hyperscalers. For more information, see [Create an AI connection for discovery](https://www.servicenow.com/docs/Kkl~AumxLlbuEyXSE5reUA "Bring AI assets from an external platform into your AI asset inventory by creating an AI connection. AI Control Tower authenticates to the platform using your credentials and imports assets on a schedule, so they're governed and monitored alongside AI systems built natively on ServiceNow.").
3. The Veza connector itself authenticates using OAuth 2.0 only. Configure OAuth in your Veza tenant. See [Configure OAuth in Veza](https://www.servicenow.com/docs/7G2cQTN0PxCykr9aDhj8bQ "Create an OAuth 2.0 client and an OAuth 2.0 app in your Veza tenant so that AI Control Tower can authenticate to Veza using OAuth 2.0 instead of an API key.").
4. Configure OAuth in the ServiceNow platform and link it to the pre-provided <kbd class="ph userinput">SN AI Security Veza Connector</kbd> connection alias. See [Configure OAuth for Veza in ServiceNow](https://www.servicenow.com/docs/eIK_L7EyQZq4B0e987rX2g "Set up two application registries, their OAuth entity scopes and credentials, then link them to the pre-provided connection alias, so that AI Control Tower can authenticate to Veza using OAuth 2.0.").
5. Create the AI connection for Veza in SettingsIntegrationsConnectors. See [Create an AI connection for Veza access intelligence](https://www.servicenow.com/docs/FHRGJNsJnYwPZkHUkrGBdQ "Connect AI Control Tower to Veza using OAuth 2.0 so that agent risk scores and severity levels from Veza access intelligence appear in the agent map. Since Veza is an enrichment connector, it doesn't import new assets.").
Once configured, select an AI asset in the agent map and view the Access intelligence tab to see risk score and other information. If your token has expired or you haven't yet authenticated, select Re-Authenticate
on that tab. See [Discover your agent network with the map](https://www.servicenow.com/docs/CV8y3VVCjI7z1ADwhS8QWA "Use the agent map to visualize your entire agentic ecosystem, including ServiceNow and third-party AI assets.").  
Tip:  
If your AI asset appears in the agent map but doesn't have information shown in the Access intelligence tab, make sure that it's a governed asset with `external_ref_id` populated and `model_category=Agentic AI`.
* **[Configure OAuth in Veza](https://www.servicenow.com/docs/7G2cQTN0PxCykr9aDhj8bQ)**   
  Create an OAuth 2.0 client and an OAuth 2.0 app in your Veza tenant so that AI Control Tower can authenticate to Veza using OAuth 2.0 instead of an API key.
* **[Configure OAuth for Veza in ServiceNow](https://www.servicenow.com/docs/eIK_L7EyQZq4B0e987rX2g)**   
  Set up two application registries, their OAuth entity scopes and credentials, then link them to the pre-provided connection alias, so that AI Control Tower can authenticate to Veza using OAuth 2.0.

*[\>]: and then