potiuk opened a new pull request, #3966: URL: https://github.com/apache/jena/pull/3966
## What this is A **draft threat model** for Apache Jena, proposed by the ASF Security team for the Jena PMC to review, correct, or reject — drafted by the Security team's threat-model tooling from Jena's public docs and repository, following the [ASF Security threat-model rubric](https://gist.github.com/potiuk/da14a826283038ddfe38cc9fe6310573). It was requested by the PMC (andy@) as a starting point. This PR: - adds `THREAT_MODEL.md` — the draft model; - adds `SECURITY.md` — a short security policy linking the threat model; - adds `AGENTS.md` with a `## Security` section, so the chain `AGENTS.md → SECURITY.md → THREAT_MODEL.md` is mechanically discoverable by automated security scanners. ## How to read it Every claim is provenance-tagged: *(documented)* (from Jena's docs/repo), *(inferred)* (reasoned from architecture, **not yet confirmed**), *(maintainer)* (confirmed by the PMC). This v0 is ~12 documented / ~34 inferred. The **§14 Open questions** section collects every inferred claim into waves — that is where review time is best spent. The model treats **Fuseki's SPARQL endpoint** as the primary boundary (public query, localhost-only admin by default are documented) and flags the high-value query surfaces for confirmation: - the SPARQL **Update** default (read-only vs update-enabled) — decides whether anonymous write is in-model (wave 1); - **`SERVICE` federation (SSRF)**, **`file:`/FROM local-file read**, **ARQ JavaScript/custom functions (code exec)**, and **RDF/XML XXE** in RIOT — is each prevented/restrictable by default? (wave 2); - the **resource/DoS line** (query timeout / result limits) — addressing the PMC's volume concern (wave 3). Nothing here is a requirement — the model is for the PMC to own. Comment inline, edit the branch, or reply on the email thread. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
