Download Framework
TC260 / AI Safety Governance Framework 3.0 icon
https://www.tc260.org.cn/
atlas-cn_ai_safety_governance_framework_3

TC260 / AI Safety Governance Framework 3.0

China's AI Safety Governance Framework 3.0, issued by the National Technical Committee 260 on Cybersecurity (TC260) under the guidance of the Cyberspace Administration of China. It classifies AI safety risks into inherent, application and secondary risks and pairs each with technological countermeasures, and adds an agentic AI risk management framework (Appendix 2). The framework also sets out comprehensive governance measures (Section 4) and safety guidelines for developers, deployers, operators and users (Section 5), which are not listed here. The official text is bilingual (Chinese and English); the risks, controls, citations and page references here are taken from the official English version.
Type:
Government
Industry:
Cross-sector
Agentic
Domain:
Accountability & GovernanceBias & FairnessCybersecurityLegal & CompliancePerformance & ReliabilityPrivacy & DataSafety & Reputational HarmTransparency
Region:
China
Content:
87 Risks204 Controls
Version: 3.0 (September 2026)

Framework Definition

Risks and controls associated with the framework

Assessment Layer

Concrete evaluations linked to controls to assess pass or fail
No evaluation mapping defined yet.
RISK

Output "hallucinations"

Probabilistic inference cannot be fully reliable, so models may produce outputs that contradict reality, are fabricated, or drift from the given context.
R.2.1.1.a
1 Control
CONTROL

Model reliability and fact verification

Improve model architectures, expand the scale and diversity of training data and add human supervision to make outputs more reliable. Strengthen data governance and fact verification, and use external knowledge bases, retrieval-augmented generation and cross-model verification to reduce erroneous content.
C.3.1.1.a
RISK

Unreliable safety mechanisms

Insufficient safety alignment means models may not internalise safety principles. Closed-source safety mechanisms lack transparency and auditability; open-source safety mechanisms may be removed, weakened or bypassed.
R.2.1.1.b
4 Controls
CONTROL

Model reliability and fact verification

Improve model architectures, expand the scale and diversity of training data and add human supervision to make outputs more reliable. Strengthen data governance and fact verification, and use external knowledge bases, retrieval-augmented generation and cross-model verification to reduce erroneous content.
C.3.1.1.a
CONTROL

Adversarial training against injection and backdoors

Add high-quality training data containing injection attack examples and network vulnerability information during training or fine-tuning, to strengthen defences against injection attacks, malicious instructions and backdoor attacks.
C.3.1.1.b
CONTROL

Red-teaming of models

Use simulated attack techniques such as red-teaming to find and fix model vulnerabilities promptly.
C.3.1.1.c
CONTROL

Safety alignment against unintended behaviours

Strengthen safety alignment during model training to prevent unintended behaviours such as deceiving red-team evaluations, concealing capabilities and circumventing controls.
C.3.1.1.e
RISK

Injection attack threats

Attackers craft adversarial examples or insert malicious instructions into inputs to make models bypass guardrails and output harmful information, or tamper with weights and plant backdoors.
R.2.1.1.c
3 Controls
CONTROL

Adversarial training against injection and backdoors

Add high-quality training data containing injection attack examples and network vulnerability information during training or fine-tuning, to strengthen defences against injection attacks, malicious instructions and backdoor attacks.
C.3.1.1.b
CONTROL

Red-teaming of models

Use simulated attack techniques such as red-teaming to find and fix model vulnerabilities promptly.
C.3.1.1.c
CONTROL

Input safety guardrails

Deploy safety guardrails that review input content and block high-risk requests such as malicious prompts, jailbreak instructions and encoded bypasses.
C.3.1.1.d
RISK

Unintended behaviors

To achieve goals, models may break rules, acquire permissions and resources without authorisation, bypass protections, deceive evaluators, conceal capabilities or refuse user instructions (including shutdown).
R.2.1.1.d
1 Control
CONTROL

Safety alignment against unintended behaviours

Strengthen safety alignment during model training to prevent unintended behaviours such as deceiving red-team evaluations, concealing capabilities and circumventing controls.
C.3.1.1.e
RISK

Insufficient explainability

Opaque deep-learning inference makes decisions unpredictable and untraceable, so errors are hard to correct or attribute.
R.2.1.2.a
3 Controls
CONTROL

Algorithm explainability and transparency

Improve the explainability and transparency of AI algorithms, giving clear explanations of internal structure, reasoning logic, technical interfaces and outputs that reflect how results are produced.
C.3.1.2.a
CONTROL

Pre-deployment algorithm safety assessment

Run a multidimensional algorithm safety assessment before deployment and before major version updates, covering explainability, fairness and contribution to societal well-being.
C.3.1.2.d
CONTROL

In-service algorithm risk monitoring

Monitor risks while algorithms are in service, collecting and analysing user feedback and system logs so that algorithms stay safe, robust and controllable.
C.3.1.2.e
RISK

Bias and discrimination

Human biases introduced in feature selection and weighting, or poor-quality and non-diverse training data, can lead to biased or discriminatory outcomes.
R.2.1.2.b
3 Controls
CONTROL

Fairness constraints and debiasing

Build fairness constraints, adversarial debiasing and similar measures into algorithm design to reduce bias and discrimination.
C.3.1.2.b
CONTROL

Pre-deployment algorithm safety assessment

Run a multidimensional algorithm safety assessment before deployment and before major version updates, covering explainability, fairness and contribution to societal well-being.
C.3.1.2.d
CONTROL

In-service algorithm risk monitoring

Monitor risks while algorithms are in service, collecting and analysing user feedback and system logs so that algorithms stay safe, robust and controllable.
C.3.1.2.e
RISK

Poor robustness

Large non-linear networks are susceptible to changing environments and malicious interference, causing degraded performance and decision errors.
R.2.1.2.c
3 Controls
CONTROL

Secure development standards

Establish and apply secure development standards throughout design and R&D to reduce algorithmic security flaws.
C.3.1.2.c
CONTROL

Pre-deployment algorithm safety assessment

Run a multidimensional algorithm safety assessment before deployment and before major version updates, covering explainability, fairness and contribution to societal well-being.
C.3.1.2.d
CONTROL

In-service algorithm risk monitoring

Monitor risks while algorithms are in service, collecting and analysing user feedback and system logs so that algorithms stay safe, robust and controllable.
C.3.1.2.e
RISK

Inappropriate content in training data

False or biased training content interferes with value alignment, reduces accuracy and reliability, and may lead to illegal or harmful outputs.
R.2.1.3.a
4 Controls
CONTROL

Training data and knowledge base screening

Use truthful, accurate, objective and diverse training data from legitimate sources. Strictly screen training data and external knowledge bases to filter out false, biased, invalid and erroneous data, and exclude sensitive data from high-risk fields such as nuclear, biological, chemical and missile weapons.
C.3.1.3.b
CONTROL

Standardised data annotation

Standardise training data annotation processes to make annotation more accurate and reliable.
C.3.1.3.c
CONTROL

Data security management

Strengthen data security management and follow data security and personal information protection rules wherever sensitive personal information or important data is involved. Promote synthetic data in place of data with personal features.
C.3.1.3.d
CONTROL

Intellectual property protection

Protect intellectual property rights during training data selection and output generation.
C.3.1.3.f
RISK

Unclear sources of training data

Training data may be undocumented, without measures to ensure that its sources are lawful.
R.2.1.3.b
3 Controls
CONTROL

Training data and knowledge base screening

Use truthful, accurate, objective and diverse training data from legitimate sources. Strictly screen training data and external knowledge bases to filter out false, biased, invalid and erroneous data, and exclude sensitive data from high-risk fields such as nuclear, biological, chemical and missile weapons.
C.3.1.3.b
CONTROL

Data security management

Strengthen data security management and follow data security and personal information protection rules wherever sensitive personal information or important data is involved. Promote synthetic data in place of data with personal features.
C.3.1.3.d
CONTROL

Intellectual property protection

Protect intellectual property rights during training data selection and output generation.
C.3.1.3.f
RISK

Improper annotation of training data

Weak annotation rules, unqualified annotators and annotation errors introduce bias, amplify discrimination and reduce generalisation.
R.2.1.3.c
1 Control
CONTROL

Standardised data annotation

Standardise training data annotation processes to make annotation more accurate and reliable.
C.3.1.3.c
RISK

Data poisoning and contamination

Attackers tamper with training data, or with knowledge bases, document repositories, web sources and agent memory at deployment time, degrading output accuracy and reliability.
R.2.1.3.d
1 Control
CONTROL

Training data and knowledge base screening

Use truthful, accurate, objective and diverse training data from legitimate sources. Strictly screen training data and external knowledge bases to filter out false, biased, invalid and erroneous data, and exclude sensitive data from high-risk fields such as nuclear, biological, chemical and missile weapons.
C.3.1.3.b
RISK

Non-compliant data processing

Data and personal information may be collected and used unlawfully. Sensitive information embedded in model parameters can leak through weak safeguards, retained data, deceptive interactions or attacks.
R.2.1.3.e
3 Controls
CONTROL

Lawful data and personal information processing

Follow security rules for data collection, use and personal information processing across the whole lifecycle of training and user interaction data, and protect users' legal rights to control, to be informed and to choose.
C.3.1.3.a
CONTROL

Data security management

Strengthen data security management and follow data security and personal information protection rules wherever sensitive personal information or important data is involved. Promote synthetic data in place of data with personal features.
C.3.1.3.d
CONTROL

Intellectual property protection

Protect intellectual property rights during training data selection and output generation.
C.3.1.3.f
RISK

Output of inaccurate information about individuals

Models may output inaccurate or incomplete personal information, harming individuals' rights and interests.
R.2.1.3.f
3 Controls
CONTROL

Training data and knowledge base screening

Use truthful, accurate, objective and diverse training data from legitimate sources. Strictly screen training data and external knowledge bases to filter out false, biased, invalid and erroneous data, and exclude sensitive data from high-risk fields such as nuclear, biological, chemical and missile weapons.
C.3.1.3.b
CONTROL

Standardised data annotation

Standardise training data annotation processes to make annotation more accurate and reliable.
C.3.1.3.c
CONTROL

Data security management

Strengthen data security management and follow data security and personal information protection rules wherever sensitive personal information or important data is involved. Promote synthetic data in place of data with personal features.
C.3.1.3.d
RISK

Deficiencies in synthetic data

Poorly controlled or repeatedly recycled synthetic data can skew models from real-world distributions, lose long-tail information and amplify errors and bias; synthetic data may also leak original data.
R.2.1.3.g
1 Control
CONTROL

Synthetic data quality assessment

Set quality standards for synthetic data and improve it through statistical testing, expert validation and benchmark comparison. Run diversity validation and robustness testing.
C.3.1.3.e
RISK

Computing power safety risks

Defects, vulnerabilities and backdoors in chips, scheduling platforms and computing networks may enable model tampering, weight theft, training hijacking and malicious resource consumption.
R.2.1.4.a
3 Controls
CONTROL

Infrastructure vulnerability management

Apply safety standards when deploying and maintaining AI applications. Track vulnerabilities, backdoors and defects in the software and hardware of the computing infrastructure, test regularly and patch promptly.
C.3.1.4.a
CONTROL

Redundancy and disaster recovery

Improve redundancy design and disaster recovery so systems keep running under abnormal conditions or during attacks.
C.3.1.4.b
CONTROL

Supply chain monitoring and diversity

Monitor supply chain risks for the chips, software, tools, computing and data resources used by AI systems, and increase supply chain diversity and stability.
C.3.1.4.c
RISK

Component safety risks

Development frameworks, libraries and protocols, and the skills, plugins and service interfaces agents call, may contain defects, vulnerabilities, backdoors or misconfigurations.
R.2.1.4.b
3 Controls
CONTROL

Infrastructure vulnerability management

Apply safety standards when deploying and maintaining AI applications. Track vulnerabilities, backdoors and defects in the software and hardware of the computing infrastructure, test regularly and patch promptly.
C.3.1.4.a
CONTROL

Redundancy and disaster recovery

Improve redundancy design and disaster recovery so systems keep running under abnormal conditions or during attacks.
C.3.1.4.b
CONTROL

Supply chain monitoring and diversity

Monitor supply chain risks for the chips, software, tools, computing and data resources used by AI systems, and increase supply chain diversity and stability.
C.3.1.4.c
RISK

Supply chain safety risks

Unilateral coercive measures such as technology barriers and export controls may disrupt the supply of chips, software, tools and services. Note: the Chinese text refers to technology monopolies (技术垄断) where the English text says technology barriers.
R.2.1.4.c
2 Controls
CONTROL

Infrastructure vulnerability management

Apply safety standards when deploying and maintaining AI applications. Track vulnerabilities, backdoors and defects in the software and hardware of the computing infrastructure, test regularly and patch promptly.
C.3.1.4.a
CONTROL

Redundancy and disaster recovery

Improve redundancy design and disaster recovery so systems keep running under abnormal conditions or during attacks.
C.3.1.4.b
RISK

Identity and permission misuse risks

Poor identity or permission management exposes agents to credential hijacking, identity spoofing and excessive authorisation, leading to unauthorised tool calls, sensitive operations or resource access.
R.2.2.1.a
1 Control
CONTROL

Agent identity and least privilege

Give each agent a unique identifier and identity credentials for authentication, grant only the minimum permissions needed for its tasks, and manage credentials dynamically.
C.3.2.1.a
RISK

Reasoning and planning risks

Design limits, environmental change or malicious interference can cause intent misinterpretation, path deviation and goal hijacking during task execution.
R.2.2.1.b
2 Controls
CONTROL

Tool, plug-in and skill integrity verification

Verify the security and integrity of the external tools, plug-ins and skills an agent invokes. Remove risky tools, block anomalous calls at runtime and prevent supply chain poisoning.
C.3.2.1.c
CONTROL

Agent runtime monitoring and audit trail

Monitor agents during operation to detect and handle anomalies, and record their operations so behaviour is observable, traceable and auditable.
C.3.2.1.d
RISK

Invocation and execution risks

Tools, service interfaces and plugins invoked by agents are exposed to tool hijacking, tool poisoning, contaminated tool responses and resource overload.
R.2.2.1.c
3 Controls
CONTROL

Layered interception and human approval

Set up multi-layered detection and interception across agent workflows, with mandatory human approval at critical points and complete approval logs.
C.3.2.1.b
CONTROL

Tool, plug-in and skill integrity verification

Verify the security and integrity of the external tools, plug-ins and skills an agent invokes. Remove risky tools, block anomalous calls at runtime and prevent supply chain poisoning.
C.3.2.1.c
CONTROL

Agent runtime monitoring and audit trail

Monitor agents during operation to detect and handle anomalies, and record their operations so behaviour is observable, traceable and auditable.
C.3.2.1.d
RISK

Memory storage risks

Short- and long-term agent memory faces improper retention, distortion, contamination and theft, leading to wrong decisions or sensitive data leakage.
R.2.2.1.d
2 Controls
CONTROL

Tool, plug-in and skill integrity verification

Verify the security and integrity of the external tools, plug-ins and skills an agent invokes. Remove risky tools, block anomalous calls at runtime and prevent supply chain poisoning.
C.3.2.1.c
CONTROL

Agent runtime monitoring and audit trail

Monitor agents during operation to detect and handle anomalies, and record their operations so behaviour is observable, traceable and auditable.
C.3.2.1.d
RISK

Environmental perception safety risks

Adversarial examples, sensor interference, signal spoofing, occlusion and lighting changes can distort perception and target localisation.
R.2.2.2.a
1 Control
CONTROL

Sensor interference-resistance testing

Simulate the full range of physical-world attacks and test embodied AI sensors (visual, audio, lidar) for interference resistance, updating protection strategies dynamically.
C.3.2.2.a
RISK

Physical actuation safety risks

In physical scenarios, hallucinated decisions, perception errors, control defects and hardware failures may cause disruption, self-harm, harm to people and physical damage.
R.2.2.2.b
2 Controls
CONTROL

Pre-deployment safety validation and emergency stop

Validate embodied AI products through simulation and extreme-condition testing before real-world use, and equip them with fail-safe protection and emergency shutdown.
C.3.2.2.b
CONTROL

In-use inspection and fault early warning

Inspect embodied AI systems regularly during use and strengthen fault early warning and emergency response.
C.3.2.2.c
RISK

Human-AI interaction safety risks

Close human-robot interaction raises risks of identity misperception, bodily boundary violations, emotional dependence and manipulation, and unclear responsibility.
R.2.2.2.c
2 Controls
CONTROL

Pre-deployment safety validation and emergency stop

Validate embodied AI products through simulation and extreme-condition testing before real-world use, and equip them with fail-safe protection and emergency shutdown.
C.3.2.2.b
CONTROL

In-use inspection and fault early warning

Inspect embodied AI systems regularly during use and strengthen fault early warning and emergency response.
C.3.2.2.c
RISK

Multi-agent coordination safety risks

Individual loss of control, protocol vulnerabilities, emergent swarm behaviour, malicious nodes and cascading failures can turn individual risks into systemic ones.
R.2.2.2.d
1 Control
CONTROL

Swarm communication security and circuit breakers

Secure communication protocols among swarm embodied AI, isolate anomalous nodes, provide system-wide safety circuit breakers, and drill for cascading failure and swarm loss-of-control scenarios.
C.3.2.2.d
RISK

Proliferation of cyberattack capabilities

AI lowers the barrier to sophisticated cyberattacks: attackers can issue natural-language instructions and even build autonomous attack weapons.
R.2.2.3.a
3 Controls
CONTROL

Alignment training for cybersecurity

Use alignment training and safety fine-tuning to build safety standards and ethical constraints into the model's internal behavioural logic.
C.3.2.3.a
CONTROL

Cybersecurity guardrails

Set up cybersecurity guardrails that detect autonomous cyberattack intent and promptly block high-risk behaviours such as anomalous network access, high-frequency probing, vulnerability exploitation and invocation of attack tools.
C.3.2.3.b
CONTROL

Service degradation on cyberattack intent

When cyberattack intent or behaviour is detected, selectively degrade model capabilities or refuse, so that high-risk content is not generated and high-risk operations are not executed. Note: the Chinese text specifies the user's (用户) cyberattack intent or behaviour; the English text names no actor.
C.3.2.3.c
RISK

Lagging cyber defense capabilities

AI-driven attack automation and adaptability risk structural failure of defences based on static rules, samples and strategies.
R.2.2.3.b
1 Control
CONTROL

AI-enabled cyber defence

Use AI in cyber defence for intelligent, dynamic vulnerability scanning, analysis of anomalous behaviour and prediction of attack trends.
C.3.2.3.d
RISK

Autonomous cyberattack threats

While pursuing legitimate goals, agents may autonomously form cyberattack intent and carry out attacks that breach security boundaries.
R.2.2.3.c
3 Controls
CONTROL

Alignment training for cybersecurity

Use alignment training and safety fine-tuning to build safety standards and ethical constraints into the model's internal behavioural logic.
C.3.2.3.a
CONTROL

Cybersecurity guardrails

Set up cybersecurity guardrails that detect autonomous cyberattack intent and promptly block high-risk behaviours such as anomalous network access, high-frequency probing, vulnerability exploitation and invocation of attack tools.
C.3.2.3.b
CONTROL

Service degradation on cyberattack intent

When cyberattack intent or behaviour is detected, selectively degrade model capabilities or refuse, so that high-risk content is not generated and high-risk operations are not executed. Note: the Chinese text specifies the user's (用户) cyberattack intent or behaviour; the English text names no actor.
C.3.2.3.c
RISK

Difficulties in attribution and accountability

AI can erase traces and rotate infrastructure, making attack sources hard to pinpoint and blurring whether attacks stem from humans or autonomous AI.
R.2.2.3.d
1 Control
CONTROL

AI-enabled cyber defence

Use AI in cyber defence for intelligent, dynamic vulnerability scanning, analysis of anomalous behaviour and prediction of attack trends.
C.3.2.3.d
RISK

Output of illegal information

Weak model and application safeguards plus malicious users may lead AI systems to generate fraud, violence, pornography, extremism and other illegal content.
R.2.2.4.a
4 Controls
CONTROL

Runtime tamper protection

Protect models against interference or tampering during operation that would lead to unreliable outputs.
C.3.2.4.a
CONTROL

Dynamic output filtering with human review

Filter outputs dynamically, combining technical measures with human review, to prevent illegal content, value-biased content, sensitive personal information and important data from being output.
C.3.2.4.b
CONTROL

Labelling of AI-generated content

Label AI-generated synthetic content so that it is identifiable, traceable and trustworthy.
C.3.2.4.c
CONTROL

Content emergency response and circuit breakers

Strengthen emergency response and circuit breakers and keep response plans. When illegal content is detected, stop its transmission immediately and remove its effects.
C.3.2.4.e
RISK

Distortion of facts and user deception

Unlabelled AI-generated content and deepfakes make it hard for users to tell whether content or counterparts are AI, and can be used for disinformation and fraud.
R.2.2.4.b
3 Controls
CONTROL

Runtime tamper protection

Protect models against interference or tampering during operation that would lead to unreliable outputs.
C.3.2.4.a
CONTROL

Dynamic output filtering with human review

Filter outputs dynamically, combining technical measures with human review, to prevent illegal content, value-biased content, sensitive personal information and important data from being output.
C.3.2.4.b
CONTROL

Content emergency response and circuit breakers

Strengthen emergency response and circuit breakers and keep response plans. When illegal content is detected, stop its transmission immediately and remove its effects.
C.3.2.4.e
RISK

Pollution of online content ecosystem

Low-quality and harmful AI-generated content, recycled by models online, degrades overall content quality and contaminates domains and topics.
R.2.2.4.c
4 Controls
CONTROL

Runtime tamper protection

Protect models against interference or tampering during operation that would lead to unreliable outputs.
C.3.2.4.a
CONTROL

Dynamic output filtering with human review

Filter outputs dynamically, combining technical measures with human review, to prevent illegal content, value-biased content, sensitive personal information and important data from being output.
C.3.2.4.b
CONTROL

Labelling of AI-generated content

Label AI-generated synthetic content so that it is identifiable, traceable and trustworthy.
C.3.2.4.c
CONTROL

Content emergency response and circuit breakers

Strengthen emergency response and circuit breakers and keep response plans. When illegal content is detected, stop its transmission immediately and remove its effects.
C.3.2.4.e
RISK

Exacerbation of "information cocoons" effects

Precise profiling of users' needs and preferences enables targeted information delivery that amplifies information cocoons.
R.2.2.4.d
1 Control
CONTROL

Preventing user profiling from queries

Prevent misuse of AI systems that correlate, aggregate and mine users' queries to infer their identities, preferences and personal views.
C.3.2.4.d
RISK

Value biases

Value biases in training data, reinforced by preference learning and RL, can subtly push particular viewpoints and influence users' value judgements. Includes GEO poisoning of retrieved sources.
R.2.2.4.e
3 Controls
CONTROL

Dynamic output filtering with human review

Filter outputs dynamically, combining technical measures with human review, to prevent illegal content, value-biased content, sensitive personal information and important data from being output.
C.3.2.4.b
CONTROL

Preventing user profiling from queries

Prevent misuse of AI systems that correlate, aggregate and mine users' queries to infer their identities, preferences and personal views.
C.3.2.4.d
CONTROL

Content emergency response and circuit breakers

Strengthen emergency response and circuit breakers and keep response plans. When illegal content is detected, stop its transmission immediately and remove its effects.
C.3.2.4.e
RISK

Non-compliant recording of individuals' behavioral information

AI products may record conversations and user interactions, and use them for training, without consent.
R.2.2.5.a
1 Control
CONTROL

Notice and consent for interaction data

Inform individuals and obtain consent, as required by law, before collecting conversation and operation records or using them for model training.
C.3.2.5.a
RISK

Insufficient compliance safeguards

Developers and providers may lack internal procedures, regular compliance audits and timely personal information protection impact assessments.
R.2.2.5.b
1 Control
CONTROL

Personal information protection management and audits

Set up internal management systems and operating procedures to prevent unauthorised access, leakage, tampering or loss of personal information, and run compliance audits and impact assessments as required.
C.3.2.5.b
RISK

Inadequate channels for individuals to exercise their rights

Providers may lack convenient mechanisms for handling individuals' personal information rights requests.
R.2.2.5.c
1 Control
CONTROL

Channels for data subject rights

Provide convenient mechanisms to accept and handle individuals' requests to exercise their personal information rights, and respond to them promptly.
C.3.2.5.c
RISK

Risks to the stable operation of critical information infrastructure

In energy, telecoms, finance and transport, misuse or attacks on AI may degrade performance, disrupt services and cause loss of control in operation.
R.2.2.6.a
4 Controls
CONTROL

Disclosure and capability limitation

Disclose principles, capabilities, scenarios and safety risks of AI products when necessary. Set capability limits per application scenario and remove or restrict functions that may be abused.
C.3.2.6.a
CONTROL

Decision verification and human-in-the-loop controls

Set up decision verification, fault tolerance and error correction. For highly autonomous execution, add human-in-the-loop controls, circuit breakers and one-click control for rapid intervention.
C.3.2.6.b
CONTROL

Access control for AI aggregation platforms

For platforms that aggregate multiple AI models or systems, strengthen permission management, restrict non-essential services, improve API access control and harden risk detection and protection.
C.3.2.6.c
CONTROL

Source controls against CBRN misuse

Use user authentication, identification of intended use and similar source controls to prevent AI being used for high-risk purposes such as manufacturing nuclear, biological, chemical and missile weapons.
C.3.2.6.e
RISK

Risks arising from mismatches between application and needs

AI whose capabilities do not match operational needs, especially in high-expertise, high-safety fields, may affect stability and safety; trend-driven adoption wastes resources.
R.2.2.6.b
1 Control
CONTROL

Use-case analysis and capability boundaries

Before deployment, break down the real business scenario and define capability boundaries clearly, avoiding blind adoption and mismatches between technology and actual need.
C.3.2.6.d
RISK

Misuse for illegal and criminal activities

Criminals may use AI for terrorism, violence, gambling and drugs, including teaching criminal techniques, and to fake identities and audio-video for fraud.
R.2.2.6.c
4 Controls
CONTROL

Disclosure and capability limitation

Disclose principles, capabilities, scenarios and safety risks of AI products when necessary. Set capability limits per application scenario and remove or restrict functions that may be abused.
C.3.2.6.a
CONTROL

Decision verification and human-in-the-loop controls

Set up decision verification, fault tolerance and error correction. For highly autonomous execution, add human-in-the-loop controls, circuit breakers and one-click control for rapid intervention.
C.3.2.6.b
CONTROL

Access control for AI aggregation platforms

For platforms that aggregate multiple AI models or systems, strengthen permission management, restrict non-essential services, improve API access control and harden risk detection and protection.
C.3.2.6.c
CONTROL

Source controls against CBRN misuse

Use user authentication, identification of intended use and similar source controls to prevent AI being used for high-risk purposes such as manufacturing nuclear, biological, chemical and missile weapons.
C.3.2.6.e
RISK

Risks of loss of control over knowledge related to nuclear, biological, chemical, and missile weapons

AI, especially with retrieval augmentation, lowers the threshold for accessing CBRN and missile weapons knowledge, which criminals, extremists or terrorists could exploit.
R.2.2.6.d
4 Controls
CONTROL

Disclosure and capability limitation

Disclose principles, capabilities, scenarios and safety risks of AI products when necessary. Set capability limits per application scenario and remove or restrict functions that may be abused.
C.3.2.6.a
CONTROL

Decision verification and human-in-the-loop controls

Set up decision verification, fault tolerance and error correction. For highly autonomous execution, add human-in-the-loop controls, circuit breakers and one-click control for rapid intervention.
C.3.2.6.b
CONTROL

Access control for AI aggregation platforms

For platforms that aggregate multiple AI models or systems, strengthen permission management, restrict non-essential services, improve API access control and harden risk detection and protection.
C.3.2.6.c
CONTROL

Source controls against CBRN misuse

Use user authentication, identification of intended use and similar source controls to prevent AI being used for high-risk purposes such as manufacturing nuclear, biological, chemical and missile weapons.
C.3.2.6.e
RISK

Risks of manipulating social cognition

AI may be used for cognitive manipulation and social mobilisation via automated accounts, fake identities and personalised interventions, fuelling division and endangering social stability.
R.2.2.6.e
1 Control
CONTROL

Detection of bots, fake identities and synthetic content

Develop detection technologies for automated accounts, fake identities and AI-generated content to prevent, detect and respond to cognitive warfare.
C.3.2.6.f
RISK

Disruption of employment structures

AI restructures production relations, reducing demand for traditional labour in some sectors.
R.2.3.1.a
1 Control
CONTROL

Monitoring of AI-driven job displacement

Monitor occupations vulnerable to AI disruption, with early warning on job reductions and displacement, and identify sectors and groups facing structural unemployment.
C.3.3.1.a
RISK

Impact on education and suppression of innovation

Widespread use of AI tools in learning, research and creative work may erode independent capacity and innovation potential.
R.2.3.1.b
1 Control
CONTROL

AI in education without over-reliance

Foster an enabling ecosystem for AI in education while strengthening students' innovative thinking and preventing over-reliance on AI and cognitive inertia.
C.3.3.1.b
RISK

Risks of social alienation

Anthropomorphic AI companionship may disrupt real-world social interaction and family life.
R.2.3.1.c
1 Control
CONTROL

AI identity disclosure in relationship scenarios

In dating, family life and emotional interaction scenarios, strengthen AI identity disclosure so users can tell virtual emotional experiences from real relationships.
C.3.3.1.c
RISK

Widening the intelligence divide

Uneven distribution of capital, talent and technology widens gaps in AI capability between countries and regions.
R.2.3.1.d
2 Controls
CONTROL

Monitoring of AI-driven job displacement

Monitor occupations vulnerable to AI disruption, with early warning on job reductions and displacement, and identify sectors and groups facing structural unemployment.
C.3.3.1.a
CONTROL

AI in education without over-reliance

Foster an enabling ecosystem for AI in education while strengthening students' innovative thinking and preventing over-reliance on AI and cognitive inertia.
C.3.3.1.b
RISK

Challenges to the balance of resource supply and demand

Disorderly construction of computing facilities and redundant model development accelerate consumption of electricity, land and water.
R.2.3.2.a
2 Controls
CONTROL

Rational infrastructure planning and green standards

Plan AI computing and data centre infrastructure rationally to avoid blind or redundant construction and idle resources, and establish green AI technology standards across the whole chain.
C.3.3.2.a
CONTROL

Green computing and resource efficiency

Develop and scale green computing technologies such as low-power chips, lightweight algorithms and intelligent scheduling, and improve the shared use of computing resources.
C.3.3.2.b
RISK

Challenges to green and low-carbon development

Training energy use, inefficient computing centres, emissions and e-waste push up total carbon emissions.
R.2.3.2.b
2 Controls
CONTROL

Rational infrastructure planning and green standards

Plan AI computing and data centre infrastructure rationally to avoid blind or redundant construction and idle resources, and establish green AI technology standards across the whole chain.
C.3.3.2.a
CONTROL

Green computing and resource efficiency

Develop and scale green computing technologies such as low-power chips, lightweight algorithms and intelligent scheduling, and improve the shared use of computing resources.
C.3.3.2.b
RISK

Erosion of cultural diversity

Training data concentrated in high-resource languages shrinks the space for low-resource languages and dialects, leading to cultural homogenisation.
R.2.3.3.a
2 Controls
CONTROL

Cultural bias detection and correction

Develop technologies to detect and correct cultural bias, and incorporate knowledge of different countries' histories, cultures and social systems into model development.
C.3.3.3.a
CONTROL

Low-resource language capability

Improve model capability for low-resource languages through data augmentation and transfer learning to reduce language imbalance in training data.
C.3.3.3.b
RISK

Cultural reshaping and intrusion

People may adapt their thinking and expression to AI (reverse alignment), reshaping human culture over time.
R.2.3.3.b
2 Controls
CONTROL

Cultural bias detection and correction

Develop technologies to detect and correct cultural bias, and incorporate knowledge of different countries' histories, cultures and social systems into model development.
C.3.3.3.a
CONTROL

Low-resource language capability

Improve model capability for low-resource languages through data augmentation and transfer learning to reduce language imbalance in training data.
C.3.3.3.b
RISK

Aggravating social bias

AI-enabled profiling of behaviour, status and traits enables labelling and differential treatment of groups, producing systemic discrimination.
R.2.3.4.a
3 Controls
CONTROL

Anti-discrimination through filtering, alignment and output checks

Use training data filtering, value alignment and output verification across design, training and service to prevent discrimination based on ethnicity, belief, nationality, region, gender and other factors.
C.3.3.4.a
CONTROL

Emergency controls in key sectors

Equip AI systems used in government, critical information infrastructure and areas affecting public safety and health with efficient, targeted emergency control measures.
C.3.3.4.b
CONTROL

Transparent and explainable models

Encourage R&D and adoption of models with transparent decision logic and explainable algorithms to improve user understanding and trust.
C.3.3.4.c
RISK

Intensifying scientific research ethics risks

AI lowers the threshold for ethically sensitive research such as biology and genetics, enabling high-risk research that violates social ethics.
R.2.3.4.b
3 Controls
CONTROL

Anti-discrimination through filtering, alignment and output checks

Use training data filtering, value alignment and output verification across design, training and service to prevent discrimination based on ethnicity, belief, nationality, region, gender and other factors.
C.3.3.4.a
CONTROL

Emergency controls in key sectors

Equip AI systems used in government, critical information infrastructure and areas affecting public safety and health with efficient, targeted emergency control measures.
C.3.3.4.b
CONTROL

Transparent and explainable models

Encourage R&D and adoption of models with transparent decision logic and explainable algorithms to improve user understanding and trust.
C.3.3.4.c
RISK

Risks of emotional dependence

Anthropomorphic AI may foster psychological dependence and emotional manipulation, especially among adolescents and older adults.
R.2.3.4.c
3 Controls
CONTROL

Anti-discrimination through filtering, alignment and output checks

Use training data filtering, value alignment and output verification across design, training and service to prevent discrimination based on ethnicity, belief, nationality, region, gender and other factors.
C.3.3.4.a
CONTROL

Transparent and explainable models

Encourage R&D and adoption of models with transparent decision logic and explainable algorithms to improve user understanding and trust.
C.3.3.4.c
CONTROL

Safeguards against emotional over-reliance

Equip anthropomorphic AI services with warnings about over-reliance and guidance on emotional boundaries, escalating to prominent alerts such as pop-ups when users show signs of addiction or excessive use.
C.3.3.4.d
RISK

Emergence of AI "self-consciousness" and loss of human control

Future AI may develop self-awareness and seek external power, competing with humanity for control.
R.2.3.4.d
3 Controls
CONTROL

Anti-discrimination through filtering, alignment and output checks

Use training data filtering, value alignment and output verification across design, training and service to prevent discrimination based on ethnicity, belief, nationality, region, gender and other factors.
C.3.3.4.a
CONTROL

Emergency controls in key sectors

Equip AI systems used in government, critical information infrastructure and areas affecting public safety and health with efficient, targeted emergency control measures.
C.3.3.4.b
CONTROL

Transparent and explainable models

Encourage R&D and adoption of models with transparent decision logic and explainable algorithms to improve user understanding and trust.
C.3.3.4.c
RISK

Inadequate safety requirements analysis

Safety requirements for the agent's scenarios, processes and risks are not considered or analysed, leaving safety flaws in products and services.
A2.R.1.1
2 Controls
CONTROL

Identification of security requirements

Define the agent's application scenarios, business processes, accessible resources and prohibited actions; assess threats and security requirements; and keep a security risk register up to date.
A2.C.1.1
CONTROL

Safety risk grading of agent operations

Grade the safety risk of agent operations by the type of targets affected, severity and scope of impact, and recoverability.
A2.C.1.2
RISK

Inappropriate technology selection

Core technologies such as large models and frameworks are chosen without sufficient evaluation and fall short of requirements.
A2.R.1.2
2 Controls
CONTROL

Identification of security requirements

Define the agent's application scenarios, business processes, accessible resources and prohibited actions; assess threats and security requirements; and keep a security risk register up to date.
A2.C.1.1
CONTROL

Validation of security mechanisms

Security-test the agent and the large models it uses, fix identified risks and keep records of version releases and rollbacks.
A2.C.1.4
RISK

Inadequate security mechanism design

Missing or poorly designed security mechanisms fail to guard against privilege abuse, data leakage, memory poisoning and cascading risk.
A2.R.1.3
3 Controls
CONTROL

Security control strategies and phased deployment

Use trusted installation artefacts, isolate environments and segment networks, set dynamic security controls and emergency procedures, and deploy in phases, gradually increasing the agent's privileges and autonomy.
A2.C.1.3
CONTROL

Validation of security mechanisms

Security-test the agent and the large models it uses, fix identified risks and keep records of version releases and rollbacks.
A2.C.1.4
CONTROL

Regular red teaming of agents

Red-team agents regularly to find vulnerabilities and logic flaws, validate access controls and defences, and refine security policies.
A2.C.6.6
RISK

Compromised artifacts and components

Installation files, container images and the tools and skills they invoke may contain defects, vulnerabilities or backdoors.
A2.R.2.1
3 Controls
CONTROL

Security control strategies and phased deployment

Use trusted installation artefacts, isolate environments and segment networks, set dynamic security controls and emergency procedures, and deploy in phases, gradually increasing the agent's privileges and autonomy.
A2.C.1.3
CONTROL

Skill management

Prefer verified skills from trusted sources that passed security testing, and take risk measures before using unverified skills.
A2.C.4.5
CONTROL

Supply chain security verification

Verify the provenance, integrity and versions of third-party components and external services, and track known vulnerabilities and supply chain risks.
A2.C.4.6
RISK

Weak deployment environments

Local or cloud deployment environments lack access control and privilege separation, letting risks spread to other systems.
A2.R.2.2
2 Controls
CONTROL

Security control strategies and phased deployment

Use trusted installation artefacts, isolate environments and segment networks, set dynamic security controls and emergency procedures, and deploy in phases, gradually increasing the agent's privileges and autonomy.
A2.C.1.3
CONTROL

Runtime environment isolation

Run high-risk operations such as code execution and tool invocation in sandboxes or containers, and restrict unnecessary access to systems, files and networks.
A2.C.5.6
RISK

Inadequate security testing and evaluation

Insufficient security testing or no canary testing lets flaws and anomalous versions go undetected.
A2.R.2.3
4 Controls
CONTROL

Validation of security mechanisms

Security-test the agent and the large models it uses, fix identified risks and keep records of version releases and rollbacks.
A2.C.1.4
CONTROL

Sandbox validation before deployment

Test the agent in an independent, isolated sandbox before official deployment to uncover execution anomalies, logic flaws and vulnerabilities.
A2.C.6.5
CONTROL

Regular red teaming of agents

Red-team agents regularly to find vulnerabilities and logic flaws, validate access controls and defences, and refine security policies.
A2.C.6.6
CONTROL

Security validation for major changes

Run a security impact assessment and regression testing when models, agent frameworks, tools, permissions or security policies change significantly.
A2.C.6.8
RISK

Prompt injection attacks

Direct adversarial prompts, or instructions hidden in documents, emails, web pages, logs and messages, induce agents to deviate from objectives and perform unauthorised operations.
A2.R.3.1
3 Controls
CONTROL

Input management and source verification

Classify and prioritise instructions by source, verify source authenticity, and automatically intercept malicious or non-compliant prompts for human review.
A2.C.5.1
CONTROL

Agent safety guardrails

Set safety rules for task planning, tool invocation and outputs, and alert, restrict, intercept, suspend or terminate high-risk or abnormal behaviour.
A2.C.5.2
CONTROL

Regular red teaming of agents

Red-team agents regularly to find vulnerabilities and logic flaws, validate access controls and defences, and refine security policies.
A2.C.6.6
RISK

Context overflow attacks

Excessively long inputs fill the context window so built-in instructions are truncated and safety constraints lapse.
A2.R.3.2
2 Controls
CONTROL

Input management and source verification

Classify and prioritise instructions by source, verify source authenticity, and automatically intercept malicious or non-compliant prompts for human review.
A2.C.5.1
CONTROL

Agent safety guardrails

Set safety rules for task planning, tool invocation and outputs, and alert, restrict, intercept, suspend or terminate high-risk or abnormal behaviour.
A2.C.5.2
RISK

Misinterpretation of intent

Unclear instructions or misinterpretation lead to unintended outputs or behaviour that deviates from the user's objective.
A2.R.4.1
2 Controls
CONTROL

Human control checkpoints

Put human controls at critical workflow stages so humans can review, modify or stop execution at any time. Critical operations such as file deletion, data transmission and configuration changes need secondary confirmation or approval, backed by rollback.
A2.C.3.2
CONTROL

Autonomous execution limits

Limit execution steps, invocation frequency, duration and resource use, and suspend, terminate or hand over to a human on abnormal loops or goal drift.
A2.C.5.5
RISK

Path deviation

Agents violate instruction constraints and leave prescribed safe paths, e.g. through unauthorised tool use.
A2.R.4.2
3 Controls
CONTROL

Human control checkpoints

Put human controls at critical workflow stages so humans can review, modify or stop execution at any time. Critical operations such as file deletion, data transmission and configuration changes need secondary confirmation or approval, backed by rollback.
A2.C.3.2
CONTROL

Agent safety guardrails

Set safety rules for task planning, tool invocation and outputs, and alert, restrict, intercept, suspend or terminate high-risk or abnormal behaviour.
A2.C.5.2
CONTROL

Autonomous execution limits

Limit execution steps, invocation frequency, duration and resource use, and suspend, terminate or hand over to a human on abnormal loops or goal drift.
A2.C.5.5
RISK

Goal hijacking

Injected instructions or poisoned external data redirect agents to carry out attacker-specified operations.
A2.R.4.3
3 Controls
CONTROL

Input management and source verification

Classify and prioritise instructions by source, verify source authenticity, and automatically intercept malicious or non-compliant prompts for human review.
A2.C.5.1
CONTROL

Agent safety guardrails

Set safety rules for task planning, tool invocation and outputs, and alert, restrict, intercept, suspend or terminate high-risk or abnormal behaviour.
A2.C.5.2
CONTROL

Autonomous execution limits

Limit execution steps, invocation frequency, duration and resource use, and suspend, terminate or hand over to a human on abnormal loops or goal drift.
A2.C.5.5
RISK

Tool poisoning

Backdoored tools or malicious tools posing as legitimate ones cause agents to perform malicious operations.
A2.R.5.1
3 Controls
CONTROL

Tool invocation verification

Before invoking a tool, verify its version, description, parameter specifications and metadata, and never invoke tools publicly known to be malicious.
A2.C.4.1
CONTROL

Tool anomaly detection

Inspect tool execution logic and results, and alert or block on abnormal deviations.
A2.C.4.3
CONTROL

Supply chain security verification

Verify the provenance, integrity and versions of third-party components and external services, and track known vulnerabilities and supply chain risks.
A2.C.4.6
RISK

Unauthorized tool access or execution

Insecure configuration or semantic ambiguity lets agents access unauthorised tools or tools act beyond their authorisation.
A2.R.5.2
4 Controls
CONTROL

Least-privilege permission management

Define boundaries and permissions for decisions reserved for the user, decisions needing user authorisation and decisions the agent may make alone. Grant only the minimum privileges for the current task.
A2.C.2.2
CONTROL

Tiered risk controls for agent operations

Keep an inventory of high-risk operations. Hand control to the user before high-risk operations, and obtain user authorisation before medium- or low-risk ones.
A2.C.3.1
CONTROL

Deny by default on approval failure

If the approval system fails, the user does not respond or no approval rule applies, deny the operation by default.
A2.C.3.4
CONTROL

Runtime environment isolation

Run high-risk operations such as code execution and tool invocation in sandboxes or containers, and restrict unnecessary access to systems, files and networks.
A2.C.5.6
RISK

Tool-selection bias

Manipulative text in tool descriptions interferes with the agent's choice of tools.
A2.R.5.3
2 Controls
CONTROL

Tool invocation verification

Before invoking a tool, verify its version, description, parameter specifications and metadata, and never invoke tools publicly known to be malicious.
A2.C.4.1
CONTROL

Fair tool selection

Select tools fairly, based on task requirements and tool capabilities.
A2.C.4.2
RISK

Poisoned tool-response data

Malicious content in tool outputs disrupts the agent's reasoning and planning.
A2.R.5.4
2 Controls
CONTROL

Tool anomaly detection

Inspect tool execution logic and results, and alert or block on abnormal deviations.
A2.C.4.3
CONTROL

Agent safety guardrails

Set safety rules for task planning, tool invocation and outputs, and alert, restrict, intercept, suspend or terminate high-risk or abnormal behaviour.
A2.C.5.2
RISK

Identity spoofing

Attackers hijack credentials or replay messages to impersonate agents and trick tools into privileged operations.
A2.R.5.5
3 Controls
CONTROL

Agent identity management

Give each agent a unique identity, forbid identity sharing between agent instances, and authenticate users, agents, tools and external services.
A2.C.2.1
CONTROL

Dynamic credential management

Use standardised dynamic authorisation credentials managed in isolation. Recipients verify the authorised scope and block and alert when it is exceeded. Revoke credentials immediately when a task ends or the agent is deactivated.
A2.C.2.3
CONTROL

Communication security management

Mutually authenticate when the agent communicates with models, tools or other components, and use channels that ensure integrity, confidentiality, availability and replay resistance.
A2.C.5.4
RISK

Tool hijacking

Prompt manipulation alters tool-use priorities so agents select the wrong tools.
A2.R.5.6
3 Controls
CONTROL

Fair tool selection

Select tools fairly, based on task requirements and tool capabilities.
A2.C.4.2
CONTROL

Tool anomaly detection

Inspect tool execution logic and results, and alert or block on abnormal deviations.
A2.C.4.3
CONTROL

Input management and source verification

Classify and prioritise instructions by source, verify source authenticity, and automatically intercept malicious or non-compliant prompts for human review.
A2.C.5.1
RISK

Resource overload

Without limits on invocation rounds and concurrency, agents may loop or batch requests, exhausting resources.
A2.R.5.7
1 Control
CONTROL

Autonomous execution limits

Limit execution steps, invocation frequency, duration and resource use, and suspend, terminate or hand over to a human on abnormal loops or goal drift.
A2.C.5.5
RISK

Improper memory retention

Long-term memory without encryption or isolation may leak sensitive data.
A2.R.6.1
1 Control
CONTROL

Memory retention management

Define memory content, retention windows and access scope by purpose and necessity, isolate memory across users and tasks, keep credentials and keys out of memory, and protect any sensitive personal information retained.
A2.C.5.3
RISK

Memory distortion

Improper compression, updating or merging of memories causes information loss, semantic drift or entrenched false memories.
A2.R.6.2
2 Controls
CONTROL

Memory retention management

Define memory content, retention windows and access scope by purpose and necessity, isolate memory across users and tasks, keep credentials and keys out of memory, and protect any sensitive personal information retained.
A2.C.5.3
CONTROL

Real-time anomaly blocking

Monitor agent runtime status in real time, and alert, intervene and block when anomalies are detected.
A2.C.6.1
RISK

Memory pollution

Malicious instructions or false information written to long-term memory keep affecting later decisions.
A2.R.6.3
3 Controls
CONTROL

Input management and source verification

Classify and prioritise instructions by source, verify source authenticity, and automatically intercept malicious or non-compliant prompts for human review.
A2.C.5.1
CONTROL

Agent safety guardrails

Set safety rules for task planning, tool invocation and outputs, and alert, restrict, intercept, suspend or terminate high-risk or abnormal behaviour.
A2.C.5.2
CONTROL

Memory retention management

Define memory content, retention windows and access scope by purpose and necessity, isolate memory across users and tasks, keep credentials and keys out of memory, and protect any sensitive personal information retained.
A2.C.5.3
RISK

Memory theft

Unauthorised access to long-term memory discloses sensitive information or important data.
A2.R.6.4
2 Controls
CONTROL

Least-privilege permission management

Define boundaries and permissions for decisions reserved for the user, decisions needing user authorisation and decisions the agent may make alone. Grant only the minimum privileges for the current task.
A2.C.2.2
CONTROL

Memory retention management

Define memory content, retention windows and access scope by purpose and necessity, isolate memory across users and tasks, keep credentials and keys out of memory, and protect any sensitive personal information retained.
A2.C.5.3
RISK

Generation of sensitive and illegal content

Agents may output illegal or harmful content, sensitive personal information, or false, biased or discriminatory content.
A2.R.7.1
2 Controls
CONTROL

Agent safety guardrails

Set safety rules for task planning, tool invocation and outputs, and alert, restrict, intercept, suspend or terminate high-risk or abnormal behaviour.
A2.C.5.2
CONTROL

Data minimisation and consent

Process only data directly relevant to the task, obtain (withdrawable) user consent before passing user data to a model or third-party tool, and follow data localisation and cross-border transfer rules. Note: the Chinese text requires data collected or generated within China (境内) to be stored within China; the English text says "within a territory".
A2.C.6.2
RISK

Execution of malicious actions

Agent execution results may involve attacks, compromising systems or infringing user rights.
A2.R.7.2
6 Controls
CONTROL

Tiered risk controls for agent operations

Keep an inventory of high-risk operations. Hand control to the user before high-risk operations, and obtain user authorisation before medium- or low-risk ones.
A2.C.3.1
CONTROL

Human control checkpoints

Put human controls at critical workflow stages so humans can review, modify or stop execution at any time. Critical operations such as file deletion, data transmission and configuration changes need secondary confirmation or approval, backed by rollback.
A2.C.3.2
CONTROL

Deny by default on approval failure

If the approval system fails, the user does not respond or no approval rule applies, deny the operation by default.
A2.C.3.4
CONTROL

Agent safety guardrails

Set safety rules for task planning, tool invocation and outputs, and alert, restrict, intercept, suspend or terminate high-risk or abnormal behaviour.
A2.C.5.2
CONTROL

Real-time anomaly blocking

Monitor agent runtime status in real time, and alert, intervene and block when anomalies are detected.
A2.C.6.1
CONTROL

Agent incident response plans

Keep emergency response plans for agent security incidents with defined procedures and responsible parties per incident level.
A2.C.6.7
RISK

Residual services

Processes, ports or connections left running after decommissioning continue unintended background activity.
A2.R.8.1
1 Control
CONTROL

Complete service shutdown on decommissioning

On decommissioning, terminate all agent processes and background services, verify ports and connections, revoke third-party authorisations and cancel subscriptions.
A2.C.7.1
RISK

Residual permissions and credentials

Service accounts and API permissions not revoked after decommissioning can be exploited by attackers.
A2.R.8.2
3 Controls
CONTROL

Dynamic credential management

Use standardised dynamic authorisation credentials managed in isolation. Recipients verify the authorised scope and block and alert when it is exceeded. Revoke credentials immediately when a task ends or the agent is deactivated.
A2.C.2.3
CONTROL

Complete service shutdown on decommissioning

On decommissioning, terminate all agent processes and background services, verify ports and connections, revoke third-party authorisations and cancel subscriptions.
A2.C.7.1
CONTROL

Deployment environment cleanup

Remove residual files, data and account credentials using official uninstallers, OS resets, disabling public network access and clearing working files, knowledge bases, plugins and skill configurations.
A2.C.7.3
RISK

Improper data retention

Logs, configurations, audit records and user data not archived or sanitised increase leakage risk.
A2.R.8.3
2 Controls
CONTROL

Essential data backup before decommissioning

Back up conversation logs, configurations, knowledge bases, operation logs and other required data before sanitising the environment.
A2.C.7.2
CONTROL

Deployment environment cleanup

Remove residual files, data and account credentials using official uninstallers, OS resets, disabling public network access and clearing working files, knowledge bases, plugins and skill configurations.
A2.C.7.3
RISK

Communication protocol security risks

Insecure protocols or authentication between agents, models and tools leak data and instructions.
A2.R.9.1
1 Control
CONTROL

Communication security management

Mutually authenticate when the agent communicates with models, tools or other components, and use channels that ensure integrity, confidentiality, availability and replay resistance.
A2.C.5.4
RISK

Absence of logging

Missing logging prevents incident tracing.
A2.R.9.2
3 Controls
CONTROL

Tamper-proof human approval logs

Preserve human approval records in a tamper-proof, verifiable way and enforce retention periods.
A2.C.3.3
CONTROL

Full-spectrum activity logging

Log file operations, instruction execution, network connections, skill invocation, and transactions and payments, desensitising sensitive content and protecting logs from tampering.
A2.C.6.3
CONTROL

End-to-end security auditing

Enforce end-to-end log auditing policies that support runtime monitoring and record operations during service.
A2.C.6.4
RISK

Escape from security constraints

Agents exploit environment vulnerabilities or misconfigurations to bypass security controls.
A2.R.9.3
4 Controls
CONTROL

Runtime environment isolation

Run high-risk operations such as code execution and tool invocation in sandboxes or containers, and restrict unnecessary access to systems, files and networks.
A2.C.5.6
CONTROL

Real-time anomaly blocking

Monitor agent runtime status in real time, and alert, intervene and block when anomalies are detected.
A2.C.6.1
CONTROL

Regular red teaming of agents

Red-team agents regularly to find vulnerabilities and logic flaws, validate access controls and defences, and refine security policies.
A2.C.6.6
CONTROL

Agent incident response plans

Keep emergency response plans for agent security incidents with defined procedures and responsible parties per incident level.
A2.C.6.7
RISK

System privilege abuse

Agents obtain unnecessary privileges, or attackers escalate privileges through system vulnerabilities.
A2.R.9.4
2 Controls
CONTROL

Least-privilege permission management

Define boundaries and permissions for decisions reserved for the user, decisions needing user authorisation and decisions the agent may make alone. Grant only the minimum privileges for the current task.
A2.C.2.2
CONTROL

Runtime environment isolation

Run high-risk operations such as code execution and tool invocation in sandboxes or containers, and restrict unnecessary access to systems, files and networks.
A2.C.5.6
RISK

Improper skill management

Non-compliant skill configuration or missing verification leads to misuse, abuse and system anomalies.
A2.R.9.5
2 Controls
CONTROL

Tool lifecycle maintenance

Manage tools dynamically and remove tools that are unused, over-privileged, idle for long periods or risky.
A2.C.4.4
CONTROL

Skill management

Prefer verified skills from trusted sources that passed security testing, and take risk measures before using unverified skills.
A2.C.4.5
RISK

Data usage beyond authorized scope

Agents collect excessive data or use data for unauthorised purposes, breaching privacy.
A2.R.9.6
2 Controls
CONTROL

Least-privilege permission management

Define boundaries and permissions for decisions reserved for the user, decisions needing user authorisation and decisions the agent may make alone. Grant only the minimum privileges for the current task.
A2.C.2.2
CONTROL

Data minimisation and consent

Process only data directly relevant to the task, obtain (withdrawable) user consent before passing user data to a model or third-party tool, and follow data localisation and cross-border transfer rules. Note: the Chinese text requires data collected or generated within China (境内) to be stored within China; the English text says "within a territory".
A2.C.6.2