Reduce SECURITY.md to a pointer to the security documentation (#13732)

SECURITY.md

@@ -2,20 +2,9 @@
 
 ## Supported Versions
 
-- We usually release 3/4 new versions (e.g. 1.1.0, 1.2.0, 1.3.0) per year.
-- Release Candidates are available before the release (e.g. 1.1.0-rc1, 1.1.0-rc2, 1.1.0-rc3, 1.1.0-rc4, before 1.1.0).
-- Bug-fixes (e.g. 1.1.1, 1.1.2, 1.2.1, 1.2.3) are released as needed (no additional features are delivered in those versions, bug-fixes only).
-
-Each version is supported until the next one is released (e.g. 1.1.x will be supported until 1.2.0 is out).
-
-We use [Semantic Versioning](https://semver.org/).
-
-| Version   | Supported          |
-|-----------|--------------------|
-| `3.6.x`   | :white_check_mark: |
-| `< 3.6.x` | :x:                |
-| `2.11.x`   | :white_check_mark: |
-| `< 2.11.x` | :x:                |
+The list of supported versions, with their active support and security support
+end dates, is maintained on the
+[Releases](https://doc.traefik.io/traefik/deprecation/releases/) page.
 
 ## Reporting a Vulnerability
 
@@ -24,4 +13,7 @@ If you've discovered a security vulnerability in Traefik,
 we appreciate your help in disclosing it to us in a responsible manner,
 by creating a [security advisory](https://github.com/traefik/traefik/security/advisories).
 
-Reported vulnerabilities can be found on [cve.mitre.org](https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=traefik).
+Before submitting, please read our
+[security documentation](https://doc.traefik.io/traefik/contributing/submitting-security-issues/):
+it covers security advisories, our CVE policy, the code of conduct for
+vulnerability submissions, and our submission quality guidelines.