Skip to content

Commit 6a0a666

Browse files
Merge pull request #45 from oracle/docs-updates
Update SECURITY.md
2 parents 47e8cf6 + 7ddc178 commit 6a0a666

File tree

1 file changed

+19
-15
lines changed

1 file changed

+19
-15
lines changed

SECURITY.md

Lines changed: 19 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,32 +1,36 @@
1-
# Reporting Security Vulnerabilities
1+
# Reporting security vulnerabilities
22

3-
Oracle values the independent security research community, and believes that
4-
responsible disclosure of security vulnerabilities helps us to ensure the security
5-
and privacy of all of 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.
66

77
Please do NOT raise a GitHub Issue to report a security vulnerability. If you
8-
believe you have found a security vulnerability, then please submit a report to
8+
believe you have found a security vulnerability, please submit a report to
99
[secalert_us@oracle.com][1] preferably with a proof of concept. Please review
1010
some additional information on [how to report security vulnerabilities to Oracle][2].
11-
Oracle encourages anyone who contacts Oracle Security to use email encryption, using
11+
We encourage people who contact Oracle Security to use email encryption using
1212
[our encryption key][3].
1313

14-
Please do not use other channels, or contact the project maintainers
14+
We ask that you do not use other channels or contact the project maintainers
1515
directly.
1616

17-
For non-vulnerability related security issues, including ideas for new or improved
18-
security features, you are welcome to post these as GitHub Issues.
17+
Non-vulnerability related security issues including ideas for new or improved
18+
security features are welcome on GitHub Issues.
1919

20-
## Security Updates, Alerts and Bulletins
20+
## Security updates, alerts and bulletins
2121

22-
Oracle issues security updates on a regular cadence. Many of our projects typically include release security fixes in conjunction with the [Oracle Critical Patch Update][3] program. Security updates are released on the
23-
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][4]
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]
2426
page.
2527

26-
## Security-Related Information
28+
## Security-related information
2729

28-
Oracle will provide security-related information in our documentation. The information can be a threat model, best practices for secure use, or any known security issues. Please note
29-
that labs and example code are intended to demonstrate a concept. These examples should not be used for production use without ensuring that the code is hardened, and in compliance with common security practices.
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.
3034

3135
[1]: mailto:secalert_us@oracle.com
3236
[2]: https://www.oracle.com/corporate/security-practices/assurance/vulnerability/reporting.html

0 commit comments

Comments
 (0)