Vulnerability Disclosure Policy

Introduction

Ansell is a global safety solutions expert, reinventing personal protection for 125 years. We deliver the most advanced protection solutions to millions of people at work and at home, keeping them out of harm’s way. Our expertise, innovative products, and advanced technology give our customers peace of mind and confidence no other brand can deliver. Ansell’s mission is to provide innovative safety solutions in a trustworthy and reliable manner, creating an Ansell-protected world.

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 cybersecurity vulnerabilities to us.

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

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

Authorisation

If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorised and we will work with you to understand and resolve any cybersecurity issue quickly, and Ansell 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 authorisation known.

Guidelines

1. Report new, unique cybersecurity vulnerabilities: This helps us focus on fixing the most impactful risks to us and our customers. Do not submit a high volume of low-quality/low-risk reports
2. Do not compromise systems or exfiltrate data: Only use exploits to the extent necessary to confirm the presence of a cybersecurity vulnerability. Once you have obtained enough information to indicate a security issue, please do not try to establish persistence, target, enumerate, or exfiltrate any internal data, establish command-line access, use a vulnerability to pivot to other systems. Stop your test and notify only Ansell, immediately, if you encounter any sensitive data (including personally identifiable information, financial information, or proprietary information or trade secrets of any party).
3. Respect others: Do not: violate the privacy of any of Ansell’s employees or customers, access or attempt to access data that does not belong to you; cause any degradation of user experience, conduct non-technical attacks (e.g., social engineering, phishing or unauthorised access to infrastructure and employees of Ansell) or perform any actions that may negatively affect Ansell or its customers; cause disruption to production systems, and exposure, destruction, or manipulation of data.
4. Collaborate: Collaborate with us only through our coordinated disclosure process as soon as a cybersecurity vulnerability is identified. The email address and HTTPS Web Form are available below.
5. Notify us (through the steps below) as soon as you discover a real or potential security issue with our system. We want to promptly address these issues and ask that timely notice to us not be sacrificed while you may be conducting further research, e.g., on other products.
6. Provide us a reasonable amount of time to resolve the issue before you disclose it publicly. 90 calendar days from receipt by us (software, including cloud-based systems and mobile apps) or 120 calendar days from receipt by us (hardware, firmware, and wireless).

Public Disclosure

As set out in the guidelines above, to comply with this policy we ask that you refrain from sharing your report about Ansell with others prior to submitting it to us and while we investigate the suspected cybersecurity vulnerability and potentially work on a patch or other resolutions. Please raise any Ansell issues with us before you make a disclosure.

We will inform you when we finalise our findings after the cybersecurity vulnerability is resolved. To comply with this policy, we require that you link to Ansell’s findings alongside your findings in any blog posts, public reports, presentations, or any other public statements on the matter. Other than potentially listing an overall timeline regarding the vulnerability you brought to our attention, we will not publish information about you or our communications with you without your permission. If you wish to be recognised, we will thank you by name or handle in our advisory. Ansell does not credit employees or contractors of Ansell and its subsidiaries for vulnerabilities they have found.

To the extent this policy refers to a “vulnerability” or “vulnerabilities,” it is intended and understood that all such references mean potential or suspected cybersecurity vulnerabilities, whether so stated or not, until such vulnerability has been investigated and confirmed by Ansell. Whether to recognise the disclosure of a vulnerability and the timing of the recognition is entirely at our discretion, and we may cancel the program at any time. Your testing must not violate any laws.

Test methods

The following test methods are not authorised:

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

• https://ansell.com
• https://guardian.ansell.com
• https://ansellguardianpartner.com
• https://ansell.corvexconnected.com
• https://motion.inteliforz.com
• https://demo.motion.inteliforz.com
• Any other subdomain of ansell.com

All customer applications are excluded from this policy.

Out of Scope Vulnerabilities

When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

• 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 Http Only or Secure flags on cookies
• Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
• Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
• Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors)
• Tabnabbing
• Open redirect - unless an additional security impact can be demonstrated
• Issues that require unlikely user interaction

Any service not expressly listed above, such as any connected services, are excluded from scope and are not authorised for testing. Additionally, cybersecurity vulnerabilities found in systems from our vendors fall outside of this policy’s scope and should be reported directly to the vendor according to their disclosure policy (if any). If you aren’t sure whether a system is in scope or not, contact us at security.vdr@ansell.com 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 intend to increase the scope of this policy over time.

Reporting a vulnerability

Information submitted under this policy will be used for defensive purposes only – to mitigate or remediate cybersecurity vulnerabilities. We will not share your name or contact information without express permission.

We accept vulnerability reports at this form below or via security.vdr@ansell.com. 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. For particularly sensitive information, submit through our HTTPS web form below.

What we would like to see from you

In order to help us triage and prioritise submissions, we recommend that your reports:

• Describe the location the cybersecurity vulnerability was discovered and the potential impact of exploitation.
• Offer a detailed description of the steps needed to reproduce the cybersecurity vulnerability (proof of concept scripts or screenshots are helpful) including (as applicable):
  o Mobile application version
  o Device type, operating system version, browser version
• Be 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 5 business days, we will acknowledge that your report has been received.
• To the best of our ability, we will confirm the existence of the cybersecurity 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.
• By reporting a security bug or vulnerability, you give us the right to use your report for any purpose.

Questions

Questions regarding this policy may be sent to security.vdr@ansell.com. We also invite you to contact us with suggestions for improving this policy.