Home Cybersecurity

Cybersecurity

Coordinated Vulnerability Disclosure (CVD) Policy

1. Introduction and Philosophy

At Naio, the security and reliability of our products are a top priority. We are aware that despite our best efforts and internal audits, vulnerabilities may still exist. We consider cybersecurity researchers to be valuable allies in our mission to protect our ecosystem. This policy is designed to provide clear guidelines for conducting vulnerability research safely and to explain how to report your findings so we can protect our users.

2. Safe Harbor

If you conduct your research and report a vulnerability in strict compliance with the rules outlined in this policy, we will consider your actions to be authorized and conducted in good faith. Consequently, Naio commits not to initiate any civil or criminal legal action against you, nor to file a complaint for unauthorized access to our systems. If a third party initiates legal action against you in connection with activities conducted under this policy, we will make it publicly known that your actions were conducted in compliance with our guidelines.

3. Scope

In-Scope:

  • Robots: Oz and Ted
  • Software tools: Easymapping and Naio App

Out-of-Scope:

  • Denial of Service (DoS/DDoS) attacks or any action that degrades the availability of our robots or services.
  • Social engineering (e.g., phishing, vishing) targeting Naio employees, partners, or customers.
  • Physical attacks against Naio’s infrastructure, premises, or robots operating in the field.
  • The compromise, exfiltration, or destruction of personal or customer data (if you accidentally access personal data, stop immediately and report it).

4. Rules of Engagement

When conducting your research, we require you to adhere to the following rules:

  • Do not exploit the vulnerability beyond what is strictly necessary to prove its existence (Proof of Concept).
  • Do not delete, modify, or destroy any data.
  • Do not attempt to pivot to other internal systems once an initial vulnerability is discovered.
  • Keep all vulnerability details strictly confidential until we have deployed a patch and authorized public disclosure (Coordinated Disclosure principle).

5. How to Report a Vulnerability

Please submit your vulnerability reports through our secure web form.

To protect the confidentiality of your findings, we strongly encourage you to encrypt your communications using our public PGP key, which is available in our security.txt file.

Your report should ideally include:

  • The specific product (Oz, Ted, Easymapping, Naio App) and the exact version affected.
  • A detailed technical description of the vulnerability.
  • Step-by-step instructions to reproduce the issue (PoC), including any necessary scripts or screenshots.

6. Our Commitments (SLA)

When you report a vulnerability in good faith, we commit to the following response timeline:

  • Acknowledgment: We will confirm receipt of your report within 72 hours.
  • Triage and Assessment: We will inform you of the validity and severity of the vulnerability within 14 days.
  • Remediation: We will actively work to develop and deploy a patch within a reasonable timeframe (typically within 90 days, depending on complexity).
  • Recognition: If you are the first to report a valid and previously unknown vulnerability, we will gladly add your name or alias to our Hall of Fame, subject to your prior approval.