Add SECURITY.md referencing EVE security policy - #23
Merged
Merged
Conversation
This repository is part of the EVE project but carries no security policy of its own, so a researcher who lands here is offered no private reporting channel and no sign that one exists. Name the private channels the project already uses, and defer to the main EVE repository for supported versions, response timeline and the coordinated disclosure process, so the project keeps one authoritative policy rather than a divergent copy per repository. Signed-off-by: eriknordmark <erik@zededa.com> Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
milan-zededa
approved these changes
Sep 9, 2026
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.
Description
eve-rustis part of the EVE project but carries no security policy of its own, so GitHub shows no reporting instructions on this repository and a researcher who finds an issue here has no private channel to use.The added
SECURITY.mdnames the private reporting channels the project already uses — eve-security@lists.lfedge.org and GitHub private vulnerability reporting onlf-edge/eve— and defers to the main EVE repository for supported versions, response timeline and the coordinated disclosure process. That keeps one authoritative policy for the project rather than a copy per repository that drifts.The same file is going into the other EVE-family repositories that lack one, and the existing copies in
edge-containers,eve-build-tools,rolandrunxare being repointed in parallel PRs: they link toeve/blob/master/docs/SECURITY.md, which has returned 404 since that file was renamed todocs/SECURITY-ARCHITECTURE.md.