Vulnerability Disclosure Policy
Security is core to our values, and we value the input of hackers acting in good-faith to help us maintain a high standard for the 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 what you can expect from us in return.
When working with us according to this policy, you can expect us to:
- Work with you to understand and validate your report, including a timely initial response to the 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.
The following types of research are strictly prohibited:
- Accessing or attempting to access accounts or data that does not belong to you
- Executing or attempting to execute a denial of service (DoS) attack
- Sending or attempting to send unsolicited or unauthorised email, spam or any other form of unsolicited messages
- Conducting social engineering (including phishing)
- Any physical attack against our property or that of our service providers
- Testing third party websites, applications or services that integrate with our services or products
- Any activity that violates any law
We don’t currently provide any rewards but we’re working on it.
Official Communication Channels
Coordinated Disclosure – A researcher can share details of the vulnerability after a fix has been applied and the program owner has provided permission to disclose, OR after 90 days from submission, whichever is sooner.
To encourage vulnerability research and to avoid any confusion between legitimate research and malicious attack, we ask that you attempt, in good faith, to:
- Play by the rules. This includes following this policy any other relevant agreements;
- 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;
- Handle the confidentiality of details of any discovered vulnerabilities according to our Disclosure Policy;
- 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: Limit the amount of data you access to the minimum required for effectively demonstrating a Proof of Concept; and cease testing and submit a report immediately if you encounter any user data during testing, such as Personally Identifiable Information (PII), Personal Healthcare Information (PHI), credit card data, or proprietary information;
- You should only interact with test accounts you own or with explicit permission from the account holder; and
- Do not engage in extortion.
When conducting vulnerability research according to this policy, we consider this research conducted under this policy to be:
- Authorized in view of 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 in view of relevant anti-circumvention laws, and we will not bring a claim against you for circumvention of technology controls;
- Exempt from restrictions in our Acceptable Usage Policy that would interfere with conducting security research, and we waive those restrictions on a limited basis; and
- Lawful, helpful 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 concerns or are uncertain whether your security research is consistent with this policy, please submit a report through one of our Official Channels before going any further.
Security Researcher’s who have reported issues to Eggy
Issues regarding website (eggy.com.au)
- Dhrupad Joshi – https://www.linkedin.com/in/dhrupad-joshi
- Devender Rao – https://www.linkedin.com/in/devender-rao/
- Vivek Panday – https://www.linkedin.com/in/vivek-panday-796768149
- Venkatesh B – https://www.linkedin.com/in/b-venkatesh-858595192
- Rohit Chela – https://www.linkedin.com/in/rohit-chela-6469011ab
- Viniket Thakare – https://twitter.com/ThakareViniket
- Parshwa Bhavsar – https://www.linkedin.com/in/parshwa-bhavsar-549185176
- Kunal Mhaske – https://www.linkedin.com/in/kunal-mhaske-59928a170
- Chetan Pathade – https://www.linkedin.com/in/chetan-pathade
- Gourab Sadhukhan – https://www.linkedin.com/in/gourab-sadhukhan-71158216a
- Ayushmaan Banerjee – https://www.linkedin.com/in/amb10
- Deepesh Kumur Pandey – https://www.linkedin.com/in/beertocode/
- Waqas Zaka – https://twitter.com/waqaszaka11
- Pratik Luhana – https://in.linkedin.com/in/pratik-luhana-69b403105
- Shubham Panchal – https://www.linkedin.com/in/shubham-panchal-636744161/
- Pritam Mukherjee – https://www.linkedin.com/in/pritam-mukherjee-urvil-b75ab9b9/