Home Overview Future Potential FAQ Protocols Test Contact
The end of user names and passwords...

Touch one button on your mobile device and you are securely signed on to your web based or mobile application.
Imagine a world where user names and passwords are no longer necessary, and authentication is simple and secure.
A system is secure if the plans for the system are public, and the bad actors can still not break in.

The Trust Nexus is the first open-source platform for secure mobile identity:
  • Consumer Friendly ~ Users touch one button on their mobile device to authenticate to both web based and mobile applications.
  • Cryptographically Secure ~ Even if a user's mobile device is lost or stolen his/her credentials are secure (no password based encryption processes; no dependency on "phone lock" OS processes).
  • Simple ~ The source code is crystal clear and easy to implement (Android and Java EE; other platforms coming soon).
  • Effective ~ We completely do away with user names and passwords and all of their weaknesses.
  • Low Cost ~ Our technology and infrastructure services are FREE for every publicly facing website for general user authentication.  There is a nominal licensing fee for corporations and government agencies for internal authentication (e.g., free for banking customers; a small annual fee for banking employees).
  • Also secures three party credentials (passports, driver's licenses, insurance and financial credentials).
  • Eliminates fraudulent financial transactions.
  • Easy Upgrade Path ~ Any web or mobile application that is currently depending on user names and passwords can make an easy upgrade.
How is our solution unique?
Think digital certificates on a mobile device with the convenience of One Touch Authentication™.
Think of the convenience of not managing cryptographic keys. The TNX One Touch mobile app generates a 4,096 bit public/private key pair and secures the private key on the mobile device (truly secure; no password based encryption processes; no dependency on "phone lock" OS processes).
Think of Identity and Authentication Management in terms of managing cryptographically valid digital credentials, not in terms of managing and verifying certificate chains of authority, or even worse, managing and validating vast amounts of personal data.
How can you trust a digital credential?
Two questions must be answered:
Can you verify that the credential was issued in a valid institutional process?
Can you verify that the person to whom the credential was issued is the person presenting the credential?
These questions can be answered with transparent cryptographic processes.
See for yourself.
The prototype of the TNX One Touch mobile app is available at the Google Play Store.
Install the app then click on "Test" in the menu bar above.
When you test the authentication process you will see near real time server logs of the cryptographic processes.
A New Archetype
Identity proofing is one of the key aspects of Identity and Authentication Management.  The current archetype requires users to prove their identity through a collection of personal data (the traditional trifecta of "know", "have" and "are"). [ref]
This archetype is fundamentally flawed in practice.  There is currently no multi-factor authentication process that is both secure and consumer friendly (e.g., no user is going to take a "selfie" every time they authenticate to an application; most users do not want to carry a key fob for every application).  In recent years there have been numerous failures of new authentication architectures due to lack of consumer acceptance (OpenID and OAuth being the latest; the most recent "flavor of the month", the FIDO alliance, has gained little consumer traction).
The Trust Nexus presents a new archetype for authentication. Users do not prove their identity through a collection of personal data; instead, the process of identity proofing (whatever the institution decides that process is) is representational in the cryptographic processes.  What matters most is an institutional validation of the individual represented by a cryptographically valid digital credential that can be repeatedly verified in a secure and consumer friendly way.
This institutional validation represents a stamp of approval.  If the stamp is cryptographically valid, the authentication can be trusted.
This new archetype presents different questions:  Has the digital credential been issued in a valid institutional process (defined by the institution)?  Is the user to whom the credential was issued the only person who can utilize the credential?  Can the institutional validation be verified when the user presents the credential?  Is the process consumer friendly?  Is the process cryptographically secure?  The Trust Nexus answers all of these questions.
Creating a Secure Mobile Identity Ecosystem is not about managing vast amounts of personal data; it is about managing digital credentials that represent valid institutional processes.  In the most basic use case, the credential provider of a web application simply wants to secure the account to the user who created the account.  Identity does not need to be established; valid authentication (from the user who created the account) simply needs to be secure and repeatable.
No organization concerned with consumers is going to institute a complicated process.  No organization concerned with security is going to trust its authentication to a delegated process that depends on a user's Facebook account; however, a high level security organization like a financial institution will be willing to trust credentials issued by another financial institution if the institutional processes can be trusted and cryptographically verified.
The ability to create and secure a 4,096-bit cryptographic key on a user's mobile device makes this new archetype possible. [ref]
The essence of our process is incredibly simple:  Through secure mobile identity, we completely do away with user names and passwords (and all of their weaknesses).  If a credential is provisioned to a user's mobile device in a valid institutional process, then when the user presents the credential (either in person or over the network) the receiver can be certain that either the credential and the user are valid or the user gave his/her mobile device and six digit HEX pin (1/16,777,216) to someone else.
Under the Trust Nexus it truly does not matter who you are; what matters are institutional validations and the ability to verify those validations.
Most authentication schemes depend on securing personal data; we focus on the ability to use credential data in a valid institutional process.  The concept of verifying institutional validations rather than securing personal data requires a shift in perspective.  Once that mental shift occurs everyone is amazed at how simple our system is.
While the Trust Nexus may "defy conventional wisdom", we are confident our core ideas are "non-consensus and right".
© Copyright 2016 ~ Trust Nexus, Inc.
All technologies described here in are "Patent Pending".