Security is core to our values, and the input of hackers acting in good faith to helps us maintain high standards to ensure security and privacy for our users. This includes encouraging responsible vulnerability research and disclosure. This policy sets out our definition of good faith in the context of finding and reporting vulnerabilities, as well as our obligations to you.
When working with us according to this policy, you can expect us to:
- work with you to understand and validate your report, including an initial response to your report within 72 hours of submission;
- work to remediate discovered vulnerabilities in a timely manner; and
- recognize your contribution to improving our security if you are the first to report a unique vulnerability, and your report triggers a code or configuration change.
If you conduct vulnerability research according to this policy, in good faith and in accordance with applicable laws, we will not take any legal action against you with respect to such vulnerability research.
If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report via our official channel (listed below) before going any further.
To encourage vulnerability research and to avoid any confusion between good-faith hacking and malicious attack, we ask that you:
- play by the rules. This includes following this policy, as well as any other relevant agreements. If there is any inconsistency between this policy and any other relevant terms, the terms of this policy will prevail;
- report any vulnerability you’ve discovered promptly;
- avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience;
- use only the Official Channels to discuss vulnerability information with us;
- keep the details of any discovered vulnerabilities confidential until we notify you that they are fixed and only after requesting and receiving explicit permission from Vista Entertainment Solutions;
- perform testing only on in-scope systems, and respect systems and activities which are out-of-scope;
- if a vulnerability provides unintended access to data: (i) limit the amount of data you access to the minimum required for effectively demonstrating a Proof of Concept; (ii) cease testing and (iii) submit a report immediately if you encounter any user data during testing, such as Personally Identifiable Information (PII), credit card data, or proprietary information;
- you should only interact with test accounts you own or with explicit permission from the account holder;
- do not engage in extortion or fraud; and
- we do not offer a bug bounty program and compensation requests will not be considered in compliance with the Responsible Disclosure Policy.
To help us receive vulnerability submissions you can email firstname.lastname@example.org, our official reporting channel.
If you think you’ve found a vulnerability, please include the following details with your report and be as descriptive as possible:
- the location and nature of the vulnerability;
- a detailed description of the steps required to reproduce the vulnerability (screenshots, compressed screen recordings, and proof-of-concept scripts are all helpful); and
- your name/handle and a hyperlink for recognition if you consent to being included in our Security Researcher Hall of Fame. We will only publish links to professional networking platforms such as LinkedIn.
If you’d like to encrypt the information, please use our PGP key.
-----BEGIN PGP PUBLIC KEY BLOCK-----
We may modify the terms of this policy or terminate this policy at any time. We won’t apply any changes we make to this policy retrospectively.
The following domains are in-scope for testing except for sub-domains that are mentioned are noted as being out out-scope
Security Researcher Hall of Fame
We would like to thank the following individuals who have responsibly disclosed vulnerabilities to us:
Responsible Disclosure Policy inspired by disclose.io