Trusted Device

REL-ID only accepts connection requests from devices that are Trusted and Trustworthy. During the initial registration process, REL-ID generates a unique device fingerprint for the customer's device and adds it to its database of Trusted devices. In addition, anytime a connection is being requested, REL-ID also validates that the device not only matches that fingerprint, but is also currently Trustworthy -- that it hasn't been rooted or jailbroken, and that it isn't running malware. If both those criteria are not met, which is virtually impossible for an attacker to simulate, then any connection request from that device will be instantly dropped.

Individual Key Per User

The heart of REL-ID's security model relies on the geneartion and distributionof unique keys that have a 1:1 relationship between the user/app/device and your service at Internet scale. This key, unkown to the user, represents a massive enhancement to the traditional multi-factor authentication model of Something You Know + Something You Have. The key represents a third and much stronger factor: Something You Have But Don't Know. Because the user doesn't know what their key is, it cannot be maliciously obtained using Credential Harvestingor any of the other common types of Credential Compromise

Mutual and Simultaneous Authentication

REL-ID strengthens the level of trust in your customer's connection with you by performing an authentication transaction is both Mutual and Simultaneous. Mutual refers to the fact that it is not only you validating your service's identity to the customer (which is the most common way by far in which TLS is deployed) but also that the customer is cryptographically verifying their identity to you. This is further enhanced by the fact that this authentication is simultaneous -- there is no opportunity for a Man-in-the-Middle type of attack where a malicious third-party can disintermediate the transaction and thus compromise or hijack the connection.

Continuous Authentication

REL-ID doesn't rely on the authentication only at the onset of a session. The underlying RMAK protocol strengthens traditional channel security by periodically re-executing the authentication transaction in order to continuously verify that both parties are mutually authenticated avoiding both client and server compromise scenarios such as a DNS compromise that kicks in while a user is already in a session with one of your applications or services.

End-to-End Trust

Ultimately, REL-ID gives you true end-to-end integrity and privacy. You have absolute, bulletproof, and non-repudiable cryptography that ensures that each and every interaction between you and your client is authentic, has not been tampered with, and is completely private. This trusted connection persists even when using valid third-party disintermediaries such as Content Deliver Networks (CDNs) and Value-Added Networks (VANs).

And REL-ID does this all while delivering a phenomenal client experience across every channel you use.