Skip to content

Security

Firmware 2.7 and later

This page describes the security features of firmware 2.7. See firmware versions.

The miro Edge is an industrial gateway for professional installation. This page explains how to commission, operate and decommission it securely.

Security features

  • Unique random administrator password per device, printed on the label
  • Web interface only over HTTPS; the key is created on the device
  • SSH with a limit for connection attempts; after hardening only with SSH keys
  • Only firmware signed by Miromico can be installed; older firmware is refused
  • No inbound connections from the LTE side; no routing between Ethernet and LTE
  • Hardening command that closes local access paths (serial console, boot loader, SSH passwords)
  • Security log of logins, firmware updates and hardening changes, kept across reboots

Commissioning

Commission the gateway on a trusted network before you install it on site.

  • Password: log in with the password from the label, see accessing the device. If you change it, use at least 15 characters and do not reuse passwords of other devices.
  • SSH keys: add your public key under System->Administration->SSH-Keys. Ed25519 keys are recommended.
  • Network server: connect the gateway with LoRa Basics™ Station or the ChirpStack MQTT Forwarder, preferably with a client certificate. Use a separate certificate and key for every gateway, so that you can revoke a single gateway at the network server, and renew them regularly, at least once a year and whenever a gateway is replaced or lost. Use the Semtech UDP packet forwarder only in separated networks, see configuration.
  • LTE: depending on the module, the gateway can fall back to 2G or 3G where LTE is not available. All protected connections (HTTPS, TLS, SSH) remain secure on these networks; the Semtech UDP packet forwarder does not.
  • Remote management: enable only the agents you use, see Remote Management.
  • Backups: a configuration backup (System->Backup / Flash Firmware) contains all credentials of the gateway. Store backups encrypted and with restricted access.

Hardening

Full hardening is recommended for productive deployments. When the configuration is complete, harden the gateway with one command over SSH:

harden-edge -n HARDEN
Before After hardening
Boot loader Can be interrupted on the serial console Boots without waiting for input
Serial console Login with password No login; system messages only
SSH Password or key Key only
Boot loader recovery Firmware recovery with the reset button Off
  • After full hardening, firmware can only be updated in the web interface, over SSH or through remote management. Recovery on site needs a factory reset with the reset button. Check the network, SSH and remote management configuration before you harden.
  • Without -n (harden-edge HARDEN), the boot loader recovery remains available.
  • The command refuses to run if no SSH key is installed, because SSH would then be closed. To harden anyway and add a key later in the web interface, add -f.
  • The hardening remains active after firmware updates and after a factory reset.

The web interface remains available with the administrator password.

Volume deployments

For larger quantities, Miromico delivers gateways with a customer-specific configuration that is already hardened. Contact your Miromico sales representative.

Network integration

  • Connect the gateway to a managed network segment, not directly to the internet.
  • Restrict access to the management services (HTTPS port 443, SSH port 22) to administrator networks with your firewall.
  • The gateway rejects all inbound connections on the LTE side. Ethernet and LTE are both connections to your network server; the gateway does not route traffic between them.

Firmware updates

  • Miromico publishes firmware releases on the downloads page and security advisories on docs.miromico.ch. The gateway does not update itself: installing updates is the responsibility of the operator. Check for updates regularly and install security updates promptly, see firmware update.
  • The gateway checks the Miromico signature of every image before installing it. Modified or unsigned images are refused; this check cannot be overridden.
  • Firmware older than the installed version is refused.

Security log

The web interface shows security events under Status->Security Log:

  • logins and failed logins over SSH and the web interface,
  • firmware checks and updates,
  • changes of the hardening,
  • starts of the gateway.

The log is kept in flash across reboots and firmware updates. Check the log regularly and after unexpected restarts.

Physical security

Full hardening is recommended for productive deployments.

  • Keep the enclosure of outdoor gateways closed and sealed.
  • If a gateway is lost or stolen, revoke its credentials at the network server and in your management systems.

Decommissioning

Before you dispose of a gateway or return it:

  1. Revoke its credentials at the network server, in qbee and in other systems.
  2. If a customer-specific factory configuration with your credentials was stored on the gateway, delete it with miro-factory-config clear, or ask Miromico to do so.
  3. Perform a factory reset.

Support period

Miromico provides security updates for the miro Edge until two years after the end of life (end of sale) of the product, and at least five years after your gateway was placed on the market. Security updates remain available for at least ten years after their release.

Reporting vulnerabilities

Report suspected vulnerabilities to security@miromico.ch. Miromico handles reports according to its vulnerability disclosure policy and informs customers about security updates.