Before deploying a NetBurner-based product, consider the areas below. Each links to more detailed guidance or a working example elsewhere in this documentation.

Credentials and Access

Change any default or factory-set password before deployment, and avoid exposing a device's configuration interface (the Advanced Configuration Server on port 20034, or any web-based configuration page your product provides) to an untrusted network unless it's protected by a password you've set yourself.

Encrypted Connections

If you have a NetBurner Serial to Ethernet or NTP product, see this guide's Security Considerations for information about uploading SSL certificates.

If you're developing an application that serves HTTPS or otherwise uses TLS, see SSL/TLS and Certificates for a full guide to certificates and connection security, including its own Security Principles and Production Checklist sections.

Verifying Firmware Image Integrity

Developers can sign their application images with an RSA key pair, so a device only accepts an update that is signed with their organization's private key. See the Application Image Security examples – particularly Signed Application (the signing/verification mechanism itself) and Board Lock (binding an image to specific hardware).

Reducing Network Attack Surface

End users should refer to their product's manual for details about disabling any network services they don't need.

Developers should evaluate and disable any network services the application doesn't need. See Disable System Features for disabling AutoIP, the discovery server, ICMP echo (ping), and the web server, and Disable Config Server for disabling the Advanced Configuration Server on port 20034 entirely, once your application provides its own, better-protected way to load updates.

If You Find a Problem

See Vulnerability Disclosure for how to report a security issue – in NetBurner's tools, or in a product built on them – to us.