Habr•September 22, 2026•🇷🇺Translated from Russian

AI Gateway Emerges as Unified Control Layer for Enterprise LLM Access and Data Protection

As LLM adoption in companies grows from a few enthusiasts using personal keys to dozens of teams, IDEs, internal agents, and automated systems, the experiment turns into production infrastructure with strict demands for security, cost control, and resilience.

AI Gateway serves as the essential layer between employees, agents, corporate systems, and LLM providers. It does not improve model intelligence but makes usage observable, manageable, and safer for the organization.

In its basic form, an AI Gateway functions as a proxy that forwards requests to the appropriate model. However, enterprise-grade gateways must make multiple decisions before each request: identify the user and originating tool, verify access rights to specific models and functions, scan for personal data, tokens, secrets, or client information, mask sensitive content when needed, select the optimal model based on quality, cost, latency, and policy, switch providers during outages, and record detailed audit and billing data.

Leading solutions already reflect this approach. Cloudflare AI Gateway offers analytics, logging, caching, rate limiting, and fallback capabilities. Kong emphasizes routing and governance for AI traffic. Microsoft demonstrates GenAI gateway patterns in Azure API Management, including token limits, quotas, load balancing, and consumption management.

Simply granting everyone access to ChatGPT creates serious risks for enterprises. Employees already connect AI features through IDEs, browser chats, CLI tools, internal agents, and external services, often using unapproved workarounds because official ChatGPT access is unavailable in Russia. This exposes organizations to data leaks, NDA violations, and potential fines of up to 20 million rubles for repeated personal data breaches under Russian regulations.

A complete ban fails because employees discover bypasses, while unrestricted access removes all control over data, budgets, and legal exposure. The practical solution is managed corporate access through a single controlled layer that preserves familiar workflows while enforcing access policies, DLP, auditing, limits, and intelligent routing.

The request pipeline includes authentication, policy enforcement, DLP scanning, depersonalization of sensitive entities, model and provider selection, response restoration when appropriate, and final audit and billing steps. Checks must occur before any data leaves the corporate perimeter.

Compatibility with the OpenAI API format minimizes adoption friction. Users change only the base URL and token, allowing existing IDEs, CLIs, OpenWebUI, and agents to continue working unchanged. This compatibility also simplifies migrations between providers, including transitions to Chinese models that may lack certain features such as web search or image generation.

Depersonalization requires more than simple string replacement. Real corporate scenarios demand entity resolution to handle name variations, grammatical cases, mixed languages, and tool calls so that restored entities remain accurate and automation does not break.

Effective policies cover names, phone numbers, emails, passport data, SNILS, INN, API tokens, passwords, code secrets, client NDA information, and internal project documents. Initial deployment should begin in shadow mode to tune rules before enforcement.

When all traffic passes through the gateway, organizations gain precise visibility into AI economics, including token consumption per employee, project, and cost center. This data supports budgeting, model selection, and chargeback processes.

The gateway also centralizes fallback handling during provider outages, using circuit breakers and defined degradation rules so that critical workflows either switch models or receive clear notifications instead of failing silently.

Clear boundaries must separate AI Gateway functions (routing, keys, limits, auditing, API compatibility) from DLP, depersonalization, MCP Gateway access to internal systems, and guardrails for agent behavior. Combining everything into one component creates an unmaintainable black box.

From day one, organizations should assign clear ownership with monitoring and runbooks, implement auditing immediately, validate real client compatibility including streaming and tool calls, run DLP in shadow mode first, and maintain transparent documentation of production architecture.

Related articles

Habr•AI Security

Docker Rebrands Around AI Agents with 'Run on Trust' and New Sandbox Tools

Docker has updated its branding to emphasize security for AI agents, introducing the slogan 'Trust Docker for the agents you don’t' and the tagline 'build, ship, and run on trust'. The company highlighted products such as Sandboxes, AI Governance, MCP Enterprise Gateway, and Hardened Images, although most of these features were released or discussed earlier in 2025. Sandboxes run agents inside microVMs with separate kernels using KVM or Windows Hypervisor Platform, allowing isolated execution of tools like Claude Code. AI Governance provides centralized policy management and audit logging for enterprise teams, while MCP Enterprise Gateway handles SSO and credential injection for MCP servers. Hardened Images remain available under Apache 2.0 with optional paid FIPS and support tiers. The shift follows the appointment of Don Johnson, formerly of Oracle, as CEO and reflects Docker’s attempt to address new security concerns around autonomous AI agents rather than traditional container workloads.

Habr•AI Security

AI Agents Exploit PaperCut Flaw, Compromising 395 Organizations Across 48 Countries

PaperCut released a security bulletin on 27 August 2026. GreyNoise observed the first real-world code execution just four days later, with the operator moving from initial access to execution in under four hours. After the mass campaign launched, 11 organizations were compromised in only 26 seconds. In total, at least 440 PaperCut NG/MF instances belonging to 395 organizations were breached. The incident is detailed in the November report by Google Threat Intelligence Group and Mandiant, which examines the role of AI agents in the attacks. GTIG also discovered an automated exploit_agent system capable of handling exploitation without constant human input. Additional cases involved LLMjacking and unauthorized configuration changes in Claude Code repositories at cryptocurrency firms.

安全客•AI Security

Google Threat Intelligence Group Warns of Fully Autonomous AI Cyberattacks Within Six Months

Google's Threat Intelligence Group (GTIG) has observed the first real-world instances of attackers using multi-agent AI frameworks to autonomously discover vulnerabilities, generate exploits, and compromise targets without human intervention. The discovery came from an exposed server running a framework called exploit_agent that analyzed software update logs from popular web applications to identify and exploit weaknesses. Four previously defensive tools—ARTEX, CAIRN, CyberStrikeAI, and HexStrike AI—have been repurposed for offensive operations, with documented cases targeting French media, U.S. aerospace, and cryptocurrency firms. GTIG projects that low-complexity automated attacks will become common within three months, while sophisticated fully autonomous operations are expected within six months. The report highlights how these systems compress patch windows, overwhelm security teams with AI-generated proof-of-concepts, and turn detailed vendor advisories into attack playbooks. Defenders are urged to minimize public exposure, accelerate patching cycles to weekly, and tightly control API keys to prevent LLMjacking.

Habr•AI Security

OpenAI Rolls Out KYC, Hardware Keys and Tiered Access for Cybersecurity Tasks in GPT-6.2

OpenAI has introduced stricter access controls for GPT-6.2 Astra and Sol models when users attempt cybersecurity-related tasks. Certain legitimate security research and testing activities now trigger automatic blocks unless the user obtains Daybreak trusted access. The program requires paid subscriptions, FIDO2 hardware keys, Advanced Account Security, and identity verification through Persona. Developers report that even after meeting preliminary requirements, access to reduced refusal rates is not guaranteed and may require separate organizational approval. The changes stem from the models reaching Critical capability levels under OpenAI’s Preparedness Framework for dual-use cybersecurity skills. Similar verification processes previously led to account blocks for users of competing services such as Anthropic’s Claude.