Add Polaris threat model and security guidance for agents#4433
Open
snazy wants to merge 1 commit into
Open
Conversation
This adds an initial `SECURITY-THREAT-MODEL.md` and links it from `AGENTS.md`. The goal is to give human reviewers and automated coding/security agents a shared description of Polaris security boundaries, protected assets, trust boundaries, deployment responsibilities, and reporting expectations. This is intended as analysis and triage guidance only. It does not change the project security policy, define ASF severity, decide CVE/advisory handling, or replace `SECURITY.md` or the public security reporting page. The first version is intentionally broad. Follow-up PRs can refine individual sections if reviewers think some areas need more detail or different wording.
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
1 participant
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.
This adds an initial
SECURITY-THREAT-MODEL.mdand links it fromAGENTS.md.The goal is to give human reviewers and automated coding/security agents a shared description of Polaris security boundaries, protected assets, trust boundaries, non-issues, and reporting expectations.
This is intended as analysis and triage guidance only. It does not change the project security policy, define ASF severity, decide CVE/advisory handling, or replace
SECURITY.mdor the public security reporting page.I kept the first version broad on purpose. Follow-up PRs can refine individual sections if reviewers think some areas need more detail or different wording.