AI governance is a key enterprise concern. Organizations are assembling councils, publishing principles, rolling out “approved AI tools” lists, and asking employees to opt in to acceptable use policies. In most enterprises, however, the reality is that AI is already widely embedded in employees' daily work, often outside sanctioned channels and oversight. The visibility and control mechanisms needed to govern AI use are immature or nonexistent.

The result is a widening gap between what leadership desires for AI governance and what’s happening inside their organizations. CIOs must turn to technology guardrails capable of transporting AI governance intent from the realm of policy principles to the world of production environments, with scalable visibility and enforcement.  

Shadow AI Is the Default

Visibility is among the biggest challenges in AI governance: A recent survey found 45% of employees have used AI tools for work without informing their manager.¹ Shadow AI can take many forms, including AI-enabled web apps, browser extensions, desktop apps, and SaaS platforms. 

Shadow AI isn’t just a compliance problem — it’s a serious security and data exposure problem. Employees may paste sensitive data into chatbots, connect critical business accounts to AI-enabled workflows, grant AI applications excessive permissions, or expose proprietary corporate files to AI agents. Every AI connection creates a new identity relationship that organizations must understand and govern. A study published earlier this year found more than half of employees admit to connecting third-party AI tools with other work systems without IT department approval or oversight.²

Traditional governance and security controls weren’t built to observe and interrogate the new AI prompt and agentic interaction layer, nor were they designed to continuously evaluate the identities and permissions behind those interactions.

AI Policy Demands a Collaborative Approach

Legal and privacy teams are essential to the development of AI policy, but they can’t be the only authors. AI governance isn’t only about what’s allowed. It’s about what’s possible in the architecture, what’s safe in the threat model, and what’s useful to the business. Effective AI governance requires these stakeholders at the table:

• Business and product owners to align governance to outcomes, so controls don’t simply block innovation but shape it toward trusted, compliant, high-value use cases
• IT and security leaders to define threat scenarios (e.g., prompt injection, model supply chain risk, agent autonomy), establish controls, and ensure detection and response can extend to AI workflows
• Engineering leaders to weigh in on architectural possibilities and limitations and commit to implementing guardrails where they matter: strong identity controls, continuous authorization, logging, segmentation, safe tool use, and secure-by-default patterns in apps that call models

Determining AI governance policy is still a work in progress for many organizations. With multiple stakeholders and rapidly changing technology, it can be tricky to achieve alignment. An IBM study conducted last year found nearly two-thirds (63%) of organizations lacked AI governance policies.³ Even among organizations that reported having AI governance policies, more than half reported they lacked both approval processes for AI deployments and the technologies needed to enforce governance policy. 

The success of AI governance depends on operationalization. Few organizations today have the means to assess adherence at scale, detect violations, and continuously prove their guardrails are working. A policy that can’t be enforced becomes an artifact — useful for signaling intent but unreliable as a risk management mechanism. AI governance must become measurable: What AI tools are being used? Where is data going? Which models are connected to which business processes? Which human and non-human identities can invoke those models, access sensitive data, or delegate actions to downstream systems? What’s the rate of policy exceptions, and are those exceptions becoming the norm?

AI Agents Raise the Governance Stakes 

As AI technology rapidly changes, AI governance becomes harder. We’re moving from users asking questions of chatbots to the deployment of full-fledged AI agents that can plan, take actions, call tools, and chain tasks together.  

These agents multiply both impact and risk. They can touch more systems, execute more steps, and make more decisions faster than traditional oversight loops. Risks can go beyond bad answers to unintended actions: sending data externally, changing records, triggering financial transactions, or interacting with third parties in ways no one anticipated.

Each AI agent operates as an identity, and they rarely operate alone. They increasingly function as part of an identity chain — a sequence of humans, agents, applications, APIs, and data stores connected through delegated trust. This creates implications for identity governance. Identity can no longer be treated as a point-in-time decision. As AI agents operate continuously, inherit permissions, invoke APIs, and interact with multiple systems, identity must become a continuously evaluated security signal based on real-time context.  

The AI agent ecosystem evolves on a nearly daily basis. In the latest wave of open-source momentum, projects like OpenClaw have gained attention as developers experiment with increasingly capable agentic frameworks. Whether a given framework becomes businesses’ standard or not, the broader trend is clear: Capabilities are diffusing rapidly, and governance must account for AI tools that employees can adopt in an afternoon.

A Strategic Opening for CIOs and CISOs

Organizations that govern AI with discipline can scale it with confidence and move faster with fewer do-overs, fewer operational and security incidents, and greater credibility with customers, auditors, and regulators. CIOs, in close partnership with CISOs, are uniquely positioned to lead. Governance without security is hollow, and security without business and operational alignment fails to deliver durable outcomes.

Leaders can focus on three practical moves:

1. Enforce technical guardrails. Define what must be technically enforced (data classification rules, approved model endpoints, least-privilege access, authentication, logging, token controls, prompt and output handling) and what can be guidance. Then invest in the controls that make enforcement real.
   

2. Treat AI governance like an operational program. If AI governance is reviewed annually, or even quarterly, it’s already stale. Set and lead a weekly or monthly cadence with security, engineering, and business stakeholders to review adoption, incidents, exceptions, and new capabilities.
   

3. Define metrics and automate measurement. Governance should be provable. Track the number of AI tools in use, sanctioned vs. unsanctioned usage, sensitive data interaction rates, policy exception volume, agent deployments, and mean time to detect/respond to AI-related events. Automate collection wherever possible.

AI is moving too fast for more static, document-driven governance approaches of the past. Organizations that treat AI governance as theater will be surprised by shadow AI, agent sprawl, and incidents that were preventable. The enterprises that build guardrails grounded in visibility, identity, and continuous enforcement will earn something far more valuable than compliance: the ability to scale AI with confidence.

Additional Resources

• Learn how CrowdStrike Falcon® AI Detection and Response secures AI. 
• CrowdStrike Services can help you assess your organization’s AI readiness — visit our Frontier AI Service Solutions page.
• Download our guide to explore the five steps for AI security readiness.
• Join us at Fal.Con 2026 as we bring together cyber leaders from across the industry to help secure the AI revolution.

1. Gusto, Is AI Coming for My Job? A Look Inside America’s Workplace Anxiety and What Employers Need to Know, July 14, 2025

2. BlackFog, BlackFog Research Reveals Rising Shadow AI Risks, Jan. 27, 2026

3. IBM Cost of a Data Breach Report 2025: The AI Oversight Gap