A secure development training company partnered with a major cloud provider to launch learning modules aimed at building applications securely by design.
The timing explains the product. With coding assistants embedded in millions of people's routines, the volume of code reaching production grew faster than review capacity, and much of it was accepted as a suggestion rather than written line by line.
Security by design is an old and resistant concept because it requires decisions before the rush arrives. It competes with deadlines, and deadlines usually win when the flaw only appears months later.
What changes with an assistant in the flow is that the design decision gets suggested by a tool optimising for working, not for withstanding attack. Accepting the suggestion is the path of least effort.
For anyone leading a team, the semester's practical lesson is about where to place the barrier: reviewing insecure patterns at the entrance costs less than finding the flaw in production, and it's the only point where generation speed can be offset.