Know which vulnerable code actually runs
Static scanning finds a lot. Runtime Code Analysis is about confirming which of those paths actually execute in your workloads, so you fix what is reachable first. It is on our roadmap, not something we ship today.
This capability is not available in CloudLens yet. We would rather say so than show a screen that does not exist. Here is what we are building and what you can use today.
Where Runtime Code Analysis is headed
Reachability, confirmed at runtime
Correlate a vulnerable function with whether it is loaded and called in a running workload, so an unreachable CVE drops below a reachable one.
Prioritise the exploitable path
Rank findings by what is actually invoked, not just what is present in the dependency tree.
Tie code to the cloud resource
Link a reachable finding back to the workload, its exposure and its role, the way attack paths already do.
What CloudLens already covers
These ship now and cover much of the same ground.
Tell us how you would use it
Ready to see CloudLens in action?
Connect a read-only AWS role or Azure service principal. We'll walk you through your bill, your security graph and the first things worth fixing.