[SPARK-56998]Add SECURITY.md + AGENTS.md Security section for scan-agent discoverability#55933
Open
potiuk wants to merge 3 commits into
Open
[SPARK-56998]Add SECURITY.md + AGENTS.md Security section for scan-agent discoverability#55933potiuk wants to merge 3 commits into
potiuk wants to merge 3 commits into
Conversation
…bility Adds a SECURITY.md to the repo root and a Security section at the end of the existing AGENTS.md so an automated scan agent can mechanically discover the project's security model via the conventional AGENTS.md -> SECURITY.md -> model URL chain. The chain terminates at the existing https://spark.apache.org/docs/latest/security.html document. Generated-by: Claude Code (Claude Opus 4.7)
gatorsmile
approved these changes
May 21, 2026
HyukjinKwon
approved these changes
May 21, 2026
Member
|
I think we should probably file a JIRA though. |
gatorsmile
changed the title
Member
|
Added a JIRA |
cloud-fan
reviewed
May 22, 2026
|
|
||
| Agents that scan this repository should consult `SECURITY.md` | ||
| for the project's threat model, in-scope / out-of-scope | ||
| declarations, and known non-findings before reporting issues. |
Contributor
There was a problem hiding this comment.
super nit: the existing style in this file is to not add line breakers manually. A long line still renders well in modern markdown editors and github web.
Member
Author
There was a problem hiding this comment.
Done in 0998f04 — unwrapped to a single line.
cloud-fan
reviewed
May 22, 2026
|
|
||
| ## Reporting a vulnerability | ||
|
|
||
| To report a security vulnerability in Apache Spark, follow the |
Member
Author
There was a problem hiding this comment.
Done in 0998f04 — all three paragraphs unwrapped to single lines.
cloud-fan
approved these changes
May 22, 2026
Per the existing style in AGENTS.md (paragraphs are single long lines; markdown renderers handle wrap), unwrap the added Security section in AGENTS.md and the body paragraphs in SECURITY.md. Generated-by: Claude Code (Claude Opus 4.7)
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
4 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 proposal for the PMC to review — please correct, reject, or discuss as needed. Nothing here is a requirement; the maintainer is the decision-maker.
This adds a
SECURITY.mdto the repo root and aSecuritysection to the existingAGENTS.mdso an automated scan agent can mechanically discover the project's security model via the conventionalAGENTS.md → SECURITY.md → model URLchain. The chain terminates at the existing https://spark.apache.org/docs/latest/security.html page — nothing about the model content itself changes.Context: the ASF Security team is preparing the project for an automated agentic security scan we're piloting. Such scans refuse to run if the model isn't discoverable by that path (refusing upfront beats wasting PMC reviewer cycles on a noise-heavy run against an unknown model). Discoverability is the one hard gate; everything else is suggestion. The Security team has reached out separately on the PMC's private list with the program details; this PR is the public-facing repo piece.
The Security team uses
threat-model-produceras the rubric for what a complete model looks like — but this PR is just the link; the existingsecurity.htmlcontent is accepted as the model.After this lands on
master, the same two files would need to be onbranch-3.5for the second scan target — happy to open a cherry-pick PR for that, or leave it to the PMC.Questions / pushback welcome. Happy to adjust the wording or move the section if the project has a house style.