AI & ML
Accept Changes, Reject Attacks: Robust Memory Management for LLM Agents
arXiv cs.CR0 views
arXiv:2610.41056v1 Announce Type: new Abstract: Since large language model (LLM) agents rely on long-term memory, what they store now shapes what they do later. A memory manager decides how each input changes this memory and which records the agent acts on. It can fail in two ways: keeping a fact that has since changed (outdated memory), or storing a planted passage or injected instruction (memory poisoning). Most prior work studies them separately, yet they call for opposite write decisions, so no fixed write rule handles both. We therefore formalize memory robustness as handling both without doing worse on other inputs. Since accuracy checks only the answer, we measure robustness with evidence-conditioned accuracy (ECA), which also checks that the records the manager selects include all the evidence the answer needs, updated and free of attacks. However, existing memory systems and defenses are not more robust than an untuned manager on our test sets. We improve robustness with a simple one-shot recipe that fine-tunes the manager on episodes synthesized around a single conversation with inserted changes and attacks. On three backbones, it improves every category score on our test sets and more than doubles the untuned manager's overall ECA, though robustness remains incomplete.
Source:https://arxiv.org/abs/2610.41056PreviousClosing the Applied Cybersecurity Gap in Critical Infrastructure: A Cyber-to-Physical Security Assessment Framework for Water SystemsNextEvaluating Structural and SAT Attack Resilience in Cryptographic Dynamic Logic Locking via Keystream Capping
Related posts
Trip Settlement for Transporters: Close Trips Cleanly
0dev.to Database
How to Remove Tourists from Your Travel Photos (Without Ruining the Shot)
0dev.to AI
Fixed Templates vs Prompt Writing for Personal AI Videos
0dev.to AI
The credential boundary: how should an AI agent use a login without holding it?
0dev.to AI

AIエージェントにAPIキーを見せずに使わせる方法
0dev.to Security

Cách cho phép AI Agent sử dụng API Key mà không để lộ
0dev.to Security