Update SECURITY.md

Author: DaneEveritt

SECURITY.md

@@ -2,18 +2,23 @@
 
 ## Supported Versions
 
-The following versions of Pterodactyl are receiving active support and maintenance. Any security vulnerabilities discovered must be reproducible in supported versions.
-
-| Panel  | Daemon       | Supported          |
-|--------|--------------|--------------------|
-| 1.11.x | wings@1.11.x | :white_check_mark: |
-| 0.7.x  | daemon@0.6.x | :x:                |
+Pterodactyl only provides security support for the latest `major.minor` versions of the Panel and Wings software.
+If a security vulnerability is found in an older version but cannot be reproduced on a supported version it will
+not be considered. Additionally, security issues found in unreleased code will be addressed, but do not warrant a
+security advisory.
 
+For example, if the latest version of the Panel is `1.2.5` then we only support security reports for issues that
+occur on `>= 1.2.x` versions of the Panel software. The Panel and Wings have their own versions, but they generally
+follow eachother.
 
 ## Reporting a Vulnerability
 
-Please reach out directly to any project team member on Discord when reporting a security vulnerability, or you can email `security@pterodactyl.io`.
+Please use our GitHub Security reporting meachnism to quickly alert the team to any security issues you come across,
+or send an email to `security@pterodactyl.io` with the details of your report.
 
-We make every effort to respond as soon as possible, although it may take a day or two for us to sync internally and determine the severity of the report and its impact. Please, _do not_ use a public facing channel or GitHub issues to report sensitive security issues.
+We make every effort to respond as soon as possible, although it may take a day or two for us to sync internally and
+determine the severity of the report and its impact. Please, _do not_ use a public facing channel or GitHub issues to
+report sensitive security issues.
 
-As part of our process, we will create a security advisory for the affected versions and disclose it publicly, usually two to four weeks after a releasing a version that addresses it.
+As part of our process, we will create a security advisory for the affected versions and disclose it publicly, usually
+two to four weeks after a releasing a version that addresses it.