Wiz Beyond the Cloud: Securing On-Prem and Hybrid

When we talk about Wiz, most of us immediately think of cloud security.

But what happens when an organization's entire environment isn't exclusively in AWS, Azure, or GCP?

In reality, many organizations continue to operate critical systems in on-premises environments, alongside their cloud infrastructure. The result is a hybrid environment where each part is managed and audited differently—sometimes using separate tools, distinct processes, and without a common security context.

Introducing Wiz for On-Prem

Wiz for On-Prem extends Wiz’s visibility and risk context to private infrastructures. This includes environments such as VMware and ESXi, self-hosted Kubernetes Clusters, bare-metal servers, and bare-metal workloads.

Key Components for On-Prem Integration

The connection is established through several complementary components:

• The vSphere Connector maps infrastructure assets and provides information on vulnerabilities in ESXi and local identities.
• The Kubernetes Connector identifies misconfigurations, exposed services, and compliance gaps. Its Admission Controller enforces policies even before a workload is deployed.
• The Sensor-Based Workload Scanner provides deep visibility into workloads, identifying vulnerabilities, misconfigurations, exposures, malware, secrets, and sensitive data. The Runtime Sensor adds context about actual activity, distinguishing between theoretical risks and those actively manifesting at runtime.

Enhancing Existing On-Prem Scanners

What about organizations already using vulnerability scanners in their on-premises environment? They don't necessarily need to replace them. Through Unified Vulnerability Management, findings from existing scanning tools can be consolidated in Wiz and enriched with context from the Security Graph.

This approach allows for the management of both cloud and on-premises environments as part of a single risk posture. It enables prioritization of remediation efforts based on exposure, identities, relationships between assets, and actual operational activity.

Because in a hybrid environment, the boundary between cloud and on-premise might still exist infrastructurally, but it should not create a boundary in security visibility.