Security teams rarely struggle to find vulnerabilities. The difficult part usually comes right after.
A scan finishes. A finding appears. Then someone asks the question that really matters:
“Where does this actually live in our environment?”
The application security platform shows the vulnerability.
The cloud security platform shows the infrastructure.
But connecting those two views often requires manual investigation.
Someone has to determine:
- which workload is running the application
- whether the service is externally exposed
- what environment it belongs to
- how it relates to other cloud assets
In small environments this process is manageable. In large organizations running dozens of services across cloud platforms, it quickly becomes slow and repetitive.
The Bright ↔ Wiz integration was created to remove that friction.
Starting March 10, Bright can automatically send dynamic scan findings to Wiz. Wiz then correlates those findings with the cloud resources hosting the application.
Instead of reviewing application vulnerabilities and infrastructure exposure separately, teams can analyze them together.
Table of Contents
- Why Application Security and Cloud Security Often Feel Disconnected
- What the Bright ↔ Wiz Integration Does.
- How the Integration Works During a Scan
- Why Runtime Findings Matter for Cloud Security Teams
- Correlating Vulnerabilities with Cloud Assets
- What Happens When Vulnerabilities Are Fixed
- Integration Setup and Configuration
- Operational Benefits for Security Teams
- A Common Vendor Trap in Security Integrations
- Release Timeline
- Frequently Asked Questions
- Conclusion
Why Application Security and Cloud Security Often Feel Disconnected
Most organizations rely on multiple security platforms because each tool focuses on a different layer of the stack.
Application security platforms analyze the behavior of running applications. They look for issues such as:
- broken access control
- injection vulnerabilities
- authentication weaknesses
- insecure API behavior
Cloud security platforms focus on infrastructure and environment risk. They evaluate things like:
- exposed workloads
- misconfigured services
- identity permissions
- cloud asset relationships
Both perspectives are important.
But when these signals exist in separate systems, connecting them requires additional investigation.
For example, imagine a runtime scan detects a vulnerability in an API endpoint.
The AppSec team now knows a weakness exists. What they may not immediately know is how that vulnerability fits into the broader environment.
Questions naturally follow:
- Is the service publicly accessible?
- Is it part of a production workload?
- Does it connect to sensitive systems?
Cloud security platforms often have this information, but they don’t necessarily know about runtime application vulnerabilities.
That gap is what the Bright–Wiz integration helps address.
What the Bright ↔ Wiz Integration Does
The integration connects Bright’s runtime security testing with Wiz’s cloud security platform.
Once enabled, Bright automatically sends scan findings to Wiz after each scan across the organization.
Wiz then correlates those findings with the relevant cloud resources.
This provides security teams with a unified view of vulnerabilities across both application and cloud layers.
The integration delivers three core capabilities.
Automatic synchronization of findings
Every time a Bright scan finishes, the findings are automatically sent to Wiz.
There is no manual export or reporting workflow required.
Correlation with cloud resources
Wiz maps the vulnerability to the cloud asset hosting the affected application.
This helps security teams understand the infrastructure context behind each finding.
Automatic vulnerability lifecycle updates
When vulnerabilities are fixed and a new Bright scan confirms the fix, Wiz automatically updates the issue status.
This keeps vulnerability tracking consistent across both platforms.
How the Integration Works During a Scan
The integration operates alongside the normal Bright scanning workflow.
First, Bright performs dynamic testing against the application or API.
During the scan, the platform interacts with the running service and evaluates its behavior under various conditions.
This runtime testing allows Bright to identify vulnerabilities such as:
- broken access control
- authentication flaws
- injection vulnerabilities
- insecure API logic
Once the scan completes, Bright generates a set of validated findings.
If the Wiz integration is enabled, those findings are automatically transmitted to Wiz.
Wiz then analyzes the data and associates the vulnerability with the cloud asset hosting the application.
Security teams can now evaluate the vulnerability alongside infrastructure context directly within Wiz.
Why Runtime Findings Matter for Cloud Security Teams
Cloud security platforms provide excellent visibility into infrastructure configuration and asset relationships.
However, they do not always reveal how an application behaves during runtime.
An application may run on properly configured infrastructure yet still contain vulnerabilities within its logic.
For example, an API endpoint may allow unauthorized data access due to an application-level flaw.
From an infrastructure perspective, the service may appear completely secure.
Runtime testing is designed to detect these behavioral issues.
By integrating runtime findings with cloud asset visibility, security teams gain a more complete understanding of risk.
They can evaluate both the vulnerability itself and the environment in which it exists.
Correlating Vulnerabilities with Cloud Assets
One of the most valuable capabilities of the integration is asset correlation.
When Wiz receives a Bright finding, it associates that vulnerability with the corresponding cloud resource.
This allows security teams to determine:
- which workload hosts the application
- which environment the service belongs to
- whether the resource is internet-facing
- how it interacts with other infrastructure components
This context can significantly influence vulnerability prioritization.
For example, a vulnerability affecting a development environment may not represent an urgent risk.
The same vulnerability affecting a production service exposed to the internet could require immediate remediation.
Correlating vulnerabilities with cloud assets helps teams make those decisions more quickly.
What Happens When Vulnerabilities Are Fixed
Remediation workflows often involve several steps.
After developers fix a vulnerability, security teams typically run another scan to confirm that the issue is no longer present.
With the Bright–Wiz integration enabled, this process becomes simpler.
When a new Bright scan confirms that the vulnerability has been resolved, Wiz automatically updates the issue status.
This automatic update ensures that vulnerability records remain accurate across both platforms.
Without automation, teams often need to manually close issues in multiple systems, which can lead to inconsistent reporting.
Integration Setup and Configuration
The integration can be enabled directly through the Bright platform interface.
Users can access the integration settings through the Integrations section in Bright.
To configure the Wiz connection, users provide the following information:
- Client ID
- Client Secret
- Wiz API endpoint URL
Once the credentials are entered, Bright establishes the connection with Wiz.
From that point forward, scan findings will automatically be transmitted to Wiz after each scan.
The goal of the setup process is to keep configuration simple while allowing security teams to connect their application security testing with their cloud security platform.
Operational Benefits for Security Teams
For organizations operating large cloud environments, the integration provides several practical benefits.
Unified visibility
Security teams can analyze vulnerabilities across both application and infrastructure layers.
Faster prioritization
Correlating vulnerabilities with cloud resources helps teams identify which issues require immediate attention.
Reduced investigation effort
Security analysts no longer need to manually correlate findings between different tools.
Better collaboration
AppSec and CloudSec teams can work with the same data and context rather than maintaining separate workflows.
A Common Vendor Trap in Security Integrations
Many security tools advertise integrations, but not all integrations deliver meaningful value.
Some integrations simply forward alerts from one platform to another.
Forwarding alerts is not the same as correlating risk.
A meaningful integration should provide context that helps teams understand how vulnerabilities relate to their environment.
When evaluating integrations, security teams should consider several questions.
Does the integration link vulnerabilities to specific cloud assets?
Does it automatically update vulnerability status when issues are resolved?
Can findings be traced back to the original scan?
Does it reduce investigation time?
If the integration only duplicates alerts without adding context, it may increase operational complexity rather than reduce it.
Release Timeline
The Bright–Wiz integration is scheduled for release on March 10.
This release will allow organizations to begin connecting Bright runtime scan findings with Wiz cloud asset context immediately.
Additional improvements and enhancements may follow as the integration evolves based on customer feedback..
Frequently Asked Questions
What does the Bright–Wiz integration connect to?
It connects Bright’s dynamic application security findings with Wiz’s cloud security platform.
Are findings sent automatically?
Yes. After the integration is enabled, Bright sends findings to Wiz automatically after each scan.
How are vulnerabilities linked to cloud assets?
Wiz correlates the vulnerability with the cloud resource hosting the affected application.
What happens when vulnerabilities are fixed?
When a new Bright scan confirms the issue has been resolved, Wiz automatically updates the vulnerability status.
Is configuration complex?
No. The integration requires entering Wiz API credentials within the Bright integration settings.
Conclusion
Application vulnerabilities do not exist in isolation.
They exist within environments composed of workloads, infrastructure, services, and cloud architecture.
Security tools that operate independently can detect issues, but they cannot always explain their real impact.
Integrations like the Bright–Wiz connection help close that gap.
By bringing runtime application findings into cloud security context, organizations gain a clearer picture of how vulnerabilities affect their environments.
For security teams responsible for protecting complex cloud systems, that visibility is not just convenient – it is essential.
As development of the integration progresses through validation and release planning, we will continue sharing updates on availability and improvements.
And as always, feedback from customers and platform partners will continue shaping how the integration evolves.
