REL-ID is a safe, simple, and scalable security platform that, for the first-time, tightly integrates your identity, authentication, and channel security. By combining strong "relative" identities with our patented protocol, secure application tunnels can be established with blazing speed and at IoT scale, enabling a phenomenal user-experience with every authorization and login.
Traditional identity and authentication approaches such as voice, retina, fingerprints, hard tokens, and challenge questions provide what can be best be described as a patchwork approach to security because they are not tightly integrated into the channel. Individually, each can and have been hacked.
You can post all of your usernames and passwords to Facebook, LinkedIn, and Twitter and still be safe with REL-ID.
What is a relative identity? REL-ID, short for "RELative-IDentity," starts with elements of the existing model of absolute identities and super-charges them. REL-ID first establishes a unique device identity, overlays an application identity, and then binds any set of absolute user-credentials (username, voice, retina, fingerprint, etc.). It also takes the device, application, and access identities at the server side of the connection and binds all of those difficult-to-spoof, mutual factors into a unique combination. This shared/mutual/relative identity, containing elements from both the user and the enterprise, is then split. Each side of the connection is responsible for part of the identity, but neither ever has full knowledge. Like writing down a note and then tearing it in half, it is impossible to recreate that tear and to guess perfectly all the contents of the half you don't posess.
Because the mathematics of the "relative identity" (torn-note) is a true 1:1 relationship, it is the basis of our very strong key-exchange and subsequent encrypted channel. By moving the key-exchange into the application layer at both ends, we keep decryption as close to the responsible parties as possible. Rather than connecting devices-to-networks, REL-ID connects apps-to-apps! You can post all of your usernames and passwords to Facebook, LinkedIn, Twitter and still be safe with REL-ID. We make the compromise of user credentials irrelevant and eliminate unauthorized entry.
If you showed an iphone to a teenager from 1977, they'd think it was magic. So we're not surpised when prospective customers and critics are incredulous about the power of REL-ID. A generational leap in technology like REL-ID looks like magic - in fact, the last time someone innovated as deeply in the security stack as we did was 1977.
But we are real. We have 2 U.S. patents and have had some of the world's best cryptographers and security specialists in banking and the military review our product. Almost all become customers after seeing it in action.
Many in the cryptographry community refuse to use any unpublished crypto. And so do we. Thankfully, REL-ID does not create any new crypto. It is an integration and enhancement of the identity model and key exchange only. We support all industry standard cryptography (AES, etc.). We will soon publish the first version of our key-exchange, once our second version is out of R&D. We know that Relative Mutual Authentication and Key Exchange (RMAK) will become an industry standard protocol within the next 3 years.
We've also seens some pretty incredible growth over the last couple of years...
Please do. Because REL-ID incorporates knowledge from both ends of the connection (i.e. Mutual Factors), regulators have been looking to REL-ID as a stronger, better way to authenticate. Soft tokens can go away entirely. We admit that hard tokens do add another physical element away from your device that must also be "stolen," but the user experience is so poor that most users don't keep the token handy and rely on customer service calls. In addition, the cost to maintain physical tokens is far greater than cost of REL-ID for an enterprise, not including the significant reduction in fraud and call-center activity that REL-ID can help you achieve.
We are confident that our solution will remove the need for hard-tokens in jurisdictions where multi-factor authentication is required by financial services regulators.
There are many types of VPNs, and they are used for a wide variety of needs. Unlike a VPN that exposes all of a device's malware and traffic to your network, REL-ID creates application-specific channels without relying on an entirely open network layer. This reduces the attack surface and enhances your BYOD capabilities.
The downside of application-specific channeling is that it can be laborious to support every legacy application on your network. So for VPN systems that connect 20-30 thick/thin client applications on a desktop, REL-ID might not be the right choice for a VPN replacement. There are still other ways to secure your network with REL-ID like REL-IDzero.
On the other hand... if your applications are all web-based or proxy-enabled, then REL-ID can certainly take the place of your existing VPN architecture. In addition, it can provide Single-Sign-On (SSO) capabilities to all of your web services.
The real benefits of replacing a VPN with REL-ID is the reduction in bandwidth overhead, administrative costs, and lag. While traditional VPN technologies start to breakdown after a few thousand concurrent sessions, requiring mesh-networks and other complex work-arounds or expensive hardware, REL-ID is built for IoT-scale. Replace your VPN mesh with REL-ID and see instantly better speed for web-apps, remote desktops, etc.
The entire web is based on SSL/TLS for encryption and server-side authentication. We're not going to change that overnight. But from an architectural persepctive, we think REL-ID and our protocol, RMAK, is better and more complete.
SSL's a priori information is outside your control. SSL IS TRUST YOU RELY ON.
RMAK's a priori information is entirely in your control. RMAK IS TRUST YOU OWN.
SSL sends the PreMaster key over the channel to the other party.
RMAK never sends the key over the channel to the other party or stores it on the device. Keys are formed simultaneously at each end.
SSL is a sequential process.
RMAK is a truly simultaneous process.
Until everyone speaks RMAK, our products will always run perfectly in conjunction with the SSL/TLS infrastructure. REL-ID works alongside your SSL infrastructure. But if you want to know more about the problems we see with the architecture of SSL/TLS, take a look at the following resources:
The REL-ID API-SDK available as a C library. All other implementations use this with wrappers or raw. The code base is common across all agents.
The REL-ID gateway server, with 4 unique runtime components, each individually scalable. The REL-IDgateway is delivered as a soft appliance.
The REL-IDcore wrapped in a mobile app. This mobile agent provides a base HTML/CSS/JS framework for UI/UX while maintaining the security of REL-ID.
The REL-IDcore wrapped in a desktop installable. This desktop agent provides a base HTML/CSS/JS framework for UI/UX while maintaining the security of REL-ID.
The REL-ID authentication and verification solution, bringing mobile, in-band verification and scalable risk assessment. REL-IDzero is ideal for logins from untrusted computers and 100% transaction verification/non-repudiation.
Yes. Our REL-IDgateway has been scaled across millions of users by large financial institutions over the past two years. We’ve built it for performance and for Internet and IoT scale deployments.
Yes. TLS/SSL has structural issues, typically around the third-party authorities in the certificate trust chain. Even with a perfect implentation of SSL, these vulnerabilities cannot be avoided. Self-signed certificates have become one alternative to third-party a priori trust, but the mechanisms of certificate delivery and diversity are still subject to scaling issues. REL-ID resolves both the structural problems of SSL while also creating the two-way uniqueness that two-way, self-signed SSL implementations have been attempting for years and have yet to easily deliver. Moreover, the way that REL-ID connections are established makes the protocol itself equivalent to or faster than SSL.
No. REL-ID currently operates with applications connecting to gateway servers that sit in your enterprise DMZ. APIs are exposed from the REL-IDgateway Integration Server that can make any enterprise-side application into a REL-ID “aware” application, using the appropriate authentication, keys, and scopes for that application. Should an enterprise not want to use the default identity store inside the REL-IDgateway, the gateway server also exposes an LDAP BIND capability for bringing existing identity stores like ActiveDirectory into the REL-ID authentication process.
Our REL-IDcore (the SDK) was built to provide absolute flexibility for clientside integrations and toolkits. We have already integrated many authentication toolkits into the REL-ID framework and are enhancing that list with the best-of-breed biometrics, set to be rolled out in the next REL-ID release. We are also planning to roll out a FIDO integration of REL-ID, in order to standardize the way that third-party toolkits can operate with the REL-ID SDK.
The REL-IDgateway has been built to provide flexibility with regard to both identity storage, like ActiveDirectory, as well as secure application connectivity inside your enterprise. We have identified a shift towards SaaS integrations and are building specific SAML/OAuth2/OpenID Connect capabilities into the REL-IDgateway. With this new flexibility, REL-ID can provide secure authentication from any device, as well as a Single-Sign-On experience with any third party application, all inside the REL-ID secure channel.