Lesson 7 of 9 · 7 min read
Agent Memory Security: Poisoning, Provenance and Forgetting
Persistent memory can carry false claims or instructions into later agent tasks when those records are retrieved. Secure the write, promotion and retrieval paths with authenticated scope, source lineage, versions and expiry. Treat recalled content as data, keep resource authorization independent, and distinguish immediate retrieval denial from removal of derivatives, backups and copies already delivered.
Get full Premium access · $25
Every worked answer in all 17 topics, every lesson in every course, the full concept curriculum, the complete practice-test bank, and the downloadable security field guides.
6 months · One payment · No auto-renewal
Practise it as an interviewer asks it
Explain the lethal trifecta and use it to triage an agent design in two minutes.What is a process from a security point of view, and what stops one process from reading another's memory?Secure an agent that reads customer data, retrieves internal documents and calls APIs. Where do you start?What is membership inference, and why does overfitting raise the risk?What is SSRF, and why do LLM tools that fetch URLs bring it back?What is excessive agency, and how do you contain it?