Create SECURITY.md (#7692)
parent
501af06001
commit
975237cbf8
@ -0,0 +1,41 @@ |
|||||||
|
# Security Policy |
||||||
|
|
||||||
|
## Supported Versions |
||||||
|
|
||||||
|
We always provide security updates for the [latest release](https://github.com/minio/minio/releases/latest). |
||||||
|
Whenever there is a security update you just need to upgrade to the latest version. |
||||||
|
|
||||||
|
## Reporting a Vulnerability |
||||||
|
|
||||||
|
All security bugs in [minio/minio](https://github,com/minio/minio) (or other minio/* repositories) |
||||||
|
should be reported by email to security@min.io. Your email will be acknowledged within 48 hours, |
||||||
|
and you'll receive a more detailed response to your email within 72 hours indicating the next steps |
||||||
|
in handling your report. |
||||||
|
|
||||||
|
Please, provide a detailed explanation of the issue. In particular, outline the type of the security |
||||||
|
issue (DoS, authentication bypass, information disclouse, ...) and the assumptions you're making (e.g. do |
||||||
|
you need access credentials for a successful exploit). |
||||||
|
|
||||||
|
If you have not received a reply to your email within 48 hours or you have not heard from the security team |
||||||
|
for the past five days please contact the security team directly: |
||||||
|
- Primary security coordinator: aead@min.io |
||||||
|
- Secondary coordinator: harsha@min.io |
||||||
|
- If you receive no response: dev@min.io |
||||||
|
|
||||||
|
### Disclosure Process |
||||||
|
|
||||||
|
MinIO uses the following disclosure process: |
||||||
|
|
||||||
|
1. Once the security report is received one member of the security team tries to verify and reproduce |
||||||
|
the issue and determines the impact it has. |
||||||
|
2. A member of the security team will respond and either confrim or reject the security report. |
||||||
|
If the report is rejected the repsonse explains why. |
||||||
|
3. Code is audited to find any potential similar problems. |
||||||
|
4. Fixes are prepared for the latest release. |
||||||
|
5. On the date that the fixes are applied a security advisory will be published on https://blog.min.io. |
||||||
|
Please inform us in your report email whether MinIO should mention your contribution w.r.t. fixing |
||||||
|
the security issue. By default MinIO will **not** publish this information to protect your privacy. |
||||||
|
|
||||||
|
This process can take some time, especially when coordination is required with maintainers of other projects. |
||||||
|
Every effort will be made to handle the bug in as timely a manner as possible, however it's important that we |
||||||
|
follow the process described above to ensure that disclosures are handled consistently. |
Loading…
Reference in new issue