Add THREAT_MODEL.md + AGENTS.md/SECURITY.md discoverability chain (draft for PMC review)#994
Open
potiuk wants to merge 1 commit into
Open
Add THREAT_MODEL.md + AGENTS.md/SECURITY.md discoverability chain (draft for PMC review)#994potiuk wants to merge 1 commit into
potiuk wants to merge 1 commit into
Conversation
…aft for PMC review) Generated-by: Claude Code
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 is a proposal for the Apache Ranger PMC to review — please correct, reject, or discuss as needed. The maintainers are the decision-makers; nothing here is a requirement.
This PR proposes a draft v0 threat model for Apache Ranger, plus the conventional
AGENTS.md → SECURITY.md → THREAT_MODEL.mddiscoverability chain (Ranger currently has noSECURITY.md). Context: the ASF Security team is preparing the project for an automated agentic security scan we're piloting; such scans need the model to be mechanically discoverable, and run far less noisily when a model exists. The Security team reached out separately on the PMC's private list with the program details.The model is written from Ranger's own public artefacts (README, ranger.apache.org, the FAQ, the public REST API docs, the repo layout) and focuses on the high-value boundaries: the policy decision/distribution path (Admin authors → plugins pull + cache), the Admin REST API, the trust placed in the per-service plugins (PEPs), and Ranger KMS.
Every claim carries a provenance tag:
Because this is v0 with no maintainer input yet, it's mostly (inferred). Every (inferred) claim has a matching question in §14 "Open questions" (20 questions in 4 waves). The fastest path: walk §14 and reply confirm / correct / strike per line — react, don't compose. We fold your answers in and the (inferred) tags become (maintainer).
A few decisions reshape the whole model — Wave 1 especially: the no-match default (deny vs. fall-through to native ACLs), the transport-security default, and the default admin credential. Those three most determine which reports are real findings vs. by-design.
If the PMC would rather author the model yourselves, close this PR and we'll wait — this is a starting point, not an imposition.