Privileged Agents

    The Privileged Agents tab lists the discovered AI agents that hold elevated permissions, including permissions that let an agent access, modify, or expose sensitive data. These agents require closer oversight and stricter controls than the rest in the agent inventory.

    Use this tab to keep the set of privileged entitlements current as platforms and roles change and to confirm that every privileged agent has a named owner. Deciding whether an agent's access is warranted calls for seeing what that agent can reach, as illustrated in its access graph.

    How SecureAI identifies a privileged agent

    SecureAI syncs agents from each configured application instance, together with the entitlements assigned to them: roles, API permissions, licenses, models, knowledge bases, and MCP servers. To run it on demand, click Fetch in Application Settings. Both the agents identified as privileged and the entitlements available for marking reflect the results of the latest successful sync of the instance the agents came from.

    SecureAI compares each agent's entitlements against the entries in the privileged entitlements list. Only enabled entries are compared. An agent holding at least one enabled privileged entitlement is identified as a privileged agent. The access graph legend shows a matching Privileged Agent marker. Because sync results are recalculated rather than stored, the access graph changes as agents gain and lose entitlements in the source platform and as entries are added, enabled, disabled, or deleted. What you see depends on your delegated role. Owner resolution works differently and is documented in Unmanaged Agents.

    Prerequisites

    • Log in as a Super Admin or as a help desk technician assigned the Governance Manager role.
    • At least one AI platform instance must be configured with the relevant service associated to it, for example, Microsoft Copilot Studio, Gemini Enterprise Agent Platform, or Zia Agents.
    • The instance must show the Sync completed status. Agents and their entitlements are compared only after a successful sync.
    • The entitlements to be marked as privileged must already have been discovered and listed under Entitlements.
    • The users you want to assign as owners must exist in a directory or application configured in SecureAI or exist as SecureAI users.

    Configuration instructions

    1. Navigate to Governance > AI Inventory > AI Agents, and then select the Privileged Agents tab.
    2. Click Manage Privileged Entitlements to view the entries already defined.
    3. Click Add Privileged Entitlements, then select the check box beside each entitlement you want to be marked as privileged. You can select entitlements of any discovered type: role, API permission, license, model, knowledge base, and MCP server.
    4. Click Add and then Close.
    5. To control whether an entry applies, use the icons in the Actions column.
      • Disable retains an entry but stops it from applying.
      • Enable puts the entry back into effect.
      • Delete removes the privileged marking, leaving the entitlement itself intact so that it can be marked again later.
    6. Click View Graph in the Access Graph column of the agent, then click Legend to examine the node types.
    7. Click Assign Owner against an agent to give it an owner. To apply the same owners to several agents, select their check boxes and click Update Owner. The owner can approve or reject access requests for the agent and review the entitlements assigned to it through the Governance Assigning Rule feature.
    8. Select the Assign owners only from native/agent ownership policy check box to restrict the choice to the users identified by the ownership policies or clear it to widen the choice.
    9. Select Save and Proceed. The agents now show their owners in the Owners column, and privileged agents remain listed under the Privileged Agents tab.

    Tips

    • A sharp rise in privileged agents after a fetch usually means one entitlement was granted broadly in the source platform. Check its assignment summary in Entitlements before treating it as an incident.
    • A privileged agent with no owner has sensitive access and nobody to approve or reject the requests raised for it. The Owners column identifies these agents, which are worth clearing ahead of the wider ownership backlog.
    • Scope certification with the built-in Privileged Agents report using Filter by Report, and attach a workflow with more than one approver.