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
The Wabbi Wire: What’s the Big Deal about ASPM?
Wabbi Wire: What's the Big Deal about ASPM? Application Security Posture Management (ASPM) is more than just another security acronym—it’s the key to turning DevSecOps from a buzzword into a business enabler. The challenge? Security and development teams often speak...
Wabbi Announces General Availability of its Advanced Application Security Risk Index Enabling Risk-Management-by-Design
BOSTON / Press Release / February 21, 2024 Wabbi, the leader in Application Security Posture Management (ASPM), today announced the general availability of its Advanced Wabbi Risk Index. The Application Security Risk Index is a key component of Wabbi’s...
The Hidden Risks: Internal Failures in Security by Design
The Hidden Risks: Internal Failures in Security by Design When we think about cybersecurity breaches, external attackers often come to mind—hackers, malware, and cybercriminals targeting organizations from the outside. However, breaches can also stem from within,...