Update SECURITY.md

Author: 0x5t4l1n

SECURITY.md

@@ -1,55 +1,29 @@
-# **Security Policy**
+## Security Policy
 
-## Supported Versions
+### Reporting Vulnerabilities
 
-The following versions of this project are currently receiving security updates:
+If you discover any security vulnerabilities, please report them responsibly.
 
+Send detailed vulnerability reports to:
 
-> **Note:** We strongly recommend upgrading to a supported version to receive the latest security patches.
+Email: w4nn4d133@gmail.com
 
----
+OpenPGP Fingerprint:
+`DEBE5591C54E947279C14A6BF53D272DA9ADAF98`
 
-## Reporting a Vulnerability
+Public Key:
+https://keys.openpgp.org/vks/v1/by-fingerprint/DEBE5591C54E947279C14A6BF53D272DA9ADAF98
 
-If you discover a security vulnerability in this project, please follow the responsible disclosure process below.
+Alternatively, you may submit your report through our official advisory channel (if available).
 
-### How to Report
+### Guidelines for Reporting
 
-Send a detailed report to: **w4nn4d133@gmail.com**
-
-Please include the following information in your report:
+Please include:
 
 - A clear description of the vulnerability
 - Steps to reproduce the issue
-- Affected version(s)
-- Potential impact of the vulnerability
-
----
-
-## What to Expect
-
-| Stage                         | Timeline            |
-| ----------------------------- | ------------------- |
-| Acknowledgement of report     | Within 48 hours     |
-| Severity assessment (CVSS v3) | Within 5 business days |
-| Status update                 | Every 7 days        |
-| Patch release (if accepted)   | Depends on severity |
-
-### If Your Vulnerability Is Accepted
-
-- You will be notified of the remediation plan and estimated fix timeline.
-- Credit will be given in the release notes (unless you prefer to remain anonymous).
-- A CVE identifier may be requested if applicable.
-
-### If Your Vulnerability Is Declined
-
-- You will receive a detailed explanation of why the report was not accepted.
-- You are welcome to provide additional information if you believe the decision should be reconsidered.
-
----
-
-## Responsible Disclosure
-
-Please do **not** publicly disclose the vulnerability until a fix has been released or we have mutually agreed on a disclosure timeline. We are committed to working with security researchers in good faith.
+- Proof-of-Concept (PoC), if possible
+- The potential security impact
+- Affected versions/components
 
-Thank you for helping keep this project secure. 
+We appreciate responsible disclosure and will work to validate and address legitimate security issues promptly.