-
Notifications
You must be signed in to change notification settings - Fork 59
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Create SECURITY.md * Update supported versions section
- Loading branch information
1 parent
dce1913
commit c2923b4
Showing
1 changed file
with
24 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,24 @@ | ||
# Security Policy | ||
|
||
## Supported Versions | ||
|
||
pg_stat_monitor project follows rolling release strategy. So all security updates go to new versions. | ||
|
||
## Reporting a Vulnerability | ||
|
||
Please report any vulnerabilities to our project in [Jira](https://perconadev.atlassian.net/jira/software/c/projects/PG/issues). | ||
|
||
If the vulnerability is accepted and confirmed by our experts, you should normally expect us to deliver | ||
a version with a fix according to the timelines provided below: | ||
|
||
For Percona created software (our engineers wrote the code): | ||
|
||
- Low/Medium: 120 days | ||
- High: 90 days | ||
- Critical: ASAP but should not exceed 30 days | ||
|
||
For Non-Percona created software (upstream provided/packaged) from the time the vendor releases a patch: | ||
|
||
- Low/Medium: 2nd release from current version | ||
- High: Next release | ||
- Critical: Hotfix or no later than next release (our regular release cadence is once every month) |