DOP 323: The Security Nightmare of Vibe Coding

Episode 323

Show Notes

#323: Vibe coding - the practice of giving AI a high-level description and letting it build applications unsupervised - has become increasingly popular among non-developers looking to quickly prototype ideas. While this approach excels at rapid prototyping and getting small, focused applications running, it creates significant security risks when deployed to production without proper oversight. The fundamental issue isn’t with AI capabilities, but with treating any tool - whether AI or human - as capable of understanding company context, security requirements, and production standards on day one.

The real value emerges when vibe coding serves as a bridge between business requirements and technical implementation. Rather than replacing traditional development workflows, it can accelerate the initial phases by providing working prototypes that stakeholders can interact with before formal development begins. However, moving from prototype to production requires the same rigorous processes that any new technology integration demands: security scanning, code review, compliance with company policies, and proper authentication handling.

In this episode, Darin and Viktor explore the security implications of unsupervised AI development, discussing when vibe coding makes sense, where it falls short, and how organizations might eventually integrate AI-assisted development into their existing workflows while maintaining security and operational standards.

Frequently Asked Questions

Where does vibe coding work and where does it break down?

Viktor Farcic draws the line on DevOps Paradox episode 323 at scope. Starting from scratch with a narrow goal works well: an HR tool for sorting candidates, or a site for a hobby. It breaks when a feature means writing a thousand lines that amount to a fraction of a percent of an existing codebase. He is describing unsupervised generation, which he distinguishes from the supervised back-and-forth most people now call vibe coding.

Can you let AI deploy to production unsupervised?

Viktor Farcic is unambiguous on DevOps Paradox episode 323: “You cannot let AI just deploy to production unsupervised Because it has no idea what to do.” His analogy is hiring the most brilliant graduate who ever lived and handing them production on day one. The problem is not capability. That person does not know whether you run on AWS or Azure, what your policies are, or where anything lives.

Is AI worse at security than a human developer?

Viktor Farcic pushes back on that framing on DevOps Paradox episode 323. If the agent operates under the same permissions as a person and receives the same company-specific knowledge a new hire gets over a year, he asks why the outcome would differ. His point is that the failure being described is inexperience rather than artificial intelligence, and it applies equally to a person on their first day.

Would a non-developer build something safer without AI?

Viktor Farcic argues on DevOps Paradox episode 323 that the same person with no-code tools, or with just enough self-taught JavaScript, reaches an equally bad outcome more slowly. The exposed credentials and the locally stored card numbers were possible before. He allows one difference in AI’s favour: a model might warn the person that they are exposing a password, which no previous route would have done.

What should a company do with a vibe-coded app from a non-developer?

Viktor Farcic suggests on DevOps Paradox episode 323 that companies pass it through the controls they already run: security scanning, checks for exposed credentials, coding standards, code review. It will surface more issues than usual, which is still less work than starting from nothing. His question to the engineer is which they prefer, a working solution carrying extra security problems or a ticket describing something nobody can articulate.

What is missing before AI coding tools are safe at work?

Viktor Farcic says on DevOps Paradox episode 323 that the tools are disconnected from everything else, closer to a hobby than part of the system. His comparison is Kubernetes: a company eventually stops letting everyone install their own and standardises on a platform with rules attached. Companies are currently assuming their existing policies do not apply to AI, and he cannot see why they would make that assumption.

What is the DevOps Paradox podcast?

DevOps Paradox is a weekly podcast co-hosted by Darin Pope and Viktor Farcic, covering DevOps, platform engineering, and modern software delivery. Episode 323 is a conversation between the two hosts about the security consequences of shipping vibe-coded applications, why the real gap is company knowledge rather than model capability, and how existing controls should apply. Every episode page carries the audio, the video, and a full transcript.

Topics

Share and Download

Hosts

Viktor Farcic

Viktor Farcic

Viktor Farcic is a member of the Google Developer Experts and Docker Captains groups, and published author.

His big passions are DevOps, Containers, Kubernetes, Microservices, Continuous Integration, Delivery and Deployment (CI/CD) and Test-Driven Development (TDD).

He often speaks at community gatherings and conferences.

He has published DevOps Paradox and Test-Driven Java Development.

His random thoughts and tutorials can be found in his blog The DevOps Toolkit.