But at the end of the day, those are just words. Marketing speak that, while true, serves to only try to reassure you about your investment in Blues Wireless.
Instead, in this article I'd like to provide a birds-eye view of what this means
from a more pragmatic perspective: how the Notecard and its JSON-based API provide the ability to transfer data from your device (any MCU or SBC!) to your cloud (any cloud!) in an extremely
To prove this point, we need to look at how the combination of the Notecard and Notehub.io work together to secure data at each stage of the journey:
- From encrypting data on your device,
- To securely transferring data off the public Internet,
- To decrypting data on your cloud application.
If your solution requires data to be encrypted on-device, and remain encrypted until it reaches your cloud application, you'll be pleased to learn this is now possible on the Notecard.
The Notecard can encrypt the body (i.e. the data you supply) of every Note generated by your host MCU or SBC. These encrypted Notes are then securely delivered to Notehub.io (see "Securing Data in Transit" below), where they can be routed to your cloud application and decrypted.
Starting with firmware version 1.5.5, the Notecard API adds an optional
key parameter in the
note.add request. The
key stores a reference to a Notehub environment variable which stores your public encryption key.
This workflow for implementing end-to-end encryption with the Notecard API involves:
- Generating an RSA key pair.
- Adding the contents of your RSA public key to an environment variable in Notehub.
- Using the
keyparameter with each
note.addrequest, providing the name of said environment variable.
- Creating a Notehub Route to send the encrypted data to your cloud application.
- Using your RSA private key to decrypt the data upon receipt by your cloud app (e.g. using a Node.js or OpenSSL cloud function).
NOTE: You can find a step-by-step implementation guide here: Encrypting Data with the Notecard.
With your data encrypted before it leaves the device, and properly decrypted at its final endpoint on your cloud, we should also take a look at how data is secured in transit.
On the hardware side, the Notecard includes a factory-installed ECC P-384 certificate provisioned at chip manufacture, an integrated STSAFE Secure Element with hardware crypto, and a true hardware random number generator.
On the communications side, transactional data is secured without any provisioning challenges, using encrypted "off the internet" communication.
To be more specific about the phrase "off the internet", when the Notecard host is set to (the default) of
a.notefile.net (e.g. Notehub), the Notecard selects an APN where the connection between the cellular network and Notehub is made over a VPN. Internal DNS servers are used to resolve the path to Notehub and the connection itself is encrypted using TLS.