Modern development practices and AI copilots have dramatically increased the volume and velocity of code, with developers often moving from prompt → tab → commit in minutes.
Wiz Code was built from day one as a complete ASPM platform to keep pace with that speed, combining native scanning for SCA, secrets, sensitive data, IaC, and supply chain posture with the flexibility to ingest findings from popular code scanners. By bringing these signals together in the Wiz Security Graph, customers can correlate issues from code to cloud and drive action through the tools and workflows their teams already use.
Today, we’re expanding that foundation with Wiz SAST in Public Preview, enabling teams to scan their applications' code, understand its runtime impact, and fix issues using the same unified graph and workflows.
Securing modern applications starts with understanding how code actually behaves once it reaches the cloud. That’s why Wiz Code is built on top of the platform’s zero-configuration code-to-cloud mapping, allowing teams to see not just that a vulnerability exists, but where it runs, how it’s deployed, and what it can access.
Through repository analysis, registry scanning, and automated container lineage, Wiz traces:
Source code → CI pipeline → Container repository → Container image
This happens without tagging, CI/CD hacks, or developer overhead.
This is where Wiz Code changes the rules. By enriching code security findings with actual deployment context, you can answer crucial questions for the first time:
Is this vulnerable code actively deployed?
Is this application internet-exposed, and does it handle sensitive or regulated data?
Who owns it and who should fix it?
This is the kind of ASPM foundation application and cloud security teams aspire to have, one operating model that connects code, cloud, and risk.
Wiz SAST extends our policy engine with code-level vulnerability detection, without introducing another tool to manage.
Wiz SAST inherits the full Wiz operating model. Setup remains easy through one-click onboarding with all your VCS platforms. Scans are all orchestrated from a unified policy engine, making enforcement predictable and exceptions consistent across risk domains. And because all findings flow into the Wiz portal, AppSec teams gain a unified view of code and cloud issues in one place, without managing another standalone tool.
Wiz SAST is fully powered by the Wiz Security Graph, allowing every finding to be understood in the broader context of workload behavior: where the code runs, whether it is exposed, what privileges it has, etc.
By correlating static findings with runtime exposure, excessive permissions, reachable sensitive data, and network paths, Wiz automatically elevates the few vulnerabilities that represent meaningful risk, like:
A Path Traversal flaw in code that builds a workload with sensitive hostPath mappings
A Code Injection vulnerability that lands in a privileged container
An SQL injection weakness in a workload that’s directly exposed to the internet
Wiz also groups related weaknesses into CWE families so AppSec teams can address the entire root cause rather than individual occurrences.
We approached security as an engineering challenge; we needed a ‘Lean security’ process transformation, not just another siloed tool. Traditional SAST delivered noise, but the shift to Wiz SAST, leveraging the Security Graph’s cloud context, allows us to prioritize only the real, exploitable issues instead of thousands of findings.
Simon Goldsmith, CISO at OVO
And for organizations using other scanners, Wiz ingests findings from tools like Checkmarx, Semgrep, Snyk Code, and others, enriching them with the same cloud context to deliver a unified view of risk.
Detecting risks is only half the job. Fixing them is what improves application security posture. Each Wiz SAST finding is tied directly to the relevant repository, code owner, and source location, giving teams immediate clarity on who should take action.
To help AppSec teams make decisions quickly, an AI-powered SAST agent provides additional context beyond the vulnerable snippet and CWE classification. It assists with triage by explaining why a finding is exploitable or by marking it as a likely false positive. This reduces the effort needed to understand and triage complex findings.
After establishing the verdict, the AI agent also suggests a recommended fix for AppSec teams to determine the appropriate remediation path.
Remediation also meets developers where they work. Within pull requests, developers also get the findings and can comment "#wiz remediate" to request an AI-assisted fix, fully grounded in the codebase context and following secure coding practices.
This is SAST designed for action, not just detection.
Our goal was simple: to give developers the right tools, not more tickets. With the Wiz Code ASPM platform and the SAST engine, developers now get actionable guidance, including the vulnerable code snippet, full runtime context, and AI remediation options. Ultimately, this integrated workflow drives faster, better remediation across our continuous, horizontal security model.
Simon Goldsmith, CISO at OVO
By combining code analysis with runtime and cloud context, Wiz SAST sets the foundation for capabilities such as exposure-aware prioritization across all risk types, source-to-runtime API mapping, and correlation of SAST, SCA, secrets, IaC, pentest, and DAST findings into a single attack path.
With every layer of application risk connected, AppSec becomes proactive rather than reactive.
Wiz SAST is now available to all Wiz Code customers. The Public Preview includes repository and pull request scanning, thousands of curated rules, AI-assisted remediation, and full Security Graph enrichment.
If you already use Wiz Code, SAST can be enabled immediately. Read the documentation (login required) to get started. By tying vulnerabilities to the environments where code actually runs, Wiz helps teams focus on exploitable issues, resolve them faster, and operate a unified AppSec program across code and cloud.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。