Updated security policy report methods

diff --git a/SECURITY.md b/SECURITY.md
index 8e173ed165abfcfb7ad61afc8d00569cf35af7b3..28f6167fe8547041eec30aba09c8a558d29938e5 100644 (file)
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -6,18 +6,8 @@ implications of configurations and misconfigurations.
 
 ## Reporting a Vulnerability
 
-Please report any vulnerabilities via one of the following methods
-(in order of preference):
-
-1. [Report a vulnerability](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability)
-within this repository. We are using the GitHub workflow that allows us to
-manage vulnerabilities in a private manner and interact with reporters
-securely.
-
-2. [Report directly to F5](https://www.f5.com/services/support/report-a-vulnerability).
-
-3. Report via email to security-alert@nginx.org.
-This method will be deprecated in the future.
+Please report any vulnerabilities
+[directly to F5](https://www.f5.com/services/support/report-a-vulnerability).
 
 ### Vulnerability Disclosure and Fix Process