Shifting the focus from reactive to proactive, with human-led secure coding
The same 10 software vulnerabilities have caused more security breaches in the last 20+ years than any others. And yet, many businesses still opt for post-breach, post-event remediation; muddling through the human and business ramifications of it all. But now a new research study points to a new, human-led direction.
The following discusses insights derived from a study conducted by Secure Code Warrior with Evans Data Corp titled ‘Shifting from reaction to prevention: The changing face of application security’ (2021) exploring developers attitudes towards secure coding, secure code practices, and security operations. Download the whitepaper here.
In the soon-to-be-released study, developers and development managers were asked about the activities they associate with secure coding. The top three responses were:
- Using scanning tools on deployed applications.
- Manually reviewing code for vulnerabilities.
- The active and ongoing practice of writing software that is protected from vulnerabilities.
So what is this telling us? Two of the top three responses are still focused on reactive approaches, the first dependent on tooling (scanners), and second on the developer (i.e. human) performing manual checks – in both cases after the code is written. Vulnerabilities detected using these methods have to be kicked back to the development team for rework with knock-on effects on project timelines and project costs.
At the same time, two of the three activities nominated rely on the human element – a pointer to growing perceptions of security as a human issue. But of all the activities nominated, the most telling is No. 3, which identifies the human factor in writing software that is protected from vulnerabilities in the first place. This highlights a shift to starting left – a proactive and preventive approach that bakes security into software right from the start of the software development lifecycle.
Reactive can equal EXPENSIVE
According to an IBM study*, it is thirty times more expensive to fix vulnerabilities in post-release code than if they were found and remediated at the beginning. That’s a powerful incentive for a new proactive and a more human approach to defense of software security that equips developers to code more securely, right from the start.
This is what you could call a human-led defense. But to get developers to start caring about security, it has to become part of the way they think and code every day. This is a call for new approaches to training that are hyper-relevant to developers’ everyday work and inspire them to want to learn – neither of which can be said of current training models.
To create a proactive security culture, new training is needed that:
- makes secure coding a positive and engaging experience for developers as they increase their software security skills
- encourages developers to view their daily coding tasks through a security mindset
- makes secure coding intrinsic to their daily workflow
When these threads come together, vulnerabilities are prevented from occurring in the first place, allowing teams to ship quality code faster, with confidence. The good news is that a Learning Platform already exists that 'starts left' in the software development process – one that is already empowering developers with the skills and tools to create quality code from the very start.
*IBM Software Group; Minimizing Code Defects to Improve Software Quality and Lower Development Costs
https://docplayer.net/11413245-Minimizing-code-defects-to-improve-software-quality-and-lower-development-costs.html
.avif)
.avif)
The same 10 software vulnerabilities have caused more security breaches in the last 20+ years than any others. And yet, many businesses still opt for post-breach, post-event remediation; muddling through the human and business ramifications of it all. But now a new research study points to a new, human-led direction.
Secure Code Warrior makes secure coding a positive and engaging experience for developers as they increase their skills. We guide each coder along their own preferred learning pathway, so that security-skilled developers become the everyday superheroes of our connected world.
Secure Code Warrior is here for your organization to help you secure code across the entire software development lifecycle and create a culture in which cybersecurity is top of mind. Whether you’re an AppSec Manager, Developer, CISO, or anyone involved in security, we can help your organization reduce risks associated with insecure code.
Book a demo
Secure Code Warrior makes secure coding a positive and engaging experience for developers as they increase their skills. We guide each coder along their own preferred learning pathway, so that security-skilled developers become the everyday superheroes of our connected world.
This article was written by Secure Code Warrior's team of industry experts, committed to empowering developers with the knowledge and skills to build secure software from the start. Drawing on deep expertise in secure coding practices, industry trends, and real-world insights.
The same 10 software vulnerabilities have caused more security breaches in the last 20+ years than any others. And yet, many businesses still opt for post-breach, post-event remediation; muddling through the human and business ramifications of it all. But now a new research study points to a new, human-led direction.
The following discusses insights derived from a study conducted by Secure Code Warrior with Evans Data Corp titled ‘Shifting from reaction to prevention: The changing face of application security’ (2021) exploring developers attitudes towards secure coding, secure code practices, and security operations. Download the whitepaper here.
In the soon-to-be-released study, developers and development managers were asked about the activities they associate with secure coding. The top three responses were:
- Using scanning tools on deployed applications.
- Manually reviewing code for vulnerabilities.
- The active and ongoing practice of writing software that is protected from vulnerabilities.
So what is this telling us? Two of the top three responses are still focused on reactive approaches, the first dependent on tooling (scanners), and second on the developer (i.e. human) performing manual checks – in both cases after the code is written. Vulnerabilities detected using these methods have to be kicked back to the development team for rework with knock-on effects on project timelines and project costs.
At the same time, two of the three activities nominated rely on the human element – a pointer to growing perceptions of security as a human issue. But of all the activities nominated, the most telling is No. 3, which identifies the human factor in writing software that is protected from vulnerabilities in the first place. This highlights a shift to starting left – a proactive and preventive approach that bakes security into software right from the start of the software development lifecycle.
Reactive can equal EXPENSIVE
According to an IBM study*, it is thirty times more expensive to fix vulnerabilities in post-release code than if they were found and remediated at the beginning. That’s a powerful incentive for a new proactive and a more human approach to defense of software security that equips developers to code more securely, right from the start.
This is what you could call a human-led defense. But to get developers to start caring about security, it has to become part of the way they think and code every day. This is a call for new approaches to training that are hyper-relevant to developers’ everyday work and inspire them to want to learn – neither of which can be said of current training models.
To create a proactive security culture, new training is needed that:
- makes secure coding a positive and engaging experience for developers as they increase their software security skills
- encourages developers to view their daily coding tasks through a security mindset
- makes secure coding intrinsic to their daily workflow
When these threads come together, vulnerabilities are prevented from occurring in the first place, allowing teams to ship quality code faster, with confidence. The good news is that a Learning Platform already exists that 'starts left' in the software development process – one that is already empowering developers with the skills and tools to create quality code from the very start.
*IBM Software Group; Minimizing Code Defects to Improve Software Quality and Lower Development Costs
https://docplayer.net/11413245-Minimizing-code-defects-to-improve-software-quality-and-lower-development-costs.html
The same 10 software vulnerabilities have caused more security breaches in the last 20+ years than any others. And yet, many businesses still opt for post-breach, post-event remediation; muddling through the human and business ramifications of it all. But now a new research study points to a new, human-led direction.
The following discusses insights derived from a study conducted by Secure Code Warrior with Evans Data Corp titled ‘Shifting from reaction to prevention: The changing face of application security’ (2021) exploring developers attitudes towards secure coding, secure code practices, and security operations. Download the whitepaper here.
In the soon-to-be-released study, developers and development managers were asked about the activities they associate with secure coding. The top three responses were:
- Using scanning tools on deployed applications.
- Manually reviewing code for vulnerabilities.
- The active and ongoing practice of writing software that is protected from vulnerabilities.
So what is this telling us? Two of the top three responses are still focused on reactive approaches, the first dependent on tooling (scanners), and second on the developer (i.e. human) performing manual checks – in both cases after the code is written. Vulnerabilities detected using these methods have to be kicked back to the development team for rework with knock-on effects on project timelines and project costs.
At the same time, two of the three activities nominated rely on the human element – a pointer to growing perceptions of security as a human issue. But of all the activities nominated, the most telling is No. 3, which identifies the human factor in writing software that is protected from vulnerabilities in the first place. This highlights a shift to starting left – a proactive and preventive approach that bakes security into software right from the start of the software development lifecycle.
Reactive can equal EXPENSIVE
According to an IBM study*, it is thirty times more expensive to fix vulnerabilities in post-release code than if they were found and remediated at the beginning. That’s a powerful incentive for a new proactive and a more human approach to defense of software security that equips developers to code more securely, right from the start.
This is what you could call a human-led defense. But to get developers to start caring about security, it has to become part of the way they think and code every day. This is a call for new approaches to training that are hyper-relevant to developers’ everyday work and inspire them to want to learn – neither of which can be said of current training models.
To create a proactive security culture, new training is needed that:
- makes secure coding a positive and engaging experience for developers as they increase their software security skills
- encourages developers to view their daily coding tasks through a security mindset
- makes secure coding intrinsic to their daily workflow
When these threads come together, vulnerabilities are prevented from occurring in the first place, allowing teams to ship quality code faster, with confidence. The good news is that a Learning Platform already exists that 'starts left' in the software development process – one that is already empowering developers with the skills and tools to create quality code from the very start.
*IBM Software Group; Minimizing Code Defects to Improve Software Quality and Lower Development Costs
https://docplayer.net/11413245-Minimizing-code-defects-to-improve-software-quality-and-lower-development-costs.html
Click on the link below and download the PDF of this resource.
Secure Code Warrior is here for your organization to help you secure code across the entire software development lifecycle and create a culture in which cybersecurity is top of mind. Whether you’re an AppSec Manager, Developer, CISO, or anyone involved in security, we can help your organization reduce risks associated with insecure code.
View reportBook a demo
Secure Code Warrior makes secure coding a positive and engaging experience for developers as they increase their skills. We guide each coder along their own preferred learning pathway, so that security-skilled developers become the everyday superheroes of our connected world.
This article was written by Secure Code Warrior's team of industry experts, committed to empowering developers with the knowledge and skills to build secure software from the start. Drawing on deep expertise in secure coding practices, industry trends, and real-world insights.
The same 10 software vulnerabilities have caused more security breaches in the last 20+ years than any others. And yet, many businesses still opt for post-breach, post-event remediation; muddling through the human and business ramifications of it all. But now a new research study points to a new, human-led direction.
The following discusses insights derived from a study conducted by Secure Code Warrior with Evans Data Corp titled ‘Shifting from reaction to prevention: The changing face of application security’ (2021) exploring developers attitudes towards secure coding, secure code practices, and security operations. Download the whitepaper here.
In the soon-to-be-released study, developers and development managers were asked about the activities they associate with secure coding. The top three responses were:
- Using scanning tools on deployed applications.
- Manually reviewing code for vulnerabilities.
- The active and ongoing practice of writing software that is protected from vulnerabilities.
So what is this telling us? Two of the top three responses are still focused on reactive approaches, the first dependent on tooling (scanners), and second on the developer (i.e. human) performing manual checks – in both cases after the code is written. Vulnerabilities detected using these methods have to be kicked back to the development team for rework with knock-on effects on project timelines and project costs.
At the same time, two of the three activities nominated rely on the human element – a pointer to growing perceptions of security as a human issue. But of all the activities nominated, the most telling is No. 3, which identifies the human factor in writing software that is protected from vulnerabilities in the first place. This highlights a shift to starting left – a proactive and preventive approach that bakes security into software right from the start of the software development lifecycle.
Reactive can equal EXPENSIVE
According to an IBM study*, it is thirty times more expensive to fix vulnerabilities in post-release code than if they were found and remediated at the beginning. That’s a powerful incentive for a new proactive and a more human approach to defense of software security that equips developers to code more securely, right from the start.
This is what you could call a human-led defense. But to get developers to start caring about security, it has to become part of the way they think and code every day. This is a call for new approaches to training that are hyper-relevant to developers’ everyday work and inspire them to want to learn – neither of which can be said of current training models.
To create a proactive security culture, new training is needed that:
- makes secure coding a positive and engaging experience for developers as they increase their software security skills
- encourages developers to view their daily coding tasks through a security mindset
- makes secure coding intrinsic to their daily workflow
When these threads come together, vulnerabilities are prevented from occurring in the first place, allowing teams to ship quality code faster, with confidence. The good news is that a Learning Platform already exists that 'starts left' in the software development process – one that is already empowering developers with the skills and tools to create quality code from the very start.
*IBM Software Group; Minimizing Code Defects to Improve Software Quality and Lower Development Costs
https://docplayer.net/11413245-Minimizing-code-defects-to-improve-software-quality-and-lower-development-costs.html
Table of contents
Secure Code Warrior makes secure coding a positive and engaging experience for developers as they increase their skills. We guide each coder along their own preferred learning pathway, so that security-skilled developers become the everyday superheroes of our connected world.
Secure Code Warrior is here for your organization to help you secure code across the entire software development lifecycle and create a culture in which cybersecurity is top of mind. Whether you’re an AppSec Manager, Developer, CISO, or anyone involved in security, we can help your organization reduce risks associated with insecure code.
Book a demoDownloadResources to get you started
Secure by Design: Defining Best Practices, Enabling Developers and Benchmarking Preventative Security Outcomes
In this research paper, Secure Code Warrior co-founders, Pieter Danhieux and Dr. Matias Madou, Ph.D., along with expert contributors, Chris Inglis, Former US National Cyber Director (now Strategic Advisor to Paladin Capital Group), and Devin Lynch, Senior Director, Paladin Global Institute, will reveal key findings from over twenty in-depth interviews with enterprise security leaders including CISOs, a VP of Application Security, and software security professionals.
Benchmarking Security Skills: Streamlining Secure-by-Design in the Enterprise
Finding meaningful data on the success of Secure-by-Design initiatives is notoriously difficult. CISOs are often challenged when attempting to prove the return on investment (ROI) and business value of security program activities at both the people and company levels. Not to mention, it’s particularly difficult for enterprises to gain insights into how their organizations are benchmarked against current industry standards. The President’s National Cybersecurity Strategy challenged stakeholders to “embrace security and resilience by design.” The key to making Secure-by-Design initiatives work is not only giving developers the skills to ensure secure code, but also assuring the regulators that those skills are in place. In this presentation, we share a myriad of qualitative and quantitative data, derived from multiple primary sources, including internal data points collected from over 250,000 developers, data-driven customer insights, and public studies. Leveraging this aggregation of data points, we aim to communicate a vision of the current state of Secure-by-Design initiatives across multiple verticals. The report details why this space is currently underutilized, the significant impact a successful upskilling program can have on cybersecurity risk mitigation, and the potential to eliminate categories of vulnerabilities from a codebase.
Resources to get you started
Close the Loop on Vulnerabilities with Secure Code Warrior + HackerOne
Secure Code Warrior is excited to announce our new integration with HackerOne, a leader in offensive security solutions. Together, we're building a powerful, integrated ecosystem. HackerOne pinpoints where vulnerabilities are actually happening in real-world environments, exposing the "what" and "where" of security issues.
Revealed: How the Cyber Industry Defines Secure by Design
In our latest white paper, our Co-Founders, Pieter Danhieux and Dr. Matias Madou, Ph.D., sat down with over twenty enterprise security leaders, including CISOs, AppSec leaders and security professionals, to figure out the key pieces of this puzzle and uncover the reality behind the Secure by Design movement. It’s a shared ambition across the security teams, but no shared playbook.
Is Vibe Coding Going to Turn Your Codebase Into a Frat Party?
Vibe coding is like a college frat party, and AI is the centerpiece of all the festivities, the keg. It’s a lot of fun to let loose, get creative, and see where your imagination can take you, but after a few keg stands, drinking (or, using AI) in moderation is undoubtedly the safer long-term solution.
Developer-driven coding.
Securely.
Contact us today and make software security an intrinsic part of your development process.
