Skip to main content

Overview

Wiz knows which cloud identities and machines are risky - exposed, over-privileged, holding sensitive data, or behaving suspiciously. Venice discovers them and shows who can reach them. The Wiz connector brings the two together: Venice reads the Wiz Issues raised on the identities and machines it already discovers, matches each Issue to the Venice Principal or Resource it belongs to, and shows it on that target’s page. Once connected, the Issues tab of a Principal, Identity, or Resource lists its Wiz Issues alongside the findings Venice raises itself, each with its source, severity, and category, and a link to open the Issue in Wiz. The connector is read-only. Venice reads Issues from Wiz and does not change anything in your Wiz tenant.
The Wiz connector enriches the targets Venice already discovers through its other data connectors, such as AWS, Microsoft Services, GCP, Okta, Salesforce, and Snowflake. Configure the connector for the platform whose targets you want enriched first, so the identities and machines exist in Venice for Wiz Issues to attach to.

Prerequisites

Before you begin, make sure you have:
  • A Wiz tenant with the Venice integration added. Add it from the Venice integration tile in the Wiz portal, following Wiz’s setup guide.
  • The Venice data connector for the platform whose targets you want enriched - AWS, Microsoft Services, GCP, Okta, Salesforce, or Snowflake - already configured and scanned.
  • A user with the Tenant Admin role or Data Connectors Integrator in Venice.

Configuration Steps

Venice authenticates to Wiz with the Client ID and Client Secret of the Venice integration in Wiz, and reads Issues through the Wiz API. Every connector connects to one Wiz tenant.
Have the Client ID, Client Secret, and API Endpoint URL that Wiz provides for the Venice integration ready before you start. For anything on the Wiz side, see Wiz’s setup guide for the Venice integration.
1

Configure connector in Venice

  1. From the Venice portal Data Connectors page: https://app.venice.io/data-connectors
  2. Configure a new connector, “Wiz”
  3. Enter a Connector Name to identify the connector on the Venice platform, for example wiz. This name does not affect your Wiz tenant.
  4. Optionally, click + Add Description
  5. Provide the Client ID and Client Secret of the Venice integration in Wiz
  6. Provide your Wiz tenant’s API Endpoint URL, for example https://api.us17.app.wiz.io/graphql. The URL depends on the data center that hosts your Wiz tenant.
  7. Provide the Authentication URL that matches your Wiz tenant:
2

Validate and save

Click Test Connector, then click Save Configuration.
Test Connector requests a token from the Authentication URL and runs one Issues query against the API Endpoint URL. If the test fails, Venice shows what to check and, underneath it, the exact response returned by Wiz. Keep the Wiz response at hand when working with Wiz support.

How Wiz Issues Appear in Venice

Which Issues are synced

Venice syncs Wiz Issues of Critical and High severity raised on the identities and machines it already discovers. Each Issue is matched to its Venice target by the cloud identifier that Wiz and Venice both hold. A Wiz Issue raised on a Principal also appears on the Identity that owns it, so a person’s page shows the Wiz risk of every account they hold.

The Issues tab

Open a Principal, Identity, or Resource and select the Issues tab. Wiz Issues are listed next to Venice’s own findings, sorted by severity:
  • Source - Venice or Wiz. Wiz Issues carry the Wiz logo.
  • Name - the Wiz control that raised the Issue.
  • Severity - the Issue’s severity in Wiz.
  • Category - the Venice category the Issue maps to.
  • User - on an Identity page, the account the Issue was raised on.
Click View in Wiz on a row to open the Issue in Wiz for the full details and Wiz’s remediation guidance. Filter by Source, Severity, or Category to focus on Wiz Issues alone, or to see every Issue in a single category across both sources.
Wiz groups its controls into risk-assessment categories and sub-categories. Venice maps each one to a Venice category, so Wiz and Venice findings are filtered and compared on the same scale. When a Wiz Issue maps to more than one category, the most important one is shown first.

Keeping Issues current

Venice reads new and changed Issues from Wiz on the connector’s scheduled scans, so the Issues tab reflects what Wiz reported at the last sync.
  • An Issue that is resolved or rejected in Wiz is removed from the target’s Issues tab on the next sync.
  • A target that is no longer in Venice no longer shows its Wiz Issues.
  • When the connector is disabled, the Issues already synced stay as they were at the last sync. When the connector is deleted, Wiz Issues are no longer shown.
Users with the Tenant Admin or Auditor role see the Issues tab.

Managing the connector

Opening an existing Wiz connector shows its configuration in read-only mode, with an Enabled / Disabled status. If the last scan or the last connection test failed, the reason is shown at the top of the page, with the response returned by Wiz. Venice re-tests the connection automatically every 30 minutes. The result is reflected in the status indicator on the Configured Connectors list.

Edit the connector

Editing is deliberately constrained. After creation you can change the Connector Name and the Description. The Client ID, Client Secret, API Endpoint URL, and Authentication URL are locked, because changing any of them would mean a materially different connection. The Client Secret is stored securely in Venice and never displayed again. To connect a different Wiz integration or tenant, or to use new credentials after the integration’s credentials change in Wiz, delete the connector and configure a new one.

What Venice Monitors

Once connected, Venice will provide insights into:

Wiz Risk on Discovered Targets

See the Critical and High Wiz Issues raised on each Principal and Resource Venice discovers, on the target’s own page, with the Wiz control name, severity, and category.

Identity-Level Risk

Review Wiz Issues rolled up from a person’s accounts to their Identity, so reviewers see the risk of the human behind the accounts.

Unified Findings

Compare Wiz and Venice findings in the same Issues tab, on the same severity and category scale, each attributed to its source.

Issue Lifecycle

Track Wiz Issues as they are raised, resolved, or rejected in Wiz, with each target’s Issues tab reflecting the latest sync.

Troubleshooting

The test result shows what to check, followed by the exact response from Wiz. Check that:
  • The Client ID and Client Secret are correct and belong to the Venice integration in Wiz. If you no longer have the secret, configure a new connector with new credentials for the Venice integration.
  • The Authentication URL matches your Wiz tenant type - Commercial, Gov (FedRAMP), or Commercial hosted on AWS GovCloud.
  • The API Endpoint URL belongs to your Wiz tenant. A URL from another data center is rejected by Wiz.
  • The Venice integration is still active in Wiz. For anything on the Wiz side, see Wiz’s setup guide for the Venice integration or contact Wiz support.
Wiz Issues appear on a target only when Venice can match the Wiz entity to it. If an Issue you expect is missing, one of the following is usually the cause:
  • The target is not in Venice yet. Venice matches Wiz entities to the Principals and Resources discovered by its own data connectors. Configure and scan the connector for that platform first.
  • The Issue is below High severity. Venice syncs Critical and High Wiz Issues.
  • The entity type is not matched. Venice matches the identity and machine types listed under Which Issues are synced.
  • The next scan has not run yet. New Issues in Wiz, and targets newly discovered in Venice, are matched on the next scheduled scan.
Venice reflects Wiz’s status at the last sync. An Issue resolved or rejected in Wiz is removed from the Issues tab on the next scheduled scan.
Open the connector to read the failure reason and the response returned by Wiz. Common causes are credentials that were revoked or rotated in Wiz, and an integration whose project scope no longer covers the projects the connector reads. Once the cause is resolved on the Wiz side, click Test Connector to confirm the connection before the next scan.

Next Steps

Once your Wiz connector is set up, you can:

Access Security Dashboard

View Wiz Issues on your Principals, Identities, and Resources in the Venice dashboard.