Security Vulnerability Disclosure
GRIN Is committed to maintaining the security of our networks and protecting our customers' data. The security researcher community regularly makes valuable contributions to the security of organizations and the broader internet, and GRIN recognizes that fostering a close relationship with the community will help improve our own security. GRIN accepts and acts on vulnerabilities discovered by security researchers.
GRIN has set the following boundaries for security testing. In scope is the following websites.
Out of Scope
While we encourage you to discover and report to us any vulnerabilities you find in a responsible manner, the following conduct is expressly prohibited:
- Performing actions that may negatively affect GRIN or its users (e.g., Spam, Brute Force, Denial of Service…)
- Accessing, or attempting to access, data or information that does not belong to you
- Destroying or corrupting, or attempting to destroy or corrupt, data or information that does not belong to you
- Conducting any kind of physical or electronic attack on GRIN personnel, property or data centers
- Social engineering any GRIN employee or contractor
- Conduct vulnerability testing of participating services using anything other than test accounts
- Violating any laws or breaching any agreements in order to discover vulnerabilities
GRIN pledges not to initiate legal action against researchers for penetrating or attempting to penetrate our systems as long as the security researcher adheres to this policy.
In order to submit a vulnerability report to GRIN’s Security Team, please utilize the OWASP Vulnerability Disclosure Cheat Sheet. GRIN has set the following criteria for vulnerability reports.
- Well-written reports in English will have a higher chance of being accepted.
- Reports that include proof of concept code will be more likely to be accepted.
- Reports that include only crash dumps or other automated tool output will most likely not be accepted.
- Reports that include out of scope sites will be ignored.
- Include how you found the bug, the impact, and any potential remediation.
- Send email to email@example.com and include any plans for public disclosure.
What you can expect from us:
- A timely response to your email (within 2 business days).
- An open dialog to discuss issues.
- Notification when the vulnerability analysis has completed each stage of our review.
- An expected timeline for patches and fixes (usually within 120 days).
- Credit after the vulnerability has been validated and fixed.
If you suspect that AWS resources (such as an EC2 instance or S3 bucket) are being used for suspicious activity, you can report it to the AWS Abuse Team.
If applicable, GRIN will coordinate public notification of a validated vulnerability with you.
When possible, we would prefer that our respective public disclosures be posted simultaneously.
In order to protect our customers, GRIN requests that you not post or share any information about a potential vulnerability in any public setting until we have researched, responded to, and addressed the reported vulnerability and informed customers if needed.