Vulnerability Disclosure Program

Introduction

Gadget is committed to ensuring the security of all our customers' data by protecting their information stored within our systems. This program 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.

This policy describes what systems and types of research are covered under this program, how to send us vulnerability reports, and how long we ask security researchers to wait before publicly disclosing vulnerabilities.

We encourage you to contact us to report potential vulnerabilities in our systems.

Guidelines

Under this program, "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 accessed 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.

Test Methods

The following test methods are not authorized: 

• 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 

Scope

This policy applies to the following systems and services: 

• *.gadget.dev 
• *.gadget.app
• *.application.new

Any service not expressly listed above, such as any connected services, are excluded from scope and are not authorized for testing. Vulnerabilities found in systems from our vendors fall outside of this program’s scope and should be reported directly to the vendor according to their disclosure program (if any). Vulnerabilities found in applications hosted on the Gadget platform are excluded from this scope, and should be reported directly to the developer of the application. If you aren’t sure whether a system is in scope or not, contact us at security@gadget.dev before starting your research. 

Though we develop and maintain other internet-accessible systems or services, we ask that active research and testing only be conducted on the systems and services covered by the scope of this document. If there is a particular system not in scope that you think merits testing, please contact us to discuss it first. We will increase the scope of this program over time.

Reporting a Vulnerability

We accept vulnerability reports via email at security@gadget.dev. Reports may be submitted anonymously. If you share contact information, we will acknowledge receipt of your report within 3 business days. 

We do not support PGP-encrypted emails.

What we would like to see from you 

In order 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). 
• Are communicated to us in English, if possible 

What you can expect from us 

When you choose to share your contact information with us, we commit to coordinating with you as openly and as quickly as possible. 

Within 3 business days, we will acknowledge that your report has been received. To the best of our ability, we will confirm the existence of the vulnerability to you and be as transparent as possible about what steps we are taking during the remediation process, including on issues or challenges that may delay resolution. We will maintain an open dialogue to discuss issues and resolutions.

Disclosure

Gadget is committed to timely correction of vulnerabilities. However, we recognize that public disclosure of a vulnerability in absence of a readily available corrective action likely increases versus decreases risk. Accordingly, we require that you refrain from sharing information about discovered vulnerabilities for 90 calendar days after you have received our acknowledgement of receipt of your report. If you believe others should be informed of the vulnerability prior to our implementation of corrective actions, we require that you coordinate in advance with us. 

We may share vulnerability reports with the Cybersecurity and Infrastructure Security Agency (CISA), as well as any affected customers. We will not share names or contact data of security researchers unless given explicit permission. 

Our Commitments

When working with us, according to this policy, you can expect us to:

• Respond to your report promptly, and work with you to understand and validate your report;
• Strive to keep you informed about the progress of a vulnerability as it is processed;
• Work to remediate discovered vulnerabilities in a timely manner, within our operational constraints; and
• Extend Safe Harbor for your vulnerability research that is related to this policy.

Safe Harbor

When conducting vulnerability research, according to this policy, we consider this research conducted under this policy to be:

• Authorized concerning 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 concerning any relevant anti-circumvention laws, and we will not bring a claim against you for circumvention of technology controls;
• Exempt from restrictions in our Terms of Service (TOS) and/or Acceptable Usage Policy (AUP) 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.

Note that the Safe Harbor applies only to legal claims under the control of the organization participating in this policy, and that the policy does not bind independent third parties.

Questions

Questions regarding this policy may be sent to security@gadget.dev