In this article, we’ll walk you through how to set up and manage your integration with WIZ. WIZ is a leading cloud security platform that continuously scans your cloud environments to detect misconfigurations, vulnerabilities, and potential risks. It helps organizations prioritize what matters most by focusing on the issues and vulnerabilities that pose real threats to business assets.

Before starting the integration, it’s important to make sure you have everything prepared. You’ll need to provide a service account in WIZ with the appropriate permissions, as this account will be used to establish the connection between WIZ and Hyver. The integration relies on an authentication process — a secure way for Hyver to verify that it has permission to access data from your WIZ account. In practice, this means supplying valid credentials so Hyver can safely connect to WIZ and retrieve issues and vulnerabilities.

To get started, you must get the following from WIZ. Please follow the instructions in the WIZ documentation to get the following details*:

*Later in this article, we’ll see exactly how to configure each of these details in practice.

For the integration to work smoothly, you may need to allow traffic from Hyver’s servers in your firewall or network configuration. This ensures that Hyver can securely connect to your environment and perform scans without being blocked.

Depending on your region and the type of scan, add the following IP addresses:

In most cases, you only need to add the IPs relevant to your region and use case.

This section explains how Hyver’s Multi-Company Dashboard works in general, and how integrations behave when used in a Multi-Company setup.

Hyver’s Multi-Company Dashboard is designed for large enterprises with multiple subsidiaries. It gives you:

To enable Multi-Company, contact your CYE Technical Account Manager.

Here’s the important part:

To get the most out of Multi-Company with integrations, we recommend:

At this stage, we’ll focus on how to obtain the connection details you’ll need in Hyver, as outlined in the prerequisites:

To generate these, you’ll first need to create a service account in WIZ. Here’s how:

Once complete, WIZ will display the Client ID and Client Secret.

To find the API URL in WIZ:

The API Endpoint URL will be displayed on this page.

To enable the integration, you’ll need to assign the correct permissions to the Hyver service account in WIZ. These permissions ensure that Hyver can securely access the issues and vulnerabilities data required for analysis. Without the right permissions, the integration will not function properly.

Configure a User in WIZ with These Permissions:

Also, ensure that you leave the Projects optional field empty:

On the Hyver side, completing the integration is a simple and straightforward process. All you need to do is take the relevant details from WIZ and enter them into the corresponding fields in Hyver. Once these fields are filled in correctly, the connection between the two platforms is established and ready to use.

Now, authenticate to WIZ:

Then:

Once the integration is up and running, the findings collected from WIZ appear on the Findings page in Hyver. From there, you can review the issues and vulnerabilities detected, track their status, and explore how they connect to your business assets. This view lets you easily manage and prioritize findings as part of your overall risk analysis.

Use the findings filter to filter by various finding fields such as sources or creation date:

For example:

If you do not see findings populated after some time, please verify connectivity to Wiz.

When Hyver integrates with WIZ, it collects data from specific WIZ “endpoints.” These endpoints are simply categories of information that WIZ makes available through its API. For this integration, the relevant endpoints are:

When possible, Hyver automatically updates the status of remediation assets (such as servers or settings) once they are fixed or removed in the source system — no manual updates needed. The status of a finding is determined by the status of its remediation assets. This integration supports Auto-fix for WIZ issues findings only (which make up most of the findings). It does not support Auto-fix for WIZ vulnerabilities.

In this section, we will understand what types of findings are involved in the WIZ integration. We will also review the mapping logic behind the integration mechanism, and see how Hyver handles the findings it receives from WIZ.

WIZ vulnerabilities and misconfigurations are added as findings in Hyver. Findings are added to the Integration with external tools engagement.

Hyver maps CVEs (from the "vulnerabilities" API) from WIZ to the Usage of Outdated and Vulnerable Technologies finding.

Hyver’s goal is to map incoming findings to its own taxonomy whenever possible.

When no direct Hyver match exists, the finding is still useful by aligning it with the NIST Cybersecurity Framework.

This approach:

You should continue to follow Hyver's Recommended Priority for triaging findings.
The prioritization logic remains consistent—regardless of whether a finding is mapped to a native Hyver category or added directly from WIZ.

You can delete or edit this integration:

Following the setup of an integration, you can delete an integration:

When you delete an integration in Hyver, the connection is immediately terminated. No new data from the deleted integration is ingested or processed, and the existing data in Hyver is retained.

Following the setup of an integration, you can edit an integration:

In this guide, we walked through the full process of integrating WIZ with Hyver — from setting up the connection with the correct service account and permissions, to understanding the specific data collected. We also covered what happens when the integration is deleted and what to do with the remaining reports on the WIZ side. With everything in place, your integration should run smoothly and support your security analysis with accurate, relevant data.