summaryrefslogtreecommitdiff
path: root/.github
diff options
context:
space:
mode:
authorMichael Klishin <klishinm@vmware.com>2022-12-14 02:47:37 +0400
committerGitHub <noreply@github.com>2022-12-14 02:47:37 +0400
commit95c2750c5e4ac6b2bfdf36c7234a9275ef7acee3 (patch)
treec11fdc0bc75c0bae5c22d7ba1fffea285442a86a /.github
parenta334ed03a33d494d5fb8a51a1a93f902682bfd54 (diff)
downloadrabbitmq-server-git-95c2750c5e4ac6b2bfdf36c7234a9275ef7acee3.tar.gz
Update SECURITY.md
Diffstat (limited to '.github')
-rw-r--r--.github/SECURITY.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/.github/SECURITY.md b/.github/SECURITY.md
index 121dd38c47..a18925e8cf 100644
--- a/.github/SECURITY.md
+++ b/.github/SECURITY.md
@@ -10,7 +10,7 @@ the observed behavior.
RabbitMQ Core team really appreciates responsible vulnerability reports
from security researchers and our user community.
-To responsibly disclose a vulnerability, please email `security@rabbitmq.com` or
+To responsibly disclose a vulnerability, please use [GitHub Security Advisories](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability) or email `security@rabbitmq.com` or
[sign up for RabbitMQ community Slack](https://rabbitmq-slack.herokuapp.com) and
send a DM to @michaelklishin. For reports received via Slack, a separate private
channel will be set up so that multiple RabbitMQ maintainers can access the disclosed