Skip to main content

Check out Port for yourself ➜ 

Wiz

Loading version...

Port's Wiz integration allows you to model Wiz resources in your software catalog and ingest data into them.

Overview

This integration allows you to:

  • Map and organize your desired Wiz resources and their metadata in Port (see supported resources below).
  • Watch for Wiz object changes (create/update/delete) in real-time, and automatically apply the changes to your entities in Port.

Supported resources

The resources that can be ingested from Wiz into Port are listed below.
It is possible to reference any field that appears in the API responses of the GET requests for these resources in the mapping configuration.

Note that Wiz's API documentation is restricted to the authenticated Wiz Documentation Portal, which requires a Wiz account to access.

  • Project
  • Issue
  • Control
  • Service ticket
  • Vulnerability
  • Repository
  • Technology
  • Hosted technology

Prerequisites

Port Credentials

To get your Port credentials, go to your Port application, click on the ... button in the top right corner, and select Credentials. Here you can view and copy your CLIENT_ID and CLIENT_SECRET:

Wiz Credentials

You need the following connection details to configure Wiz:

  • Wiz API URL (API Endpoint URL)
  • Wiz Token URL
  • Client ID and Client Secret
Wiz Token URL

There are two possible endpoints depending on your service account's identity provider:

Learn more here.


  1. Finding Your Wiz API URL:
    • Login to Wiz account.
    • Click the User Profile icon available at the top right of the screen and click the User Settings option.
    • Click the Tenant option from the left options menu.
    • The system displays the API Endpoint URL.
    • Copy and save the API URL to use while configuring the Wiz integration.

For more details, refer to the documentation


  1. Getting the Client ID and Client Secret

You must create a service account in Wiz to generate the Client ID and Client Secret. Follow the below steps to get the Client ID and Client Secret:

  • Login to Wiz with the Project Admin role.
  • Click the Settings icon available at the top-right of the page.
  • On the Settings page, Click Service Accounts from the left menu.
  • Create a Service Account:
    • Click Add Service Account.
    • Provide a descriptive Service Account Name.
    • Type: Select Custom Integration (GraphQL API).
    • Project: Choose the relevant project(s).
    • API Scopes: Select only the read:projects, read:issues, read:vulnerabilities and read:inventory permissions.
    • Click Add Service Account at the bottom of the page to save.


  • Retrieve Credentials: Wiz will display your Client ID and Client Secret.
  • Save Credentials: Copy and store them securely for use in Port.


Setup

Choose one of the following installation methods:
Not sure which method is right for your use case? Check the available installation methods.

  1. Go to the data source page in your portal.

  2. Under Select your installation method, choose Hosted by Port.

  3. Configure the Installation parameters and Advanced configuration as you wish (see below for details).

Installation parameters

Each integration requires specific parameters (such as an API token, a URL, etc.), as seen in Port's UI when installing it. Hover over the ⓘ icon next to each parameter to see more details about it.

Advanced configuration

  • During the installation process each integration may have additional settings under the Advanced configuration section in Port's UI.
    Additionally, each integration has one or more settings that can be configured after installation. To do so, click on the integration's name in the Data sources page and navigate to the Setting tab.
    Hover over the ⓘ icon next to each setting to see more details about it.

  • If the integration supports live events, the option to enable/disable them will be available in this section.

    Currently, live events are not supported for this integration.
    Resyncs will be performed periodically (with a configurable interval), or manually triggered by you via Port's UI.

    Therefore, real-time events (including GitOps) will not be ingested into Port immediately.
    Live events support for this integration is WIP and will be supported in the near future.

Port secrets

Some integration settings require sensitive pieces of data, such as tokens. For these settings, Port secrets will be used, ensuring that your sensitive data is encrypted and secure.

When filling in such a setting, its value will be obscured (shown as ••••••••). For each such setting, Port will automatically create a secret in your organization.

To see all secrets in your organization, follow these steps.

Limitations

  • The maximum time for a full sync to run is based on the configured resync interval. For very large amounts of data where a resync operation is expected to take longer, please use a longer interval.

Port source IP addresses

When using this installation method, Port will make outbound calls to your 3rd-party applications from static IP addresses. You may need to add these addresses to your allowlist, in order to allow Port to interact with the integrated service:

  • Europe (EU): 54.73.167.226, 63.33.143.237, 54.76.185.219
  • United States (US): 3.234.37.33, 54.225.172.136, 3.225.234.99

Configuration

Port integrations use a YAML mapping block to ingest data from the third-party api into Port.

The mapping makes use of the JQ JSON processor to select, modify, concatenate, transform and perform other operations on existing fields and values from the integration API.

Default mapping configuration

This is the default mapping configuration for this integration:

Default mapping configuration (Click to expand)
createMissingRelatedEntities: true
deleteDependentEntities: true
resources:
- kind: project
selector:
query: 'true'
port:
entity:
mappings:
blueprint: '"wizProject"'
identifier: .id
title: .name
properties:
archived: .archived
businessUnit: .businessUnit
description: .description
- kind: issue
selector:
query: 'true'
port:
entity:
mappings:
blueprint: '"wizIssue"'
identifier: .id
title: .entitySnapshot.name + " | " + .entitySnapshot.type
properties:
url: .id as $id | "https://app.wiz.io/issues#~(issue~'" + $id + ")"
status: .status
severity: .severity
vulnerabilityType: .type
notes: .notes
wizIssueID: .entitySnapshot.id
cloudResourceType: .entitySnapshot.type
resourceName: .entitySnapshot.name
cloudPlatform: .entitySnapshot.cloudPlatform
linkToResource: if .entitySnapshot.cloudProviderURL == "" then null else .entitySnapshot.cloudProviderURL end
cloudResourceID: .entitySnapshot.providerId
cloudRegion: .entitySnapshot.region
resourceGroupExternalId: .entitySnapshot.resourceGroupExternalId
subscriptionExternalId: .entitySnapshot.subscriptionExternalId
subscriptionName: .entitySnapshot.subscriptionName
subscriptionTags: .entitySnapshot.subscriptionTags
resourceTags: .entitySnapshot.tags
vulnerability: .entitySnapshot
createdAt: .createdAt
updatedAt: .updatedAt
statusChangedAt: .statusChangedAt
resolvedAt: .resolvedAt
relations:
projects: .projects | map(.id)
serviceTickets: .serviceTickets[].externalId
control: .sourceRule.id
- kind: control
selector:
query: 'true'
port:
entity:
mappings:
blueprint: '"wizControl"'
identifier: .id
title: .name
properties:
controlDescription: .controlDescription
resolutionRecommendation: .resolutionRecommendation
- kind: serviceTicket
selector:
query: 'true'
port:
entity:
mappings:
blueprint: '"wizServiceTicket"'
identifier: .externalId
title: .name
properties:
url: .url
- kind: vulnerability-finding
selector:
query: 'true'
port:
entity:
mappings:
blueprint: '"wizVulnerabilityFinding"'
identifier: .id
title: .name
properties:
status: .status
severity: .severity
categories: .categories
version: .version
score: .score
description: .description
detailedName: .detailedName
artifactMetadata: .artifactType
remediation: .remediation
detectionMethod: .detectionMethod
environments: .environments
link: .link
portalUrl: .portalUrl
origin: .origin
vulnerabilityExternalId: .vulnerabilityExternalId
CVEDescription: .CVEDescription
hasFix: .hasFix
hasExploit: .hasExploit
isHighProfileThreat: .isHighProfileThreat
updatedAt: .updatedAt
resolvedAt: .resolvedAt
firstDetectedAt: .firstDetectedAt
publishedDate: .publishedDate
rootComponent: .rootComponent
applicationServices: .applicationServices
relations:
projects: .projects | map(.id)
- kind: vulnerability-finding
selector:
query: '.detailedName != null and .version != null'
port:
entity:
mappings:
identifier: .detailedName + "-" + .version | gsub("[^\\p{L}0-9@_.+:\\/=-]"; "")
title: .detailedName + "-" + .version | gsub("[^\\p{L}0-9@_.+:\\/=-]"; "")
blueprint: '"sbomPackage"'
properties:
version: .version
package: .detailedName
manager: .artifactType.osPackageManager // .artifactType.codeLibraryLanguage
- kind: repository
selector:
query: 'true'
port:
entity:
mappings:
blueprint: '"wizRepository"'
identifier: .id
title: .name
properties:
url: .url
platform: .platform
public: .public
archived: .archived
visibility: .visibility
organization: .organization.id
branches: .branches | map(.id)
relations:
projects: .projects | map(.id)
- kind: technology
selector:
query: 'true'
port:
entity:
mappings:
blueprint: '"wizTechnology"'
identifier: .id
title: .name
properties:
description: .description
categories: .categories | map(.name)
usage: .usage
status: .status
risk: .risk
note: .note
ownerName: .ownerName
businessModel: .businessModel
popularity: .popularity
projectCount: .projectCount
codeRepoCount: .codeRepoCount
isCloudService: .isCloudService
supportedOperatingSystems: .supportedOperatingSystems
- kind: hosted-technology
selector:
query: 'true'
port:
entity:
mappings:
blueprint: '"wizHostedTechnology"'
identifier: .id
title: .name
properties:
detectionMethods: .detectionMethods
installedPackages: .installedPackages
firstSeen: .firstSeen
updatedAt: .updatedAt
cpe: .cpe
relations:
technology: .technology.id

Monitoring and sync status

To learn more about how to monitor and check the sync status of your integration, see the relevant documentation.

Examples

To view and test the integration's mapping against examples of the third-party API responses, use the jq playground in your data sources page. Find the integration in the list of data sources and click on it to open the playground.

Examples of blueprints and the relevant integration configurations can be found on the Wiz examples page.

Let's Test It

This section includes a sample response data from Wiz. In addition, it includes the entity created from the resync event based on the Ocean configuration provided in the previous section.

Payload

Here is an example of the payload structure from Wiz:

Project response data
{
"id": "d6ac50bb-aec0-52fc-80ab-bacd7b02f178",
"name": "Project1",
"isFolder": false,
"archived": false,
"businessUnit": "Dev",
"description": "Test project"
}
Control response data
{
"__typename": "Control",
"id": "9d7ef6e4-baed-47ba-99ec-a78a801f1e19",
"name": "Publicly Exposed Assets with DataFindings ",
"controlDescription": "",
"resolutionRecommendation": "",
"securitySubCategories": [
{
"title": "Data Security",
"category": {
"name": "8 Data Security",
"framework": {
"name": "Wiz"
}
}
}
]
}
Issue response data
{
"id": "fffedba9-587f-4251-8c96-d966c183f10c",
"sourceRule": {
"__typename": "Control",
"id": "9d7ef6e4-baed-47ba-99ec-a78a801f1e19",
"name": "Publicly Exposed Assets with DataFindings ",
"controlDescription": "",
"resolutionRecommendation": "",
"securitySubCategories": [
{
"title": "Data Security",
"category": {
"name": "8 Data Security",
"framework": {
"name": "Wiz"
}
}
}
]
},
"createdAt": "2023-08-23T07:56:09.903743Z",
"updatedAt": "2023-09-12T08:33:16.327851Z",
"dueAt": null,
"type": "TOXIC_COMBINATION",
"resolvedAt": "2023-08-30T08:17:54.613564Z",
"statusChangedAt": "2023-08-30T08:17:54.613564Z",
"projects": [
{
"id": "d6ac50bb-aec0-52fc-80ab-bacd7b02f178",
"name": "Project1",
"slug": "project1",
"businessUnit": "Dev",
"riskProfile": {
"businessImpact": "MBI"
}
}
],
"status": "RESOLVED",
"severity": "HIGH",
"entitySnapshot": {
"id": "3d7dafdc-0087-55e0-81fd-a9e2b152fb47",
"type": "DATA_FINDING",
"nativeType": "",
"name": "GDPR 2415",
"status": null,
"cloudPlatform": null,
"cloudProviderURL": "",
"providerId": "data##wizt-recEIECHXqlRPMZRw##wfke-jpb8-twwk-l7mm",
"region": "",
"resourceGroupExternalId": "",
"subscriptionExternalId": "",
"subscriptionName": "",
"subscriptionTags": null,
"tags": {},
"externalId": "data##wizt-recEIECHXqlRPMZRw##wfke-jpb8-twwk-l7mm"
},
"serviceTickets": [],
"notes": [
{
"createdAt": "2023-09-12T08:33:16.29091Z",
"updatedAt": "2023-09-12T08:33:16.366971Z",
"text": "test",
"user": null,
"serviceAccount": {
"name": "bot-ise"
}
},
{
"createdAt": "2023-09-12T08:22:20.13926Z",
"updatedAt": "2023-09-12T08:33:16.369728Z",
"text": "test",
"user": null,
"serviceAccount": {
"name": "bot-ise"
}
},
{
"createdAt": "2023-09-12T08:21:49.663314Z",
"updatedAt": "2023-09-12T08:33:16.371541Z",
"text": "test",
"user": null,
"serviceAccount": {
"name": "bot-ise"
}
}
]
}
Service Ticket response data
{
"externalId": "data##wizt-customID##ja63-kx0z-f27x-mpvl",
"name": "Security Vulnerability in AWS S3 Bucket",
"url": "https://api.wiz.com/wiz/service-tickets/data##wizt-customID##ja63-kx0z-f27x-mpvl"
}
Vulnerability response data
{
"id": "0ac9b058-fe02-5e5c-990f-5d181343d09d",
"severity": "LOW",
"categories": "DOS",
"version": "2.2.4",
"detectionMethod": "PACKAGE",
"score": 3.7,
"status": "OPEN",
"detailedName": "apt",
"artifactType": {
"group": "OS_PACKAGE",
"ciComponent": null,
"custom": null,
"plugin": null,
"osPackageManager": "DPKG",
"codeLibraryLanguage": null
},
"description": "The package `apt` version `2.2.4` was detected in `APT package manager` on a machine running `Debian 11.11` is vulnerable to `CVE-2011-3374`, which exists in `all current versions`.\n\nThe vulnerability was found in the [Official Debian Security Advisories](https://security-tracker.debian.org/tracker/CVE-2011-3374) with vendor severity: `Low` ([NVD](https://nvd.nist.gov/vuln/detail/CVE-2011-3374) severity: `Low`).\n\nThis vulnerability has a known exploit available. Source: [VulnCheck](https://seclists.org/fulldisclosure/2011/Sep/221).\n\nThis vulnerability cannot be remediated because a fix has not been released.",
"resolvedAt": null,
"updatedAt": "2025-12-02T12:41:24.069936Z",
"firstDetectedAt": "2022-11-06T14:05:28.414309Z",
"publishedDate": "2019-11-26T00:15:00Z",
"remediation": null,
"environments": [
"PRODUCTION"
],
"link": "https://security-tracker.debian.org/tracker/CVE-2011-3374",
"vulnerabilityExternalId": "CVE-2011-3374",
"portalUrl": "https://app.wiz.io/explorer/vulnerability-findings#~(entity~(~'0ac9b058-fe02-5e5c-990f-5d181343d09d*2cSECURITY_TOOL_FINDING))",
"origin": "WIZ",
"CVEDescription": "It was found that apt-key in apt, all versions, do not correctly validate gpg keys with the master keyring, leading to a potential man-in-the-middle attack.",
"name": "CVE-2011-3374",
"hasFix": false,
"hasExploit": true,
"isHighProfileThreat": false,
"projects": [
{
"id": "0f19bcc4-c17b-57d0-a187-db3a6b1a5100",
"name": "Project 3"
}
],
"rootComponent": null,
"applicationServices": null
}
Repository response data
{
"id": "78342",
"name": "payment-service",
"url": "https://github.com/org/payment-service",
"platform": "GITHUB",
"public": false,
"archived": false,
"visibility": "PRIVATE",
"organization": {
"id": "org-4821",
"name": "acme-engineering"
},
"projects":[
{
"name": "Project1",
"id": "d6ac50bb-aec0-52fc-80ab-bacd7b02f178"
}

],
"branches": [
{
"id": "branch-a1",
"name": "main",
"url": "https://github.com/org/payment-service/tree/main"
},
{
"id": "branch-a2",
"name": "develop",
"url": "https://github.com/org/payment-service/tree/develop"
}
]
}
Technology response data
{
"id": "10071",
"name": ".NET Core SDK",
"description": ".NET Core SDK is a set of libraries and tools that allow developers to create .NET Core applications and libraries. It includes the .NET Core runtime for running applications, but also provides additional capabilities for building, testing, and debugging .NET Core applications. The SDK also includes a command line interface (CLI) for performing various tasks such as project creation, code compilation, and package management.",
"categories": [
{
"name": "Frameworks & Libraries"
}
],
"usage": "COMMON",
"status": "UNREVIEWED",
"risk": "MEDIUM",
"note": null,
"ownerName": "Microsoft Corporation",
"businessModel": "COMMERCIAL_OPEN_SOURCE",
"popularity": "VERY_COMMON",
"projectCount": 0,
"codeRepoCount": 0,
"isCloudService": false,
"supportedOperatingSystems": [
"WINDOWS",
"LINUX"
]
}
Hosted technology response data
{
"id": "08be2ce6-e850-5bac-b116-bb63f991d2bd",
"name": "Linux Debian (docker.io/httpd@96b1e8f6)",
"technology": {
"id": "4370",
"name": "Linux Debian"
},
"resource": {
"id": "b8ca4430-1676-54cd-a342-b9f6110cdfa9",
"name": "docker.io/httpd@96b1e8f6"
},
"detectionMethods": [
"OS"
],
"installedPackages": [
"adduser (3.152)",
"apt (3.0.3)",
"base-files (13.8+deb13u3)",
"base-passwd (3.6.7)",
"bash (5.2.37-2+b7)",
"bsdutils (1:2.41-5)",
"ca-certificates (20250419)",
"coreutils (9.7-3)",
"dash (0.5.12-12)",
"debconf (1.5.91)",
"debian-archive-keyring (2025.1)",
"debianutils (5.23.2)",
"diffutils (1:3.10-4)",
"dpkg (1.22.21)",
"findutils (4.10.0-3)",
"gcc-14-base (14.2.0-19)",
"grep (3.11-4)",
"gzip (1.13-1)",
"hostname (3.25)",
"init-system-helpers (1.69~deb13u1)",
"libacl1 (2.3.2-2+b1)",
"libapr1t64 (1.7.5-1)",
"libaprutil1-ldap (1.6.3-3+b1)",
"libaprutil1t64 (1.6.3-3+b1)",
"libapt-pkg7.0 (3.0.3)",
"libattr1 (1:2.5.2-3)",
"libaudit-common (1:4.0.2-2)",
"libaudit1 (1:4.0.2-2+b2)",
"libblkid1 (2.41-5)",
"libbrotli1 (1.1.0-2+b7)",
"libbsd0 (0.12.2-2)",
"libbz2-1.0 (1.0.8-6)",
"libc-bin (2.41-12+deb13u1)",
"libc6 (2.41-12+deb13u1)",
"libcap-ng0 (0.8.5-4+b1)",
"libcap2 (1:2.75-10+b3)",
"libcom-err2 (1.47.2-3+b7)",
"libcrypt1 (1:4.4.38-1)",
"libcurl4t64 (8.14.1-2+deb13u2)",
"libdb5.3t64 (5.3.28+dfsg2-9)",
"libdebconfclient0 (0.280)",
"libexpat1 (2.7.1-2)",
"libffi8 (3.4.8-2)",
"libgcc-s1 (14.2.0-19)",
"libgdbm6t64 (1.24-2)",
"libgmp10 (2:6.3.0+dfsg-3)",
"libgnutls30t64 (3.8.9-3+deb13u2)",
"libgssapi-krb5-2 (1.21.3-5)",
"libhogweed6t64 (3.10.1-1)",
"libidn2-0 (2.3.8-2)",
"libjansson4 (2.14-2+b3)",
"libk5crypto3 (1.21.3-5)",
"libkeyutils1 (1.6.3-6)",
"libkrb5-3 (1.21.3-5)",
"libkrb5support0 (1.21.3-5)",
"liblastlog2-2 (2.41-5)",
"libldap-common (2.6.10+dfsg-1)",
"libldap2 (2.6.10+dfsg-1)",
"liblua5.2-0 (5.2.4-3+b3)",
"liblz4-1 (1.10.0-4)",
"liblzma5 (5.8.1-1)",
"libmd0 (1.1.0-2+b1)",
"libmount1 (2.41-5)",
"libnettle8t64 (3.10.1-1)",
"libnghttp2-14 (1.64.0-1.1)",
"libnghttp3-9 (1.8.0-1)",
"libp11-kit0 (0.25.5-3)",
"libpam-modules (1.7.0-5)",
"libpam-modules-bin (1.7.0-5)",
"libpam-runtime (1.7.0-5)",
"libpam0g (1.7.0-5)",
"libpcre2-8-0 (10.46-1~deb13u1)",
"libpsl5t64 (0.21.2-1.1+b1)",
"librtmp1 (2.4+20151223.gitfa8646d.1-2+b5)",
"libsasl2-2 (2.1.28+dfsg1-9)",
"libsasl2-modules-db (2.1.28+dfsg1-9)",
"libseccomp2 (2.6.0-2)",
"libselinux1 (3.8.1-1)",
"libsemanage-common (3.8.1-1)",
"libsemanage2 (3.8.1-1)",
"libsepol2 (3.8.1-1)",
"libsmartcols1 (2.41-5)",
"libsqlite3-0 (3.46.1-7)",
"libssh2-1t64 (1.11.1-1)",
"libssl3t64 (3.5.4-1~deb13u2)",
"libstdc++6 (14.2.0-19)",
"libsystemd0 (257.9-1~deb13u1)",
"libtasn1-6 (4.20.0-2)",
"libtinfo6 (6.5+20250216-2)",
"libudev1 (257.9-1~deb13u1)",
"libunistring5 (1.3-2)",
"libuuid1 (2.41-5)",
"libxml2 (2.12.7+dfsg+really2.9.14-2.1+deb13u2)",
"libxxhash0 (0.8.3-2)",
"libzstd1 (1.5.7+dfsg-1)",
"login (1:4.16.0-2+really2.41-5)",
"login.defs (1:4.17.4-2)",
"mawk (1.3.4.20250131-1)",
"mount (2.41-5)",
"ncurses-base (6.5+20250216-2)",
"ncurses-bin (6.5+20250216-2)",
"openssl (3.5.4-1~deb13u2)",
"openssl-provider-legacy (3.5.4-1~deb13u2)",
"passwd (1:4.17.4-2)",
"perl-base (5.40.1-6)",
"sed (4.9-2)",
"sqv (1.3.0-3+b2)",
"sysvinit-utils (3.14-4)",
"tar (1.35+dfsg-3.1)",
"tzdata (2025b-4+deb13u1)",
"util-linux (2.41-5)",
"zlib1g (1:1.3.dfsg+really1.3.1-1+b1)"
],
"firstSeen": "2026-03-04T12:25:53.351929Z",
"updatedAt": "2026-03-04T12:25:53.351929Z",
"cpe": "cpe:/o:debian:debian_linux:13.3"
}

Mapping Result

The combination of the sample payload and the Ocean configuration generates the following Port entity:

Project entity in Port(Click to expand)
{
"identifier": "d6ac50bb-aec0-52fc-80ab-bacd7b02f178",
"title": "Project1",
"blueprint": "wizProject",
"team": [],
"icon": "NewRelic",
"properties": {
"archived": false,
"businessUnit": "Dev",
"description": "Test project"
},
"createdAt": "2024-2-6T09:30:57.924Z",
"createdBy": "hBx3VFZjqgLPEoQLp7POx5XaoB0cgsxW",
"updatedAt": "2024-2-6T11:49:20.881Z",
"updatedBy": "hBx3VFZjqgLPEoQLp7POx5XaoB0cgsxW"
}
Control entity in Port(Click to expand)
{
"identifier": "9d7ef6e4-baed-47ba-99ec-a78a801f1e19",
"title": "Publicly Exposed Assets with DataFindings",
"blueprint": "wizControl",
"icon": "Flag",
"properties": {
"controlDescription": "",
"resolutionRecommendation": ""
},
"createdAt": "2024-2-6T09:30:57.924Z",
"createdBy": "hBx3VFZjqgLPEoQLp7POx5XaoB0cgsxW",
"updatedAt": "2024-2-6T11:49:20.881Z",
"updatedBy": "hBx3VFZjqgLPEoQLp7POx5XaoB0cgsxW"
}
Issue entity in Port(Click to expand)
{
"identifier": "fffedba9-587f-4251-8c96-d966c183f10c",
"title": "GDPR 2415 | DATA_FINDING",
"blueprint": "wizIssue",
"icon": "Alert",
"properties": {
"url": "https://app.wiz.io/issues#~(issue~'fffedba9-587f-4251-8c96-d966c183f10c)",
"status": "RESOLVED",
"severity": "HIGH",
"type": "TOXIC_COMBINATION",
"notes": [],
"vulnerability": {
"id": "3d7dafdc-0087-55e0-81fd-a9e2b152fb47",
"type": "DATA_FINDING",
"nativeType": "",
"name": "GDPR 2415",
"status": null,
"cloudPlatform": null,
"cloudProviderURL": "",
"providerId": "data##wizt-recEIECHXqlRPMZRw##wfke-jpb8-twwk-l7mm",
"region": "",
"resourceGroupExternalId": "",
"subscriptionExternalId": "",
"subscriptionName": "",
"subscriptionTags": null,
"tags": {},
"externalId": "data##wizt-recEIECHXqlRPMZRw##wfke-jpb8-twwk-l7mm"
},
"createdAt": "2023-08-23T07:56:09.903743Z",
"updatedAt": "2023-09-12T08:33:16.327851Z",
"resolvedAt": "2023-08-30T08:17:54.613564Z",
"statusChangedAt": "2023-08-30T08:17:54.613564Z",
},
"relations": {
"projects": ["d6ac50bb-aec0-52fc-80ab-bacd7b02f178"],
"serviceTickets": [],
"control": "9d7ef6e4-baed-47ba-99ec-a78a801f1e19"
},
"createdAt": "2023-08-23T07:56:09.903743Z",
"createdBy": "hBx3VFZjqgLPEoQLp7POx5XaoB0cgsxW",
"updatedAt": "2023-09-12T08:33:16.327851Z",
"updatedBy": "hBx3VFZjqgLPEoQLp7POx5XaoB0cgsxW"
}
Service Ticket entity in Port(Click to expand)
{
"identifier": "data##wizt-customID##ja63-kx0z-f27x-mpvl",
"title": "Security Vulnerability in AWS S3 Bucket",
"blueprint": "serviceTicket",
"icon": "Book",
"properties": {
"url": "https://api.wiz.com/wiz/service-tickets/data##wizt-customID##ja63-kx0z-f27x-mpvl"
},
"relations": {},
"createdAt": "2023-08-23T07:56:09.903743Z",
"createdBy": "hBx3VFZjqgLPEoQLp7POx5XaoB0cgsxW",
"updatedAt": "2023-09-12T08:33:16.327851Z",
"updatedBy": "hBx3VFZjqgLPEoQLp7POx5XaoB0cgsxW"
}
Vulnerability entity in Port(Click to expand)
{
"identifier": "0ac9b058-fe02-5e5c-990f-5d181343d09d",
"title": "CVE-2011-3374",
"properties": {
"status": "OPEN",
"severity": "LOW",
"categories": [
"DOS"
],
"version": "2.2.4",
"detectionMethod": "PACKAGE",
"score": 3.7,
"detailedName": "apt",
"artifactMetadata": {
"group": "OS_PACKAGE",
"osPackageManager": "DPKG"
},
"description": "The package `apt` version `2.2.4` was detected in `APT package manager` on a machine running `Debian 11.11` is vulnerable to `CVE-2011-3374`, which exists in `all current versions`.\n\nThe vulnerability was found in the [Official Debian Security Advisories](https://security-tracker.debian.org/tracker/CVE-2011-3374) with vendor severity: `Low` ([NVD](https://nvd.nist.gov/vuln/detail/CVE-2011-3374) severity: `Low`).\n\nThis vulnerability has a known exploit available. Source: [VulnCheck](https://seclists.org/fulldisclosure/2011/Sep/221).\n\nThis vulnerability cannot be remediated because a fix has not been released.",
"firstDetectedAt": "2022-11-06T14:05:28.414309Z",
"publishedDate": "2019-11-26T00:15:00Z",
"environments": [
"PRODUCTION"
],
"link": "https://security-tracker.debian.org/tracker/CVE-2011-3374",
"vulnerabilityExternalId": "CVE-2011-3374",
"portalUrl": "https://app.wiz.io/explorer/vulnerability-findings#~(entity~(~'0ac9b058-fe02-5e5c-990f-5d181343d09d*2cSECURITY_TOOL_FINDING))",
"origin": "WIZ",
"CVEDescription": "It was found that apt-key in apt, all versions, do not correctly validate gpg keys with the master keyring, leading to a potential man-in-the-middle attack.",
"hasFix": false,
"hasExploit": true,
"isHighProfileThreat": false,
"updatedAt": "2025-12-02T12:41:24.069936Z"
},
"relations": {
"projects": [
"0f19bcc4-c17b-57d0-a187-db3a6b1a5100"
]
},
"icon": "Wiz"
}
Repository entity in Port(Click to expand)
{
"identifier": "78342",
"title": "payment-service",
"icon": "Wiz",
"properties": {
"url": "https://github.com/org/payment-service",
"platform": "GITHUB",
"public": false,
"archived": false,
"visibility": "PRIVATE",
"organization": "acme-engineering",
"branches": [
"main",
"develop"
]
},
"relations": {
"projects": ["d6ac50bb-aec0-52fc-80ab-bacd7b02f178"]
}
}
Technology entity in Port(Click to expand)
{
"identifier": "12306",
"title": "AWS App Mesh",
"properties": {
"description": "AWS App Mesh is a service mesh that provides application-level networking to make it easy for your services to communicate with each other across multiple types of compute infrastructure. It standardizes how your services communicate, giving you end-to-end visibility and helping to ensure high availability for your applications.",
"categories": [
"Cloud Networking Services"
],
"usage": "COMMON",
"status": "UNREVIEWED",
"risk": "HIGH",
"ownerName": "Amazon Web Services, Inc.",
"businessModel": "COMMERCIAL_PROPRIETARY",
"projectCount": 0,
"codeRepoCount": 0,
"isCloudService": true
},
"relations": {},
"icon": "Wiz"
}
Hosted Technology entity in Port(Click to expand)
{
"identifier": "08be2ce6-e850-5bac-b116-bb63f991d2bd",
"title": "Linux Debian (docker.io/httpd@96b1e8f6)",
"properties": {
"detectionMethods": [
"OS"
],
"installedPackages": [
"adduser (3.152)",
"apt (3.0.3)",
"base-files (13.8+deb13u3)",
"base-passwd (3.6.7)",
"bash (5.2.37-2+b7)",
"bsdutils (1:2.41-5)",
"ca-certificates (20250419)",
"coreutils (9.7-3)",
"dash (0.5.12-12)",
"debconf (1.5.91)",
"debian-archive-keyring (2025.1)",
"debianutils (5.23.2)",
"diffutils (1:3.10-4)",
"dpkg (1.22.21)",
"findutils (4.10.0-3)",
"gcc-14-base (14.2.0-19)",
"grep (3.11-4)",
"gzip (1.13-1)",
"hostname (3.25)",
"init-system-helpers (1.69~deb13u1)",
"libacl1 (2.3.2-2+b1)",
"libapr1t64 (1.7.5-1)",
"libaprutil1-ldap (1.6.3-3+b1)",
"libaprutil1t64 (1.6.3-3+b1)",
"libapt-pkg7.0 (3.0.3)",
"libattr1 (1:2.5.2-3)",
"libaudit-common (1:4.0.2-2)",
"libaudit1 (1:4.0.2-2+b2)",
"libblkid1 (2.41-5)",
"libbrotli1 (1.1.0-2+b7)",
"libbsd0 (0.12.2-2)",
"libbz2-1.0 (1.0.8-6)",
"libc-bin (2.41-12+deb13u1)",
"libc6 (2.41-12+deb13u1)",
"libcap-ng0 (0.8.5-4+b1)",
"libcap2 (1:2.75-10+b3)",
"libcom-err2 (1.47.2-3+b7)",
"libcrypt1 (1:4.4.38-1)",
"libcurl4t64 (8.14.1-2+deb13u2)",
"libdb5.3t64 (5.3.28+dfsg2-9)",
"libdebconfclient0 (0.280)",
"libexpat1 (2.7.1-2)",
"libffi8 (3.4.8-2)",
"libgcc-s1 (14.2.0-19)",
"libgdbm6t64 (1.24-2)",
"libgmp10 (2:6.3.0+dfsg-3)",
"libgnutls30t64 (3.8.9-3+deb13u2)",
"libgssapi-krb5-2 (1.21.3-5)",
"libhogweed6t64 (3.10.1-1)",
"libidn2-0 (2.3.8-2)",
"libjansson4 (2.14-2+b3)",
"libk5crypto3 (1.21.3-5)",
"libkeyutils1 (1.6.3-6)",
"libkrb5-3 (1.21.3-5)",
"libkrb5support0 (1.21.3-5)",
"liblastlog2-2 (2.41-5)",
"libldap-common (2.6.10+dfsg-1)",
"libldap2 (2.6.10+dfsg-1)",
"liblua5.2-0 (5.2.4-3+b3)",
"liblz4-1 (1.10.0-4)",
"liblzma5 (5.8.1-1)",
"libmd0 (1.1.0-2+b1)",
"libmount1 (2.41-5)",
"libnettle8t64 (3.10.1-1)",
"libnghttp2-14 (1.64.0-1.1)",
"libnghttp3-9 (1.8.0-1)",
"libp11-kit0 (0.25.5-3)",
"libpam-modules (1.7.0-5)",
"libpam-modules-bin (1.7.0-5)",
"libpam-runtime (1.7.0-5)",
"libpam0g (1.7.0-5)",
"libpcre2-8-0 (10.46-1~deb13u1)",
"libpsl5t64 (0.21.2-1.1+b1)",
"librtmp1 (2.4+20151223.gitfa8646d.1-2+b5)",
"libsasl2-2 (2.1.28+dfsg1-9)",
"libsasl2-modules-db (2.1.28+dfsg1-9)",
"libseccomp2 (2.6.0-2)",
"libselinux1 (3.8.1-1)",
"libsemanage-common (3.8.1-1)",
"libsemanage2 (3.8.1-1)",
"libsepol2 (3.8.1-1)",
"libsmartcols1 (2.41-5)",
"libsqlite3-0 (3.46.1-7)",
"libssh2-1t64 (1.11.1-1)",
"libssl3t64 (3.5.4-1~deb13u2)",
"libstdc++6 (14.2.0-19)",
"libsystemd0 (257.9-1~deb13u1)",
"libtasn1-6 (4.20.0-2)",
"libtinfo6 (6.5+20250216-2)",
"libudev1 (257.9-1~deb13u1)",
"libunistring5 (1.3-2)",
"libuuid1 (2.41-5)",
"libxml2 (2.12.7+dfsg+really2.9.14-2.1+deb13u2)",
"libxxhash0 (0.8.3-2)",
"libzstd1 (1.5.7+dfsg-1)",
"login (1:4.16.0-2+really2.41-5)",
"login.defs (1:4.17.4-2)",
"mawk (1.3.4.20250131-1)",
"mount (2.41-5)",
"ncurses-base (6.5+20250216-2)",
"ncurses-bin (6.5+20250216-2)",
"openssl (3.5.4-1~deb13u2)",
"openssl-provider-legacy (3.5.4-1~deb13u2)",
"passwd (1:4.17.4-2)",
"perl-base (5.40.1-6)",
"sed (4.9-2)",
"sqv (1.3.0-3+b2)",
"sysvinit-utils (3.14-4)",
"tar (1.35+dfsg-3.1)",
"tzdata (2025b-4+deb13u1)",
"util-linux (2.41-5)",
"zlib1g (1:1.3.dfsg+really1.3.1-1+b1)"
],
"firstSeen": "2026-03-04T12:25:53.351929Z",
"updatedAt": "2026-03-04T12:25:53.351929Z",
"cpe": "cpe:/o:debian:debian_linux:13.3"
},
"relations": {
"technology": "4370"
},
"icon": "Wiz"
}

Alternative installation via webhook

While the Ocean integration described above is the recommended installation method, you may prefer to use a webhook to ingest data from Wiz. If so, use the following instructions:

Note that when using the webhook installation method, data will be ingested into Port only when the webhook is triggered.

Webhook installation (click to expand)

In this example you are going to create a webhook integration between Wiz and Port, which will ingest Wiz issue entities into Port.

Port configuration

Create the following blueprint definition:

Wiz issue blueprint
{
"identifier": "wizIssue",
"description": "This blueprint represents a wiz issue",
"title": "Wiz Issue",
"icon": "Alert",
"schema": {
"properties": {
"status": {
"title": "Status",
"type": "string",
"enum": [
"OPEN",
"IN_PROGRESS",
"RESOLVED",
"REJECTED"
],
"enumColors": {
"OPEN": "blue",
"IN_PROGRESS": "orange",
"RESOLVED": "green",
"REJECTED": "darkGray"
}
},
"severity": {
"title": "Severity",
"type": "string",
"enum": [
"INFORMATIONAL",
"LOW",
"MEDIUM",
"HIGH",
"CRITICAL"
],
"enumColors": {
"INFORMATIONAL": "blue",
"LOW": "yellow",
"MEDIUM": "orange",
"HIGH": "red",
"CRITICAL": "red"
}
},
"control": {
"title": "Control",
"type": "string",
"description": "A security graph query defining a risk"
},
"vulnerability": {
"title": "Vulnerability",
"type": "object",
"description": "The identified security risk"
},
"createdAt": {
"title": "Created At",
"type": "string",
"format": "date-time"
}
},
"required": []
},
"mirrorProperties": {},
"calculationProperties": {},
"relations": {}
}

Create the following webhook configuration using Port's UI

Wiz issue webhook configuration
  1. Basic details tab - fill the following details:

    1. Title : Wiz Mapper;
    2. Identifier : wiz_mapper;
    3. Description : A webhook configuration to map Wiz issues to Port;
    4. Icon : Box;
  2. Integration configuration tab - fill the following JQ mapping:

    [
    {
    "blueprint": "wizIssue",
    "entity": {
    "identifier": ".body.issue.id",
    "title": ".body.resource.name",
    "properties": {
    "status": ".body.issue.status",
    "severity": ".body.issue.severity",
    "control": ".body.control.name",
    "vulnerability": ".body.resource",
    "createdAt": ".body.issue.created"
    }
    }
    }
    ]

Create a webhook in Wiz

  1. Send an email to win@wiz.io requesting for access to the developer documentation or reach out to your Wiz account manager.
  2. Follow this guide in the documentation to create a webhook.

Done! Any issue created in Wiz will trigger a webhook event to the webhook URL provided by Port. Port will parse the events according to the mapping and update the catalog entities accordingly.