Skip to content

docs(security): add SECURITY.md security policy#856

Open
subodhstha wants to merge 2 commits into
FairwindsOps:masterfrom
subodhstha:docs/security-policy
Open

docs(security): add SECURITY.md security policy#856
subodhstha wants to merge 2 commits into
FairwindsOps:masterfrom
subodhstha:docs/security-policy

Conversation

@subodhstha

Copy link
Copy Markdown

This PR introduces a SECURITY.md file detailing supported versions, reporting guidelines, response SLAs, and scope, aligned with open-source security best practices.

Add SECURITY.md outlining supported versions, reporting procedures, SLA response times, and scope for vulnerability reports.
Copilot AI review requested due to automatic review settings May 21, 2026 18:05
@CLAassistant

CLAassistant commented May 21, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds a repository security policy to clarify supported versions, vulnerability reporting, scope, and operator guidance for Goldilocks.

Changes:

  • Introduces SECURITY.md with supported versions and security-reporting instructions
  • Defines in-scope / out-of-scope security surfaces and expected response SLAs
  • Documents operator best practices (RBAC, network policies, signature verification)

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread SECURITY.md
Comment thread SECURITY.md
Comment thread SECURITY.md Outdated
Comment thread SECURITY.md
Comment thread SECURITY.md
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
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.

3 participants