StackHawk

StackHawk and Wiz give security and engineering teams unified visibility across their application and cloud infrastructure layers. StackHawk runs dynamic application security testing (DAST) across the development lifecycle from dev environments and CI/CD pipelines to staging and production, testing APIs and application endpoints for exploitable vulnerabilities before they reach production. Those findings automatically flow into the Wiz Security Graph as attack surface enrichment data, where they are correlated with the cloud context Wiz maintains. For joint customers, that means application-layer risk and cloud-layer risk land in one place.

Market Challenge

Security teams are already managing too many alerts across disconnected tools, and AI-generated code is accelerating the problem. Pre-production DAST findings and cloud risk from Wiz have lived separately, with no shared view or owner, forcing teams to manually correlate findings across systems. By the time a cloud security team sees the risk, the fix belongs to a developer who's already moved on.

Key Benefits of the Integration

Application and Cloud Risk in One View: StackHawk DAST findings sync directly into the Wiz Security Graph, correlated with the cloud context Wiz maintains. Security teams get a single place to see what's exploitable in the application layer alongside what's at risk in the cloud, without switching tools or manually connecting findings across systems.

Pre-Production Findings, Cloud-Level Context: StackHawk tests what is about to be deployed into the clouds Wiz is protecting. Pre-production findings reach Wiz before a vulnerability has a chance to compound with infrastructure-level exposure, giving teams a signal when it’s easiest and cheapest to fix, rather than weeks after context has gone stale and the developer who introduced it has moved on. 

Prioritize Based On Full Impact, Remediate Faster: When findings land in Wiz, the context needed to prioritize is already there. StackHawk tells you it’s real and exploitable, and Wiz’s cloud context tells you how much is at stake. From there, developers can start fixing quickly with request and response details, a curl command to recreate the attack, and tailored fix recommendations for their stack, provided by StackHawk. 

Better Together

Wiz maps your cloud infrastructure: the resources, misconfigurations, identities, and ownership. StackHawk tests what's running on that infrastructure: the APIs, the authentication flows, the business logic that attackers actually target.

When a StackHawk scan finds a broken authentication vulnerability on an API endpoint, that finding flows into the Wiz Security Graph, where cloud context gets automatically correlated: which workload it's running on, whether it's internet-exposed, and who owns the remediation. The result is a combined risk picture where application exploitability and cloud exposure land in the same place.

Unified Application and Cloud Risk Visibility

Challenge

Security signals are scattered across application testing tools and cloud security platforms, with each surfacing a different layer of risk. Without a unified view connecting exploitable application vulnerabilities to the cloud infrastructure that runs them, it’s difficult to assess true exposure, assign ownership, or prioritize what to fix first.

How the integration solves it

When StackHawk completes a DAST scan, findings are synced to Wiz’s Attack Surface Findings page, where they are mapped to the corresponding assets on the Wiz Security Graph. Wiz correlates those findings with existing cloud context, giving security teams a combined view of application and cloud risk in one place.

Impact

Remediation cycles shorten because findings arrive in Wiz with ownership identified and cloud infrastructure context attached, so teams can prioritize based on full impact and start fixing without cross-referencing systems. Teams are notified of exploitable vulnerabilities before they reach production, and StackHawk gives them everything they need to act: request and response details, a curl command to recreate the attack, and fix recommendations tailored to your stack.