Responsible Disclosure of Security Vulnerabilities
Syncfusion is committed to the privacy, safety, and security of our customers.
Syncfusion aims to keep its service safe for everyone, and data security is of the utmost priority. If you are a security researcher and have discovered a security vulnerability in our product, website, or service, we appreciate your help in disclosing it to us in a responsible manner.
This policy is intended to give security researchers clear guidelines for conducting vulnerability discovery activities and to convey our preferences in how to submit discovered vulnerabilities to us.
If you are a current customer
If you feel your account may have been compromised, or if you suspect fraudulent behavior, do not hesitate to contact our support team. Your issue will be investigated immediately and thoroughly.
If you are a security researcher or have discovered a vulnerability
What Is Research
Under this policy, “research” means activities in which you:
- Notify us as soon as possible after you discover a real or potential security issue.
- Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
- Only use exploits to the extent necessary to confirm a vulnerability’s presence. Do not use an exploit to compromise or exfiltrate data, establish persistent command line access, or use the exploit to pivot to other systems.
- Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.
- Do not submit a high volume of low-quality reports.
Once you’ve established that a vulnerability exists or encounter any sensitive data (including personally identifiable information, financial information, or proprietary information or trade secrets of any party), you must stop your test, notify us immediately, and not disclose this data to anyone else.
The following test methods are not authorized:
- Use of automated testing tools.
- Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data.
- Physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing.
If you think you’ve found a security vulnerability in Bold BI, contact us immediately via email@example.com.
Please read the policy and program rules before reporting anything.
We will investigate all legitimate reports and make every effort to quickly correct any vulnerability. We ask in return that you:
- Provide details of the vulnerability, including information needed to reproduce and validate the vulnerability and a Proof of Concept (POC).
- Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our services.
- Do not modify or access data that does not belong to you.
- Give Syncfusion a reasonable time to correct the issue before making any information public.
Syncfusion does not typically offer a reward for the disclosure of security issues. We reserve the right to acknowledge your contribution in a manner we see fit.
- When experimenting, please only attack test accounts you control. A PoC unnecessarily involving accounts of other end users or Syncfusion employee may be disqualified. It’s also good practice to tell us the accounts you are using for testing even when they are under your control.
- Do not run automated scans without checking with us first.
- Do not test the physical security of Syncfusion offices, employees, equipment, etc.
- Do not test using social engineering techniques (phishing, spear-phishing, pretexting, etc.).
- Do not perform DoS or DDoS attacks. You are welcome and encouraged to look for vulnerabilities that can be leveraged for DoS or DDoS attacks, we just don’t want you actually exploiting the issue outside of a tightly controlled environment.
- Do not, in any way, attack our end users or engage in the trade of stolen user credentials.
Syncfusion uses a number of third-party providers and services. Our bug bounty program does not give you permission to perform security testing on their systems. Vulnerabilities in third-party systems will be assessed case-by-case, and party if needed.
Low severity, purely theoretical and best-practice issues do not qualify for submission. Here are some examples:
- Theoretical security issues with no specific supporting evidence.
- HTTP 404 codes/pages or other HTTP.
- Reports exploiting the behavior of, or vulnerabilities in, outdated browsers.
What we would like to see from you
To help us triage and prioritize submissions, we recommend that your reports:
- Describe the location the vulnerability was discovered and the potential impact of exploitation.
- Offer a detailed description of the steps needed to reproduce the vulnerability (proof of concept scripts or screenshots are helpful).
If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized, we will work with you to understand and resolve the issue quickly, and Syncfusion will not recommend or pursue legal action related to your research. Should legal action be initiated by a third party against you for activities that were conducted in accordance with this policy, we will make this authorization known.