docs: add basic verbiage and link to new GH security report (#31)

Signed-off-by: Sean Beckett <[email protected]>
Co-authored-by: Justin Tieri <[email protected]>

SECURITY.md

@@ -1,5 +1,9 @@
-# Security Policy
+# Reporting Security Issues
 
-## Reporting a Vulnerability
-If you think you may have found a security vulnerability, please do not post it in the public issue tracker. 
-Instead, all security issues must be sent to `[email protected]`.
+The Strangelove team and the IBC community take security issues seriously. We appreciate your efforts to responsibly disclose your findings, and we will make all reasonable efforts to acknowledge your contributions.
+
+To report a security issue, please use the GitHub Security Advisory ["Report a Vulnerability"](security/advisories/new) tab. Please provide any data you have, and the more you can provide the more rapidly we can respond. However, do not let lack of knowledge delay your report. You may leave blank any areas of the security advisory except the detailed description of the issue, the steps to reproduce, and the version or versions you know to be affected.
+
+The Strangelove team will send a response indicating the next steps in handling your report. After the initial reply to your report, the security team will keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance. We may also coordinate with Amulet or other security consultants in the Cosmos/IBC space. 
+
+Report security bugs in third-party modules or plugins to the person or team maintaining the module.