|
1 |
| -# Reporting Security Vulnerabilities |
| 1 | +# Reporting security vulnerabilities |
2 | 2 |
|
3 |
| -Oracle values the independent security research community and believes that responsible disclosure of security vulnerabilities helps us ensure the security and privacy of all our users. |
| 3 | +Oracle values the independent security research community and believes that |
| 4 | +responsible disclosure of security vulnerabilities helps us ensure the security |
| 5 | +and privacy of all our users. |
4 | 6 |
|
5 |
| -Please do NOT raise a GitHub Issue to report a security vulnerability. If you believe you have found a security vulnerability, please submit a report to [[email protected]](mailto:[email protected]) preferably with a proof of concept. We provide additional information on [how to report security vulnerabilities to Oracle ](https://www.oracle.com/corporate/security-practices/assurance/vulnerability/reporting.html) which includes public encryption keys for secure email. |
| 7 | +Please do NOT raise a GitHub Issue to report a security vulnerability. If you |
| 8 | +believe you have found a security vulnerability, please submit a report to |
| 9 | +[[email protected]][1] preferably with a proof of concept. Please review |
| 10 | +some additional information on [how to report security vulnerabilities to Oracle][2]. |
| 11 | +We encourage people who contact Oracle Security to use email encryption using |
| 12 | +[our encryption key][3]. |
6 | 13 |
|
7 |
| -We ask that you do not use other channels or contact project contributors directly. |
| 14 | +We ask that you do not use other channels or contact the project maintainers |
| 15 | +directly. |
8 | 16 |
|
9 |
| -Non-vulnerability related security issues such as great new ideas for security features are welcome on GitHub Issues. |
| 17 | +Non-vulnerability related security issues including ideas for new or improved |
| 18 | +security features are welcome on GitHub Issues. |
10 | 19 |
|
11 |
| -## Security Updates, Alerts and Bulletins |
| 20 | +## Security updates, alerts and bulletins |
12 | 21 |
|
13 |
| -Security updates will be released on a regular cadence. Many of our projects will typically release security fixes in conjunction with the [Oracle Critical Patch Update](https://www.oracle.com/security-alerts/) program. Security updates are released on the Tuesday closest to the 17th day of January, April, July and October. A pre-release announcement will be published on the Thursday preceding each release. Additional information, including past advisories, is available on our [Security Alerts](https://www.oracle.com/security-alerts/) page. |
| 22 | +Security updates will be released on a regular cadence. Many of our projects |
| 23 | +will typically release security fixes in conjunction with the |
| 24 | +[Oracle Critical Patch Update][3] program. Additional |
| 25 | +information, including past advisories, is available on our [security alerts][4] |
| 26 | +page. |
14 | 27 |
|
15 |
| -## Security-Related Information |
| 28 | +## Security-related information |
16 | 29 |
|
17 |
| -We will provide security related information such as a threat model, considerations for secure use, or any known security issues in our documentation. Please note that labs and sample code are intended to demonstrate a concept and may not be sufficiently hardened for production use. |
| 30 | +We will provide security related information such as a threat model, considerations |
| 31 | +for secure use, or any known security issues in our documentation. Please note |
| 32 | +that labs and sample code are intended to demonstrate a concept and may not be |
| 33 | +sufficiently hardened for production use. |
| 34 | + |
| 35 | + |
| 36 | +[2]: https://www.oracle.com/corporate/security-practices/assurance/vulnerability/reporting.html |
| 37 | +[3]: https://www.oracle.com/security-alerts/encryptionkey.html |
| 38 | +[4]: https://www.oracle.com/security-alerts/ |
0 commit comments