arXivDaily arXiv每日学术速递 周一至周五更新
arXiv周末暂无论文更新,休息一下吧,周末愉快~~
arXiv 2602.09433cs.CRcs.AI
收藏

自主动作运行时管理(AARM):为在运行时安全保护AI驱动的动作制定系统规范

Autonomous Action Runtime Management(AARM):A System Specification for Securing AI-Driven Actions at Runtime

Independent Researcher, IEEE Member(独立研究者,IEEE会员)

Herman Errico

AI总结:

AARM提出了一种开放规范,旨在通过运行时安全机制保护AI驱动的动作,定义了拦截动作、评估策略和记录凭证等核心功能,以应对AI自主执行带来的安全挑战。

摘要:

随着人工智能系统从被动助手发展为能够执行具有后果性动作的自主代理,安全边界从模型输出转移到了工具执行。传统安全范式——日志聚合、周界防御和事后取证——无法保护那些AI驱动的动作不可逆、以机器速度执行,并可能来自潜在被篡改的编排层的系统。本文介绍了自主动作运行时管理(AARM),一种开放的规范,用于在运行时安全保护AI驱动的动作。AARM定义了一个运行时安全系统,该系统在执行前拦截动作,积累会话上下文,对照策略和意图对齐进行评估,执行授权决策,并记录具有防篡改特性的凭证以供取证重建。我们正式化了一个威胁模型,针对提示注入、混淆代理攻击、数据外泄和意图漂移。我们引入了一个动作分类框架,区分禁止、依赖上下文拒绝和依赖上下文允许的动作。我们提出了四种实现架构——协议网关、SDK仪器化、内核eBPF和供应商集成——具有不同的信任属性,并指定了符合AARM系统的最低兼容要求。AARM是模型无关、框架无关和供应商中立的,将动作执行视为稳定的网络安全边界。该规范旨在在专有碎片化之前建立行业标准,以防止互操作性受阻。

英文摘要:

As artificial intelligence systems evolve from passive assistants into autonomous agents capable of executing consequential actions, the security boundary shifts from model outputs to tool execution. Traditional security paradigms - log aggregation, perimeter defense, and post-hoc forensics - cannot protect systems where AI-driven actions are irreversible, execute at machine speed, and originate from potentially compromised orchestration layers. This paper introduces Autonomous Action Runtime Management (AARM), an open specification for securing AI-driven actions at runtime. AARM defines a runtime security system that intercepts actions before execution, accumulates session context, evaluates against policy and intent alignment, enforces authorization decisions, and records tamper-evident receipts for forensic reconstruction. We formalize a threat model addressing prompt injection, confused deputy attacks, data exfiltration, and intent drift. We introduce an action classification framework distinguishing forbidden, context-dependent deny, and context-dependent allow actions. We propose four implementation architectures - protocol gateway, SDK instrumentation, kernel eBPF, and vendor integration - with distinct trust properties, and specify minimum conformance requirements for AARM-compliant systems. AARM is model-agnostic, framework-agnostic, and vendor-neutral, treating action execution as the stable security boundary. This specification aims to establish industry-wide requirements before proprietary fragmentation forecloses interoperability.

机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。

↑