vtlim commented on code in PR #13886: URL: https://github.com/apache/druid/pull/13886#discussion_r1128549042
########## docs/operations/security-overview.md: ########## @@ -272,3 +272,19 @@ Cluster to deep storage: Cluster to client: 1. Druid authenticates with the client based on the configured authenticator. 2. Druid only performs actions when an authorizer grants permission. The default configuration is `allowAll authorizer`. + +## Reporting security issues + +The Apache Druid team takes security very seriously. If you have found a potential security issue in Druid, such as a way to bypass the security mechanisms described above, we encourage you to report this problem at [[email protected]](mailto:[email protected]). This is a private mailing list. Please send one plain-text email for each vulnerability you are reporting. + +### Vulnerability handling + +A summary of the vulnerability handling process is: + +* The reporter reports the vulnerability privately to [[email protected]](mailto:[email protected]) +* You will receive a response that we have received the report and will investigate the issue. Review Comment: ```suggestion * The reporter receives a response that the Druid team has received the report and will investigate the issue. ``` ########## docs/operations/security-overview.md: ########## @@ -272,3 +272,19 @@ Cluster to deep storage: Cluster to client: 1. Druid authenticates with the client based on the configured authenticator. 2. Druid only performs actions when an authorizer grants permission. The default configuration is `allowAll authorizer`. + +## Reporting security issues + +The Apache Druid team takes security very seriously. If you have found a potential security issue in Druid, such as a way to bypass the security mechanisms described above, we encourage you to report this problem at [[email protected]](mailto:[email protected]). This is a private mailing list. Please send one plain-text email for each vulnerability you are reporting. + +### Vulnerability handling + +A summary of the vulnerability handling process is: + +* The reporter reports the vulnerability privately to [[email protected]](mailto:[email protected]) +* You will receive a response that we have received the report and will investigate the issue. +* The Druid project security team works privately with the reporter to resolve the vulnerability. +* The Druid project creates a new release of the package the vulnerabilty affects to deliver its fix. Review Comment: ```suggestion * The Druid team delivers the fix by creating a new release of the package that the vulnerability affects. ``` ########## docs/operations/security-overview.md: ########## @@ -272,3 +272,19 @@ Cluster to deep storage: Cluster to client: 1. Druid authenticates with the client based on the configured authenticator. 2. Druid only performs actions when an authorizer grants permission. The default configuration is `allowAll authorizer`. + +## Reporting security issues + +The Apache Druid team takes security very seriously. If you have found a potential security issue in Druid, such as a way to bypass the security mechanisms described above, we encourage you to report this problem at [[email protected]](mailto:[email protected]). This is a private mailing list. Please send one plain-text email for each vulnerability you are reporting. Review Comment: ```suggestion The Apache Druid team takes security very seriously. If you find a potential security issue in Druid, such as a way to bypass the security mechanisms described earlier, please report this problem to [[email protected]](mailto:[email protected]). This is a private mailing list. Please send one plain text email for each vulnerability you are reporting. ``` ########## docs/operations/security-overview.md: ########## @@ -272,3 +272,19 @@ Cluster to deep storage: Cluster to client: 1. Druid authenticates with the client based on the configured authenticator. 2. Druid only performs actions when an authorizer grants permission. The default configuration is `allowAll authorizer`. + +## Reporting security issues + +The Apache Druid team takes security very seriously. If you have found a potential security issue in Druid, such as a way to bypass the security mechanisms described above, we encourage you to report this problem at [[email protected]](mailto:[email protected]). This is a private mailing list. Please send one plain-text email for each vulnerability you are reporting. + +### Vulnerability handling + +A summary of the vulnerability handling process is: + +* The reporter reports the vulnerability privately to [[email protected]](mailto:[email protected]) +* You will receive a response that we have received the report and will investigate the issue. +* The Druid project security team works privately with the reporter to resolve the vulnerability. +* The Druid project creates a new release of the package the vulnerabilty affects to deliver its fix. +* The Druid project publicly announces the vulnerability and describes how to apply the fix. Review Comment: ```suggestion * The Druid team publicly announces the vulnerability and describes how to apply the fix. ``` ########## docs/operations/security-overview.md: ########## @@ -272,3 +272,19 @@ Cluster to deep storage: Cluster to client: 1. Druid authenticates with the client based on the configured authenticator. 2. Druid only performs actions when an authorizer grants permission. The default configuration is `allowAll authorizer`. + +## Reporting security issues + +The Apache Druid team takes security very seriously. If you have found a potential security issue in Druid, such as a way to bypass the security mechanisms described above, we encourage you to report this problem at [[email protected]](mailto:[email protected]). This is a private mailing list. Please send one plain-text email for each vulnerability you are reporting. + +### Vulnerability handling + +A summary of the vulnerability handling process is: Review Comment: ```suggestion The following list summarizes the vulnerability handling process: ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
