Initial commit adding Security TAG policies - #1
Conversation
Signed-off-by: Craig Perkins <cwperx@amazon.com>
Signed-off-by: Craig Perkins <cwperx@amazon.com>
Signed-off-by: Craig Perkins <cwperx@amazon.com>
Signed-off-by: Craig Perkins <cwperx@amazon.com>
Signed-off-by: Craig Perkins <cwperx@amazon.com>
Signed-off-by: Craig Perkins <cwperx@amazon.com>
|
@DarshitChanpura @cliu123 @nishthm to review |
| name: Vulnerability Report | ||
| description: Report a security vulnerability in an OpenSearch project. For private reports, use the Security tab instead. | ||
| title: "[VULN] " | ||
| labels: ["vulnerability", "triage"] |
There was a problem hiding this comment.
are we limiting to these labels for now?
| attributes: | ||
| label: Affected Versions | ||
| description: Which versions are affected? | ||
| placeholder: "e.g., 2.10.0–2.12.0" |
There was a problem hiding this comment.
let's promote usage of <, ≤, =, >, ≥ instead of hyphen.
| @@ -0,0 +1,2 @@ | |||
| # Default: Security TAG members review all changes | |||
| * @cwperks @nibix @aparajita31pandey @kumargu @kkhatua @willyborankin @shikharj05 @jochen-kressin | |||
There was a problem hiding this comment.
i believe this list needs an update.
| @@ -0,0 +1,13 @@ | |||
| # Vulnerability Announcement — Slack | |||
|
|
|||
| _Post this to the `#security` channel on [OpenSearch Slack](https://opensearch.org/slack.html)._ | |||
There was a problem hiding this comment.
can link be updated to point to the channel directly?
https://opensearch.slack.com/archives/C051Y637FKK
|
|
||
| | Phase | Target Timeline | | ||
| | --- | --- | | ||
| | Advisory sent to pre-disclosure list | Within 2 weeks of confirmed report | |
There was a problem hiding this comment.
are we committing to this timeline strictly?
| ## Working in the Private Fork | ||
|
|
||
| 1. **Clone the private fork** using the URL provided in the Draft GHSA. | ||
| 2. **Create a feature branch** from the target release branch (e.g., `main` or a version branch). |
There was a problem hiding this comment.
requires admin perms for this.
| | --- | --- | --- | | ||
| | Kunal Khatua | [@kkhatua](https://github.com/kkhatua) | Amazon | | ||
| | Craig Perkins | [@cwperks](https://github.com/cwperks) | Amazon | | ||
| | Nils Bandener | [@nibix](https://github.com/nibix) | Eliatra | |
There was a problem hiding this comment.
this list should be updated to add new members
| | --- | --- | --- | | ||
| | Kunal Khatua | [@kkhatua](https://github.com/kkhatua) | Amazon | | ||
| | Craig Perkins | [@cwperks](https://github.com/cwperks) | Amazon | | ||
| | Nils Bandener | [@nibix](https://github.com/nibix) | Eliatra | |
There was a problem hiding this comment.
this list also needs an update
| ## How the SRT and TAG Work Together | ||
|
|
||
| ``` | ||
| ┌──────────────────────────────────────────────────────────┐ |
There was a problem hiding this comment.
can we do mermaid style instead?
|
|
||
| ## Summary Flowchart | ||
|
|
||
| ``` |
There was a problem hiding this comment.
mermaid style here as well please
Description
This repo seeks to collect policies pertaining to Security as advised by the Security TAG for the OpenSearch project.
Security is a fast moving landscape, especially with AI Bounty Hunters, and this repo will aim to stay up to date to communicate security practices for the project. While this initial seed focuses on the security response process, we can also use this repo to document security coding practices specific to the OpenSearch project.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.