Introduction

SenseOn Tech Ltd (“SenseOn”) welcomes feedback from security researchers and the general public to help improve our security. If you believe you have discovered a vulnerability, privacy issue, exposed data, or other security issues in any of our assets, we want to hear from you. This policy outlines steps for reporting vulnerabilities to us, what we expect, and what you can expect from us.

SenseOn may update this policy from time to time without notice so please make sure you refer to the most recent version.

Scope

This policy applies to any digital assets owned, operated, or maintained by SenseOn including all SenseOn products, services and websites. Assets are only within the scope of this policy when the following conditions have been met:

• The vulnerability is not already known to SenseOn, either previously reported or identified through internal procedures.

• There is a demonstrable impact to SenseOn, its customers or its users should the vulnerability be exploited by malicious actors.

Out of Scope

When reporting vulnerabilities please consider the attack scenario and potential business impact of the bug. Without limitation and by way of example only, the following vulnerability classes are considered out of scope and will not be triaged:

• Vulnerabilities that require phishing.

• Clickjacking on pages with no sensitive actions.

• Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions.

• Attacks requiring MITM or physical access to a user’s device.

• Previously known vulnerable libraries without a working Proof of Concept.

• Comma Separated Values (CSV) injection without demonstrating a vulnerability.

• Missing best practices in SSL/TLS configuration.

• Any activity that could lead to the disruption of our service (DoS).

• Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS.

• Rate limiting or brute force issues on non-authentication endpoints.

• Missing best practices in Content Security Policy.

• Missing HttpOnly or Secure flags on cookies.

• Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.).

• Software version disclosure / Banner identification issues / Descriptive error messages or headers.

• Open redirect – unless an additional security impact can be demonstrated.

• Self XSS – Where the user would have to paste code into their browser.

• Assets or other equipment not owned by parties participating in this policy.

Vulnerabilities discovered or suspected in out-of-scope systems should be reported to the appropriate vendor or applicable authority.

Our Commitments

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

• Respond to your report promptly; and

• 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.

Our Expectations

In participating in our vulnerability disclosure program in good faith, we ask that you:

• Play by the rules, including following this policy and any other relevant agreements.  For example if you are an employee of Senseon or a SenseOn customer you should comply with your or your employer’s agreement with us.

• 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 (see below) to discuss vulnerability information with us;

• Provide us with a reasonable amount of time (at least 120 days from the initial report) to resolve the issue before you request to disclose it publicly;

• 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;

• should only interact with test accounts you own or with explicit permission from the account holder; and

• Do not engage in extortion or similar behaviour.

Official Channels

Please report security issues via responsible.disclosure[at]senseon.io, providing all relevant information. The more details you provide, the easier it will be for us to triage and fix the issue.

Bug Bounty

At this time SenseOn does not offer a paid bug bounty programme.

Legality

When conducting vulnerability research, according to this policy, we consider this research conducted under this policy to be lawful, helpful to the overall security of the Internet, and conducted in good faith. 

We do not intend to initiate or support legal action against you for accidental, good-faith violations of this policy. However, you are expected, as always, to comply with all applicable laws.

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.