Agir avec le NIST : notre position dirigée par l'homme sur l'avenir de la cyberdéfense
The recent cybersecurity Executive Order from the Biden Administration has certainly got the security industry talking, especially those who are looking to win over developers to the importance of applying secure coding best practices in their day-to-day work. For the first time, developers who are working on software in use by the federal government must have verified security skills, as well as adherence to new, evolved guidelines.
This marks a positive change in the cyber defense status quo, and finally makes adequate upskilling of developers part of the conversation. While these policies are US government-centric, they offer a global opportunity for organizations to address and upgrade current security standards, everything from developers to security analysis of software supply chains.
NIST recently sought public comment to inform their next updates to HIPAA legislation, among others, and this was an unmissable opportunity for us to pool our company expertise into positioning papers that can help inform a safer, and more effective, human-led approach to cybersecurity that will help organizations leverage their teams for greater outcomes.
As an expert-driven organization, we are fortunate to have some of the most dedicated and accomplished cybersecurity professionals working with us, including Ph.D. candidate Pieter de Cremer, and Dr. Brian Chess, who is part of our Technical Advisory Board. The three of us put our heads together to formally submit positioning papers to NIST, calling out ways our approach to developer upskilling and preventative security at the software creation stage could positively impact cybersecurity standards going forward.
A secure development pathway, paved for developers
Vulnerability scanning tools, monitoring and other forms of security automation are increasingly prevalent, and they feature in both the new Executive Order, as well as within NIST guidelines. They are an increasingly essential part of a modern security program, but history and the present show that scanning tools in particular certainly find vulnerabilities in software with ever-increasing efficiency, yet this alone has no effect on reducing them, or, indeed, improving security from the start.
A cumbersome tech stack that is distracting and slows down the developer workflow is one of the fundamental reasons that developers disengage with security and view it in a negative light. However, if developers had a paved pathway for secure development, one that was customized to suit not just the technology, but also languages, frameworks, and project-specific development objectives, then embedding security into the development process from the beginning - with as little disruption to their productivity as possible - is an ideal that would result in significant reduction in common vulnerabilities over time.
To read our NIST positioning paper in full, download it now:
.webp)
Certification framework for secure development practices: The (current) missing link
To date, there is no formal certification to verifying secure coding skills and best practices. This has been an industry oversight for a long time, and it’s our position that this is essential for the future of improved cyber defense and secure development.
We know there are many forms of security training targeting developers, but if the volume of large-scale data breaches, cyberattacks, and poor quality code out there is any indication, it’s not creating security-aware developers, and they are not being equipped with the knowledge to make a dent in a problem that is only getting worse.
Developer upskilling requires tools and education that is day-job relevant, contextual, bite-sized (yet frequent), and allows them to build upon existing knowledge in the languages and frameworks they actually use. Generic training does not suffice, and this needs to be made abundantly clear in legislation and industry bodies such as NIST.
The NICE Framework is more than suitable to build out comprehensive certification guidelines that actively use methodologies that work, and are of most interest and relevance to developers, and their work. Aligning with this recognized institutional framework helps to standardize practices that truly make a difference, and provides more concrete pathways for organizations to follow.
To read our second NIST positioning paper in full, download it now:
The people factor in cybersecurity is often forgotten, and it’s time we worked towards human solutions for human problems such as recurrent common vulnerabilities. Decades-old bugs should no longer trip us up, but it will take the backing of global governments to change the status quo and provide measurable, positive impact.
Are you ready to certify your developers? You’ve come to the right place. Check out our Learning Platform today.
Le récent décret sur la cybersécurité de l'administration Biden a certainement fait parler le secteur de la sécurité, en particulier ceux qui cherchent à convaincre les développeurs de l'importance d'appliquer les meilleures pratiques de codage sécurisé dans leur travail quotidien.
Matias Madou, Ph.D. is a security expert, researcher, and CTO and co-founder of Secure Code Warrior. Matias obtained his Ph.D. in Application Security from Ghent University, focusing on static analysis solutions. He later joined Fortify in the US, where he realized that it was insufficient to solely detect code problems without aiding developers in writing secure code. This inspired him to develop products that assist developers, alleviate the burden of security, and exceed customers' expectations. When he is not at his desk as part of Team Awesome, he enjoys being on stage presenting at conferences including RSA Conference, BlackHat and DefCon.
Secure Code Warrior est là pour aider votre organisation à sécuriser le code tout au long du cycle de développement logiciel et à créer une culture dans laquelle la cybersécurité est une priorité. Que vous soyez responsable de la sécurité des applications, développeur, responsable de la sécurité informatique ou toute autre personne impliquée dans la sécurité, nous pouvons aider votre organisation à réduire les risques associés à un code non sécurisé.
Réservez une démo
Matias Madou, Ph.D. is a security expert, researcher, and CTO and co-founder of Secure Code Warrior. Matias obtained his Ph.D. in Application Security from Ghent University, focusing on static analysis solutions. He later joined Fortify in the US, where he realized that it was insufficient to solely detect code problems without aiding developers in writing secure code. This inspired him to develop products that assist developers, alleviate the burden of security, and exceed customers' expectations. When he is not at his desk as part of Team Awesome, he enjoys being on stage presenting at conferences including RSA Conference, BlackHat and DefCon.
Matias is a researcher and developer with more than 15 years of hands-on software security experience. He has developed solutions for companies such as Fortify Software and his own company Sensei Security. Over his career, Matias has led multiple application security research projects which have led to commercial products and boasts over 10 patents under his belt. When he is away from his desk, Matias has served as an instructor for advanced application security training courses and regularly speaks at global conferences including RSA Conference, Black Hat, DefCon, BSIMM, OWASP AppSec and BruCon.
Matias holds a Ph.D. in Computer Engineering from Ghent University, where he studied application security through program obfuscation to hide the inner workings of an application.
The recent cybersecurity Executive Order from the Biden Administration has certainly got the security industry talking, especially those who are looking to win over developers to the importance of applying secure coding best practices in their day-to-day work. For the first time, developers who are working on software in use by the federal government must have verified security skills, as well as adherence to new, evolved guidelines.
This marks a positive change in the cyber defense status quo, and finally makes adequate upskilling of developers part of the conversation. While these policies are US government-centric, they offer a global opportunity for organizations to address and upgrade current security standards, everything from developers to security analysis of software supply chains.
NIST recently sought public comment to inform their next updates to HIPAA legislation, among others, and this was an unmissable opportunity for us to pool our company expertise into positioning papers that can help inform a safer, and more effective, human-led approach to cybersecurity that will help organizations leverage their teams for greater outcomes.
As an expert-driven organization, we are fortunate to have some of the most dedicated and accomplished cybersecurity professionals working with us, including Ph.D. candidate Pieter de Cremer, and Dr. Brian Chess, who is part of our Technical Advisory Board. The three of us put our heads together to formally submit positioning papers to NIST, calling out ways our approach to developer upskilling and preventative security at the software creation stage could positively impact cybersecurity standards going forward.
A secure development pathway, paved for developers
Vulnerability scanning tools, monitoring and other forms of security automation are increasingly prevalent, and they feature in both the new Executive Order, as well as within NIST guidelines. They are an increasingly essential part of a modern security program, but history and the present show that scanning tools in particular certainly find vulnerabilities in software with ever-increasing efficiency, yet this alone has no effect on reducing them, or, indeed, improving security from the start.
A cumbersome tech stack that is distracting and slows down the developer workflow is one of the fundamental reasons that developers disengage with security and view it in a negative light. However, if developers had a paved pathway for secure development, one that was customized to suit not just the technology, but also languages, frameworks, and project-specific development objectives, then embedding security into the development process from the beginning - with as little disruption to their productivity as possible - is an ideal that would result in significant reduction in common vulnerabilities over time.
To read our NIST positioning paper in full, download it now:
Certification framework for secure development practices: The (current) missing link
To date, there is no formal certification to verifying secure coding skills and best practices. This has been an industry oversight for a long time, and it’s our position that this is essential for the future of improved cyber defense and secure development.
We know there are many forms of security training targeting developers, but if the volume of large-scale data breaches, cyberattacks, and poor quality code out there is any indication, it’s not creating security-aware developers, and they are not being equipped with the knowledge to make a dent in a problem that is only getting worse.
Developer upskilling requires tools and education that is day-job relevant, contextual, bite-sized (yet frequent), and allows them to build upon existing knowledge in the languages and frameworks they actually use. Generic training does not suffice, and this needs to be made abundantly clear in legislation and industry bodies such as NIST.
The NICE Framework is more than suitable to build out comprehensive certification guidelines that actively use methodologies that work, and are of most interest and relevance to developers, and their work. Aligning with this recognized institutional framework helps to standardize practices that truly make a difference, and provides more concrete pathways for organizations to follow.
To read our second NIST positioning paper in full, download it now:
The people factor in cybersecurity is often forgotten, and it’s time we worked towards human solutions for human problems such as recurrent common vulnerabilities. Decades-old bugs should no longer trip us up, but it will take the backing of global governments to change the status quo and provide measurable, positive impact.
Are you ready to certify your developers? You’ve come to the right place. Check out our Learning Platform today.
The recent cybersecurity Executive Order from the Biden Administration has certainly got the security industry talking, especially those who are looking to win over developers to the importance of applying secure coding best practices in their day-to-day work. For the first time, developers who are working on software in use by the federal government must have verified security skills, as well as adherence to new, evolved guidelines.
This marks a positive change in the cyber defense status quo, and finally makes adequate upskilling of developers part of the conversation. While these policies are US government-centric, they offer a global opportunity for organizations to address and upgrade current security standards, everything from developers to security analysis of software supply chains.
NIST recently sought public comment to inform their next updates to HIPAA legislation, among others, and this was an unmissable opportunity for us to pool our company expertise into positioning papers that can help inform a safer, and more effective, human-led approach to cybersecurity that will help organizations leverage their teams for greater outcomes.
As an expert-driven organization, we are fortunate to have some of the most dedicated and accomplished cybersecurity professionals working with us, including Ph.D. candidate Pieter de Cremer, and Dr. Brian Chess, who is part of our Technical Advisory Board. The three of us put our heads together to formally submit positioning papers to NIST, calling out ways our approach to developer upskilling and preventative security at the software creation stage could positively impact cybersecurity standards going forward.
A secure development pathway, paved for developers
Vulnerability scanning tools, monitoring and other forms of security automation are increasingly prevalent, and they feature in both the new Executive Order, as well as within NIST guidelines. They are an increasingly essential part of a modern security program, but history and the present show that scanning tools in particular certainly find vulnerabilities in software with ever-increasing efficiency, yet this alone has no effect on reducing them, or, indeed, improving security from the start.
A cumbersome tech stack that is distracting and slows down the developer workflow is one of the fundamental reasons that developers disengage with security and view it in a negative light. However, if developers had a paved pathway for secure development, one that was customized to suit not just the technology, but also languages, frameworks, and project-specific development objectives, then embedding security into the development process from the beginning - with as little disruption to their productivity as possible - is an ideal that would result in significant reduction in common vulnerabilities over time.
To read our NIST positioning paper in full, download it now:
Certification framework for secure development practices: The (current) missing link
To date, there is no formal certification to verifying secure coding skills and best practices. This has been an industry oversight for a long time, and it’s our position that this is essential for the future of improved cyber defense and secure development.
We know there are many forms of security training targeting developers, but if the volume of large-scale data breaches, cyberattacks, and poor quality code out there is any indication, it’s not creating security-aware developers, and they are not being equipped with the knowledge to make a dent in a problem that is only getting worse.
Developer upskilling requires tools and education that is day-job relevant, contextual, bite-sized (yet frequent), and allows them to build upon existing knowledge in the languages and frameworks they actually use. Generic training does not suffice, and this needs to be made abundantly clear in legislation and industry bodies such as NIST.
The NICE Framework is more than suitable to build out comprehensive certification guidelines that actively use methodologies that work, and are of most interest and relevance to developers, and their work. Aligning with this recognized institutional framework helps to standardize practices that truly make a difference, and provides more concrete pathways for organizations to follow.
To read our second NIST positioning paper in full, download it now:
The people factor in cybersecurity is often forgotten, and it’s time we worked towards human solutions for human problems such as recurrent common vulnerabilities. Decades-old bugs should no longer trip us up, but it will take the backing of global governments to change the status quo and provide measurable, positive impact.
Are you ready to certify your developers? You’ve come to the right place. Check out our Learning Platform today.
Cliquez sur le lien ci-dessous et téléchargez le PDF de cette ressource.
Secure Code Warrior est là pour aider votre organisation à sécuriser le code tout au long du cycle de développement logiciel et à créer une culture dans laquelle la cybersécurité est une priorité. Que vous soyez responsable de la sécurité des applications, développeur, responsable de la sécurité informatique ou toute autre personne impliquée dans la sécurité, nous pouvons aider votre organisation à réduire les risques associés à un code non sécurisé.
Afficher le rapportRéservez une démo
Matias Madou, Ph.D. is a security expert, researcher, and CTO and co-founder of Secure Code Warrior. Matias obtained his Ph.D. in Application Security from Ghent University, focusing on static analysis solutions. He later joined Fortify in the US, where he realized that it was insufficient to solely detect code problems without aiding developers in writing secure code. This inspired him to develop products that assist developers, alleviate the burden of security, and exceed customers' expectations. When he is not at his desk as part of Team Awesome, he enjoys being on stage presenting at conferences including RSA Conference, BlackHat and DefCon.
Matias is a researcher and developer with more than 15 years of hands-on software security experience. He has developed solutions for companies such as Fortify Software and his own company Sensei Security. Over his career, Matias has led multiple application security research projects which have led to commercial products and boasts over 10 patents under his belt. When he is away from his desk, Matias has served as an instructor for advanced application security training courses and regularly speaks at global conferences including RSA Conference, Black Hat, DefCon, BSIMM, OWASP AppSec and BruCon.
Matias holds a Ph.D. in Computer Engineering from Ghent University, where he studied application security through program obfuscation to hide the inner workings of an application.
The recent cybersecurity Executive Order from the Biden Administration has certainly got the security industry talking, especially those who are looking to win over developers to the importance of applying secure coding best practices in their day-to-day work. For the first time, developers who are working on software in use by the federal government must have verified security skills, as well as adherence to new, evolved guidelines.
This marks a positive change in the cyber defense status quo, and finally makes adequate upskilling of developers part of the conversation. While these policies are US government-centric, they offer a global opportunity for organizations to address and upgrade current security standards, everything from developers to security analysis of software supply chains.
NIST recently sought public comment to inform their next updates to HIPAA legislation, among others, and this was an unmissable opportunity for us to pool our company expertise into positioning papers that can help inform a safer, and more effective, human-led approach to cybersecurity that will help organizations leverage their teams for greater outcomes.
As an expert-driven organization, we are fortunate to have some of the most dedicated and accomplished cybersecurity professionals working with us, including Ph.D. candidate Pieter de Cremer, and Dr. Brian Chess, who is part of our Technical Advisory Board. The three of us put our heads together to formally submit positioning papers to NIST, calling out ways our approach to developer upskilling and preventative security at the software creation stage could positively impact cybersecurity standards going forward.
A secure development pathway, paved for developers
Vulnerability scanning tools, monitoring and other forms of security automation are increasingly prevalent, and they feature in both the new Executive Order, as well as within NIST guidelines. They are an increasingly essential part of a modern security program, but history and the present show that scanning tools in particular certainly find vulnerabilities in software with ever-increasing efficiency, yet this alone has no effect on reducing them, or, indeed, improving security from the start.
A cumbersome tech stack that is distracting and slows down the developer workflow is one of the fundamental reasons that developers disengage with security and view it in a negative light. However, if developers had a paved pathway for secure development, one that was customized to suit not just the technology, but also languages, frameworks, and project-specific development objectives, then embedding security into the development process from the beginning - with as little disruption to their productivity as possible - is an ideal that would result in significant reduction in common vulnerabilities over time.
To read our NIST positioning paper in full, download it now:
Certification framework for secure development practices: The (current) missing link
To date, there is no formal certification to verifying secure coding skills and best practices. This has been an industry oversight for a long time, and it’s our position that this is essential for the future of improved cyber defense and secure development.
We know there are many forms of security training targeting developers, but if the volume of large-scale data breaches, cyberattacks, and poor quality code out there is any indication, it’s not creating security-aware developers, and they are not being equipped with the knowledge to make a dent in a problem that is only getting worse.
Developer upskilling requires tools and education that is day-job relevant, contextual, bite-sized (yet frequent), and allows them to build upon existing knowledge in the languages and frameworks they actually use. Generic training does not suffice, and this needs to be made abundantly clear in legislation and industry bodies such as NIST.
The NICE Framework is more than suitable to build out comprehensive certification guidelines that actively use methodologies that work, and are of most interest and relevance to developers, and their work. Aligning with this recognized institutional framework helps to standardize practices that truly make a difference, and provides more concrete pathways for organizations to follow.
To read our second NIST positioning paper in full, download it now:
The people factor in cybersecurity is often forgotten, and it’s time we worked towards human solutions for human problems such as recurrent common vulnerabilities. Decades-old bugs should no longer trip us up, but it will take the backing of global governments to change the status quo and provide measurable, positive impact.
Are you ready to certify your developers? You’ve come to the right place. Check out our Learning Platform today.
Table des matières
Matias Madou, Ph.D. is a security expert, researcher, and CTO and co-founder of Secure Code Warrior. Matias obtained his Ph.D. in Application Security from Ghent University, focusing on static analysis solutions. He later joined Fortify in the US, where he realized that it was insufficient to solely detect code problems without aiding developers in writing secure code. This inspired him to develop products that assist developers, alleviate the burden of security, and exceed customers' expectations. When he is not at his desk as part of Team Awesome, he enjoys being on stage presenting at conferences including RSA Conference, BlackHat and DefCon.
Secure Code Warrior est là pour aider votre organisation à sécuriser le code tout au long du cycle de développement logiciel et à créer une culture dans laquelle la cybersécurité est une priorité. Que vous soyez responsable de la sécurité des applications, développeur, responsable de la sécurité informatique ou toute autre personne impliquée dans la sécurité, nous pouvons aider votre organisation à réduire les risques associés à un code non sécurisé.
Réservez une démoTéléchargerRessources pour vous aider à démarrer
Sujets et contenus de formation sur le code sécurisé
Notre contenu de pointe évolue constamment pour s'adapter à l'évolution constante du paysage du développement de logiciels tout en tenant compte de votre rôle. Des sujets couvrant tout, de l'IA à l'injection XQuery, proposés pour une variété de postes, allant des architectes aux ingénieurs en passant par les chefs de produit et l'assurance qualité. Découvrez un aperçu de ce que notre catalogue de contenu a à offrir par sujet et par rôle.
%20(1).avif)
.avif)
Threat Modeling with AI: Turning Every Developer into a Threat Modeler
Walk away better equipped to help developers combine threat modeling ideas and techniques with the AI tools they're already using to strengthen security, improve collaboration, and build more resilient software from the start.
Ressources pour vous aider à démarrer
Cybermon est de retour : les missions d'IA Beat the Boss sont désormais disponibles à la demande
Cybermon 2025 Beat the Boss est désormais disponible toute l'année dans SCW. Déployez des défis de sécurité avancés liés à l'IA et au LLM pour renforcer le développement sécurisé de l'IA à grande échelle.
Explication de la loi sur la cyberrésilience : ce que cela signifie pour le développement de logiciels sécurisés dès la conception
Découvrez ce que la loi européenne sur la cyberrésilience (CRA) exige, à qui elle s'applique et comment les équipes d'ingénieurs peuvent se préparer grâce à des pratiques de sécurité dès la conception, à la prévention des vulnérabilités et au renforcement des capacités des développeurs.
Facilitateur 1 : Critères de réussite définis et mesurables
Enabler 1 donne le coup d'envoi de notre série en 10 parties intitulée Enablers of Success en montrant comment associer le codage sécurisé à des résultats commerciaux tels que la réduction des risques et la rapidité pour assurer la maturité à long terme des programmes.
