VULNERABILITY DISCLOSURE POLICY
Zeotap considers the security of our systems as a top priority. This Policy is particularly designed to provide guidance to External/Independent Security Analysts with respect to reporting any Vulnerabilities present in Zeotap systems in a responsible manner.
This Policy is applicable to all Independent Security Researchers who report any Vulnerabilities present in our Infrastructure/systems.
Vulnerabilities/findings not acceptable for fix
Not all the findings reported might be applicable to Zeotap. Some of them are as given below:
- Third-Party application vulnerabilities/related issues
- Disclosure of version information
- Reports of compromised accounts, accounts exposed in data breaches, or publicly accessible password dumps are not in scope for the bug bounty program but can be reported to us with the provided infosec mail id
- Open redirect vulnerabilities that use a zeotap subdomain and the logout URL to implement a redirect
- Descriptive error messages (e.g. Stack Traces, application, or server errors).
- HTTP 404 codes/pages or other HTTP non-200 codes/pages.
- Fingerprinting/banner disclosure on common/public services.
- Disclosure of known public files or directories, (e.g. robots.txt).
- Clickjacking and issues only exploitable through clickjacking.
- CSRF on forms that are available to anonymous users (e.g. the contact form).
- Logout Cross-Site Request Forgery (logout CSRF).
- Presence of application or web browser ‘autocomplete’ or ‘save password’ functionality.
- Lack of Secure/HTTPOnly flags on non-sensitive Cookies.
- Lack of Security Speed Bump when leaving the site.
- Weak Captcha / Captcha Bypass
- Forgot Password page brute force and account lockout not enforced.
- OPTIONS HTTP method enabled
- Username/email enumeration via Login Page error message or via Forgot Password error message
- Missing HTTP security headers, specifically (https://www.owasp.org/index.php/List_of_useful_HTTP_headers), e.g.
- Content-Security-Policy, X-Content-Security-Policy, X-WebKit-CSP
- SSL Issues, e.g.
- SSL Attacks such as BEAST, BREACH, Renegotiation attack
- SSL Forward secrecy not enabled
- SSL weak/insecure cipher suites
- Content spoofing / text injection without HTML/CSS
- Weak password policies
- Mail configuration issues including SPF, DKIM, DMARC settings
- Host header injection without exploitation
- DNSSEC configuration
Rules of engagement
Researchers are required to adhere to the following while reporting a finding to Zeotap:
- Do not use leaked or compromised accounts belonging to other users. Vulnerabilities that were discovered using leaked or compromised accounts will be disqualified.
- Do not run automated scans without intimating us. They are often very noisy.
- Do not test using social engineering techniques (phishing, vishing, etc)
- Do not perform DoS or DDoS attacks.
- In any way attack our end users, or engage in trade of stolen user credentials.
E-mail your findings to [email protected]. Report the findings in an Encrypted format to prevent this critical information from falling into the wrong hands,
Do not take advantage of the vulnerability or problem you have discovered, for example by downloading more data than necessary to demonstrate the vulnerability or deleting or modifying other people’s data,
Do not reveal the problem to others until it has been resolved,
Do not use attacks on physical security, social engineering, distributed denial of service, spam or applications of third parties, and
Do provide sufficient information to reproduce the problem, so we will be able to resolve it as quickly as possible. Usually, the IP address or the URL of the affected system and a description of the vulnerability will be sufficient, but complex vulnerabilities may require further explanation.
What we promise
We will respond to your report within 3 business days with our evaluation of the report and an expected resolution date.
If you have followed the instructions above, we will not take any legal action against you in regard to the report.
We will handle your report with strict confidentiality, and not pass on your personal details to third parties without your permission.
We will keep you informed of the progress towards resolving the problem.
As a token of our gratitude for your assistance, we offer a reward for every report of a security problem that was not yet known to us. The amount of the reward will be determined based on the severity of the leak and the quality of the report. In the event of public information concerning the problem being reported, we will give your name as the discoverer of the problem (unless you desire otherwise).
We strive to resolve all problems as quickly as possible, and we would like to play an active role in the ultimate publication of the problem after it is resolved.
If you have found a bug, please contact us using the below email address.