Last Updated: March 13, 2022
Vulnerability Disclosure Policy
We take the security of our systems seriously, and we value the role that independent security researchers play in internet security. The disclosure of security vulnerabilities helps us ensure the security and privacy of our users. Please review these terms before you test and/or report a vulnerability.
1. We require that all researchers:
- Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction of data during security testing;
- Perform research only within the scope set out below;
- Use the identified communication channels to report vulnerability information to us;
- Keep information about any vulnerabilities you’ve discovered confidential between yourself and ProDeal until we’ve had 90 days to validate, reproduce, and resolve the issue.
2. If you follow the requirements documented in this policy when reporting an issue to us, we commit to:
- Not pursue or support any legal action related to your research;
- Respond in a timely manner, acknowledging receipt of your vulnerability report;
- Provide an estimated time frame for addressing the vulnerability report;
- Notify you when the vulnerability has been fixed;
- Recognize your contribution on our Security Researcher Hall of Fame, if you are the first to report the issue, the issue is not a known issue, and we make a code or configuration change based on the issue..
3. ProDeal does not permit the following types of security research
In the interest of the safety of our users, staff, the Internet at large and you as a security researcher, the following conduct is expressly prohibited:
- Performing actions that may negatively affect ProDeal or its users (e.g. Spam, Brute Force, Denial of Service…);
- Conduct vulnerability testing of participating services using anything other than test accounts;
- Violating any laws or breaching any agreements in order to discover vulnerabilities;
- Destroying or corrupting, or attempting to destroy or corrupt, data or information that does not belong to you;
- Accessing, or attempting to access, data or information that does not belong to you;
- Findings from physical testing such as office access (e.g. open doors, tailgating);
- Findings derived primarily from social engineering (e.g. phishing, vishing);
- Findings from third party applications or third party systems;
- UI and UX bugs and spelling mistakes;
- Network level Denial of Service (DoS/DDoS) vulnerabilities.
4. Things we do not want to receive:
- Personally identifiable information (PII);
- Credit card holder data;
- Informational vulnerabilities.
5. How to report a security vulnerability?
If you believe you’ve found a new security vulnerability in one of our products or platforms please send it to us by emailing firstname.lastname@example.org. Please include the following details with your report:
- Description of the location and potential impact of the vulnerability;
- A detailed description of the steps required to reproduce the vulnerability (POC scripts, screenshots, and compressed screen captures are all helpful to us);
- Your name/handle and a link for recognition in our Hall of Fame.