Add umbrella threat model + SECURITY.md + AGENTS.md for security-model discoverability#352
Merged
elecharny merged 2 commits intoJun 2, 2026
Conversation
…odel discoverability Adds a draft (v0) umbrella threat model for the Apache Directory identity stack (shared trust model with per-domain addenda for LDAP, Kerberos, Fortress RBAC, SCIM, and MVCC storage), plus SECURITY.md and AGENTS.md, so an automated scan agent can discover it via AGENTS.md -> SECURITY.md -> THREAT_MODEL.md. The model is a proposal for the PMC to review; most claims are (inferred) and route to open questions in its section 14. Generated-by: Claude Code (Claude Opus 4.8)
Generated-by: Claude Opus 4.8 (1M context)
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
2 participants
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 draft proposal for the Directory PMC to review — please correct, reject, or discuss as needed. Nothing here is a requirement; the maintainers are the decision-makers, and this describes the project as the PMC says it is.
This PR adds the Apache Directory umbrella
THREAT_MODEL.md(hosted here indirectory-server) plusSECURITY.mdandAGENTS.md, wiringAGENTS.md -> SECURITY.md -> THREAT_MODEL.md. The other nine in-scope repos (directory-ldap-api,directory-kerby, the fourdirectory-fortress-*,directory-scimple,directory-mavibot,directory-studio) get discoverability pointers to this umbrella in companion PRs.The model captures the shared trust boundary across the stack — a network service that authenticates a remote principal and authorizes its requests over a wire protocol (LDAP / Kerberos / SCIM / REST) — with per-domain addenda where the surface diverges (LDAP bind/ACI, Kerberos KDC crypto, Fortress RBAC/SoD, SCIM, MVCC storage).
Draft-first, mostly inferred (~18 documented / 0 maintainer / ~70 inferred); every
*(inferred)*claim routes to a numbered §14 question, grouped by domain. The wave-1 rulings decideVALID-vs-misconfiguration across the stack:A meta question (§14 q10): would the PMC rather have Kerby / Fortress / SCIMple each carry their own full model (they are semi-independent products) instead of the umbrella? Proposed: umbrella + pointers now, split later if preferred.
Context: the ASF Security team is preparing the project for an automated agentic security scan we're piloting. Drafted via the threat-model-producer rubric. If you'd rather author it yourselves, close this PR and we'll regroup.