Nearly 70% of Companies Lack Control Over AI Agent Privileges, PAM Survey Finds
A new survey highlights a critical gap in Privileged Access Management (PAM) practices: organizations are struggling to secure the growing number of machine identities created by AI agents, automated services, and cloud infrastructure.
Just a few years ago, privileged access primarily referred to human system administrators receiving root or Administrator rights. Today, however, non-human entities such as programs, services, and AI agents routinely hold equivalent or greater privileges. These machine identities can deploy applications to production, access databases, or create and delete virtual machines through CI/CD pipelines, API integrations, and cloud roles.
According to the AM Media poll, privileges of AI agents and automated services remain outside full control in 68% of cases. API keys, tokens, and secrets follow closely at 67%, while CI/CD and DevOps tool access accounts for 63%. Cloud roles reached 52%. In contrast, human system administrator accounts sit at 34% and service accounts at 26%.
Dmitry Simak, Product Manager for PAM Infrascope at NGR Softlab, explained that machine accounts frequently interact with multiple systems simultaneously and are therefore granted wide privileges. Their compromise can therefore grant attackers access to every connected system rather than a single target.
Ruslan Sharifulin of Safeinspect at Solar Group stressed that humans cannot respond to AI-driven threats in milliseconds. The primary task of modern PAM is therefore to place strict boundaries around non-human entities and enforce least-privilege principles.
Survey respondents indicated that usability for administrators and end users (72%) and simplicity of implementation (63%) are the top factors when choosing a PAM solution. Only 41% cited price as a primary concern.
Denis Morozov, CEO of JumpServer PAM, suggested that integrating AI into PAM platforms could analyze complex permission matrices, calculate risk scores, and present clear recommendations to security teams. Participants concluded that while AI agents introduce new threats, PAM remains essential and must evolve to cover machine identities.
Related articles
Agent-Ops 0.4.0 Released: Methodology for Secure Human-AI Collaboration in IT Operations
Sergey Zhitinsky, founder of Git in Sky, has published the public normative candidate for Agent-Ops 0.4.0, an open industry methodology governing how engineers and AI agents jointly handle IT infrastructure tasks. The framework keeps humans firmly in the decision-making loop while using deterministic programs for data collection and approved changes. It addresses risks such as prompt injection through processed data, unverified model outputs, and unclear accountability when AI recommendations lead to incidents. The methodology divides work across eight explicit steps and three separate planes: data, governance, and independent verification performed by a Guardian role. Two additional companies have joined as maintainers following agreements at the IT Elements 2026 conference, turning the project into a multi-organization effort. Contributors are invited to help refine contracts, schemas, and operational scenarios through GitHub and GitVerse.
ProxyKey MCP: Securing API Access for AI Agents Without Exposing Credentials
ProxyKey has released an MCP server that allows AI coding agents such as Claude Code and Cursor to manage API credentials without ever reading the actual secret values. The solution addresses the risk that any key visible to an agent becomes compromised through logging, tracing, or prompt injection. Real provider keys are stored encrypted with AES-256-GCM and never returned by any API endpoint after initial entry. Agents instead receive limited virtual passes that support IP binding, rate limits, TTL, and detailed request logging. A pending-secret workflow lets agents prepare services before the real token exists, with the human entering the secret only through a web panel. The approach deliberately restricts the MCP tool contract so no operation can read or return secret values.
Shadow AI in CI/CD: Why AI Agents Must Be Modeled as Security Threats
A new analysis from the CNCF highlights the growing risks of Shadow AI within continuous integration and continuous deployment pipelines. The report argues that AI agents should be treated as potential threats rather than simple productivity tools. Starting from a developer's laptop and extending to Kubernetes clusters, these agents can introduce unauthorized access paths and data exposure risks. Security teams are urged to incorporate AI agent behavior into formal threat modeling exercises. The discussion emphasizes the need for visibility and control over autonomous AI components operating in production environments.
Detecting Lateral Movement with Neural Networks Trained Solely on Synthetic Data
A researcher generated entire corporate network histories using a 135-line configuration file to create synthetic authentication logs containing lateral movement attacks. Neural networks trained exclusively on these artificial datasets were then evaluated against 1.65 billion real authentication events from Los Alamos National Laboratory, including 749 red team events across 301 compromised machines. The best ensemble of six models flagged 3.6 million hourly machine windows and placed 16 genuine attacks among the top 23 highest-scoring entries, producing only seven false positives. In comparison, a simple threshold counter required 161,000 false alarms to reach the same detection level. The approach also demonstrated an iterative feedback loop where detector errors directly informed refinements to the synthetic world generator. The work shows that synthetic data can reach AUC performance comparable to models trained on real labeled attacks while providing full control over the underlying attack definitions.