|
1 | 1 | # Security Policy |
2 | 2 |
|
3 | | -There are many users using LibOSDP in some capacity in production. If you think |
4 | | -you found a bug that may have security implications, please follow the usual |
5 | | -responsible disclosure protocols. Any issue reported in this channel will be |
6 | | -acknowledged withing 3 business days. |
| 3 | +LibOSDP is deployed in production by a wide range of users. We take the |
| 4 | +security of the library and its downstream consumers seriously and welcome |
| 5 | +reports of any issue that may have security implications. |
7 | 6 |
|
8 | | -If an issue has been confirmed by a maintainer, we request the reporter to |
9 | | -respect a 90 day embargo period before making the issue public. |
| 7 | +## Reporting a Vulnerability |
10 | 8 |
|
11 | | -## Supported Versions |
| 9 | +If you believe you have found a vulnerability, please follow responsible |
| 10 | +disclosure practices and email us at security@osdp.dev ([GPG][2]). We will |
| 11 | +acknowledge your report within 3 business days. |
12 | 12 |
|
13 | | -LibOSDP will support the last 2 [releases][1] for security and bug fixes. |
| 13 | +Once a maintainer has confirmed the issue, we ask that reporters honour a |
| 14 | +90-day embargo before disclosing it publicly. This window allows us to notify |
| 15 | +subscribers of the security mailing list and gives downstream consumers time to |
| 16 | +update their systems. |
14 | 17 |
|
15 | | -| Version | Branch | Supported | |
16 | | -| ------- | -------|------------------- | |
17 | | -| <= 1.5 | N/A | :x: | |
18 | | -| 2.4.x | 2.4.x | :white_check_mark: | |
19 | | -| latest | master | :white_check_mark: | |
| 18 | +## Supported Versions |
20 | 19 |
|
21 | | -## Reporting a Vulnerability |
| 20 | +LibOSDP provides security and bug fixes for the latest two [releases][1], in |
| 21 | +addition to the `master` branch. |
22 | 22 |
|
23 | | -Please send an email to sidcha.dev@gmail.com ([GPG][2]). |
| 23 | +| Version | Branch | Supported | |
| 24 | +| ------- | ------------- | ------------------ | |
| 25 | +| <= 2.0 | N/A | :x: | |
| 26 | +| 3.1.x | release_3.1 | :white_check_mark: | |
| 27 | +| 3.2.x | release_3.2 | :white_check_mark: | |
| 28 | +| latest | master | :white_check_mark: | |
24 | 29 |
|
25 | 30 | ## Security Mailing List |
26 | 31 |
|
27 | | -If you are a vendor using LibOSDP in a product (or any production capacity), |
28 | | -please send an email to sidcha.dev@gmail.com to get added to a private mailing |
29 | | -list which will be used to notify about critical incidents such as |
30 | | -vulnerabilities and potential fixes or workarounds before the issue has been made |
31 | | -public. |
| 32 | +If you use LibOSDP in a product or any other production capacity, we encourage |
| 33 | +you to join our private security mailing list. Subscribers are notified of |
| 34 | +critical incidents — such as vulnerabilities and their fixes or workarounds — |
| 35 | +before the details are made public. To request access, email security@osdp.dev. |
| 36 | + |
| 37 | +We recommend subscribing with a dedicated, role-based address such as |
| 38 | +security@your-company.com rather than an individual's mailbox, as this keeps the |
| 39 | +list current as personnel change. |
32 | 40 |
|
33 | | -You can also follow the [security advisories][3] page but this will be updated |
34 | | -only after the issue has been made public. |
| 41 | +Membership is limited to verified production users. Writing to us from a company |
| 42 | +email address is usually sufficient to establish this. |
35 | 43 |
|
36 | | -Note: For very obvious reasons, not everyone can be added to this list. You |
37 | | -should be able to prove that you are indeed using LibOSDP in production. |
| 44 | +You may also monitor the [security advisories][3] page, though it is updated only |
| 45 | +after an issue has been disclosed publicly. |
38 | 46 |
|
39 | 47 | [1]: https://github.com/goToMain/libosdp/releases |
40 | 48 | [2]: https://github.com/sidcha.gpg |
|
0 commit comments