of organizations that reported an AI-related breach lacked proper AI access controls.
IBM Cost of a Data Breach 2025

Where AI enters your business
Sensitive data and risky code reach AI through more than a typed question. Select an entry point to see how PexLens covers it.
Control what employees can share with AI, with which AI tools, and under what policy, across prompts, files, uploads and AI-connected workflows.
Employees do not only send text prompts. They paste confidential documents, upload spreadsheets, share source code, submit customer records, attach internal policies and ask AI to analyze sensitive business data.
The risk is not limited to one AI platform. It applies to public AI chat interfaces, enterprise AI assistants, AI features embedded in SaaS applications, browser-based AI tools and locally installed AI applications.
PexLens helps organizations apply consistent controls across these interactions:
Sensitive information can leave the organization through prompts, uploads, copied text and AI-connected workflows, not only through a typed question.
PexLens helps organizations use AI confidently by controlling what employees can share, with which AI tools, and under what policy.
The enterprise AI browser with security built in. It turns the browser from an unmanaged AI risk surface into a controlled, observable workspace.
The enterprise AI browser with security built in. Much of modern AI usage happens in the browser: AI chat tools, AI-enhanced SaaS applications, browser extensions, web-based agents and AI features built into business applications.
The browser is also where traditional security controls often lose visibility. Employees may paste sensitive information into an AI interface, upload files, use personal AI accounts, install unapproved extensions or connect AI agents to business systems.
PexLens Enterprise AI Browser helps secure this layer with:
Browser extensions can request broad access to page content, form data, cookies, session tokens and enterprise applications. A compromised extension can become a silent channel for data theft or account takeover.
PexLens turns the browser from an unmanaged AI risk surface into a controlled, observable workspace.
Verify packages, AI models, extensions, plugins, MCP servers and AI tooling before they enter your environment, whether a developer, an AI agent or a non-technical employee installs them.
The third entry point is the software supply chain. Developers have always installed packages, libraries, IDE extensions and build tools. AI changes the scale and speed of that risk: developers may accept an agent’s suggested dependency, and non-technical employees may use AI agents to build internal tools, automate workflows or install packages without understanding the security implications.
AI agents can also download and install dependencies automatically. In some cases the human checkpoint disappears entirely: an agent selects a package, runs an installation command and executes install scripts before anyone reviews the change.
PexLens Supplytrust helps protect this surface by:
Hugging Face and model hubs
A model file can run code the moment it loads. Supplytrust scans models before they reach notebooks, pipelines or production.
Formulae, casks and taps
Allow only approved taps and casks per team, and stop unvetted tools landing on developer laptops.
Employees outside engineering are now building tools with AI. Research on AI-agent usage found non-engineering users running code, builds, package installs and cloud or cluster commands; in one organization, 12% of non-engineering users installed packages through agents.
Source: Sysdig AI usage researchPexLens protects the components that enter your environment, whether installed by a developer, an AI agent or a non-technical employee building an internal tool.
Why AI security, why now
Employees paste data into AI tools, developers let AI pick dependencies, and attackers target both. Most organizations still have no control point in between.
of organizations that reported an AI-related breach lacked proper AI access controls.
IBM Cost of a Data Breach 2025
added to average breach costs for organizations with high levels of shadow AI. One in five reported a shadow AI breach.
IBM Cost of a Data Breach 2025
of enterprise employees using generative AI admit entering confidential information into public AI tools.
TELUS Digital survey, 2025
new open source malware packages found in one quarter across npm, PyPI and Hugging Face, up 140%.
Sonatype Open Source Malware Index, Q3 2025
The PexLens platform
PexLens TrustGate, PexLens Enterprise AI Browser and PexLens Supplytrust share one policy engine and one view of risk, so a rule you write once applies to the prompt an employee types, the browser they work in and the package a developer installs.
AI DLP · AI data loss prevention for prompts and responses
Inspects prompts and responses on the device across ChatGPT, Claude, Gemini, AI search and local developer tools.
SEB · Secure enterprise browser for AI
The enterprise AI browser with security built in. Chromium-based, with control over AI-assisted work, sessions and sensitive data.
SSCS · Software supply chain security with SCA and malware blocking
Real-time protection for npm, PyPI, Maven, RubyGems and Homebrew, AI models from Hugging Face, browser and IDE extensions, AI coding assistants and agent components.
Where AI risk enters
Code, credentials and customer data leave through prompts and uploads, often from personal accounts.
TrustGate · PexLens Browser 02 · PROMPT INJECTIONWeb pages, files and tool responses can steer assistants into leaking data or taking unintended actions.
TrustGate · Supplytrust 03 · UNAPPROVED MODELSTeams adopt new chatbots, copilots and AI search tools faster than policy can keep up.
PexLens Browser · TrustGate 04 · MALICIOUS PACKAGES AND MODELSAssistants recommend packages that are malicious, typosquatted or do not exist yet, and models downloaded from public hubs can run hidden code when loaded.
Supplytrust 05 · RISKY AI EXTENSIONSBrowser and IDE extensions read pages, code and credentials, and can turn hostile through a single update.
Supplytrust · PexLens Browser 06 · AGENTIC AI AND MCPCoding agents and MCP servers extend what AI can reach and do, with your credentials.
Supplytrust · TrustGateHow PexLens works
AI tools, models, extensions, packages and agent components across devices, browsers and CI.
Sensitive data in prompts, risky AI components and malicious packages, before they reach production.
Signals meet dependency, identity and policy context, and return allow, redact, alert or block.
A complete record of AI use and enforcement for security reviews, auditors and incident response.
Built for the teams that own AI risk
Approve AI with confidence: one view of AI risk and one policy across prompts, browsers and code.
Stop malicious packages and risky AI tools in IDEs, CI and agents without slowing developers.
Roll out the PexLens Browser and TrustGate with zero-touch deployment and central browser policies.
Turn your AI policy into enforced controls, with audit trails for every AI decision.
Simple, predictable pricing
Works with any plan, or on its own.
Core, Govern and Command plans. Minimum 50 seats, save 20% on annual contracts.
Free for npm and PyPI. Priced by unique package versions, never per developer.
AI security protects how an organization builds and uses AI: the data employees share with AI tools, the AI-related components and extensions developers install, and the agents that act on their behalf.
PexLens Enterprise AI Browser is the enterprise AI browser with security built in, for secure, managed AI-powered browsing. The PexLens Browser is Chromium-based and uses the same policy engine as PexLens TrustGate. Plans start at $12 per seat per month (Core), with Govern at $15 and Command at $21.
PexLens TrustGate inspects prompts on the employee device and detects source code, secrets, API keys and personal information before they reach an AI service. Depending on your policy it allows, redacts or blocks the content and logs the decision.
They work together. The PexLens Browser controls AI sessions, models, clipboard and browser policy, and TrustGate inspects prompts and responses on the device, including in browsers and local tools you already use.
AI assistants and agents install packages, extensions and tools on your behalf. PexLens Supplytrust, our software supply chain security (SSCS) product, checks each one at install time, so AI-driven development cannot bring malicious code into your environment.
Yes. PexLens Supplytrust scans AI models from Hugging Face and other model hubs for unsafe serialization, embedded code and tampering before they are loaded, and covers Homebrew formulae and casks alongside npm, PyPI, Maven and RubyGems. Organization-based policies let you approve sources, model hubs and taps per team, device group or project.
Yes. AI guardrails are designed around organization-defined rules, so your team decides which AI-related signals are approved, need review or should be blocked.
Yes. The same policy engine can allow, warn on or block AI tools and AI-related components, and PexLens TrustGate applies policy to prompts and responses.
In three places: the prompts, files and conversations people share with AI tools, the browser where AI work happens, and the packages, extensions, models and AI tools teams install. PexLens TrustGate, the PexLens Enterprise AI Browser and PexLens Supplytrust secure each one under one policy.
PexLens is for security leaders, engineering organisations, IT teams and compliance and privacy teams in organisations that want to adopt AI safely and protect the software they build and use.
Request a demo. The PexLens team will review the AI tools, browsers and package ecosystems you use and plan a pilot with your security and engineering teams.