When enterprises introduce AI agents to handle daily operations, a frequently overlooked issue arises: as documents migrate from their original systems to AI platforms, the permission attributes they carry may cease to exist. Go Dong-hyun, Executive Director of South Korean document security firm Pasu AI, provided a specific explanation on this matter during a media interview.
Go Dong-hyun noted that once connected to AI, the inherent permission attributes of data begin to disintegrate. This does not imply that permissions are intentionally deleted; rather, during the migration process—for instance, when encrypted documents are decrypted and placed into independent storage readable by the AI platform—the original access control information may not automatically follow along. If an enterprise merely reconfigures permissions on the AI platform side, it must additionally verify whether these new permissions align with existing security policies, which itself creates a risk exposure.
His proposed remediation strategy is that permission validation should not be executed by the AI agent requesting the data, but rather by the entity providing the data. When an AI agent requests a specific document, the data provider first verifies the requester's identity and permissions, returning content only after confirming the requester has the right to access it. This ensures that even when multiple agents collaborate, the scope of information provision remains based on the original data permissions, rather than on new permissions independently set by the AI platform.
Go Dong-hyun categorized the foundational requirements for enterprise-grade AI agent orchestration into three areas: data management, account and permission management, and AI governance. Data management addresses consistency regarding document versions, change history, and storage locations—if an AI agent references an outdated report or a duplicate copy, the output results will deviate. Account and permission management ensure that the identity and permissions of every requester (whether a human employee or an AI agent) can be verified. AI governance requires enterprises to manage AI agents similarly to how they manage employees: new agents must be registered with their creators and intended purposes, and idle agents must have their permissions revoked.
These three foundations correspond to different system roles: the data platform determines what materials can be provided, the account and permission system confirms who is making the request, and the AI agent platform utilizes this information to complete tasks. Go Dong-hyun believes that attempting to use a single platform to manage all data, accounts, and AI agents is unrealistic, as enterprises typically already possess independently operating data management systems and identity authentication frameworks. A more feasible approach is to clearly define the responsibility boundaries of each system and transmit permission information to the AI agent platform via interfaces.
However, he also acknowledged that currently connecting all enterprise business processes through AI agents remains difficult. Work systems and data are scattered across different locations, and access permissions operate under varying standards. To achieve cross-departmental agent collaboration, data and permissions must be managed uniformly. Go Dong-hyun distinguished between two scenarios: utilizing AI agents in individual business units versus implementing organization-wide agent orchestration, which are issues at different levels. The latter requires enterprises to first establish unified standards for data and permission management; otherwise, differences in security strategies among various systems will be exposed during collaboration.