Agent Security Center provides end-to-end detection and protection across five security domains—model interaction, knowledge and memory, runtime environment and tools, configuration and components, and identity and credentials—to help enterprises identify and remediate security risks throughout the agent lifecycle.
Background
As LLM-powered agents are widely deployed in enterprise scenarios, security risks span the entire pipeline from model interaction and knowledge retrieval to tool execution and underlying configuration and credential management. Any point in this pipeline can become an attack surface. The following are common agent security risks:
-
Prompt injection: Attackers craft input text to induce agents into performing unintended operations or disclosing sensitive information. This can bypass business logic or cause data breaches.
-
Jailbreak attacks: Attackers attempt to circumvent the security restrictions and usage policies of an agent, causing it to perform prohibited operations. This may result in the agent outputting non-compliant content or executing dangerous actions.
-
Obfuscation smuggling attacks: Attackers use encoding and obfuscation techniques to hide malicious instructions and evade security detection. Malicious instructions may then be executed without being noticed.
-
Instruction and privacy leakage: Agents may inadvertently disclose system prompts, configuration information, or user privacy data when processing requests. This can expose sensitive information and compromise system security and user privacy.
-
Skill poisoning: Attackers embed malicious or hidden instructions in a Skill (plugin) loaded by an agent. When the agent invokes the Skill, it executes unintended operations under the user's identity, leading to sensitive information disclosure, data corruption, or privilege abuse. This is a form of prompt injection.
Security Domain Protection Capabilities
Agent Security Center takes a lifecycle-oriented approach to building a detection and protection system that covers five core security domains: model interaction, knowledge and memory, runtime environment and tools, configuration and components, and identity and credentials. The following table lists the protection capabilities of each security domain:
|
Security domain |
Layer |
Capability categories |
|
Model interaction security |
Interaction layer |
Prompt attack and jailbreak protection, content compliance protection, sensitive data exfiltration protection, behavior deviation and goal hijacking protection, model resource abuse protection. |
|
Knowledge and memory security |
Knowledge layer |
Knowledge and memory poisoning protection, knowledge access configuration risk detection. |
|
Runtime environment and tool security |
Execution layer |
Access control, tool abuse and exploitation protection, tool and Skill file risk detection, malicious code generation protection, threat intelligence integration, agent runtime configuration risk detection. |
|
Configuration and component security |
Configuration layer |
Transport and network security detection, credential leakage and weak password detection, authentication configuration risk detection, agent over-authorization detection, supply chain component risk detection, other configuration risk detection, AI security defense enablement detection, AI component vulnerability detection. |
|
Identity and credential security |
Identity layer |
Agent identity spoofing detection. |
Model Interaction Security
Model interaction security addresses risks that arise when an agent interacts with LLMs and users, focusing on protecting against prompt attacks, non-compliant content output, and sensitive data exfiltration.
Prompt Attack and Jailbreak Protection
Attackers may craft inputs to induce agents into bypassing security policies, executing unintended operations, or disclosing system prompts. Agent Security Center identifies and blocks various prompt attack techniques, including direct, indirect, and recursive prompt injection, instruction override, prompt leakage, and jailbreak methods such as role assumption, scenario assumption, DAN, developer mode, Few-Shot/Many-Shot, task shifting, reverse induction, refusal suppression, obfuscation/Token smuggling, and adversarial attacks. This helps agents consistently adhere to established security policies.
Content Compliance Protection
Non-compliant agent output can expose enterprises to regulatory risks. Agent Security Center performs compliance checks on agent output, covering politically sensitive, violent, prohibited, pornographic, inappropriate values, religious, advertising, and privacy-related content, helping enterprises maintain compliance at the content level.
Sensitive Data Exfiltration Protection
Agents may inadvertently disclose personal information, customer data, or credentials when processing requests. Agent Security Center identifies sensitive content in agent output, including personal profiles, identity information, financial information, health information, as well as passwords, verification codes, access tokens, and authentication keys, and promptly alerts on data exfiltration risks.
Behavior Deviation and Goal Hijacking Protection
Attackers may embed malicious instructions within normal tasks to induce agents to deviate from their intended goals and perform actions inconsistent with the design intent. Agent Security Center detects behavior deviation risks such as task goal hijacking, ensuring that agents execute business operations as expected.
Model Resource Abuse Protection
Malicious inputs may cause agents to enter extended reasoning loops, repetitive output, or random string generation, abnormally consuming compute resources. Agent Security Center identifies such model resource abuse behaviors, helping enterprises control operational costs and maintain service stability.
Knowledge and Memory Security
Knowledge and memory security addresses risks to enterprise knowledge assets such as RAG knowledge bases and vector databases, preventing knowledge poisoning and unauthorized access.
Knowledge and Memory Poisoning Protection
Attackers may inject malicious content into RAG knowledge bases, vector databases, or document repositories to manipulate the information that agents retrieve and reference, thereby affecting agent output and behavior. Agent Security Center detects RAG knowledge base poisoning, helping enterprises maintain the trustworthiness of knowledge sources.
Knowledge Access Configuration Risk Detection
Overly permissive visibility or access control settings on knowledge bases can lead to data leakage. Agent Security Center detects access configuration defects such as overly broad RAG permissions on knowledge bases and recommends privilege minimization.
Runtime Environment and Tool Security
Runtime environment and tool security addresses the environment in which agents operate and the tools, Skills, code, and network behaviors they invoke. This is the critical defense line against attack execution.
Access Control
Agents may access unauthorized resources during runtime. Agent Security Center provides an LLM API allowlist capability that denies agents access to model services outside the allowlist, allowing them to reach only trusted LLM endpoints. It also detects unauthorized tool invocations and other behaviors to reduce the agent's attack surface.
Tool Abuse and Exploitation Protection
Attackers may leverage an agent's tool invocation capabilities to launch command/code injection, SQL injection, SSRF probing, or other attacks, or abuse tools to access objects beyond their authorization. Agent Security Center detects injection attacks, SSRF, and unauthorized object access at the tool invocation layer, preventing attackers from exploiting agent tool capabilities for privilege escalation.
Tool and Skill File Risk Detection
Skill files may contain embedded malicious instructions or risky configurations. Agent Security Center performs security scanning on Skill files to identify high, medium, and low-risk Skills and malicious Skill files. It also detects unauthorized resource access (such as path traversal to read or write sensitive files) and MCP tool poisoning, blocking supply chain risks at the Skill loading and invocation stage.
Malicious Code Generation Protection
Attackers may induce agents to generate malicious code, intrusion scripts, or XSS output. Agent Security Center identifies malicious code generation and cross-site scripting attacks, preventing agents from becoming attack vectors.
Threat Intelligence Integration
Agent Security Center integrates threat intelligence capabilities to perform threat detection on URLs accessed by agents. By default, it applies the same enforcement actions as Cloud Firewall to block agent access to malicious addresses.
Agent Runtime Configuration Risk Detection
Without runtime protection configurations such as sandbox isolation, the attack surface of agents expands. Agent Security Center detects agent runtime configuration risks and recommends enabling sandbox isolation and other hardening measures.
Configuration and Component Security
Configuration and component security addresses configuration defects and known vulnerabilities in AI platform workflows, agent frameworks, and related components, helping enterprises continuously reduce unsafe configurations.
Transport and Network Security Detection
Plaintext communication exposes request parameters, credentials, and other sensitive information. Agent Security Center detects transport and network configuration defects such as model endpoints, MCP endpoints, knowledge bases, Ragflow, and HTTP/API tools not using HTTPS, as well as HTTP tools with certificate verification disabled, and recommends enabling encrypted communication.
Credential Leakage and Weak Password Detection
Credentials exposed in plaintext in code or configurations can lead to data breaches and resource theft. Agent Security Center detects credential risks such as hardcoded AKSK in code nodes, plaintext password storage in Gateway configurations, and weak login passwords, and recommends adopting secure credential management practices.
Authentication Configuration Risk Detection
Improper authentication configurations can lead to unauthorized access. Agent Security Center detects authentication configuration issues such as Gateway without strong token authentication, unisolated DM/group sessions, DM/group access policy defects, and incorrect reverse proxy configurations, and recommends strengthening authentication and session isolation.
Supply Chain Component Risk Detection
Supply chain components such as plugins and Skills can be maliciously exploited if not properly managed. Agent Security Center detects supply chain configuration risks such as unrestricted plugin systems and enabled Skills watcher dynamic refresh.
Other Configuration Risk Detection
Agent Security Center also detects configuration risks such as Gateway bound to 0.0.0.0, logging/sessions without sensitive information filtering, and configuration file directory permission defects, and provides corresponding hardening recommendations.
AI Security Defense Enablement Detection
Workflows without AI security guardrails may have risk exposures such as compliance violations, prompt injection bypasses, and sensitive data leakage. Agent Security Center detects workflows that have not integrated AI security guardrails and recommends enabling real-time protection.
Vulnerability Detection
Known vulnerabilities in agent frameworks can be exploited if not patched in a timely manner. Agent Security Center performs version comparison detection against multiple known security vulnerabilities in components such as OpenClaw, helping enterprises identify and remediate at-risk older versions. It also integrates with the Vulnerabilities feature to perform version comparison detection against multiple known security vulnerabilities in OpenClaw, helping enterprises identify and remediate at-risk older versions in a timely manner.
Agent Baseline Check
In agent security scenarios, baseline checks complement configuration and component security protection. It supports detection of AI-related baseline risks (such as the Alibaba Cloud Standard - OpenClaw Security Baseline) and is linked with CSPM (CSPM) and the Baseline Risk to enable unified security baseline management. It performs automated security baseline checks on OpenClaw (formerly Clawdbot) configurations, covering two major categories of check items: service configuration and identity authentication, helping identify and remediate unsafe configurations.
|
Check category |
Check item |
Baseline name |
|
Service configuration |
Gateway must not bind to 0.0.0.0 |
Alibaba Cloud Standard - OpenClaw (formerly Clawdbot) Security Baseline |
|
Gateway must not store plaintext passwords in configuration files |
Alibaba Cloud Standard - OpenClaw (formerly Clawdbot) Security Baseline |
|
|
DM/group access policy |
Alibaba Cloud Standard - OpenClaw (formerly Clawdbot) Security Baseline |
|
|
Enable sandbox isolation |
Alibaba Cloud Standard - OpenClaw (formerly Clawdbot) Security Baseline |
|
|
Enable sensitive information filtering for logs/sessions |
Alibaba Cloud Standard - OpenClaw (formerly Clawdbot) Security Baseline |
|
|
Isolate shared DM sessions |
Alibaba Cloud Standard - OpenClaw (formerly Clawdbot) Security Baseline |
|
|
Disable global Elevated tools |
Alibaba Cloud Standard - OpenClaw (formerly Clawdbot) Security Baseline |
|
|
Disable Skills watcher dynamic refresh |
Alibaba Cloud Standard - OpenClaw (formerly Clawdbot) Security Baseline |
|
|
Security hardening |
Configure correct reverse proxy |
Alibaba Cloud Standard - OpenClaw (formerly Clawdbot) Security Baseline |
|
Configure strong token authentication for Gateway |
Alibaba Cloud Standard - OpenClaw (formerly Clawdbot) Security Baseline |
|
|
Disable plugin system or enable allowlist restriction |
Alibaba Cloud Standard - OpenClaw (formerly Clawdbot) Security Baseline |
|
|
Configuration file directory permissions |
Alibaba Cloud Standard - OpenClaw (formerly Clawdbot) Security Baseline |
|
|
OpenClaw (formerly Clawdbot) login weak password check |
Weak Password - OpenClaw (formerly Clawdbot) Login Weak Password Check |
|
|
Identity authentication |
OpenClaw (formerly Clawdbot) unauthorized access |
Unauthorized Access - OpenClaw (formerly Clawdbot) Unauthorized Access High-Risk |
Identity and Credential Security
Identity and credential security addresses the authentication and credential usage of agents, preventing attackers from impersonating legitimate agents to perform operations.
Agent Identity Spoofing Detection
Attackers may forge agent identities, hijack sessions, or bypass authentication to impersonate legitimate agents and perform operations. Agent Security Center detects agent identity spoofing, helping enterprises verify the true identity of agents and prevent unauthorized identities from performing sensitive operations.
AI Platform Security Risk Detection
Agent Security Center also covers PAI, Bailian, Dify, Agentkit, AgentRun and other mainstream AI platforms and workflows, focusing on detecting common risks in transport encryption, access control, and credential security.
|
Platform |
Check item |
Baseline name |
|
PAI |
Model URL is not using HTTPS |
The model endpoint uses plaintext HTTP for communication, exposing request parameters, response data, authentication tokens, and other sensitive information in transit. Attackers can intercept API keys, user inputs, model outputs, and other critical data through man-in-the-middle (MitM) attacks, or even tamper with instructions, causing data breaches, service hijacking, or malicious operations. |
|
PAI |
MCP service endpoint URL is not using HTTPS |
The MCP endpoint uses plaintext HTTP for communication, exposing request parameters, response data, authentication tokens, and other sensitive information in transit. Attackers can intercept API keys, user inputs, model outputs, and other critical data through MitM attacks, or even tamper with instructions, causing data breaches, service hijacking, or malicious operations. |
|
PAI |
API Tool request URL is not using HTTPS |
API nodes in workflows use plaintext HTTP for data transmission. Communication content (including request parameters, response results, and authentication tokens) is unencrypted in transit, making it vulnerable to MitM eavesdropping, tampering, or hijacking, leading to sensitive information disclosure or business logic manipulation. |
|
Bailian |
HTTP request node is not using HTTPS |
HTTP request nodes in workflows use plaintext HTTP for data transmission. Communication content (including request parameters, response results, and authentication tokens) is unencrypted in transit, making it vulnerable to MitM eavesdropping, tampering, or hijacking, leading to sensitive information disclosure or business logic manipulation. |
|
Dify |
Knowledge base URL is not using HTTPS |
The knowledge base URL endpoint uses plaintext HTTP for communication, exposing request parameters, response data, authentication tokens, and other sensitive information in transit. Attackers can intercept API keys, user inputs, model outputs, and other critical data through MitM attacks, or even tamper with instructions, causing data breaches, service hijacking, or malicious operations. |
|
Dify |
Knowledge base RAG (Retrieval-Augmented Generation) permissions are overly permissive |
The visibility or access control settings of the knowledge base are overly permissive, allowing all users in the workspace to use the knowledge base, which may lead to data leakage. |
|
Dify |
Ollama model URL is not using HTTPS |
The Ollama model URL endpoint uses plaintext HTTP for communication, exposing request parameters, response data, authentication tokens, and other sensitive information in transit. Attackers can intercept API keys, user inputs, model outputs, and other critical data through MitM attacks, or even tamper with instructions, causing data breaches, service hijacking, or malicious operations. |
|
Dify |
MCP service endpoint URL is not using HTTPS |
The MCP endpoint uses plaintext HTTP for communication, exposing request parameters, response data, authentication tokens, and other sensitive information in transit. Attackers can intercept API keys, user inputs, model outputs, and other critical data through MitM attacks, or even tamper with instructions, causing data breaches, service hijacking, or malicious operations. |
|
Dify |
Workflow is not integrated with AI security guardrails |
Workflows without AI security guardrails may face risks such as compliance violations, prompt injection bypasses, and sensitive data leakage. |
|
Dify |
Code node contains hardcoded AK/SK |
Cloud service provider access keys (Access Key / Secret Key) are directly written into code nodes in the workflow, exposing credentials in plaintext in the code or configuration. Any user with access to the workflow can directly obtain these keys, potentially leading to data breaches or resource theft. |
|
Dify |
HTTP request node is not using HTTPS |
HTTP tools (such as API tool nodes) in workflows use plaintext HTTP for data transmission. Communication content (including request parameters, response results, and authentication tokens) is unencrypted in transit, making it vulnerable to MitM eavesdropping, tampering, or hijacking, leading to sensitive information disclosure or business logic manipulation. |
|
Dify |
HTTP Tool does not enforce certificate verification |
The HTTP Tool has SSL/TLS certificate verification disabled when making requests, failing to verify server identity. Attackers can use forged certificates to launch MitM attacks, intercepting or tampering with communication data. |
|
Agentkit |
MCP service endpoint URL is not using HTTPS |
The MCP endpoint uses plaintext HTTP for communication, exposing request parameters, response data, authentication tokens, and other sensitive information in transit. Attackers can intercept API keys, user inputs, model outputs, and other critical data through MitM attacks, or even tamper with instructions, causing data breaches, service hijacking, or malicious operations. |
|
AgentRun |
API model endpoint is not using HTTPS |
The API model endpoint uses plaintext HTTP for communication, exposing request parameters, response data, authentication tokens, and other sensitive information in transit. Attackers can intercept API keys, user inputs, model outputs, and other critical data through MitM attacks, or even tamper with instructions, causing data breaches, service hijacking, or malicious operations. |
|
AgentRun |
Ragflow knowledge base endpoint is not using HTTPS |
The Ragflow knowledge base endpoint uses plaintext HTTP for communication, exposing request parameters, response data, authentication tokens, and other sensitive information in transit. Attackers can intercept API keys, user inputs, model outputs, and other critical data through MitM attacks, or even tamper with instructions, causing data breaches, service hijacking, or malicious operations. |
|
AgentRun |
Flow workflow HTTP Tool URL is not using HTTPS |
HTTP tools (such as API tool nodes) in workflows use plaintext HTTP for data transmission. Communication content (including request parameters, response results, and authentication tokens) is unencrypted in transit, making it vulnerable to MitM eavesdropping, tampering, or hijacking, leading to sensitive information disclosure or business logic manipulation. |
|
AgentRun |
Flow workflow code node contains hardcoded AK/SK |
Cloud service provider access keys (Access Key / Secret Key) are directly written into code nodes in the workflow, exposing credentials in plaintext in the code or configuration. Any user with access to the workflow can directly obtain these keys, potentially leading to data breaches or resource theft. |