Skip to content

docs: note on securing agent memory writes (OWASP ASI06) - #4002

Open
vgudur-dev wants to merge 1 commit into
redis:mainfrom
vgudur-dev:docs-agent-memory-integrity
Open

vgudur-dev wants to merge 1 commit into
redis:mainfrom
vgudur-dev:docs-agent-memory-integrity

Conversation

@vgudur-dev

@vgudur-dev vgudur-dev commented Sep 14, 2026

Copy link
Copy Markdown

Adds one bullet to the "Security and Privacy" list on the "How agents work" page (content/develop/ai/agent-builder/agent-concepts.md): memory integrity. Content that an agent writes to its memory from tool results, web pages or other agents can carry instructions that are replayed into later prompts (OWASP Top 10 for Agentic Applications ASI06; MITRE ATLAS AML.T0080.000), so it should be validated before it is written and protected records verified on read. The bullet links the two references and an open-source guard that implements the checks.

Docs-only change, one added line, no other edits. Disclosure: the linked guard (OWASP Agent Memory Guard) is an OWASP Incubator project I lead; the wording is implementation-neutral and I am happy to drop that link if you prefer to keep the page vendor-free.


Note

Low Risk
Documentation-only addition to an existing security checklist; no runtime or product behavior changes.

Overview
Extends the Security and Privacy section on How agents work with a new memory integrity bullet.

The guidance calls out that memory populated from tool output, web content, or other agents can inject instructions that reappear in later prompts, and recommends validating writes and verifying protected records on read. It links OWASP Agentic Top 10 (ASI06), MITRE ATLAS AML.T0080.000, and optionally OWASP Agent Memory Guard as a reference implementation.

Reviewed by Cursor Bugbot for commit e77690a. Bugbot is set up for automated code reviews on this repo. Configure here.

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@mich-elle-luna mich-elle-luna self-assigned this Sep 14, 2026
@mich-elle-luna

Copy link
Copy Markdown
Collaborator

Thank you @vgudur-dev please sign the contributor agreement and I will merge your change, much appreciated!

@mich-elle-luna mich-elle-luna left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants