55% of CISOs and CTOs Demand Centralized Controls for AI-Generated Software, Survey Finds
What happened
Retool published its State of AI Governance in 2026 report on June 28, 2026, drawing on survey responses from 307 senior technology executives including CTOs, CIOs, and CISOs based in the United States. The report's headline finding is that 55% of respondents believe security and access controls for AI-generated internal software should be managed through a centralized platform rather than distributed across individual teams or tools. A central focus of the report is the governance challenge posed by vibe coding tools, which allow employees to generate functional internal applications using AI with minimal engineering oversight, and by shadow AI adoption more broadly. The report positions these trends as creating blind spots in enterprise control environments where internally deployed AI-generated software bypasses standard intake, approval, and access management workflows. The findings underscore a growing mismatch between the pace of AI-assisted development and the maturity of governance infrastructure designed to oversee it.
Why it matters
- ·Shadow AI and vibe coding tools create ungoverned deployment pathways for AI-generated internal software, meaning access controls, data handling standards, and approval workflows may never be applied to applications that nonetheless process sensitive business data.
- ·The 55% consensus figure reveals that a majority of senior technology leaders have already identified centralized control as the solution, but the gap between that recognition and implemented controls creates near-term regulatory exposure as AI-specific obligations under frameworks like the EU AI Act and emerging US state laws begin to require documented governance over all AI system deployments.
- ·For compliance functions, AI-generated internal applications present an inventory problem first: systems that are never logged in a model registry or AI system inventory cannot be risk-classified, monitored for drift, or included in audit trails, leaving compliance teams unable to demonstrate the coverage their programs claim.
Governance controls affected
What to do now
- ☐Audit your current AI system intake and approval workflow to determine whether AI-generated internal applications built with vibe coding tools are subject to any formal review gate before deployment.
- ☐Extend your shadow AI inventory process to explicitly cover internally developed AI-generated applications, not only externally procured AI tools and SaaS products.
- ☐Assess whether least-privilege access controls are applied to AI-generated internal software, including who can deploy, modify, and access data processed by these applications.
- ☐Brief your AI governance committee or equivalent body on the vibe coding risk category and establish a policy position on whether such tools require pre-approval, post-deployment review, or are prohibited in regulated data environments.
- ☐Review your AI system registry to confirm it captures AI-assisted development outputs as a distinct asset class and assign ownership for ongoing classification and monitoring of that category.
What to watch next
Compliance teams should monitor whether US state AI laws currently moving through legislatures, including those modeled on Colorado SB205 and Texas HB149, extend documentation and risk classification requirements to internally developed AI-generated software as a covered AI system category. The EU AI Act's conformity assessment obligations, which continue to phase in through 2026 and 2027, may also reach AI-generated internal tooling depending on how national competent authorities interpret the definition of deployer obligations. Enforcement patterns from the FTC and sector regulators on AI access control failures will be an early indicator of how seriously shadow AI gaps are treated in practice.
Stay ahead of stories like this
Get every US AI governance development like this one, plus the rest of the week's developments. Every Thursday.