Cyber security
      Back to home
      1. Help centre
      2. Cyber security

      Vulnerability Disclosure Policy

      If you believe you have found a security vulnerability in a measurable.energy (m.e) product, service or website please submit your report to us.

      m.e is committed to resolving vulnerabilities to meet the needs of its customers and the broader technology community. This vulnerability disclosure policy applies to any vulnerabilities you are considering reporting to us. We recommend reading this Vulnerability Disclosure Policy fully before you report a vulnerability and always acting in compliance with it.

      We value those who take the time and effort to report security vulnerabilities according to this policy. However, we do not offer monetary rewards for vulnerability disclosures.

      Reporting

      If you believe you have found a security vulnerability, please submit your report to us at security@measurable.energy.

      In your report, please include details of:

      • The website, IP, page, device model or app version where the vulnerability can be observed.
      • A brief description of the type of vulnerability, for example: “XSS vulnerability”.
      • Steps to reproduce – these should be benign, non-destructive, proof of concept/exploitation – this helps to ensure that the report can be triaged quickly and accurately and also reduces the likelihood of duplicate reports, or malicious exploitation of some vulnerabilities, such as sub-domain take overs.
      • What you believe the impact of the vulnerability could be.
      • Your contact details so that we can keep you updated and work together on a CVD

      What to expect

      After you have submitted your report, we will respond to your report within 5 working days and aim to triage your report within 10 working days. We will also aim to keep you informed of our progress.

      Priority for remediation is assessed by looking at the impact, severity and exploit complexity. Vulnerability reports might take some time to triage or address. You are welcome to enquire on the status but should avoid doing so more than once every 14 days. This allows our teams to focus on the remediation.

      We will notify you when the reported vulnerability is remediated, and you may be invited to confirm that the solution covers the vulnerability adequately.

      Once your vulnerability has been resolved, we welcome requests to disclose your report. We’d like to unify guidance to affected users, so please do continue to coordinate public release with us. If applicable, m.e will coordinate public notification of a validated vulnerability with you. When possible, we would prefer that our respective public disclosures be posted simultaneously as a Coordinated Vulnerability Disclosure (CVD). The CVD will be in line with the ISO/IEC 29147:2014 standard.

      In order to protect our customers, m.e requests that you do not post or share any information about a potential vulnerability in any public setting until we have researched, responded to, and addressed the reported vulnerability and informed customers if needed.

      Guidance

      You must not:

      • Break any applicable law or regulations.
      • Access unnecessary, excessive or significant amounts of data.
      • Modify data in m.e’s systems or services.
      • Use high intensity invasive or destructive scanning tools to find vulnerabilities.
      • Attempt or report any form of denial of service or seek volumetric vulnerabilities, e.g. simply overwhelming a service with a high volume or requests.
      • Disrupt m.e’s services or systems.
      • Submit reports detailing non-exploitable vulnerabilities, or reports indicating that the services do not fully align with best practice, for example missing security headers.
      • Submit report detailing TLS configuration weaknesses, for example ‘weak’ cipher suite support or the presence or TLS1.0 support.
      • Communicate any vulnerabilities or associated details other than by means described in this policy.
      • Social engineer, ‘phish’ or physically attack m.e’s staff, infrastructure, or products.
      • Demand financial compensation in order to disclose any vulnerabilities.

      You must:

      • Always comply with data protection rules and must not violate the privacy of m.e’s users, staff, contractors, services or systems – you must not, for example, share, redistribute or fail to properly secure data retrieved from the systems or services.
      • Securely delete all data retrieved during your research as soon as it is no longer required or within 1 month of the vulnerability being resolved, whichever occurs first (or as otherwise required by data protection law).

      Legalities

      You are solely responsible for your own compliance with law. Complying with this policy is not intended to provide you with any protection if you breach the law, nor does this policy give you permission to act in any manner that is inconsistent with the law as it applies to you or m.e.

      There are no express or implied warranties or assurances with regard to this information. m.e does not accept any liability whatsoever for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this policy.

      However, if legal action is initiated by a third party against you, and you have complied with this policy, m.e can take steps to make it known that your actions were conducted in compliance with this policy. m.e pledges not to initiate legal action against researchers as long as they adhere to this policy and are in good faith.

       

      Thank you for taking the time to read this policy and for your interest in our security.

       

      Last updated:    30-November-2020

      Last review:        20-March-2024

      To be reviewed: 01-July-2024