Compliance

Nicolab and its products are compliant with standards for quality, safety and security.

Introduction

This vulnerability disclosure policy applies to any vulnerabilities you are considering reporting to Nico.lab (“company”,

“we”, “us”). 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:

infosec@nico-lab.com

In your report please include details of:

● The URL or IP where the vulnerability can be observed

● A brief description of the type of vulnerability (example: “XSS vulnerability”)

● Steps to reproduce. These should be a benign, non-destructive, proof of concept. This helps to ensure that

the report can be triaged quickly and accurately. It also reduces the likelihood of duplicate reports, or

malicious exploitation of some vulnerabilities, such as sub-domain takeovers.

What to expect

After you have submitted your report, we will do our best to respond to your report within 10 working days and aim to

triage your report within 14 working days. We’ll 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 inquire about 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.

Guidance

You must NOT:

● Break any applicable law or regulations

● Access unnecessary, excessive or significant amounts of data

● Modify data in the Organisation’s systems or services

● Use high-intensity, invasive or destructive scanning tools to find vulnerabilities

● Attempt any form of denial of service, e.g. overwhelming a service with a high volume of requests

● Disrupt the Organisation’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

● Communicate any vulnerabilities or associated details other than by means described in the published

security.txt. (https://www.nico-lab.com/.well-known/security.txt)

● Social engineer, “phish” or physically attack the Organisation’s staff or infrastructure

● Demand financial compensation in order to disclose any vulnerabilities

 

You must:

● Always comply with data protection rules and must not violate the privacy of the Organisation’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 2 weeks

of the vulnerability being resolved, whichever occurs first (or as otherwise required by GDPR 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 Organisation or partner

organisations to be in breach of any legal obligations.

Certifications

CE
The Conformitè Europëenne (CE) Mark is defined as the European Union’s (EU) mandatory conformity marking for regulating the goods sold within the European Economic Area (EEA) since 1985. The mark indicates conformity with health, safety, and environmental protection standards.

LVO Detection & Location, Hemorrhage Detection

TGA
The Therapeutic Goods Administration (TGA) is part of the Australian Gorvernment Department of Health, and is responsible for regulating therapeutic goods including prescription medicines, vaccines and medical devices.

LVO Detection & Location, Hemorrhage Detection, Automated Perfusion Analysis

FDA
The Food and Drug Administration is responsible for protecting the public health by ensuring the safety, efficacy, and security of human and veterinary drugs, biological products, and medical devices.

LVO Detection

ISO 13485:2016 specifies requirements for a quality management system where an organization needs to demonstrate its ability to provide medical devices and related services that consistently meet customer and applicable regulatory requirements.

ISO/IEC 27001:2013 is an international standard on how to manage information security. It details requirements for establishing, implementing, maintaining and continually improving an information security management system (ISMS) – the aim of which is to help organizations make the information assets they hold more secure.