本专题内容
Generative AI · Agents · RAG · Evaluation · Model security · Governance
Deploy useful AI with appropriate controls
How should you evaluate an AI assistant or agent before deployment? Define a task, an authorised corpus and observable failure criteria. Then measure accuracy, source quality, access control, cost and response time on representative cases. The decision record preserves model, instruction and document versions. It distinguishes response quality from permission to execute an action.
阅读指南 EN新闻观察
全部国际新闻 →已保存的标题 · 无法更新 · 最近成功获取时间 : 2026年10月22日 21:20
AI会带来什么？在外滩年会，全球央行热议最大未知变量 - 新浪财经
via Google News · aggregator中国工程院院士邓中翰：将CPU所承载的规则约束嵌入大模型底层，可减少AI幻觉 - 新浪财经
via Google News · aggregator坚决抵制AI仿冒“明星”侵权带货 - 新浪网
via Google News · aggregator课堂前移岗位出题 实景研训！看“人工智能+”赋能产业工人成长 - 新浪网
via Google News · aggregator计算机科学与工程学院党委理论学习中心组赴润和软件开展示范学习 - 钟声网
via Google News · aggregator“人工智能+”样本如何诞生？千里科技的新旧动能转型 - 新浪财经
via Google News · aggregator参考资料：数据、用途与局限
文档核查日期 .
此语言版本的详细参考说明以英语提供。
| 来源与目的 | 已核实的数据或指标 | 使用方法 | 需要保留的局限 |
|---|---|---|---|
| MITRE ATLAS Examine documented tactics, techniques and cases involving AI systems. |
The official repository publishes ATLAS tactics, techniques and case-study data. They support analysis of the actual deployed system. | Select scenarios matching your application’s data, interfaces and tools. Test permissions and consequences, not only model responses. | A technique catalogue is neither an exhaustive coverage guarantee nor a test result for your system. |
| NIST · AI Risk Management Framework Organise management of AI-related risks. |
The AI RMF Core is organised around Govern, Map, Measure and Manage. It is a voluntary risk-management framework. | Define intended use, affected people and error consequences. Connect each risk to an evaluation, owner and stop or recovery mechanism. | The framework certifies neither a model nor an application. Using it does not remove the need to examine applicable requirements. |
| OWASP · LLM Top 10 Prepare tests for language-model application risks. |
The 2025 edition includes Prompt Injection, Sensitive Information Disclosure and Excessive Agency. | Turn a risk into an observable scenario: hostile document, restricted data or out-of-scope tool. Record expected behaviour and evidence of refusal. | A risk list is not a complete assessment. Input filtering alone does not establish authorisation for every action. |
RAG：访问权限、引用与缓存
此语言版本的详细参考说明以英语提供。
RAG does not delegate permissions to the model
The corpus supplies information; the access service decides which passages an identity may receive. Distinguish relevance selection, object permission and authority to act after reading.
- Cover vector retrieval, lexical branches, citations and caches.
- Apply rights removal to existing conversations.
- Verify answer quality and absence of disclosure separately.
Explore the RAG access matrix and replay cases →
References consulted on · OWASP · LLM08:2025 Vector and Embedding Weaknesses OWASP · API1:2023 Broken Object Level Authorization
OAuth/OIDC：受众与权限
此语言版本的详细参考说明以英语提供。
An AI agent retains each tool’s authorisation boundaries
A model instruction does not create a grant. For every tool, identify the calling client, resource server, audience and object policy.
- Restrict permissions to the operation and recipient needed for the use case.
- Do not forward one tool’s token to another API merely for convenience.
- Test that an agent cannot read another tenant’s objects despite having a read scope.
See token recipients and the ten OAuth/OIDC cases →
Sources reviewed on · IETF · RFC 9700 · OAuth 2.0 Security BCP · IETF · RFC 9068 · JWT access token profile · OpenID Foundation · OpenID Connect Core 1.0 · IETF · RFC 8725 · JWT Best Current Practices · IETF · RFC 6749 · OAuth 2.0 framework
SSRF：URL与连接
此语言版本的详细参考说明以英语提供。
An AI agent tool keeps bounded network access
Text produced by a model, retrieved document or search result must not expand an allowed tool destination. Defining the connector by operation and service makes the agent’s actual network reach controllable.
- Reconstruct requests from business identifiers when the service is known.
- Enforce resolution, connection, proxy and each redirect at the egress component.
- Keep a traceable decision and response limits, including after retry or fallback.
Read the 12 cases and connection controls →
Sources reviewed on · OWASP · SSRF Prevention Cheat Sheet · WHATWG · URL Living Standard · AWS EC2 · Instance metadata options · IETF · RFC 3849
AI：验证JSON结果
此语言版本的详细参考说明以英语提供。
An extraction contract precedes every agent action
An AI-generated object remains an input to validate. Correct types establish neither document values, actor identity nor permission to write into the target system.
- Validate fields before handing them to the connector.
- Route unknown values and missing evidence into an explicit review path.
- Apply context and authorization controls to every downstream operation.
Compare the 14 outputs and their reasons →
Sources reviewed on · IETF · RFC 8259 · JSON Schema · Object reference · JSON Schema · Draft 2020-12 validation · Python 3.12 · json decoder · python-jsonschema · Schema validation · OWASP · LLM05:2025 Improper Output Handling