Cyble’s Vulnerability Disclosure Policy

Cyble values the work done by security experts and supports a coordinated approach to improve, in a responsible manner, the security of our products and services. We are dedicated to working with the security research community to investigate, reproduce, and where practical, address legitimate reported vulnerabilities..

This vulnerability disclosure policy applies to any vulnerabilities you are considering reporting to Cyble (the “Organization”). We recommend reading this vulnerability disclosure policy fully before you report a vulnerability and always acting in compliance with it.

We value those who take the time and effort to report security vulnerabilities according to this policy. We do not offer any monetary rewards for vulnerability disclosures, however, reporters of qualifying vulnerabilities may be offered a unique Cyble reward. The reward shall be determined and given to the reporter solely at the discretion of Cyble based on considerations as may be deemed appropriate. Please note that mere submission by a Reporter will not automatically entitle the reporter to receive any benefits in the form of Cyble Rewards.

Reporting

If you believe you have found a security vulnerability, please submit your report to us using the contact form at the bottom of the page.

What To Expect

After you have submitted your report, we will respond to your report within 5 working days and aim to triage your report within 10 working days. We’ll also aim to keep you informed of our progress.

Priority for remediation is assessed by looking at the impact, severity, and exploit complexity. Vulnerability reports might take some time to triage or address. You are welcome to enquire about the status but should only do so once every 14 days. This allows our teams to focus on the remediation.

We will let you know when the reported vulnerability is remediated, and you may be invited to confirm that the solution covers the exposure adequately.

You won’t be able to disclose the vulnerability without express written consent from the Organization. If the organization approves public disclosure, we will request unified guidance from affected users. Please continue to coordinate the public release with us.

You Must NOT

1. Access unnecessary, excessive or significant amounts of data.
2. Modify data in the Organization’s systems or services.
3. Use high-intensity invasive or destructive scanning tools to find vulnerabilities.
4. Attempt or report any form of denial of service, e.g. overwhelming a service with a high volume of requests.
5. Disrupt the Organization’s services or systems.
6. Submit reports detailing non-exploitable vulnerabilities, or reports indicating that the services do not fully align with “best practice”, for example missing security headers.
7. Submit reports detailing TLS configuration weaknesses, for example, “weak” cipher suite support or the presence of TLS1.0 support.
8. Communicate any vulnerabilities or associated details other than by means described in the published security.txt.
9. Social engineer, ‘phish’ or physically attack the Organization’s staff or infrastructure.
10. Demand financial compensation or threaten the Organization in order to disclose any vulnerabilities.

Must

• Always comply with data protection rules and must not violate the privacy of the Organization’s users, staff, contractors, services or systems. You must not, for example, share, redistribute or fail to properly secure data retrieved from the systems or services.
• Securely delete all data retrieved during your research as soon as it is no longer required or within 1 month of the vulnerability being resolved, whichever occurs first (or as otherwise required by data protection law).
• Maintain strict confidentiality to avoid any possibility of causing any kind of loss to the company.