Make your own mandate: How CISOs can implement GenAI governance
The real governance problem is not whether generative tools should be used, but who owns the risk once they are embedded in development. The source makes the stronger case that regulation will always trail adoption, so waiting for external rules leaves enterprises exposed to security, financial, and liability losses. For practitioners, the practical lesson is plain: governance has to be defined internally, with security leadership setting mandatory controls before productivity gains become an operational excuse for weak discipline.
The mechanism is the software development lifecycle itself, where unchecked tool use turns speed into amplified defect creation. The cited findings are not marginal: model-generated code is often incorrect or vulnerable, while productivity gains coincide with larger failures such as privilege escalation and architectural design flaws. That matters because the risk is not just bad syntax; it is the introduction of weaknesses that survive into production. The recommended platform approach emphasizes observability, policy enforcement, and risk metrics tied to commits and developer skill.
The chief limitation is that point fixes cannot keep pace with decentralized tool adoption, especially when employees use unapproved systems outside official review. Mandatory secure-code review, approved tool lists, and proficiency benchmarks are presented as controls, but they only work if leadership treats them as enforceable policy rather than training theater. The editorial significance is that governance is framed as an operating model, not a compliance afterthought: enterprises that fail to formalize it will absorb the speed benefits while inheriting the security debt.
The risks grow with AI-generated code
The reasons for AI’s rapid growth in software development are easy to see. In Darktrace’s 2025 State of AI Cybersecurity report, 88% of the 1,500 respondents said they are already seeing significant time savings from using AI. And 95% say they believe AI can improve the speed and efficiency of cyber defense. Not only do the vast majority of developers prefer using AI tools, but many CEOs are also beginning to mandate their use. As with any powerful new technology, however, the other shoe will drop and could have a significant impact on enterprise risk. The increased productivity of generative AI tools also brings forth an increase in familiar flaws, such as authentication errors and misconfigurations, as well as a new wave of AI-borne threats, such as prompt injection attacks. The potential for problems could get even worse. Recent research by Apiiro found that AI tools have increased development speeds by three to four times, but they also have increased risk tenfold. Although AI tools have cleaned up relatively minor mistakes, such as syntax errors (down by 76%) and logic bugs (down by 60%), they are introducing bigger problems. For example, privilege escalation, in which an attacker gains higher levels of access, increased by 322%, and architectural design problems jumped by 153% according to the report. CISOs are aware that risks are mounting, but not all of them are sure how to handle them. In Darktrace’s report, 78% of CISOs said they believe AI is affecting cybersecurity. Most said they’re better prepared than they were a year ago, but 45% admitted they are still not ready to address the problem. It’s time for CISOs to implement essential guardrails to mitigate the risks of AI use and establish governance policies that can endure, regardless of which regulatory requirements emerge from the legislative pipelines.Secure AI use starts with the SDLC
For all the benefits it provides in speed and functionality, AI-generated code is not deployment-ready. According to BaxBench, 62% of code created by large language models (LLMs) is either incorrect or contains a security vulnerability. Veracode researchers studying more than 100 large language models have found that 45% of functional code is insecure, while researchers at Cornell University determined that about 30% contains security vulnerabilities related to 38 different Common Weakness Enumeration categories. A lack of visibility into and governance over how AI tools are used creates serious risks for enterprises, leaving them open to attacks that result in data theft, financial loss and reputational damage, among other consequences. Since the weaknesses associated with AI development stem from the quality of the code it generates, enterprises need to incorporate governance into the software development lifecycle (SDLC). A platform (as opposed to point solutions) that focuses on the key issues facing AI software development can help organizations gain control over this ever-accelerating process. The features of such a platform should include: Observability: Enterprises should have clear visibility into AI-assisted development. They should know which developers are using LLM models and with which codebases they are working. Deep visibility can also help curb the use of shadow AI among employees using unapproved tools. Governance: Organizations need to have a clear idea of how AI is being used and who will use it, which requires clear governance policies. Once those policies are in place, a platform can automate policy enforcement to ensure that developers using AI meet secure coding standards before their work is accepted for production use.Organizations need to have a clear idea of how AI is being used and who will use it.
Enjoyed this article? Sign up for our newsletter to receive regular insights and stay connected.
