Skip to main content

Introduction

Agentic Artificial Intelligence (AI) is a category of AI systems that can autonomously, or with human supervision, execute decisions to achieve goals.  These systems are adaptable and can proactively adjust their responses. 

Types of Agentic AI include: 

  • Business-task or enterprise agents: serve internal users, accessing enterprise systems and integrations (e.g., Course chatbots, Salesforce Agentforce, UiPath) 
  • Coding agents: for software development (e.g., Claude Code, OpenAI Codex) 
  • Computing infrastructure and operations agents (e.g., used to automate various cloud compute resources) 
  • Personal agents (e.g., ChatGPT Work, Claude Cowork, Google Gemini, OpenClaw)  
  • Agentic AI web browsers (e.g., ChatGPT Atlas, Google Chrome AI, Perplexity Comet, Wave Browser) 

Risks

The risks associated with using agentic AI can be significant because agents can take actions, use tools, access data, and operate with limited or no human oversight.  To prevent negative outcomes, it is helpful to describe these risks in more detail. 

Excessive Privileges and Identity Abuse

AI agents often access multiple organizational systems, including Software-as-a-Service (SaaS) systems, cloud computing resources, application programming interfaces (APIs), and email.  If a user is not careful to grant the agent the “least privileges” access, it can lead to situations in which the autonomous agent exceeds its authority when performing tasks.  Additionally, if an attacker gains control of the AI agent, the attacker can direct the agent to perform tasks using excess privileges to change or exfiltrate data. 

Data Leakage and Exfiltration

Data leakage can occur if AI agents have excessive privileges or expose data during transactions or integrations, in outputs, logs, memory, or downstream actions.  Additionally, if agentic AI is compromised, the attacker can potentially access sensitive data through permissions and/or integrations that the agent is already authorized to use.   

In Penn’s environment, this is particularly concerning for regulated data (e.g., FERPA, HIPAA) and other confidential data (e.g., PCI-DSS, human resource information, financial data). 

Unauthorized Actions

Without predefined constraints on their actions, AI agents may use unintended tools or access sensitive data, leading to unpredictable behavior.  Additionally, agentic systems may take actions such as modifying records, sending emails, approving financial transactions, or updating system configurations. 

Prompt Injection 

Prompt injection is the process of using malicious inputs or commands to manipulate AI systems into unintended or harmful behavior; this is often referred to as “agent hijacking.”   

Attackers can insert malicious instructions via prompts or documents, or through systems the agent uses for its work. 

Loss of Human Oversight

Users of agentic AI can trust them too much in a variety of ways, including failure to review outputs or missing security incidents, such as privilege escalation by the agent.  The human-in-the-loop approach is important for mitigating this risk by embedding consistent human interaction and oversight into agentic AI. 

Security Guidance

General Recommendations 

The following steps should be followed to ensure the secure deployment of agentic AI. 

  1. Define the agent’s function scope: Use clearly defined permissions that limit access to only the tools and data required. 
  2. Isolate the execution environment: Use sandboxing or containerization to restrict the agent’s operating environment. 
  3. Control API/integration access: Permit integrations using allow lists and validate agent-initiated requests at runtime. 
  4. Implement human oversight: Use human operators as the escalation check on actions that exceed the defined function scope or result in uncertain outcomes. Examples of situations that require human approval include deleting files, executing financial transactions, or emailing external domains. 
  5. Manage agent identities: Use short-lived, agent-specific credentials scoped to each agent’s tasks (Note that it is against the Acceptable Use policy to provide agents with PennKey credentials); ensure authorization does not exceed the user’s level; finally, inventory all agents, their owners, and active integrations. 

Getting Assistance

For assistance with securely setting up AI agents, please work with your Local Support Provider (LSP).  You can find the support directory here: 

Additional Resources

“Critical AI Security Guidelines, v1.4” SANS Research Program, March 2026 

“State of Agentic AI Security and Governance, v2.01” OWASP, GenAI Security Project, June 2026. 

“Identify Risk for Autonomous Agentic AI Systems,” Microsoft Security, March 19, 2026.