Product security · Vulnerability disclosure

Security is part of every Navijin product

Signed firmware, Navijin-only connections, published security updates and a clear process for reporting vulnerabilities. This page explains how we protect your network and how to work with us.

48 h
acknowledgement of reports
Signed
firmware only
SHA-256
checksums published
Navijin-only
device connections

Published policy

Security vulnerability disclosure policy

Navijin is committed to the security of its products, services and systems. We value the security community and encourage responsible disclosure.

1. Report it privately

If you believe you have found a vulnerability in a Navijin product, service or website, email support@navijin.com. Please do not disclose it publicly before a fix is available.

2. Include the details

A description of the vulnerability, the affected product or service, steps to reproduce, a proof of concept if available, and your contact information.

3. Our commitment

Acknowledgement within 48 hours, investigation and validation by our security team, regular progress updates, and notification when it is resolved.

Responsible disclosure

Act in good faith, avoid privacy violations, do not exploit beyond a proof of concept, do not access or modify user data, and do not disrupt services.

Out of scope

Issues requiring physical access, social engineering, spam or phishing unrelated to Navijin, and denial-of-service without evidence of impact.

Safe harbour

Navijin will not take legal action against researchers who follow this policy and act responsibly. Valid findings may be recognised or rewarded.

Product security

Navijin's approach to product security

Coordinated vulnerability disclosure

We welcome reports from researchers, customers and partners. Reports are acknowledged, investigated and resolved, then disclosed responsibly.

Signed firmware

Firmware for Navijin gateways and access points is distributed as digitally signed images, so the device can confirm the update comes from Navijin and has not been altered. Current releases and SHA-256 checksums are published on our firmware page.

Secure configuration

We publish hardening guidance so administrators set strong credentials and restrict management access to trusted networks.

Report a vulnerability

How to report a security issue

  1. 01

    Prepare details

    Affected model, firmware version, description, impact and steps to reproduce. Include a proof of concept where possible.

  2. 02

    Contact us privately

    Send your report through our technical support contact. Please do not disclose publicly before a fix is available.

  3. 03

    Investigation

    Our team confirms the issue, assesses severity and develops a fix.

  4. 04

    Fix & advisory

    We release updated firmware and publish an advisory on this page.

Best practice

Hardening checklist for Navijin devices

Change default credentials

Set strong, unique admin passwords on every device during installation.

Update firmware

Install the latest release, verify its SHA-256 checksum and review advisories regularly.

Isolate management

Put device management interfaces in a dedicated VLAN reachable only by administrators.

Found a security issue?

Contact our technical team privately and we will respond as quickly as possible.