Master Lock Vulnerability Disclosure Policy

Master Lock is committed to protecting the security of our customers, and we endeavor to provide our users with a secure, stable product and service, and protect the privacy and security of customers’ data.

This vulnerability disclosure policy applies to any vulnerabilities you are considering reporting to us (the “Organization”).

We recommend reading this vulnerability disclosure policy fully before you report a vulnerability and always act 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 using the following email productsecurity@mlock.com.

In your report, please include details of the following where possible:

• The App, website, IP, or device where the vulnerability can be observed if applicable.
• A brief description of the vulnerability, for example “XSS vulnerability.”
• Potential root cause.
• Steps to reproduce. These should be benign, non-destructive, proof of concept. This helps to ensure that the report can be triaged quickly and accurately.

 

What to expect 

After you have submitted your report, we will acknowledge receipt of 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 or ask for additional information when applicable.

Priorities for remediation are 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.

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

Once the vulnerability has been resolved, we will provide the reporter of the vulnerability with a status update to close the matter.

 

Guidance 

You must NOT:

• Violate any applicable law or regulations.
• Access unnecessary, excessive, or significant amounts of data.
• Modify data in the Organization’s systems or services.
• Use high-intensity invasive or destructive scanning tools to find vulnerabilities.
• Attempt to report any form of denial of service, e.g. overwhelming a service with a high volume of requests.
• Disrupt the Organization’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 reports detailing TLS configuration weaknesses, for example “weak” cipher suite support or the presence of TLS1.0 support.
• Social engineer, “phish” or physically attack the Organization’s staff or infrastructure.
• Demand financial compensation to disclose any vulnerabilities. 
• Discuss or disclose vulnerabilities to any third parties without the express permission of the Organization.

 

You Must

• Always comply with the data protection rules and must not violate the privacy of the Organization’s users, staff, contractors, services, or systems. You must not, for example, share, re-distribute 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 

This policy is designed to be compatible with common vulnerability disclosure good practice. It does not give you permission to act in any manner that is inconsistent with the law, or which might cause the Organization or partner organizations to be in breach of any legal obligations.