@@ -44,7 +44,7 @@ Logstash user base and our own goals for the project. Through this process, we t
4444## Found a Security Issue?
4545
4646If you've found a security issue, before submitting anything via a PR, please
47- get in touch with our security team [ here] ( https://www.elastic.co/community/ security ) .
47+ get in touch with our security team [ here] ( https://www.elastic.co/product- security ) .
4848
4949# Contributing Documentation and Code Changes
5050
@@ -163,7 +163,7 @@ Labels (optional):
163163- ** ` [DOC] ` ** for a change that affects only documentation, and not code.
164164- ** ` [SECURITY] ` ** for a security fix. If you're working on a security issue,
165165please make sure to follow the process outlined by our security team.
166- If you haven't done so already, please [ get in touch with them] ( https://www.elastic.co/community/ security ) first.
166+ If you haven't done so already, please [ get in touch with them] ( https://www.elastic.co/product- security ) first.
167167
168168Keywords (copied from [ keepachangelog.com] ( https://keepachangelog.com/en/1.0.0/#how ) ):
169169
@@ -176,7 +176,7 @@ Keywords (copied from [keepachangelog.com](https://keepachangelog.com/en/1.0.0/#
176176 - ** Important reminder** : If you're working on a security issue, please make sure
177177 you're following the process outlined by our security team. If you haven't
178178 done so already, please get in touch with them
179- [ here] ( https://www.elastic.co/community/ security ) first.
179+ [ here] ( https://www.elastic.co/product- security ) first.
180180
181181Example:
182182
0 commit comments