The following lists the built-in security features of the LISNR Radius SDK:
SDK and API tokens limit who can use Radius
SDK/API Tokens are cryptographically signed using key(s) specific to LISNR, adding a level of protection to prevent unauthorized use
a LISNR tone can not be generated/transmitted or unintentionally demodulated by an unauthorized user without the use of the Radius SDK
LISNR's patent portfolio
Radius SDK is a transport mechanism. Payload contents are not stored/observed
The PKAB2 tone profile is close range (3 feet) and physically difficult to intercept
The PKAB2 tone profile provides a high throughput (1000-2000 bits/sec) to support additional security measures listed below.
(Future) In the release of Radius 3.0, a new feature called ToneLock will be enabled for the PKAB2 tone profile. This will allow a UUID to be set on outbound transmitters and listening receivers. Data payloads will be unable to be demodulated/received by the SDK unless these UUIDs match. Ask our Customer Success team (email@example.com) about release dates.
The Radius SDK can also enable and support the transmission of OTP (one time passwords), tokenized, or encrypted payloads that are generated by our users and can ensure a secure connection.
QR Code comparison - fraud attempts with QR codes are caused by malicious users generating fake QR codes which can be easily done by any type of user. LISNR's Radius SDK has an advantage over this because it is much easier to create a fake/malicious QR code and put it in front of a consumer VS creating a Radius tone from scratch that is able to be demodulated by our SDK.