Insights from experts shaping secure development

À l'heure actuelle, seuls 15 % des développeurs pensent que les pratiques de code sécurisées devraient être la responsabilité de chacun. Dans un monde où les menaces à la sécurité augmentent, cela ne suffit tout simplement pas. Il faut faire quelque chose. Pour créer une culture AppSec saine, il est essentiel de comprendre les principales influences (et influenceurs !) en train de jouer.

Nous devons renforcer l'approche humaine des meilleures pratiques en matière de cybersécurité, et elle donnera de meilleurs résultats qu'une dépendance excessive à l'automatisation, aux outils et à la réaction à des problèmes déjà intégrés et découverts.

Le code non sécurisé coûte des millions aux entreprises. Alors, qu'est-ce qui les empêche d'adopter des pratiques de codage sécurisées ? Dans un monde qui repose sur les logiciels pour à peu près tout, il est essentiel de garantir la sécurité du code. La réputation de la marque et sa viabilité financière en dépendent. Cela dit, le codage sécurisé suscite de nombreuses préoccupations et de nombreux obstacles entravent son adoption complète et efficace. Plus que jamais, une nouvelle façon de travailler s'impose.

Kamer van Koophandel shares how it embedded secure coding into everyday development through role-based certifications, Trust Score benchmarking, and a culture of shared security ownership.

See how Paysafe's partnership with Secure Code Warrior led to a 45% boost in developer productivity and a major reduction in code vulnerabilities.

DigitalOcean's use of Secure Code Warrior training has significantly reduced security debt, allowing teams to focus more on innovation and productivity. The improved security has strengthened their product quality and competitive edge. Looking ahead, the SCW Trust Score will help them further enhance security practices and continue driving innovation.

AI is now a key piece of modern software development. More than four out of five developers use AI coding tools daily or weekly – with many relying on multiple tools in parallel. Teams must understand where automation ends, and where accountability begins.

Secure code should be grounded more in concepts like secure by default and secure by design than by “spot the vuln” thinking. Matias Madou shares his experience in secure coding training and the importance of teaching critical thinking. He also discusses why critical thinking is so closely related to threat modeling and how LLMs can be a tool for helping developers get beyond the superficial advice of, “Think like an attacker.”

Organizations are at an inflection point driven by the explosive adoption of AI, which promises significant changes in how businesses operate. That leaves CISOs on unsteady ground. As the gatekeepers of their organization’s data and access, they must ensure the security of the enterprise. However, the prospects of a headlong charge into wide-ranging, and possibly unchecked, use of AI could create a flood of security issues that many CISOs, under their current organizational structures, aren’t equipped to handle.

AI risk doesn't stop at engineering. Get the one-pager on Citizen AI — build AI literacy and safe habits across your whole workforce.

From AI autocomplete to autonomous agents—explore how software development is evolving and what it means for security, governance, and your team.

Gartner named SCW twice in the 2026 Hype Cycle for Secure Software Engineering. Here's why it matters for AI-driven development.