Skip to content

Create SECURITY.md #148

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Create SECURITY.md #148

wants to merge 2 commits into from

Conversation

ramantehlan
Copy link
Collaborator

@ramantehlan ramantehlan commented Jul 16, 2025

Add a security policy to report vulnerabilities.

Summary by CodeRabbit

  • Documentation
    • Added a security policy outlining supported versions, scope of security reporting, responsible disclosure process, and recognition for vulnerability reporters.

Copy link
Contributor

coderabbitai bot commented Jul 16, 2025

Walkthrough

A new SECURITY.md file has been added, establishing the security policy for the KubeElasti project. The document details supported versions, in-scope components, reporting procedures, disclosure policy, and recognition for security reporters, while clarifying exclusions and the absence of a monetary bounty.

Changes

File(s) Change Summary
SECURITY.md Added security policy outlining supported versions, scope, reporting procedures, disclosure policy, and contributor recognition for vulnerabilities in KubeElasti.

Estimated code review effort

1 (<30 minutes)

Poem

A brand new shield for KubeElasti’s code,
With policies clear and a thank-you bestowed.
If bugs you may find, report with great care—
No bounties in gold, but recognition to share!
🐇🔒


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 658ed28 and 953a399.

📒 Files selected for processing (1)
  • SECURITY.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
SECURITY.md

[style] ~54-~54: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ease notes once a patch is available. * We credit reporters **unless anonymity is ...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

🪛 markdownlint-cli2 (0.17.2)
SECURITY.md

14-14: Trailing spaces
Expected: 0 or 2; Actual: 1

(MD009, no-trailing-spaces)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)
  • GitHub Check: test (/home/runner/work/KubeElasti/KubeElasti/pkg)
  • GitHub Check: golangci-lint (/home/runner/work/KubeElasti/KubeElasti/operator)
  • GitHub Check: test (/home/runner/work/KubeElasti/KubeElasti/resolver)
  • GitHub Check: test (/home/runner/work/KubeElasti/KubeElasti/operator)
  • GitHub Check: Run Kuttl E2E Tests
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch ramantehlan-patch-2

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 4

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 455680b and 658ed28.

📒 Files selected for processing (1)
  • SECURITY.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
SECURITY.md

[grammar] ~1-~1: Use correct spacing
Context: # Security Policy KubeElasti values the contributions of i...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~3-~3: Use correct spacing
Context: ...intainers committed to safeguarding the project. --- ## 🛡️ Supported Versions | Version | Supp...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~7-~7: Use correct spacing
Context: ...ing the project. --- ## 🛡️ Supported Versions | Version | Supported | Notes ...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~12-~12: Use correct spacing
Context: ... ❌ | End‑of‑life | > We generally provide security fixes for ...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~14-~14: Use correct spacing
Context: ...rity fixes for the latest minor release lines. --- ## 🔐 Scope The following components are *...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~18-~18: Use correct spacing
Context: ...atest minor release lines. --- ## 🔐 Scope The following components are *in‑scope...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~24-~24: There might be a mistake here.
Context: ...s manifests distributed in the official repository * All container images published under `gh...

(QB_NEW_EN_OTHER)


[grammar] ~25-~25: Use correct spacing
Context: ...sitory * All container images published under ghcr.io/truefoundry/elasti* Out‑of‑scope issues include but are not ...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~35-~35: Use correct spacing
Context: ...security impact --- ## 📬 Reporting a Vulnerability 1. Email a detailed report to our private...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~38-~38: Use correct spacing
Context: ...(mailto:[email protected])**. 2. Include: * A descriptive title (e.g., *"Denial‑of‑S...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~46-~46: Use correct spacing
Context: ...open a public GitHub issue for security problems. --- ## 🔄 Disclosure Policy * We follow **coor...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~50-~50: Use correct spacing
Context: ...curity problems. --- ## 🔄 Disclosure Policy * We follow coordinated disclosure. * ...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[style] ~54-~54: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ease notes once a patch is available. * We credit reporters **unless anonymity is ...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[grammar] ~57-~57: Use correct spacing
Context: ...re happy to provide swag and public recognition. --- ## 🙏 Thank You Your efforts make the Kube...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~61-~61: Use correct spacing
Context: ...d public recognition. --- ## 🙏 Thank You Your efforts make the KubeElasti ecosyst...

(QB_NEW_EN_OTHER_ERROR_IDS_5)

🪛 markdownlint-cli2 (0.17.2)
SECURITY.md

14-14: Trailing spaces
Expected: 0 or 2; Actual: 1

(MD009, no-trailing-spaces)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)
  • GitHub Check: test (/home/runner/work/KubeElasti/KubeElasti/pkg)
  • GitHub Check: golangci-lint (/home/runner/work/KubeElasti/KubeElasti/operator)
  • GitHub Check: test (/home/runner/work/KubeElasti/KubeElasti/resolver)
  • GitHub Check: test (/home/runner/work/KubeElasti/KubeElasti/operator)
  • GitHub Check: Run Kuttl E2E Tests

SECURITY.md Outdated
Comment on lines 37 to 46
1. **Email** a detailed report to our private list: **[[email protected]](mailto:[email protected])**.
2. Include:

* A descriptive title (e.g., *"Denial‑of‑Service via oversized HTTP header"*).
* Affected versions and environment details.
* Reproduction steps or proof‑of‑concept (PoC) code.
* Expected vs. actual behavior.
* Impact assessment (confidentiality, integrity, availability).
* *Optional* patch or mitigation ideas.
3. *Do NOT* open a public GitHub issue for security problems.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Offer an encrypted channel for sensitive reports

Industry norm is to publish a PGP key or at least accept encrypted mail (per CVE.org guidelines). Attackers may intercept unencrypted disclosures. Add a “PGP key” subsection with fingerprint & download link.

🧰 Tools
🪛 LanguageTool

[grammar] ~38-~38: Use correct spacing
Context: ...(mailto:[email protected])**. 2. Include: * A descriptive title (e.g., *"Denial‑of‑S...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~46-~46: Use correct spacing
Context: ...open a public GitHub issue for security problems. --- ## 🔄 Disclosure Policy * We follow **coor...

(QB_NEW_EN_OTHER_ERROR_IDS_5)

🤖 Prompt for AI Agents
In SECURITY.md around lines 37 to 46, the security reporting instructions
currently only mention sending unencrypted email. To improve security, add a new
subsection titled "PGP key" that provides a PGP key fingerprint and a download
link for the public key. This will enable reporters to send encrypted
vulnerability reports, protecting sensitive information from interception.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant