docs: note on securing agent memory writes (OWASP ASI06) - #4002
Open
vgudur-dev wants to merge 1 commit into
Open
vgudur-dev wants to merge 1 commit into
vgudur-dev wants to merge 1 commit into
Conversation
|
|
Collaborator
|
Thank you @vgudur-dev please sign the contributor agreement and I will merge your change, much appreciated! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.