What it Takes to Keep Code Secure
Team Wabbi
July 9, 2022
This interview originally appeared on The Journal of Cyber Policy, July 8 2022
Nine out of ten security breaches originate with defects in software code. This reality puts pressure on developers, and the people who manage them, to make code more secure. But, what does it mean for code to be secure? According to Brittany Greenfield, Founder and CEO of Wabbi, application security (AppSec) is different from other areas of cybersecurity. There is no “locked/unlocked” binary state when it comes to code. Rather, as Greenfield explains in this video, secure code is code that has been developed in accordance with processes and procedures. Security is part of the software development lifecycle, which makes it challenging to get right.
Related Articles
December DevSecOps Roundup: Trends Steering the Future of AppSec
Hey! We’re back with the latest in DevSecOps, security by design, and everything in between. Grab your coffee ☕, and let’s dive in! 📌 Top Blogs 🟣 Zero Trust in AppSec: Why It Belongs in Your Pipelines, Too Zero Trust doesn’t end at the firewall. It belongs in your...
Wabbi Announces Findings of Annual Continuous Security Report
BOSTON / Press Release / May 6, 2024 Progress in Integrating Security into Software Development, Progress in Adoption, but Bottlenecks Persist Wabbi, the leading application security posture management platform, today announced the findings of its annual report on...
Why Your Vulnerability Backlog Will Never Shrink (and What to Do Instead)
Why Your Vulnerability Backlog Will Never Shrink (and What to Do Instead) For most organizations, the vulnerability backlog has become a permanent fixture of software development. Thousands of issues sit unresolved across code, containers, dependencies, and...