Why are static code analysis and vulnerability scanning not enough?

Why are static code analysis and vulnerability scanning not enough?

HomesimplyblockWhy are static code analysis and vulnerability scanning not enough?
Why are static code analysis and vulnerability scanning not enough?
ChannelPublish DateThumbnail & View CountDownload Video
Channel AvatarPublish Date not found Thumbnail
0 Views
Using static code analysis and multi-stage vulnerability scanning is a big step in securing your application. Many of today's scanners also allow runtime scanning of dynamic environments like Java or Python. However, none of them protect against deeper issues like code injection if they are not yet known (there is no CVE yet). For true zero-day exploits, analyzing application behavior using application firewalls is critical.

Transcript:
What would be the biggest benefit from a user perspective? I mean, if I don't have malicious traffic, why should I care?

We still see a lot of applications that go into production with a number of vulnerabilities, that's just a fact. You also have to ship features. If you look at a particular software stack that's built on open source components and it has vulnerabilities that can be used to break into the container and in some cases through the node and things like that. If you look at the behavior of what that's actually doing, you're just allowing that behavior and then most of those vulnerabilities to go silent because they can't do step two or step three. And the exploit chain that they have and the ability to contain your application while still having a lot of velocity in building new features and building and updating your product, we think it's an added benefit to have something that can automatically contain it and understand it as it evolves.

Please take the opportunity to connect with your friends and family and share this video with them if you find it useful.