読書リサーチレーダー投資フレームワーク
ログイン / 新規登録
← 読解に戻る
ニューストピック · AI Agent Identity Management重大2 分で読めるDisconfirmAI 編集部

Palo Alto Networks Survey: Over 70% of Enterprises Allow AI Agents to Modify Code, but Less Than 10% Can Fully Detect Unmanaged AI Activity

A new cloud security survey by Palo Alto Networks reveals that while AI agents are widely used in software development, enterprises face significant gaps in identity management and security monitoring.

2026-11-19 08:00 GMT+8

Cybersecurity firm Palo Alto Networks recently published its "2026 State of Cloud-Native Security" report, revealing that while AI agents are ubiquitous in enterprise software development, security measures have failed to keep pace. Nearly all surveyed organizations use AI agents in their software development lifecycle, and more than 70% allow these agents to modify code, adjust Continuous Integration/Continuous Delivery (CI/CD) settings, or make changes to production environments. However, less than 10% of respondents can comprehensively detect and classify unmanaged AI activity across different cloud environments.

The introduction of AI-assisted development has significantly increased the frequency of infrastructure changes. Over 80% of surveyed organizations reported that AI agents lead to more frequent cloud infrastructure modifications, yet fewer than 40% enforce mandatory manual security reviews. Additionally, only about 30% of organizations can track the complete process from code commit to deployment execution for most production workloads. Regarding Infrastructure as Code (IaC), more than 40% of organizations use AI to generate IaC templates, but only about 30% require mandatory security scanning before deployment. Data shows that during a 90-day period, an average of nearly 20% of high-severity application security issues made it into production, with the average time from discovering a code security issue to deploying a patch exceeding 18 days.

Identity management for AI agents presents another critical vulnerability. Nearly 40% of surveyed organizations admitted that their AI development tools or agents can access production cloud environments through development or deployment pipelines. More concerning is that over half of the responding engineers stated that AI agent operations are attributed to the engineer's own identity or personal access tokens, rather than a distinct AI agent identity. This makes it difficult for enterprises to distinguish human actions from machine behaviors during audits, and 40% of organizations cannot reconstruct what operations an AI agent performed, hindering their ability to confirm whether the agent accessed sensitive resources or exceeded its intended scope.

ログイン / 新規登録
読書リサーチレーダー投資フレームワーク

Credential management also suffers from significant gaps. 30% of surveyed organizations discovered that credentials used by AI agents in CI/CD pipelines were not included in enterprise management systems. Over 30% reported difficulty in revoking or rotating credentials used by AI agents during security incident investigations, while 60% still require manual intervention to revoke access rights for Nonhuman Identities (NHI). Data leakage risks are also rising: about 20% of organizations only discover shadow AI after an incident or audit, 40% have found managed data copied to unmanaged AI environments, and nearly 40% have identified sensitive or regulated data being used for AI model training or fine-tuning without authorization.

ソース

  • ithome.com.twiThome↗
トピック

AI Agent Identity Management

The rapid deployment of autonomous AI agents in enterprise environments has outpaced traditional identity and access man…

5 ステップ1 件更新日 2026-11-22 01:27

経緯

  1. 2026-03-20March 20, 2026: Google Cloud's Office of the CISO publishes guidelines on countering 'shadow agents,' emphasizing the need for strict IAM protocols and defining two primary agentic models: workload agents and workforce agents.cloud.google.com ↗
  2. 2026-05-28May 28, 2026: The Cloud Security Alliance releases a whitepaper stating that 98% of organizations report unsanctioned AI use, yet 86% lack visibility into data flows, identifying shadow AI as a contributing factor in one in five data breaches.labs.cloudsecurityalliance.org ↗
  3. 2026-08-25August 25, 2026: TrueFoundry publishes a guide on AI agent identity, detailing how to implement verifiable credentials and delegation contexts to ensure auditability across enterprise systems.truefoundry.com ↗

未解決の問題

  • How will regulatory bodies define legal accountability when an autonomous agent causes harm without direct human intervention?
  • What standards will emerge for interoperable agent identity verification across different cloud providers (e.g., AWS vs. Azure vs. GCP)?
  • Can existing SIEM and DLP tools be effectively adapted to parse the non-deterministic audit trails generated by autonomous agents?
トピック全文を読む →
リサーチを続ける →