CVE scanning is the automated process of checking your software, systems, and networks against a database of known security flaws to identify vulnerabilities before attackers can exploit them.

Container image scanning is the automated process of analyzing container images for security vulnerabilities, misconfigurations, and compliance violations.

API scanning is the automated process of analyzing APIs to detect security vulnerabilities, misconfigurations, and logic flaws.

SAST scanning, or Static Application Security Testing, is a "white-box" testing method that analyzes your application's source code, bytecode, or binaries to find security flaws

Penetration Testing vs Vulnerability Scanning: Penetration testing simulates attacks to exploit flaws while vulnerability scanning identifies known risks.

Internal vulnerability scanning is the process of identifying security weaknesses within an organization’s internal network infrastructure.

Discover top OSS API security testing tools. See how Wiz’s Dynamic Scanner delivers complete visibility, runtime protection, and contextual risk analysis.

Attack surface scanning is the process of continuously discovering and monitoring internet-facing assets to identify entry points attackers can exploit.

Agentless scanning vs agent-based scanning compares API-based assessments requiring no software installation with host-based agents for deep runtime visibility

.

.

This article will help you understand the benefits of using both tools together, along with a solution like Wiz to fill the cross-cloud visibility gap and optimize both costs and security.

.

This FAQ is designed to help teams evaluate whether Wiz is the right cloud security solution for them by answering the most common technical, strategic, and logistical questions.

Nicolas Ehrman

12 de diciembre de 2025

Container monitoring is the process of collecting, analyzing, and reporting metrics and data related to the performance and health of containerized applications and their hosting environments.

Attack surface discovery (ASD) is the continuous, automated process of identifying and mapping every asset, connection, and service an attacker could target across your entire digital footprint (cloud, hybrid, and on-premises environments).

Runtime scanning answers a critical question: 'What is runtime security for containers?' It focuses on detecting live behaviors, active threats, and anomalies that only appear when containers execute under real production traffic.

Source code scanning is automated analysis of your code, dependencies, and infrastructure definitions to find security issues before you deploy. This means a tool reads your code the way a careful reviewer would, but at high speed and at scale.

CI/CD security scanning is the practice of adding automated security checks into your build and deployment pipelines. This means every meaningful code change is tested for risk before it can reach production.