Introduction
PatchPulse welcomes feedback from security researchers and the general public to help improve our security. If you believe you have discovered a vulnerability, privacy issue, exposed data or other security issue in any of our assets, we want to hear from you. This policy outlines the steps for reporting vulnerabilities, what we expect, and what you can expect from us.
Systems in Scope
This policy applies to any digital asset owned, operated or maintained by PatchPulse.
Out of Scope
- Assets or equipment not owned by PatchPulse
- Third-party infrastructure (Cloudflare, Brevo, etc.)
- Social Engineering attacks
- Denial of Service (DoS/DDoS) attacks
Vulnerabilities discovered or suspected in out-of-scope systems should be reported to the appropriate vendor or applicable authority.
Our Commitments
When working with us according to this policy, you can expect that we will:
- Respond to your report promptly and work with you to understand and validate your report;
- Strive to keep you informed about the progress of the vulnerability as it is processed;
- Work to remediate discovered vulnerabilities in a timely manner, within our operational constraints;
- Extend Safe Harbor for your vulnerability research conducted in accordance with this policy.
Our Expectations
By participating in our vulnerability disclosure program in good faith, we ask you to:
- Respect the rules, including this policy and any other relevant agreement. In case of inconsistency between this policy and other applicable terms, the terms of this policy will prevail;
- Report any discovered vulnerability promptly;
- Avoid violating others' privacy, disrupting our systems, destroying data and/or harming the user experience;
- Use only official channels to discuss vulnerability information with us;
- Give us a reasonable amount of time (at least 90 days from initial report) to resolve the issue before disclosing it publicly;
- Perform testing only on in-scope systems and respect out-of-scope systems and activities;
- If a vulnerability provides unintended access to data: limit the amount of data accessed to the minimum required to effectively demonstrate a Proof of Concept; and cease testing immediately and submit a report if user data is encountered during testing, such as personally identifiable information (PII), personal health information (PHI), credit card data or proprietary information;
- Interact only with test accounts you own or with the explicit permission of the account holder;
- Not engage in extortion.
Official Channels
Report security issues to [email protected], providing all relevant information. The more details you provide, the easier it will be for us to evaluate and resolve the issue.
Safe Harbor
When conducting vulnerability research according to this policy, we consider research conducted within the scope of this policy to be:
- Authorized with respect to any applicable anti-hacking laws, and we will not initiate or support legal action against you for accidental, good-faith violations of this policy;
- Authorized with respect to any relevant anti-circumvention laws, and we will not bring a claim against you for circumvention of technological controls;
- Exempt from restrictions in our Terms of Service (ToS) and/or Acceptable Use Policy (AUP) that would interfere with conducting security research, and we waive those restrictions on a limited basis;
- Lawful, useful to the overall security of the Internet, and conducted in good faith.
You are expected, as always, to comply with all applicable laws. If legal action is initiated by a third party against you and you have complied with this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.
If at any time you have doubts or are uncertain whether your security research is consistent with this policy, please submit a report through our official channels before proceeding further.