Product security
How the platform protects device connections, credentials and secrets, so you don't have to build this layer yourself.
-
Secrets storage
An AES-256 encrypted vault for API tokens, passwords and certificates used in integrations and rule chains, so credentials don't sit in plain configuration. -
Device authentication
- MQTT: access token, MQTT Basic credentials or X.509 certificate.
- HTTP: access token.
- CoAP: access token or X.509 certificate.
- LwM2M: pre-shared key, raw public key or X.509 certificate.
- SNMP: community string (v1/v2c) or USM credentials (v3).
- Mutual TLS: on MQTT, CoAP and LwM2M, both the device and the server authenticate with X.509 certificates. For a device fleet, we recommend X.509 with a certificate chain.
-
Encrypted device transport
ConfigurableMQTT over TLS on port 8883, HTTP over TLS on 443, CoAP over DTLS on 5684, LwM2M over DTLS on 5686 and 5688, and SNMPv3 with USM authentication and encryption. -
Custom domains with automatic SSL (ThingsBoard Cloud, web UI)
Bind your own domain name; the platform provisions the SSL certificate automatically.
Read next
Can’t find what you need?
Our security team answers questions, shares documents under NDA and handles vulnerability reports.
-
Contact our security team
Questions, questionnaires and data requests.
-
Get documents
Certificates and policies; request the NDA ones from the library.
-
Report a vulnerability
Tell us privately. We reply within three business days.