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.
Secure Code Warrior builds a culture of security-driven developers by giving them the skills to code securely. Our flagship Agile Learning Platform delivers relevant skills-based pathways, hands-on missions, and contextual tools for developers to rapidly learn, build, and apply their skills to write secure code at speed.
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.
Secure Code Warrior builds a culture of security-driven developers by giving them the skills to code securely. Our flagship Agile Learning Platform delivers relevant skills-based pathways, hands-on missions, and contextual tools for developers to rapidly learn, build, and apply their skills to write secure code at speed.
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
Resources to get you started
10 Key Predictions: Secure Code Warrior on AI & Secure-by-Design’s Influence in 2025
Organizations are facing tough decisions on AI usage to support long-term productivity, sustainability, and security ROI. It’s become clear to us over the last few years that AI will never fully replace the role of the developer. From AI + developer partnerships to the increasing pressures (and confusion) around Secure-by-Design expectations, let’s take a closer look at what we can expect over the next year.
OWASP Top 10 For LLM Applications: What’s New, Changed, and How to Stay Secure
Stay ahead in securing LLM applications with the latest OWASP Top 10 updates. Discover what's new, what’s changed, and how Secure Code Warrior equips you with up-to-date learning resources to mitigate risks in Generative AI.
Trust Score Reveals the Value of Secure-by-Design Upskilling Initiatives
Our research has shown that secure code training works. Trust Score, using an algorithm drawing on more than 20 million learning data points from work by more than 250,000 learners at over 600 organizations, reveals its effectiveness in driving down vulnerabilities and how to make the initiative even more effective.
.png)
Reactive Versus Preventive Security: Prevention Is a Better Cure
The idea of bringing preventive security to legacy code and systems at the same time as newer applications can seem daunting, but a Secure-by-Design approach, enforced by upskilling developers, can apply security best practices to those systems. It’s the best chance many organizations have of improving their security postures.
Developer-driven coding.
Securely.
Contact us today and make software security an intrinsic part of your development process.
