Add SECURITY.md and AGENTS.md for security-model discoverability#364
Merged
Conversation
shukitchan
approved these changes
May 21, 2026
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.
Summary
Adds SECURITY.md and AGENTS.md to apache/trafficserver-ingress-controller so the project's security model is mechanically discoverable from the repo root.
SECURITY.md references apache/trafficserver/SECURITY.md as the umbrella model for the C++ core, then adds two repo-specific paragraphs covering the trust surfaces that aren't covered by the umbrella:
remap.configtranslation; RBAC onIngresscreate/update is the trust boundary on the outbound routing table.AGENTS.md points coding agents at SECURITY.md for security-model reads (same shape as
apache/trafficserver/AGENTS.md's security bridge).Coordinated with the Traffic Server PMC.
Test plan