Skip to main content

Wiz

Cloud Security

The Wiz Connector integrates with the Wiz cloud security platform to synchronize cloud inventory assets, security issues, configuration findings, and vulnerability data. It uses Wiz's GraphQL API and V2 Cloud Inventory Reports to retrieve resources across AWS, Azure, GCP, OCI, Alibaba Cloud, and VMware vSphere environments.

The connector synchronizes the following categories of data:

  • Cloud Inventory Assets — Virtual Machines, Containers, Container Images, Databases, Serverless Functions, Network Segments, and 20+ additional cloud resource types
  • Security Issues — Wiz Issues and Issue Definitions (available in both V1 GraphQL and V2 Report-based variants)
  • Configuration Findings — Cloud configuration assessments and associated Configuration Finding Definitions (via V2 Reports API)
  • Vulnerabilities — A single unified model covering all severities, scopable to specific severities with the severity operation option, with associated Vulnerability Definitions
  • Secret Findings — Leaked credentials/keys detected by Wiz, with deduplicated Secret Finding Definitions (one per Wiz detection rule)
  • Grouped Findings — Condensed reporting views (Grouped Vulnerability, Grouped Configuration Finding, Grouped Issue) that roll findings up to a configurable grain — by default resource + subscription + component for vulnerabilities — carrying distinct-valued collections, worst-case risk attributes and finding counts by status and severity

Data retrieved from Wiz​

Connector ObjectRequiredMaps to Data Model
Virtual MachineYesHost
ContainerYesContainer
Container ImageYesContainer Image
Database ServerYesCloud Resource
ServerlessYesCloud Resource
Virtual Machine ImageYesHost Image
Virtual NetworkYesCloud Resource
Application EndpointYesApplication Endpoint
BucketYesBucket
Compute Instance GroupYesCompute Instance Group
Access RoleYesAccess Role
Access Role BindingYesAccess Role Binding
API GatewayYesAPI Gateway
Backup ServiceYesBackup Service
CI/CD ServiceYesCI/CD Service
Cloud Log ConfigurationYesCloud Log Configuration
Container RegistryYesContainer Registry
Container ServiceYesContainer Service
DaemonSetYesDaemonSet
Data WorkloadYesData Workload
DeploymentYesDeployment
Encryption KeyYesEncryption Key
File System ServiceYesFile System Service
FirewallYesFirewall
GatewayYesGateway
Kubernetes ClusterYesKubernetes Cluster
Load BalancerYesLoad Balancer
Messaging ServiceYesMessaging Service
PodYesPod
Raw Access PolicyYesRaw Access Policy
Repository BranchYesCode Repository
Resource GroupYesResource Group
Route TableYesRoute Table
Secret ContainerYesSecret Container
SnapshotYesSnapshot
Storage AccountYesStorage Account
SubnetYesSubnet
SubscriptionYesSubscription
VolumeYesVolume
Web ServiceYesWeb Service
Issue (V1)YesViolation
Issue Definition (V1)YesViolation Definition
Issue V2YesViolation
Issue Definition V2YesViolation Definition
Configuration FindingYesViolation
Configuration Finding DefinitionYesViolation Definition
VulnerabilityYesVulnerability
Vulnerability DefinitionYesVulnerability Definition
Grouped VulnerabilityYes(none — reporting view only)
Grouped Configuration FindingYes(none — reporting view only)
Grouped IssueYes(none — reporting view only)
Secret FindingYes(unassigned)
Secret Finding DefinitionYes(unassigned)

Model relationships​

note

For detailed steps on how to view the data retrieved from Wiz in the Brinqa Platform, see How to view your data.

warning

Not Supported by Wiz V2 Inventory Report

The Access Role Binding (ACCESS_ROLE_BINDING) and Application Endpoint (ENDPOINT) models are no longer returned by the CLOUD_RESOURCE_V2 report that this connector uses (BaseInventoryModel). As part of Wiz's Cloud Resource Inventory V2 migration, the "Native Types" were consolidated to include only cloud-native resources, and both ACCESS_ROLE_BINDING and ENDPOINT are on the list of types excluded from V2 reports. See Wiz's V1 vs V2 resource-count discrepancies.

As a result, these two models return no data on connector versions that use the V2 report (3.x since v3.4.0, 2.x since v2.1.22). They are retained for backward compatibility only; existing data will not be refreshed.

Last updated on