A system is secure if the plans for the system are public,
and the bad actors can still not break in.
Announcing the first open-source platform for secure mobile identity.
The current archetype for authentication can be summarized by the following two questions:  Can we create a collection of data that uniquely identifies an individual? Can we enable the individual to associate to that data in a secure and consumer friendly process that allows his/her identity to be verified?
This archetype is fundamentally flawed because the management of the identity data is problematic and there currently is no process for associating to the data that is both secure and consumer friendly. How many times each year is there a major breach of identity data? How many new authentication architectures have failed due to lack of consumer acceptance (OpenID and OAuth being the latest)?
If the problem of secure authentication is going to be solved there must be a new archetype: Data about the individual's identity does not matter for authentication (very counter-intuitive). What matters is an institutional validation of the individual represented by a digital credential that can be repeatedly verified in a secure and consumer friendly way.
This new archetype presents different questions: Has the digital credential been issued in a valid institutional process? Is the user to whom the credential was issued the only person who can present the credential? Can the institutional validation be verified when the user presents the credential? Is the process consumer friendly?
Secure authentication is not about managing vast amounts of identity data; it is about managing digital credentials that represent valid institutional processes.
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 verified.
The ability to create and secure a private key on a user's mobile device makes this new archetype possible.
The essence of our process is incredibly simple: 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.
Video, Process and Technical Overview: Click Here
PowerPoint, Secure Mobile Identity Ecosystem: Click Here
General Overview: Click Here
Detailed Technical Specifications: Click Here