Document how to report security issues (#13886)

Document how to report security issues on the security overview page, so we can link this page from the homepage. That should make all the other important security information easier to find as well.
This commit is contained in:
Arnout Engelen 2023-03-27 07:56:37 +02:00 committed by GitHub
parent 13ffeb50ba
commit daff7fe73b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 21 additions and 1 deletions

View File

@ -1,7 +1,7 @@
---
id: security-overview
title: "Security overview"
description: Overiew of Apache Druid security. Includes best practices, configuration instructions, and a description of the security model.
description: Overiew of Apache Druid security. Includes best practices, configuration instructions, a description of the security model and documentation on how to report security issues.
---
<!--
@ -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 find a potential security issue in Druid, such as a way to bypass the security mechanisms described earlier, please report this problem to [security@apache.org](mailto:security@apache.org). This is a private mailing list. Please send one plain text email for each vulnerability you are reporting.
### Vulnerability handling
The following list summarizes the vulnerability handling process:
* The reporter reports the vulnerability privately to [security@apache.org](mailto:security@apache.org)
* The reporter receives a response that the Druid team has received the report and will investigate the issue.
* The Druid project security team works privately with the reporter to resolve the vulnerability.
* The Druid team delivers the fix by creating a new release of the package that the vulnerability affects.
* The Druid team publicly announces the vulnerability and describes how to apply the fix.
Committers should read a [more detailed description of the process](https://www.apache.org/security/committers.html). Reporters of security vulnerabilities may also find it useful.

View File

@ -25,6 +25,7 @@
ACL
ACLs
APIs
apache.org
AvroStorage
ARN
autokill

View File

@ -48,6 +48,9 @@ entries.forEach((entry) => {
// Ignore external doc links
if (url.startsWith('/') && !url.startsWith('/docs/')) return;
// Ignore mailto links
if (url.startsWith('mailto:')) return;
// This one will get created externally
if (url === '/docs/latest') return;