-
Notifications
You must be signed in to change notification settings - Fork 378
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Document vulnerability reporting process
Signed-off-by: Jussi Nummelin <[email protected]>
- Loading branch information
Showing
1 changed file
with
22 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
# Security Policy | ||
|
||
## Supported Versions | ||
|
||
Following versions are supported and maintained: | ||
|
||
| Version | Supported | | ||
|-----------|--------------------| | ||
| v1.31.x | :white_check_mark: | | ||
| v1.30.x | :white_check_mark: | | ||
| v1.29.x | :white_check_mark: | | ||
| < v1.29.x | :x: | | ||
|
||
## Reporting a Vulnerability | ||
|
||
k0s supports responsible disclosure and endeavors to resolve security issues in a reasonable timeframe. | ||
|
||
To report a security vulnerability, you can use Github [private security reporting] feature under the [Security tab]. | ||
That allows the reporter and maintainers to coordinate the disclosure and the fix before public disclosure. | ||
|
||
[Security tab]: https://github.com/k0sproject/k0s/security | ||
[private security reporting]: https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability |