> For the complete documentation index, see llms.txt.
Skip to main content

Check out Port for yourself ➜ 

Visualize your Wiz security issues

Implement with AI

Send this guide to your coding agent.

Prerequisite: Install Port MCP

Open plan mode. Implement this Port guide in my org via MCP:

https://docs.port.io/guides/all/visualize-your-wiz-vulnerabilities

Goal: get the guide's core flow working end-to-end in my org; adapting it to fit my existing setup takes priority over matching the guide 1:1.

Plan:
1. Confirm MCP is connected, in the right org, with sufficient permissions.
2. Diff the guide's data model (blueprints, properties, relations, actions, agents, automations, integrations, secrets) against mine.
3. Propose adaptations for gaps, reusing existing blueprints/relations over guide-named duplicates.
4. Flag what needs a UI click, credential, or secret from me, testing MCP capability empirically before ruling anything out.
5. Stop on any blocker and give me options. Approving this plan authorizes the writes it lists; pause only for writes beyond what's listed.

Build:
- Extend blueprint schema additively when upserting; don't remove or overwrite existing properties, and treat type conflicts as a blocker, not an auto-fix.
- List any mock data in the plan, minimal and labeled mock; once approved, seed it without re-asking, and tell me what you seeded.
- For anything the guide writes downstream (e.g. a webhook target), use a real entity, not a mock.
- For pages/widgets, use the real page identifier from the app URL, not a guessed slug.
- When you hit a UI step confirmed (not assumed) unsupported via MCP, pause, give exact clicks, then resume via MCP.
- Validate and give links after each meaningful step (only a tool-returned URL, no guessed paths); don't proceed if the last run wasn't a success.

Done:
- Confirm the guide's expected output exists and runs in Port.
- Summarize adaptations, seeded data, what was mocked or skipped, remaining UI steps, and how to verify.

This guide demonstrates how to set up a monitoring solution to gain visibility into security issues from your Wiz account.
We will see how to visualize vulnerabilities across your projects and track them over time using Port's Wiz integration.

Wiz Security Insight dashboard overview Wiz dashboard open issues count and status chart

Common use cases

  • Monitor open and resolved Wiz issues across projects.
  • Understand the distribution of issues by severity and status.

Prerequisites

This guide assumes the following:

Visualize metrics

Once the Wiz data is synced to the catalog, we can create a dedicated dashboard in Port to monitor and analyze vulnerabilities using customizable widgets.

Create a dashboard

  1. Navigate to your context lake.
  2. Click on the + button in the left sidebar.
  3. Select New dashboard.
  4. Name the dashboard Wiz Security Insight.
  5. Select the Wiz icon.
  6. Click Create.

We now have a blank dashboard where we can start adding widgets to visualize insights from the Wiz issues.

Add widgets

In the new dashboard, create the following widgets:

Issue by severity (click to expand)
  1. Click + Widget and select Pie chart.

  2. Title: Issue by severity.

  3. Choose the Wiz Issue blueprint.

  4. Under Breakdown by property, select the Severity property

    Pie chart Wiz issues by severity
  5. Click Save.

Issue by status (click to expand)
  1. Click + Widget and select Pie chart.

  2. Title: Issue by status.

  3. Choose the Wiz Issue blueprint.

  4. Under Breakdown by property, select the Status property

    Pie chart Wiz issues by status
  5. Click Save.

Total number of issues (click to expand)
  1. Click + Widget and select Number Chart.

  2. Title: Total issues.

  3. Select Count entities Chart type and choose Wiz Issue as the Blueprint.

  4. Select count for the Function.

  5. Select custom as the Unit and input issues as the Custom unit.

    Number chart counting total Wiz issues
  6. Click Save.

Open issue created in the last 6 months (click to expand)
  1. Click + Widget and select Number Chart.

  2. Title: Open issues (add the Alert icon).

  3. Select Count entities Chart type and choose Wiz Issue as the Blueprint.

  4. Select count for the Function.

  5. Add this JSON to the Additional filters editor to filter OPEN issues created in the last 6 months:

    [
    {
    "combinator":"and",
    "rules":[
    {
    "property":"status",
    "operator":"=",
    "value":"OPEN"
    },
    {
    "property":"createdAt",
    "operator":"between",
    "value":{
    "preset":"last6Months"
    }
    }
    ]
    }
    ]
    Number chart counting open Wiz issues
  6. Click Save.

Resolved issues (click to expand)
  1. Click + Widget and select Number Chart.

  2. Title: Resolved issues.

  3. Select Count entities Chart type and choose Wiz Issue as the Blueprint.

  4. Select count for the Function.

  5. Add this JSON to the Additional filters editor to filter RESOLVED issues:

    [
    {
    "combinator":"and",
    "rules":[
    {
    "property":"status",
    "operator":"=",
    "value":"RESOLVED"
    }
    ]
    }
    ]
    Number chart counting resolved Wiz issues
  6. Click Save.

Open critical issues (click to expand)
  1. Click + Widget and select Number Chart.

  2. Title: Open critical issues.

  3. Select Count entities Chart type and choose Wiz Issue as the Blueprint.

  4. Select count for the Function.

  5. Add this JSON to the Additional filters editor to filter OPEN and CRITICAL issues:

    [
    {
    "combinator":"and",
    "rules":[
    {
    "property":"status",
    "operator":"=",
    "value":"OPEN"
    },
    {
    "property":"severity",
    "operator":"=",
    "value":"CRITICAL"
    }
    ]
    }
    ]
    Number chart counting open critical Wiz issues
  6. Click Save.