|
| 1 | +--- |
| 2 | +layout: default |
| 3 | +title: Security Policy |
| 4 | +--- |
| 5 | + |
| 6 | +<!-- IMPORTANT: This content is also maintained in https://github.com/resteasy/.github/blob/main/SECURITY.md - keep both files in sync! --> |
| 7 | + |
| 8 | +# Security Policy |
| 9 | + |
| 10 | +## The RESTEasy community and our sponsor, Commonhaus Foundation, take security bugs very seriously |
| 11 | + |
| 12 | +We aim to take immediate action to address serious security-related problems that involve our projects. |
| 13 | + |
| 14 | +## Reporting Security Issues |
| 15 | + |
| 16 | +When reporting a security vulnerability it is important to not accidentally broadcast to the world that the issue exists, |
| 17 | +as this makes it easier for people to exploit it. The software industry uses the term [embargo](https://www.redhat.com/en/blog/security-embargoes-red-hat) |
| 18 | +to describe the time a security issue is known internally until it is public knowledge. |
| 19 | + |
| 20 | +Our preferred way of reporting security issues in RESTEasy and its related projects is listed below. |
| 21 | + |
| 22 | +### Email the mailing list |
| 23 | + |
| 24 | +The list at [resteasy-security@redhat.com](mailto:resteasy-security@redhat.com) is the preferred mechanism for outside |
| 25 | +users to report security issues. A member of the RESTEasy team will open the required issues. |
| 26 | + |
| 27 | +### Other considerations |
| 28 | + |
| 29 | +If you would like to work with us on a fix for the security vulnerability, please include your GitHub username in the |
| 30 | +above email, and we will provide you access to a temporary private fork where we can collaborate on a fix without it |
| 31 | +being disclosed publicly, **including in your own publicly visible git repository**. |
| 32 | + |
| 33 | +Do not open a public issue, send a pull request, or disclose any information about the suspected vulnerability publicly, |
| 34 | +**including in your own publicly visible git repository**. If you discover any publicly disclosed security |
| 35 | +vulnerabilities, please notify us immediately through [resteasy-security@redhat.com](mailto:resteasy-security@redhat.com). |
0 commit comments