Skip to main content
Cortex connects to many third-party vendors whose system interfaces frequently change. As a result, integration behavior or configuration steps may shift without notice. If you encounter unexpected issues, check with your system administrator or refer to the vendor’s documentation for the most current information. Additionally, integration sync times vary and are subject to scheduling overrides and timing variance.
Wiz is a security platform that allows teams to find and fix issues in their code. Cortex integrates with Wiz to bring cloud and container vulnerabilities into your catalog. Integrating Wiz with Cortex allows you to:

​
How to configure Wiz with Cortex

​
Prerequisites

Before getting started:

​
Configure the integration in Cortex

  1. In Cortex, navigate to the Wiz integration settings page:
    1. Click Integrations from the main nav. Search for and select Wiz.
  2. Click Add configuration.
  3. Configure the Wiz integration form:
    • Client ID and Client secret: Enter your client ID and client secret from Wiz.
    • Tenant data center: Enter the data center from Wiz.
    • Authentication provider: Select your authentication provider. You can confirm the provider in Wiz under User Settings > Tenant.
  4. Click Save.
If you see a “No address associated with hostname” error, verify that you have entered the correct authentication provider.

​
How to connect Cortex entities to Wiz

​
Match entity names to Wiz projects

By default, Cortex will use the Cortex tag (e.g. my-service) as the “best guess” for Wiz project. For example, if your entity name is “My Service” or your tag is my-service, then the corresponding project name in Wiz should also be My Service or my-service. If your Wiz project names don’t cleanly match the Cortex entity name or tag, you can override this in the Cortex entity descriptor.

​
Considerations for mapping Wiz projects to entities

Expand the tile below to see how Cortex customers have modeled their data when mapping Wiz projects to entities.
Domain-level auto-mappingSome customers organize their Cortex domain structure to match their Wiz projects, enabling auto-mapping across domains based on their name.For example:
  • Cortex domain entity name: Engineering project
    • Entity tag: engineering-project
  • Wiz project name: Engineering project
Auto-mapping across multiple integrationsSome customers organize multiple integrations to use consistent names and tags across all of them.For example:
  • Cortex domain entity name: Engineering project
    • Entity tag: engineering-project
  • Wiz project name: Engineering project
  • Jira project name: engineering-project
    • When you integrate Cortex with Jira, Cortex will tie Jira tickets to entities by searching for any tickets where the label, component, or project field for the work item includes the Cortex tag.
Service-level auto-mapping based on repo structureSome customers use a standardized repository naming convention that makes service-level auto-mapping simple and automated to the Wiz projects.For example:
  • Repository name: engineering/integrations/eng-repo
  • Cortex domain entity name: Eng Repo
    • Entity tag in Cortex: eng-repo
  • Wiz project name: eng-repo

​
Editing the entity descriptor

Define the following block in your Cortex entity descriptor:

​
Using the Wiz integration

​
View Wiz information on entity pages

On an entity details page, you’ll see Wiz issues, listed by risk level, under the Code and Security header. In the entity’s sidebar, click Code & Security > Wiz to view a list of Wiz issues including their severity, status, basic details, and a link to view the issue directly in Wiz: View Wiz issues on the entity details page under Code & security.

​
Scorecards and CQL

With the Wiz integration, you can create Scorecard rules and write CQL queries based on Wiz projects. See more examples in the CQL Explorer in Cortex.
Check if entity has a registered Wiz project in its entity descriptor.Definition: wiz (==/!=) null: BooleanExampleAn initial level in a security Scorecard might include a rule to make sure entities are associated with Wiz project:
Setting a wiz != null rule can also serve as a secondary check to confirm an entity is synced properly with Wiz and is reporting frequently.
List of Wiz issues, filterable on severity and statusDefinition: wiz.issues(): ListExampleThe Scorecard’s top level might include a rule to ensure that entities have fewer than 3 issues in OPEN status:
You could set rule to verify an entity has less than 10 issues with a HIGH or CRITICAL severity:
You can write a rule to verify an entity has less than 25 issues:

​
View integration logs

This feature is available in Cortex cloud.
While viewing an integration’s settings page, select the Error logs tab to view errors from the last 7 days. You can filter the logs list by configuration and by operation (for example, you could filter to view errors surfaced only via Scorecards).
The 'Logs' tab on an integration's settings page shows error information over the past 7 days.
Click into a row to get more information, including time stamp, status code, full error, and request path.

​
Still need help?↗

The following options are available to get assistance from the Cortex Customer Engineering team:
  • Email: help@cortex.io, or open a support ticket in the in app Resource Center
  • Slack: Users with a connected Slack channel will have a workflow added to their account. From here, you can either @CortexTechnicalSupport or add a :ticket: reaction to a question in Slack, and the team will respond directly.
Don’t have a Slack channel? Talk with your Customer Success Manager.
Last modified on September 9, 2026