From a9ac1d63c5318486e9620f5089075d3c6e99c1c3 Mon Sep 17 00:00:00 2001
From: Prakhar Maurya <109527284+nuke100pr@users.noreply.github.com>
Date: Mon, 25 Mar 2024 20:56:38 +0530
Subject: [PATCH] Updated SECURITY.MD file with relevant details. (#324)

* Update SECURITY.md

* Update SECURITY.md

I have updated the Security.md file by listing all the versions released yet and the latest version that is being worked on is being supported with security patches.

Steps to report a vulnerablity is same as mentioned in the docs.

* Update SECURITY.md

* Update SECURITY.md
---
 SECURITY.md | 22 ++++++++++------------
 1 file changed, 10 insertions(+), 12 deletions(-)

diff --git a/SECURITY.md b/SECURITY.md
index 034e8480..492488ac 100644
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -2,20 +2,18 @@
 
 ## Supported Versions
 
-Use this section to tell people about which versions of your project are
-currently being supported with security updates.
+Only the lastest version are supported with updates.
+
+| Version    | Supported          |
+| ---------- | ------------------ |
+| 20220608.2 | :white_check_mark: |
+
 
-| Version | Supported          |
-| ------- | ------------------ |
-| 5.1.x   | :white_check_mark: |
-| 5.0.x   | :x:                |
-| 4.0.x   | :white_check_mark: |
-| < 4.0   | :x:                |
 
 ## Reporting a Vulnerability
 
-Use this section to tell people how to report a vulnerability.
+Please report successful attacks with example input via OWASP's bugcrowd queue or contact mikesamuel@gmail.com and I will create a repository security advisory to coordinate.
+
+If you wish to be credited, please provide a name or handle for me to credit.
 
-Tell them where to go, how often they can expect to get an update on a
-reported vulnerability, what to expect if the vulnerability is accepted or
-declined, etc.
+If you wish to remain anonymous, please create a sock account, and email the address above.