chore: add security-related (#391)

* chore: add security-related

Signed-off-by: yuluo-yx <[email protected]>

---------

Signed-off-by: yuluo-yx <[email protected]>

.github/ISSUE_TEMPLATE/config.yml

@@ -1,2 +1,5 @@
 blank_issues_enabled: false
-
+contact_links:
+  - name: "Crash bug"
+    url: https://github.com/LinuxSuRen/api-testing/SECURITY.md
+    about: "Please file any crash bug with [email protected]."

SECURITY.md

@@ -0,0 +1,18 @@
+## Reporting Security Issues
+
+The API Testing commnity takes a rigorous standpoint in annihilating the security issues in its software projects. API Testing is highly sensitive and forthcoming to issues pertaining to its features and functionality.
+
+## REPORTING VULNERABILITY
+
+If you have apprehensions regarding API Testing's security or you discover vulnerability or potential threat, don’t hesitate to get in touch with the api-testing Security Team by dropping a mail at [[email protected]](mailto:[email protected]). In the mail, specify the description of the issue or potential threat. You are also urged to recommend the way to reproduce and replicate the issue. The API Testing community will get back to you after assessing and analysing the findings.
+
+PLEASE PAY ATTENTION to report the security issue on the security email before disclosing it on public domain.
+
+## VULNERABILITY HANDLING
+
+An overview of the vulnerability handling process is:
+
+The reporter reports the vulnerability privately to API Testing community.
+The appropriate project's security team works privately with the reporter to resolve the vulnerability.
+A new release of the API Testing product concerned is made that includes the fix.
+The vulnerability is publically announced.