Skip to content
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

chore: security markdown #662

Merged
merged 8 commits into from
Mar 20, 2024
Merged

chore: security markdown #662

merged 8 commits into from
Mar 20, 2024

Conversation

cmwylie19
Copy link
Collaborator

Description

  • Creates a preferred method of contact by security researchers in the event of a security vulnerability instead of posting it publicly which could lead to disclosure of vulnerability details.
  • Provides description of where and how to report
  • When a vulnerability is reported, we can accept it, ask more questions, or reject it. If accepted, we are ready to collaborate on a fix.
  • Vulnerability is less likely to be in the public eye
  • Updates the docs

Related Issue

Fixes #639

Relates to #

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Other (security config, docs update, etc)

Checklist before merging

Signed-off-by: Case Wylie <cmwylie19@defenseunicorns.com>
Signed-off-by: Case Wylie <cmwylie19@defenseunicorns.com>
SECURITY.md Outdated Show resolved Hide resolved
Signed-off-by: Case Wylie <cmwylie19@defenseunicorns.com>
@cmwylie19 cmwylie19 merged commit 9e67c18 into main Mar 20, 2024
11 checks passed
@cmwylie19 cmwylie19 deleted the 639 branch March 20, 2024 20:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

(SPIKE) Fix code scanning alert - Security-Policy
3 participants