From Telemetry to Action: What Real Enterprise AI Usage Data Reveals About Risk

AI Risk

min read

From Telemetry to Action: What Real Enterprise AI Usage Data Reveals About Risk

March 16, 2026

AI adoption inside the enterprise is accelerating at a pace few security teams expected.

In the past year alone, organizations have introduced AI tools across nearly every function: software development, marketing, customer support, finance, and operations. From large language model APIs to AI-powered copilots and autonomous agents, the enterprise technology stack is quickly becoming an AI ecosystem.

But for security leaders, one question remains difficult to answer: How is AI actually being used inside our organization?

AI Adoption Is Happening Faster Than Governance

Most organizations did not plan for the speed of AI adoption. Unlike traditional enterprise software, AI tools are often introduced bottom-up.

Developers experiment with new model APIs. Teams install AI browser extensions. Business units adopt AI copilots for productivity. Many of these tools can be deployed in minutes. Security reviews, governance policies, and architecture reviews rarely move that fast.

The result is an environment where AI adoption spreads organically across the organization, often without centralized oversight.

What Enterprise AI Telemetry Shows

When organizations begin mapping their AI usage, several patterns quickly emerge.

1. The Number of AI Tools Is Much Higher Than Expected

Most security teams initially assume their organization uses a small number of AI platforms. In reality, once discovery begins, organizations commonly uncover dozens of AI browser extensions, multiple LLM APIs used by developers, internal AI models running in experimentation environments, and AI-powered SaaS tools embedded in existing platforms.

In some enterprises, security teams discover hundreds of AI-enabled services interacting with enterprise systems.

2. AI Usage Is Distributed Across the Entire Organization

AI is not confined to engineering teams. Marketing teams use AI to generate campaigns. Customer support teams deploy AI assistants. Sales teams use AI tools to research accounts. Operations teams use AI to automate workflows.

Each use case introduces new AI systems interacting with enterprise data. From a security perspective, this creates a challenge: AI adoption is decentralized.

3. AI Identities Are Growing Rapidly

One of the most overlooked aspects of enterprise AI adoption is the rise of non-human identities. AI agents accessing internal APIs, models querying enterprise databases, and automation systems triggering workflows — each represents a digital identity operating inside the organization.

In many environments, these AI identities accumulate permissions over time, often without the same governance applied to human accounts.

4. Sensitive Data Is Frequently Involved

Another common discovery is the frequency with which AI tools interact with sensitive enterprise data — internal documents, customer records, financial data, intellectual property, and product roadmaps.

Many employees use AI tools to summarize documents, generate reports, or analyze datasets. In some cases, this data is transmitted to external AI services without clear visibility.

The Gap Between Visibility and Action

Discovering AI usage is only the first step. The real challenge is: which of these risks actually matter?

Large enterprises may identify thousands of AI-related findings — exposed model endpoints, unapproved AI tools, vulnerable dependencies, data access risks, identity misconfigurations. If every issue receives equal priority, security teams quickly become overwhelmed.

This is the same problem organizations faced during the early days of cloud security. Thousands of alerts were generated — but few were tied to real business impact.

Why AI Security Requires Context

Not every AI system represents the same level of risk. A chatbot analyzing public marketing data presents a very different risk profile than an AI system connected to production customer records.

Understanding AI risk requires evaluating what data the system can access, what permissions it has, where it runs, whether it is exposed externally, and how it connects to other systems. The most dangerous scenarios involve combinations of conditions — what security teams call toxic combinations.

Turning AI Telemetry Into Risk Intelligence

Organizations need to discover AI assets — models, agents, and AI-enabled tools across code repositories, developer environments, cloud infrastructure, SaaS applications, and employee endpoints.

They must map relationships between models, data sources, APIs, identities, and infrastructure. A model connected to sensitive data may be safe if it operates within a secure environment. But if that same model also has internet exposure, weak authentication, and privileged access, the risk profile changes dramatically.

And they must score risk in business context — evaluating data sensitivity, identity permissions, exposure level, regulatory implications, and operational dependencies.

Moving From Awareness to Control

AI will continue transforming how organizations operate. Security teams cannot — and should not — attempt to stop this innovation.

But they must ensure that AI adoption occurs with visibility, governance, and control. The organizations that succeed will be those that move beyond basic discovery and develop the ability to understand how AI systems interact with enterprise data, prioritize risks based on real business context, and enable AI innovation while maintaining security discipline.

In other words, they will move from telemetry to action.

‍

See Your AI Attack Surface

Discover every AI tool, agent, and model running in your enterprise — before attackers do.

Request a Demo

AI Risk

min read

Why AI Risk Requires Classification and Scoring — Not Just Alerts

Without a structured way to classify and score AI risk, security teams risk repeating the mistakes of the early cloud era: overwhelming noise with very little actionable insight.

March 18, 2026

Security teams are used to alerts. Over the past decade, organizations have deployed dozens of security tools designed to detect threats, vulnerabilities, and misconfigurations. These tools generate thousands — or sometimes millions — of signals every day.

The problem has never been a lack of alerts. The problem has always been understanding which ones actually matter.

Now, as artificial intelligence spreads across enterprise environments, the same challenge is emerging again — only this time, the stakes are even higher.

The AI Risk Visibility Problem

As organizations begin discovering AI usage, they encounter an unexpected reality. AI adoption is rarely limited to a handful of projects.

Enterprises typically uncover a rapidly expanding ecosystem: internal machine learning models, external AI APIs, AI agents and automation tools, browser extensions and AI copilots, developer tools integrated with large language models, and data pipelines connected to AI systems.

But not every AI system represents the same level of risk. A chatbot analyzing public marketing content does not present the same exposure as an AI model connected to customer financial data.

Why AI Risk Is Different

AI risk is not simply another category of application security.

AI systems interact with data dynamically — through prompts, retrieval systems, and automated actions. This makes it harder to anticipate how data may be accessed or used.

AI systems accumulate permissions over time. AI agents, models, and automation systems often operate through service accounts, tokens, or API credentials that may end up with privileged access to sensitive resources.

AI systems depend on complex supply chains — open-source model packages, third-party APIs, external model providers, container images, and automation frameworks. A vulnerability in one component may impact multiple systems.

The Problem With 'Flat' Security Alerts

When security tools generate alerts without context, they treat each issue independently.

A model endpoint exposed to the internet triggers an alert. A dataset containing sensitive information triggers another. An AI service running with elevated permissions triggers a third.

Viewed individually, each finding may appear manageable. But the true risk may lie in the combination: an exposed model endpoint connected to a sensitive dataset and operating with privileged access represents a very different level of risk.

Introducing AI Risk Classification

To manage AI risk effectively, organizations must begin by classifying AI assets across several dimensions.

AI Asset Type: models, agents, APIs, AI-powered SaaS tools, developer frameworks, and automation services. Each introduces different risk considerations.

Data Sensitivity: from public data to internal operational data, confidential business information, and regulated or personal data. AI systems interacting with sensitive datasets require stronger controls.

Access and Identity Permissions: Does the AI system use a service account? What APIs can it access? Does it interact with production systems?

Exposure Level: Some AI systems operate entirely within internal environments. Others expose APIs to external users or interact with third-party platforms.

From Classification to Risk Scoring

Classification provides the foundation. But to prioritize effectively, organizations need a risk scoring model that evaluates the combination of factors for each AI asset.

An effective AI risk score considers data sensitivity, identity and access permissions, exposure level, supply chain dependencies, and regulatory implications.

The most dangerous scenarios — toxic combinations — emerge when multiple high-risk factors converge: a model with privileged access to sensitive data, exposed externally, with vulnerable dependencies.

By scoring these combinations, security teams can focus on the risks most likely to result in real business impact rather than chasing thousands of low-priority alerts.

Building an Operational AI Risk Program

The shift from flat alerts to classification and scoring represents a fundamental evolution in how organizations approach AI security.

Security teams must discover all AI assets across the enterprise, classify them by type, data sensitivity, access level, and exposure, score risk based on the combination of these factors, and continuously monitor as the AI ecosystem evolves.

This approach mirrors the maturity curve organizations followed in cloud security — moving from basic visibility to contextual risk prioritization.

The organizations that adopt this model early will be best positioned to manage AI risk at scale, enabling innovation while maintaining the security discipline that enterprise environments demand.

Get My AI Inventory