Security Policy

Introduction

At Measurlabs, we are committed to ensuring the security of our systems and protecting our users' data. We believe that collaborating with the security research community is a critical part of a strong security posture. This policy 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.

Authorization

If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized, we will work with you to understand and resolve the issue quickly, and Measurlabs will not recommend or pursue legal action related to your research. Should legal action be initiated by a third party against you for activities that were conducted in accordance with this policy, we will make this authorization known.

Guidelines

Under this policy, "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 with a reasonable amount of time to resolve the issue before public disclosure.

Once you've established that a vulnerability exists or encounter 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, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing.
  • Don't run automated scanners from tools like Burp, Zap or Acunetix before discussing with us first, because they often generate trash data in our system that we need to clean up manually.

Scope

This policy applies to the following digital assets:

  • Measurlabs' website
  • All Measurlabs' APIs
  • Measurlabs' customer portal

Any other systems or digital properties are exlcluded from scope. If there is a particular system not in scope that you think merits testing, please contact us to discuss it first.

Reporting a Vulnerability

Please report security vulnerabilities by emailing us at security@measurlabs.com. In your report, please include:

  • A clear and concise description of the vulnerability.
  • A detailed description of the steps needed to reproduce the vulnerability (proof-of-concept scripts or screenshots are helpful).
  • Your contact information if you would like us to communicate with you regarding your report.

What You Can Expect from Us

When you submit a report to us, we commit to coordinating with you as openly and as quickly as possible.

  • Within a reasonable timeframe, 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.
  • Notify you when the vulnerability is fixed.
  • we don't pay bounties, but we appreciate all findings.