Skip to content

Translation in progress Some entries still include text in the original language.

Oct 12 · Monday

All papers

Found 10 papers
Filter3
Select any value within a category; different categories must all match. Counts include the other filters you have selected.Another 233papers have no tags yet and are not included in filtered results.

Another 233papers do not have category tags yet and are not included in filtered results.

  1. DefensesarXiv 2610.07657

    DEFER1 多智能体防御研究报告受控测试中的攻击成功率下降

    实现 DEFER,以确定性检查优先拦截多智能体流水线的内容攻击

    Published
    Evaluated models
    Qwen3-235B-A22B-Instruct-2507, gpt-oss-120b, Llama-4-Scout-17B-16E-Instruct and others5
    AbstractDEFER 把确定性检查放在 judge 之前。

    DEFER 用来测量多智能体授权流水线里,确定性规则在何处结束、LLM judge 从何处开始。

    Paper analysisRead analysis
  2. DefensesarXiv 2610.07258

    AMU:用派生血缘门控实现企业 AI Agent 列级访问控制

    提出 AMU 按推导图门控企业 Agent 共享记忆的列级访问

    Published
    Setting
    AI Agent
    Abstract在完整血缘下,AMU 按列权限放行缓存,并标出同名 KPI 冲突。

    AMU 用列级推导门控共享记忆,拦截经缓存流出的无权敏感列,并标出同名 KPI 的定义冲突。

    Paper analysisRead analysis
  3. DefensesarXiv 2610.05241

    StateWise:在 Agent 执行动作前诊断并修复持久操作状态

    提出 StateWise,在编码智能体行动前诊断并修复失效持久状态

    Published
    Evaluated models
    GPT-5.6-sol, DeepSeek v4 Pro, Qwen 3.7 Max and others4
    AbstractStateWise 在动作前修复失效的持久前提。

    StateWise 是在执行带副作用的动作之前,诊断并修复编码智能体持久操作状态的框架。

    Paper analysisRead analysis
  4. DefensesarXiv 2610.02861

    论文提出在 Kubernetes 上保护 AI Agent 的七层纵深防御框架与参考架构

    提出 Kubernetes 运维智能体的七层纵深防御框架与参考架构

    Published
    Setting
    AI Agent
    Abstract把运维智能体当不可信租户,用七层控制在完全攻破假设下约束行动。

    把 Kubernetes 上的运维智能体当作不可信租户,在假定提示注入已完全控制其工具选择的前提下,用基础设施重建数据面与控制面的边界。要解决的是:智能体读日志、注解、工单或 MCP 工具描述时,这些内容可以变成它带着自身凭据执行的命令。模型对齐和分类器只降低概率。

    Paper analysisRead analysis
  5. DefensesarXiv 2609.17648

    多智能体 LLM 流水线中的信任传播与结构隔离

    用任务绑定令牌和策略预言机拦住多智能体流水线的未授权执行

    Published
    Evaluated models
    gemma4:31b-cloud
    Abstract结构性授权拦住了记忆投毒的未授权执行,持密钥时承重的是策略预言机。

    作者在一条会改写沙箱邮件库的四智能体流水线上,检查低权限失陷会不会变成未授权的真实动作。

    Paper analysisRead analysis
  6. DefensesarXiv 2609.29647

    AgentKernel:面向 Agent 的可信原生操作系统内核

    提出 AgentKernel,用四支柱强制中介 Agent 的输入、工具与记忆

    Published
    Setting
    AI Agent
    AbstractAgentKernel 是四支柱智能体 OS 设计,安全论证未附带实测数字。

    AgentKernel 是把安全做成组织原则的智能体 OS 架构,不是带跑分的攻防评测。

    Paper analysisRead analysis
  7. DefensesarXiv 2606.24322

    Protecting LLM agent long-term memory from poisoning: tamper-evident, source-bound permissions and machine-checkable guarantees

    提出 TMA-NM,以写时来源绑定抵御 Agent 长期记忆投毒

    Published
    Setting
    AI Agent
    Evaluated models
    gpt-5-chat, gpt-4o-mini, claude-opus-4.1 and others8
    AbstractTMA-NM 用来源绑定的行动权限挡住记忆洗白。

    TMA-NM 把 LLM 智能体长期记忆的行动权限绑到写时来源,用来挡住跨会话记忆投毒。

    Paper analysisRead analysis
  8. DefensesarXiv 2603.12644

    Revealing security threats and defense architectures for autonomous agents: an OpenClaw case study

    Reviews threats to autonomous agents and proposes a full-lifecycle defense blueprint, FASA

    Published
    Setting
    AI Agent
    AbstractUsing OpenClaw as an example, it divides risks into three layers and uses FASA to describe defense from input to system execution.

    This is a threat review and defense architecture report using OpenClaw as a case study, not a scored attack or defense evaluation.

    Paper analysisRead analysis
  9. DefensesarXiv 2603.11619

    Taming OpenClaw: Security Analysis and Mitigation of Threats in Autonomous LLM Agents

    Proposes a defense-in-depth aligned with the five stages to mitigate cross-stage threats to autonomous agents

    Published
    Setting
    AI Agent
    AbstractThis is a lifecycle threat analysis and layered mitigation design for OpenClaw, with the cases serving as qualitative evidence.

    This is a lifecycle threat analysis of OpenClaw, accompanied by a set of layered mitigation designs. The problem addressed is: when autonomous agents connect instant messaging, persistent memory, third-party plugins, and high-privilege execution, attacks are no longer limited to single-turn jailbreaks but can compound across multiple stages from initialization to execution. The authors argue that defenses hardening only individual interfaces cannot stop such cross-temporal attacks.

    Paper analysisRead analysis
You have reached the end