|
| 1 | +## Security Policy |
| 2 | + |
| 3 | +### Supported Versions |
| 4 | + |
| 5 | +The following versions of the project are currently being supported with |
| 6 | +security updates: |
| 7 | + |
| 8 | +| Version | Supported | |
| 9 | +| ------- | ------------------ | |
| 10 | +| 4.0.x | :white_check_mark: | |
| 11 | +| < 4.0 | :x: | |
| 12 | + |
| 13 | +### Reporting a Vulnerability |
| 14 | + |
| 15 | +If you find a security vulnerability in the project, please report it to the |
| 16 | +security team. |
| 17 | + |
| 18 | +When reporting a vulnerability, please include the following information: |
| 19 | + |
| 20 | +- A description of the vulnerability. |
| 21 | +- Steps to reproduce the vulnerability. |
| 22 | +- Any other relevant information. |
| 23 | + |
| 24 | +The security team will investigate the vulnerability and take appropriate |
| 25 | +action. You will be notified of the outcome of the investigation. |
| 26 | + |
| 27 | +### Expected Response Times |
| 28 | + |
| 29 | +When you report a vulnerability, the security team will respond within 72 hours. |
| 30 | +In case the vulnerability is critical, they will respond within 1 hour. |
| 31 | + |
| 32 | +### Expected Outcomes |
| 33 | + |
| 34 | +The security team will take appropriate action to mitigate any reported |
| 35 | +vulnerabilities. Such things may include: |
| 36 | + |
| 37 | +- Patching the vulnerability. |
| 38 | +- Releasing a new version of the project. |
| 39 | +- Disclosing the vulnerability to the public. |
| 40 | + |
| 41 | +### Acknowledgment |
| 42 | + |
| 43 | +The security team appreciates your help in keeping the project secure. If you |
| 44 | +have any questions, please contact the security team. |
| 45 | + |
| 46 | +## Organization-wide Security Policy |
| 47 | + |
| 48 | +For more information on the organization-wide security policy, please see the |
| 49 | +following document: |
| 50 | + |
| 51 | +- https://github.com/OpenINF/.github/blob/HEAD/SECURITY.md |
0 commit comments