Conversation
Documents supported versions, private reporting through GitHub security advisories, the repository-specific vulnerability scope and response targets. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This branch has not been deployed
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.
BLUF
sigma-clihas no security policy, and private vulnerability reporting is disabled, so there is currently no private channel for reporting vulnerabilities.SECURITY.mdcovering supported versions, how to report privately via GitHub advisories, what counts as a vulnerability for this repository, and response targets.Priority: medium
Details
Scope. The scope is tailored to this repository: a CLI that reads third-party rules and writes files (file-system safety, code execution, output injection, plugin supply chain, DoS).
Timelines. 5 days to acknowledge, 14 days to assess, 90-day coordinated disclosure, and a GHSA/CVE through GitHub. These are common defaults; adjust as you see fit.
Consistency. Part of one initiative: the same policy skeleton is proposed for every SigmaHQ code repository, starting with SigmaHQ/pySigma#564.
SigmaHQ/.githubrepository with a defaultSECURITY.mdwould also give every repository a policy; these per-repository files can then be dropped or kept for their repository-specific scope.Testing
Documentation only; no code or test changes.
🤖 Generated with Claude Code