01 / Automatic vulnerability scanning in development
A telecom operator’s cloud
Vulnerability scanning built into the development flow.
- Engagement
- PoC
- Stage
- Completed
- Runs on
- The customer’s existing development flow (commit, merge, release)
- Tech
- Static analysis · symbolic execution · deep learning · dependency CVEs
- The problem
- They wanted vulnerabilities, including high-severity CVEs in dependencies, caught automatically at commit and merge, without setting up another system.
- What we delivered
- A vulnerability-detection engine at the commit and merge steps, combining static analysis, symbolic execution and deep learning.
Effect
- About 50%lower false-positive rate
About half the false alarms are gone, so the security team no longer wades through alerts and can spend its time on real vulnerabilities.
How we did it
What we did
- 01The flow: enterprise code → commit / merge → automatic vulnerability scan → release
- 02The detection engine: static analysis + symbolic execution + deep learning
- 03Flags high- and medium-severity CVEs in dependencies and supports fixing them
Talk to us if this sounds familiar
- Your pipeline already has a scanner, but nobody reads it any more because of the false alarms
- You depend on many third-party libraries and want to know which high-severity CVEs really affect you
- You want vulnerability checks added without replacing your CI