docs: add security extension points guidance - #8198
Draft
maxpetrusenkoagent wants to merge 1 commit into
Draft
Conversation
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.
Why are these changes needed?
AutoGen is in maintenance mode, but issue #7669 asks where Agent Threat Rules-style content scanning should fit for existing AutoGen users.
This PR adds a docs-only security extension points page that explains the maintainer-shaped path: keep fast-changing threat rule packs outside AutoGen, and compose external scanners at existing message, tool, or workbench boundaries. It specifically calls out that tool and workbench boundaries are better fits than chat-message-only scanning for prompt injection and exfiltration entering through web pages, files, MCP servers, or other tool outputs.
Related issue number
Related to #7669
Verification
security-extension-points.mdpage and no extensions-guide toctree entry.python3characterization check after docs change:PASS: docs coverage for #7669 existsuv run python check_md_code_blocks.py docs/src/user-guide/extensions-user-guide/security-extension-points.mdpassed.git diff --check FETCH_HEAD...HEADpassed.uv run sphinx-build -b html -W --keep-going docs/src docs/buildreached and rendereduser-guide/extensions-user-guide/security-extension-points; it still exits non-zero on pre-existing optional dependency autodoc warnings forcv2,chromadb,mem0,redisvl,llama_cpp,ollama,semantic_kernel,graphrag, andjson_schema_to_pydantic.Second-agent review
Preferred reviewer
claude -pwas available but failed authentication withOAuth access token has been revoked.Fallback reviewer
hermes chat -Qreviewed/tmp/oss-pr-second-agent-review.diffand returnedCLEAN: no blocking correctness, regression, test, security, duplicate/superseded, or maintainer-fit issues found.Checks
Created with: Hermes Agent