blob: e823e227aac31342c0ae02de6002b8232c84ee5a (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
|
<!--
title: "Security Policy"
description: "The Netdata team maintains and adheres to a formal process any time a member of the community reports a security vulnerability."
custom_edit_url: https://github.com/netdata/netdata/edit/master/SECURITY.md
-->
# Security Policy
## Supported Versions
| Version | Supported |
|------- | --------- |
| Latest | Yes |
## Reporting a Vulnerability
We're extremely grateful for security researchers and users that report vulnerabilities to Netdata Open Source Community. All reports are thoroughly investigated by a set of community volunteers.
To make a report, please send an email to **security@netdata.cloud** with
the vulnerability details and the details expected for [all Netdata bug
reports](https://github.com/netdata/netdata/blob/c1f4c6cf503995cd4d896c5821b00d55afcbde87/.github/ISSUE_TEMPLATE/bug_report.md).
### When Should I Report a Vulnerability?
- You think you discovered a potential security vulnerability in Netdata
- You are unsure how a vulnerability affects Netdata
- You think you discovered a vulnerability in another project that Netdata depends on (e.g. python, node, etc)
### When Should I NOT Report a Vulnerability?
- You need help tuning Netdata for security
- You need help applying security related updates
- Your issue is not security related
### Security Vulnerability Response
Each report is acknowledged and analyzed by Netdata Team members within 3 working days. This will set off a Security Release Process.
Any vulnerability information shared with the Netdata Team stays within the Netdata project and will not be disseminated to other projects unless it is necessary to get the issue fixed.
As the security issue moves from triage, to identified fix, to release planning we will keep the reporter updated.
### Public Disclosure Timing
A public disclosure date is negotiated by the Netdata team and the bug submitter. We prefer to fully disclose the bug as soon as possible once a user mitigation is available. It is reasonable to delay disclosure when the bug or the fix is not yet fully understood, the solution is not well-tested, or for vendor coordination. The timeframe for disclosure is from immediate (especially if it's already publicly known) to a few weeks. As a basic default, we expect report date to disclosure date to be on the order of 7 days. The Netdata team holds the final say when setting a disclosure date.
### Security Announcements
Every time a security issue is fixed in Netdata, we immediately release a new version of it. So, to get notified of all security incidents, please subscribe to our releases on github.
[](<>)
|
