A free open source IT asset/license management system
Fixed typo, added additional clarifications
snipee44e547f0982
diff --git a/SECURITY.md b/SECURITY.mdindex 13e55b1d35..fc7180460e 100644--- a/SECURITY.md+++ b/SECURITY.md@@ -1,13 +1,11 @@# Security Policy-We take security issues very seriously, and will always attempt to address any-vulnerabilities as quickly as possible.+We take security issues very seriously, and will always attempt to address any vulnerabilities as quickly as possible.## Supported Versions-We try to make a reasonable effort to support older versions of Snipe-IT,-however there are times when library dependencies and/or PHP/MySQL dependencies-make it impossible to backport security fixes on older versions.+We try to make a reasonable effort to support older versions of Snipe-IT, however there are times when library+dependencies and/or PHP/MySQL dependencies make it impossible to backport security fixes on older versions.| Version | Supported ||---------|--------------------|@@ -21,15 +19,18 @@ make it impossible to backport security fixes on older versions.## Reporting a Vulnerability-__Security vulnerabilities should be reported [via a new GHSA](https://github.com/grokability/snipe-it/security) or-via email [email protected].__+__Security vulnerabilities should be reported [via a new GHSA](https://github.com/grokability/snipe-it/security) or via+email [email protected].__-If we find that your security report is valid but has been reported in a previous GHSA that is currently still-in draft mode (therefore invisiable to you), we will add your Github username to the GHSA so that you can be+If we find that your security report is valid but has been reported in a previous GHSA that is currently still in draft+mode (therefore currently invisible to you), we will add your Github username to the original GHSA so that you can becredited for your discovery.-You can typically expect a response within two business days, and we typically have fixes out in under a week-from the initial disclosure.+When creating a GHSA, please leave the "package" field blank. Snipe-IT is not a package, so we will just have to blank+that field out when reviewing your GHSA.++You can typically expect a response within five business days, and we typically have fixes out in under a week from the+initial disclosure.This obviously varies based on the severity of the security issue and the difficulty in remediation, but those havehistorically been the timelines we work around.@@ -38,10 +39,8 @@ __We do ask that you do not disclose the vulnerability publicly until we have harelease__ so that we can protect our users, and we will work with you to coordinate a public disclosure once we have afix out.-We will also work with you to ensure that you receive appropriate credit for the discovery of the vulnerability,-if you would like to be credited. (Please provide a GitHub username or other information if you would like to be-credited, and please let us know if you would like to remain-anonymous.)+If you alert us to the security issue via [email protected], please provide a GitHub username or other+information if you would like to be credited, or please let us know if you would like to remain anonymous.For responsible disclosure, we ask that you give us at least __90 days__ to address the issue before disclosing itpublicly, but we will work with you if you need to disclose it sooner than that.