Blog

Shifting Left

September 22, 2017
Pieter Danhieux
Close-up of a person riding a unicycle on a cobblestone street in black and white.

If a developer writes a cross-site scripting error as they're coding in JavaScript, and they're able to detect that within minutes of creating that flaw, it will likely only require minutes or seconds to fix.

Whereas if that flaw is discovered two weeks later by a manual tester, that's going to be then entered into a defect tracking system. It's going to be triaged. It's going to be put into someone's bug queue.

With the delay in identification, it will have to be researched in its original context and will slow down development. Now, you're potentially talking hours of time to fix the same flaw. Maybe a scale of 10 or 100 times more time is taken

I couldn't agree with Chris Wysopal (CTO, Veracode) more in his recent podcast with O'Reilly Security Podcast where he explains why shifting security to the left (to developers at the start of the development life cycle) is key in an agile environment to keep up the pace and speed.

Security should be made easy for developers by using IDE plug-ins, scanners and educating them to have the basic security skills (hygiene). Organisations should not be solely relying on security experts or a centralised security team who validates all changes.

Our typical security modus operandi is broken (call in the expert!) and we need to integrate security into development teams to ensure quality is maintained whilst staying agile.

https://www.oreilly.com/ideas/chris-wysopal-on-a-shared-responsibility-model-for-developers-and-defenders

Govern AI-driven development before it ships

Measure AI-assisted risk, enforce secure coding policy at commit, and accelerate secure delivery across your SDLC.

Book a demo
Resource library

Explore more blogs

Access expert content on secure coding, AI governance, and software risk management.

browse all
Blog
Filter Label
This is some text inside of a div block.

If the model is the smallest security lever, what actually makes AI-generated code safer?

Earlier this year, we released the SCW AI Trust Index, and, in conjunction with RMIT University, assessed 16 leading AI models from OpenAI, Anthropic, Google, and others, generating 1760 codebases and finding 15 vulnerabilities on average in each one. This data, using our original methodology, allowed us to ultimately identify that security risk is predictable by model and framework. 

‍

Learn More
Blog
Filter Label
This is some text inside of a div block.

Run your secure coding program from your AI tool

Track training progress, draft Quests, and report on your SCW secure coding program from any MCP-compatible AI tool. Included with every SCW plan.

Learn More
Blog
Filter Label
This is some text inside of a div block.

Hell in a PHP2Shell: How AI has shrunk the patch window from days to hours

PHP2Shell: how AI shrank the patch window from days to hours, and what security teams should rethink about old bugs and technical debt.

Learn More

Secure AI-driven development before it ships

See developer risk, enforce policy, and prevent vulnerabilities across your software development lifecycle.

Book a demo
trust score
No items found.