Wiz (Pro)

The Wiz connector imports Issues and vulnerability findings. DefectDojo creates a Record for each Wiz Project, plus a tenant-level Record named after the tenant itself, for example Wiz Tenant abc12, that covers the entire Wiz tenant.

You do not need Wiz Projects to use this connector. If your tenant has no Projects, map the that tenant-level Record Record and DefectDojo imports every Issue and vulnerability finding your service account can see. That Record also picks up findings on resources that no Project covers, so map it alongside your Project Records if your Projects do not cover everything. Mapping both a Project Record and the that tenant-level Record Record imports that Project’s findings into two Assets, so only do that if you want both views.

Using the Wiz connector requires you to create a service account: see the Wiz documentation for more info. You will need a Wiz account to access the documentation.

The service account must meet all of the following requirements. A service account that misses one of them can still authenticate successfully but will import nothing:

  • Type: Custom Integration (GraphQL API).
  • API scopes: at minimum read:projects, read:issues, and read:vulnerabilities. read:projects is required even on a tenant with no Projects, because Discover still asks Wiz for the Project list.
  • Project visibility: the service account must be scoped to every Wiz Project you want imported (or to all Projects). An account that can read issues but has no Project visibility discovers no Project Records, and only the that tenant-level Record Record is available.

Connector Mappings

  1. Enter your Wiz Client ID in the Client ID field.
  2. Enter the Wiz Client Secret in the Secret field.
  3. Choose which data classes to import in Import Finding Types. Both are selected by default.
  4. Optionally, list the Wiz tags to copy onto findings in Wiz Tags to Copy. See Wiz Tags.

Import Finding Types

Wiz serves two different data classes, and the connector imports both by default:

  • Issues: a Wiz Control fired on a resource. These are policy and posture violations. A typical tenant has hundreds or thousands. An Issue is tagged with each NIST 800-53, PCI DSS and CIS requirement its Control maps to, for example nist_sp_800-53_revision_5:ac-6(3). DefectDojo Pro maps the NIST 800-53 and PCI DSS tags to controls (see Control Coverage). CIS tags are kept on the finding but are not mapped to a catalog. Other frameworks stay in the description only.
  • Vulnerability Findings: one CVE on one package on one asset. A tenant with a few thousand assets can hold millions. Each asset carries many packages, and each package can carry many CVEs.

If your DefectDojo finding count is far higher than your asset count, Vulnerability Findings are the reason. That is expected: a finding is one problem on one asset, not one asset.

Deselect Vulnerability Findings to import Issues only. The connector then skips the vulnerability query entirely, so nothing is fetched from Wiz rather than fetched and discarded.

Two things to know before you change this setting:

  • Changing it triggers one full resync. The connector normally asks Wiz only for what changed since the last sync. That cursor is cleared when you change the selection, so the next sync re-reads everything. Without the reset, re-enabling a data class never backfills the rows it skipped while it was off.
  • Deselecting a data class closes its existing findings. The next sync sends none of that class, and DefectDojo closes what it no longer receives. Suppose you turn off Vulnerability Findings on a connector that already imported a million of them. That sync closes all one million.

Minimum Severity is a separate control and cannot be changed after the connector is created.

Wiz Tags

Cloud teams often record who owns a resource as tags on it, for example OwnerName and OwnerEmail on each VM, bucket or cluster, or on the account or subscription that holds it. Wiz Tags to Copy brings those tags onto the findings, so you can filter findings and build reports by owner in DefectDojo.

Enter the tag keys as a comma-separated list, for example OwnerName, OwnerEmail. Leave the field blank to copy no tags, which is the default.

Every finding whose resource carries one of the listed tags gets a finding tag of the form wiz-tag-<key>:<value>. A resource tagged OwnerName: Platform Team and OwnerEmail: platform@example.com gives each finding on it the tags wiz-tag-ownername:platform-team and wiz-tag-owneremail:platform@example.com:

  • Each key is read from the resource’s own tags first. For Issues, a key the resource does not carry is then read from its subscription’s tags, so an owner tagged on the account still reaches Issues on untagged resources. Vulnerability Findings use the resource’s tags only, because Wiz does not return subscription tags with them.
  • Keys match without regard to case, so ownername finds a tag named OwnerName.
  • Tags are lowercase, spaces become hyphens, and commas and quotes are removed, because DefectDojo tags cannot contain them.
  • A listed key that neither the resource nor its subscription carries, or that is empty, adds nothing.

To list every finding one owner is responsible for, filter findings by the tag, for example wiz-tag-owneremail:platform@example.com.

Things to know:

  • A tag change reaches existing findings at the next full resync. After the first sync, the connector asks Wiz only for findings that changed since the last sync. Retagging a resource does not change its findings in Wiz, so a finding keeps its old wiz-tag- tag until the finding itself changes in Wiz or a full resync runs. Each time a finding is synced, its wiz-tag- tags are replaced with the current ones. Other tags on the finding, including ones added by hand, are left alone. Do not add wiz-tag- tags by hand: a sync treats them as its own and removes any Wiz does not report.
  • To pick up a tag change everywhere, force a full resync by changing Wiz Tags to Copy, for example by adding a key. Reordering the keys or changing their case does not count as a change.
  • Changing the list triggers one full resync, as with Import Finding Types, so findings imported before the change get their tags on the next sync. Removing a key removes its tags from the findings at that resync.

Asset Exposure

With Asset Exposure enabled, each sync also reports how reachable each Wiz Project’s asset is. The connector reads two things Wiz already knows and keeps the strongest result across the Project’s resources:

  • Network exposure: the network paths Wiz found to a resource. A path from any internet address records Externally Exposed; one from a narrower internet source range, or from a custom IP range holding a public address, records Partially Exposed; one from another cloud account, a VPN, or a custom range of private addresses records Internally Reachable. A path inside the resource’s own cloud account records nothing. The panel’s evidence names each exposed resource with its port range and protocol.
  • Vulnerable assets: the internet and network exposure fields Wiz sets on each asset that carries a vulnerability. These are read only while Vulnerability Findings is selected.

Network exposure is read on every sync whatever Import Finding Types says, and it never becomes a finding: it describes the asset, not a problem on it. Wiz cannot say when a path closes, so a path it stops reporting ages out of the asset’s exposure after 30 days. If the service account cannot read network exposure, the sync logs a warning and reports the vulnerable-asset fields alone.

Runtime Reachability

If the Wiz Runtime Sensor runs on a workload, Wiz marks a vulnerability finding as Validated in Runtime when the sensor sees the vulnerable package loaded in memory. The connector sends that flag to DefectDojo as a Reachable (runtime) reachability verdict.

A finding without the flag gets no verdict from Wiz. This includes a finding that Wiz reports as not validated, because a package the sensor did not see loaded can still run later. Without the Runtime Sensor, Wiz does not set the flag, so no Wiz finding gets a verdict. The connector reads the flag on vulnerability findings only, so an Issue never gets a verdict from it.

When Wiz stops reporting the flag, the verdict ends as described in How verdicts end.

After the first sync, the connector reads only the findings that Wiz updated since the last sync. A finding Wiz did not update is unchanged, so each complete sync renews the Wiz verdicts of the active findings it did not send, and the daily staleness sweep does not remove them while Wiz still marks the finding as validated in runtime. A verdict on a finding that is closed is not renewed, and it expires at the end of the staleness window.