Independent & educational platform Not a government body. No link or affiliation with any government organisation. Made for learning only. Test only systems you own or are authorised to test. Become a Partner or Sponsor → Full disclaimer
vulnerability Imported story

How organizations can secure their AI-generated code

Source: CSO Online · Published · Last checked 33 minutes ago · 3 min read
How organizations can secure their AI-generated code
Image: CSO Online
Read original source ↗ (www.csoonline.com)

Publisher excerpt From CSO Online

The IT manager didn’t know the company hired a “vibe coder” straight out of school. By the time they met a few months later, the new hire had already built a web application that operated with customer data and private contracts. The app ran under a domain the new hire controlled, stored data on Supabase’s free plan, and deployed directly from his GitHub repository to Cloudflare’s serverless infrastructure. “He vibe-codes everything straight into production, on servers all over the world,” the IT manager wrote on Reddit. “We’re EU based.” When asked whether he had read the AI-generated code or taken any security precautions, the new hire said, “My GitHub repo is private.” The IT manager took the concern to the CEO, who brushed it aside: “Let it go.” In many organizations, vibe coders build software without thinking much about security. Their apps may get the job done, but they are ticking bombs. In SusVibes, a benchmark of 186 real-world feature requests from open-source projects, agents given feature descriptions without security guidance produced working code up to 57% of the time. But only 11.8% of their solutions were secure. “The failures we saw were not careless errors,” says Danqing Wang of Carnegie Mellon University’s Language Technologies Institute, author of the paper describing SusVibes. “Spotting those requires reasoning about what an attacker can do, not just what the feature should do.” What has changed, especially this year, is that AI code-generating tools have gotten so good at producing working code that people are just trusting them, says Dr. Katie Paxton-Fear, staff security advocate at Semgrep. “Developers simply aren’t being as critical now as they were when AI was worse at writing code.” Whether it’s the vibe-coder in marketing or the seasoned engineering team boosting its productivity, AI-generated code is an increasing security concern for CISOs. Much of that is a function of volume, but even as AI has proved highly capable of finding flaws in code bases, it is not yet adept at contributing code without introducing its own. Treating AI-generated code as ‘untrusted input’ Leading AI coding agents such as Claude Code, Cursor, GitHub Copilot, and Amazon Q Developer have become developer go-to tools, and CIOs are increasingly enlisting business users to vibe code their own apps. But as AI-generated code surfaces everywhere, CISOs have only one option: to treat it “as untrusted input that has to earn its way into the codebase,” says Bianca Lankford, VP of engineering at Datadog. To do so, security leaders are moving security checks closer to where code is written: static analysis, secrets scanning, and dependency checks run on every pull request and, increasingly, in the developer’s editor. “Companies are also approving specific AI tools, limiting what assistants can access, and training reviewers to spot common AI mistakes like outdated libraries, weak input validation, and overly permissive defaults,” Lankford…

Excerpt only, shown with attribution. This content belongs to the original publisher and has not been independently verified by CyberSecurity.pk.

Reference: CSO Online — www.csoonline.com ↗

Related news