New version of the security page

.github/SECURITY.md

@@ -1,13 +1,34 @@
 # Security Policy
 
+## 🔐 Reporting Security Issues
+
+> Please do not open issues that might have security implications!
+>
+> It is critical that security related issues are reported privately to ensure we have time to address them before they become public.
+
+Vulnerabilities can be reported by getting in touch with the project stakeholder(s):
+
+- [project maintainers](mailto:[email protected])
+
+Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
+
+- Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
+- Full paths of source file(s) related to the manifestation of the issue
+- The location of the affected source code (tag/branch/commit or direct URL)
+- Any special configuration required to reproduce the issue
+- Environment (e.g. Linux / Windows / macOS)
+- Step-by-step instructions to reproduce the issue
+- Proof-of-concept or exploit code (if possible)
+- Impact of the issue, including how an attacker might exploit the issue
+
+This information will help us triage your report more quickly.
+
 ## Supported & Maintained Versions
 
 | Version | Supported          |
-| ------- | ------------------ |
+|---------|--------------------|
 | 0.x.x   | :white_check_mark: |
 
-## Reporting a Vulnerability
+## Preferred Languages
 
-Individuals or organizations that are experiencing a product security issue are strongly encouraged to contact the [project maintainers](mailto:[email protected]).
-We welcome reports from independent researchers, industry organizations, vendors, customers, and other sources concerned with our project security.
-The minimal data needed for reporting a security issue is a description of the potential vulnerability.
+We prefer all communications to be in English.