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

(SPIKE) Fix code scanning alert - Security-Policy #639

Closed
1 task
cmwylie19 opened this issue Mar 11, 2024 · 1 comment · Fixed by #662
Closed
1 task

(SPIKE) Fix code scanning alert - Security-Policy #639

cmwylie19 opened this issue Mar 11, 2024 · 1 comment · Fixed by #662
Assignees

Comments

@cmwylie19
Copy link
Collaborator

Add a Security.md

Tracking issue for:

@cmwylie19 cmwylie19 self-assigned this Mar 18, 2024
@cmwylie19
Copy link
Collaborator Author

  • 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.
  • They are able to report to us via a simple form
  • When a vulnerability is reported, we can accept it, ask more questions, or reject it. If accepted, you are ready to collaborate on a fix.
  • Vulnerability is less likely to be in the public eye

@cmwylie19 cmwylie19 mentioned this issue Mar 18, 2024
10 tasks
cmwylie19 added a commit that referenced this issue Mar 20, 2024
## Description

- [x] 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.
- [x] Provides description of where and how to report
- [x] 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.
- [x] Vulnerability is less likely to be in the public eye
- [x] Updates the docs 

## Related Issue

Fixes #639 
<!-- or -->
Relates to #

## Type of change

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

## Checklist before merging

- [x] Test, docs, adr added or updated as needed
- [x] [Contributor Guide
Steps](https://github.com/defenseunicorns/pepr/blob/main/CONTRIBUTING.md#submitting-a-pull-request)
followed

---------

Signed-off-by: Case Wylie <cmwylie19@defenseunicorns.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant