February 2010 - Community - mailman.kantarainitiative.org

Need your input on your standards testing needs
by Newlands, Ellen J 10 Feb '10

10 Feb '10

Dear Kantara Community, The Kantara Initiative Interoperability program is actively working to understand your interoperability testing needs with regard to the certification of some of the more widely-used and emerging identity and access management standards. We developed this short survey (just one page!) to help us determine what standards testing is important to you in the coming year: http://www.surveymonkey.com/s/ki_interoperability_program Thank you in advance for your response. Regards; Ellen Newlands Acting Interoperability Review Board Co-Chair

1 0

Diverse Market Leaders from the Identity Ecosystem Converge to Stage Kantara Initiative's RSA Security Pre-Conference workshop March 1 2010
by Dervla O'Reilly 10 Feb '10

10 Feb '10

Below is the press release that crossed the wire this morning regarding Kantara Initiative's annual identity workshop March 1 at the RSA Security Conference. We're looking forward to a great day and hope to see you at the event. I encourage you to register for this free workshop using the code1310KANEXPO for an Expo only pass - select Kantara Initiative from the ‘Registration Package’ page. ===================== Diverse Market Leaders from the Identity Ecosystem Converge to Stage Kantara Initiative’s RSA Security Pre-Conference Workshop on “Technology, Policy and Compliance for Identity Services in 2010 and Beyond” Gain State-of-Identity Insight of common Cloud/SaaS scenarios and recent developments in assurance, multi-protocol interoperability, privacy-enablement and more from Enterprise and Consumer Market Leaders. Piscataway, NJ, 8 February 2010 Kantara Initiative announced today its annual public Identity Workshop at the RSA Security Conference. The one-day event to be held on March 1st from 8:00am- 5:00pm in the Moscone Center in San Francisco is designed to equip attendees with the vital information required to ensure success in employing the right identity management approach with the proper considerations. Recent developments in identity assurance, multi-protocol interoperability, liability models, usability, privacy-enablement and identity services certification will be spotlighted by key market leaders including Google, Oracle, CA, Aetna, NTT and Ping Identity. “If you run a login system of any type (Enterprise, Consumer, SaaS vendor) you will find this workshop to be packed with information about major changes in the space, both in terms of security design and new functionality that can improve your identity infrastructure,” reveals Eric Sachs, Product Manager for Google Security. “Since its inception nearly one year ago, Kantara Initiative has built momentum for service deployment across the identity ecosystem,” says Roger Sullivan, Oracle. “This workshop will help deployers understand how to connect the dots between cloud computing and identity management”. “Identity protocols like SAML, OpenID, OAuth, and Information Cards continue to evolve,” says Paul Madsen, Identity Management Researcher at NTT. “This workshop will discuss recent developments, and present opportunities for combining the protocols in useful ways.” “Identity Assurance is the key to successful, secure transactions across the emerging National Health Information Network, “ explains Mark Coderre, Head of Security Architecture for Aetna. “At this workshop we will be showcasing what the healthcare industry is doing with Kantara Initiative programs to improve the security of sensitive data transactions across operational boundaries.” The identity workshop will feature a series of presentations, panels and demonstrations of common Cloud/SaaS deployment scenarios and innovations from various market leaders. Technology, Policy and Compliance for identity Services in 2010 & Beyond is open to the public and to all RSA Conference attendees. To register for this free Kantara Initiative workshop, please click http://www.emc.com/microsites/rsa-conference/2010/usa/registration-and-rate… and use the code: 1310KANEXPO for the Expo only pass and select Kantara Initiative from the ‘Registration Package’ page. Note that this pass only allows access to the Kantara Initiative workshop on March 1. About Kantara Initiative Kantara Initiative is a global, open, public-private, technology- agnostic forum comprised of identity ecosystem stakeholders. Co- founded by Liberty Alliance, Internet Society, and the Information Card Foundation, among others, its inspired mission is to promote technical interoperability and harmonization; to develop policy frameworks for operational interoperability and; to provide certification and assessment programs to grow trust in the standards, products, and service deployments. Kantara Initiative freely provides the governance and resources whereby diverse members of the ecosystem successfully collaborate on a diverse portfolio of common policy frameworks, technical specifications and deployment guidelines driven by the identity community, industry and governments from around the world. For more information about getting involved in Kantara Initiative, visit www.kantarainitiative.org. Media Contact Michelle Hunt Kantara Initiative Michelle.Hunt(a)ieee-isto.org (732) 981.3434 (o) ### ________________________ Dervla O’Reilly Program Manager Kantara Initiative +1 415 731 4487 business +1 415 948 3650 mobile +1 509 757 4487 fax dervla[at]kantarainitiative.org http://www.kantarainitiative.org

1 0

Fwd: CSI SX 2010: Call for Papers open, event date May 26-27 at the San Francisco Marriott Marquis
by Dervla O'Reilly 09 Feb '10

09 Feb '10

The paper submissions deadline for CSI SX 2010 is March 17, 2010. Is anyone interested to collaborate and submit a session(s) on behalf of Kantara? Please let me know, I can help with the submission. Dervla >> From: <Rosilia.Montalvo(a)ubm.com> >> Date: February 4, 2010 1:09:04 PM EST >> To: <brett(a)projectliberty.org> >> Subject: CSI SX 2010: Call for Papers >> >> Dear Brett McDowell, >> >> The Call for Papers for CSI SX 2010 is now open. Submissions are >> due by March 17, 2010. CSI SX 2010 will take place May 26-27, 2010 >> at the San Francisco Marriott Marquis in San Francisco, CA. >> >> CSI is looking for security professionals, business leaders and >> technology providers to address current key security topics, as >> well as share best practices, experience and case studies. The CSI >> SX 2010 program will focus on the challenges of managing security >> in an increasingly mobile business environment and show >> organizations how to stay secure while increasing business agility. >> >> We invite you to submit and become a part of this select crowd. The >> deadline for submissions is March 17, 2010. >> >> Thank you for your continued support of our events. Should you have >> any questions, feel free to contact me. >> >> Best, >> Rosie >> >> Rosie Montalvo >> Event Specialist >> Computer Security Institute :: UBM International Media >> 11 West 19th Street, 3rd Fl., NY, NY 10011 >> Rosilia.Montalvo(a)ubm.com >> Phone +1.212.600.3018 >> www.GoCSI.com :: www.CSIsx.com :: www.CSIannual.com >> >> =========================== >> Unsubscribe information. You received this email because you >> participated in past CSI Events. If you do not want any other >> correspondence from us, please change your Opt In preferences at https://www.cmpevents.com/?M=$FLL1JIGDHH1J1D1D1D1D1MHIJG1D1D >

1 0

A system that models and coordinates real-time and near-real time device activity and interactivity.
by Owen Thomas 04 Feb '10

04 Feb '10

Hi Sampo. I've started this message in a separate thread. I hope the new title is appropriate. See my replies where appropriate below. 2010/2/1 <sampo(a)symlabs.com> > Owen Thomas wrote: > > Hello Robin. > > > > May I pick you up there on what you say about "spanning borders", and > > apply > > Clique Space to it. The notion of Clique spanning and Clique Space > > federations model many collaborative endeavours of the physical world in > a > > virtual context. > > We are doing very similar research in the EU funded TAS3 project. Our > notion is to make the plumbing (e.g. metadata exchange and basic > trust establishment) fully automatic, but then rely on trust > computation and scoring to determine exatly how close collaboration > is possible with a given partner. This also connects with user > driven access control. > > Our business model for building the Circles-of-Trust appears as > Annex E (really in the end of the document) of TAS3 architecture, > available from http:/zxid.org/tas3/ "TAS3 Architecture Deliverable". > > Another interesting initiative in this same space is the > Internet of Subjects (IoS), http://www.iosf.org/ which advocates > that the institutional web of trust should be a not-for-profit > entity, such as a trust (pardon the pun) or foundation. This model > does not require government to perform this function, but it > clearly states that the entity should not have a commercial > conflict of interest. I am trying to architect > this such that multiple such foundations could coexist. > Indeed, it looks as both organisations are on to a similar bone to myself. However, there do seem to differences (merely complimentary - I envisage that there would be mutual advantage to getting Clique Space and these architectures to cooperate) and so let me attempt to explain some of the differences in relation to Clique Space. I have had a very quick look over TAS3 and IoS and these are some of the impressions I draw from each. TAS3 appears to concentrate on a authorisation/authentication mechanism for access to and transfer of electronically stored personal information. In this regard, Clique Space differs in that it was primarily conceived by me to handle real-time and near real-time operation of devices. The page that is displayed directly from the IoS link you provide explains the organisations philosophy stating that the only one who ultimately owns personal data is the person to whom it relates. This is a similar philosophy to the one that motivated me to conceive Clique Space. Again, the notion of Personal Data Stores and the like leads me to conclude that IoS is based around information storage and retrieval, and not device activity. So, a bit more on the technical side... There are a few things to consider with regard to a device and the network infrastructure it uses; Clique Space is neutral with regard to physical networks because devices may use different physical networks to "the internet". Hence, while multiple Clique Spaces might exist on one network (say, "the internet") one Clique Space may also span multiple networks. The "one Clique Space - multiple networks" paradigm may be achieved through federating multiple sub Clique Spaces, but this may be complicated, and I would envisage it would be easier simply to use Media Profiles, and do what is necessary to bring physical access to other networks on an internet based Clique Space through one or more Agent Devices that were underlying members of the associated Agent Collaboration. > > Now, regarding the proprietary technology of Institutional Web of Trust, > if this IPR gets released on royalty-free basis, but with revocation > of license in case of law suit, I would actually view this as valuable > founding capital for the foundation. It is pretty clear that such > universal CoT would be disruptive business model, so if the foundation > had in its portfolio a couple of patents, it could quite well defend > itself, and its users, against the hostile forces. > > Cheers, > --Sampo > I have registered a patent for the technology. Its strength may yet be tested, and it is currently a PCT in international phase. It lapses 15 July. I do not know what I am going to do at this moment with regard to turning this into a business should I get that chance. What I need is venture capital to help secure national phase patent applications, people willing to help in ongoing development of the system, and people to ultimately manage a public Clique Space. I envisage that the Clique Space system would be available free-of-charge so that anyone can set up and run a proprietary Clique Space without having to worry about outlay for the software. I would also be averse to charging users for registration of Accounts. I believe this would not only create resistance in the product's uptake, but runs against my philosophical notions of the sacrosanct nature of the self; I don't expect to be charged for existing in a physical world, so I will not accept the proposition that I might be charged for existence in a virtual extension. The majority of revenue would be realised through federating proprietary Clique Spaces to the public Clique Space and in the registration of Account Profiles. I think the registration of Media Profiles might not provide a stable source of income for the public Clique Space, so I'm a bit reluctant to advocate charging their registration. I may re-enrol at my alma mater to do a research Masters degree with Clique Space as the subject. I'm trying to get this uni involved in supporting Clique Space, and they have set up a time for me to give a seminar on the subject. It would be great to hear that you or anyone else here might be able to help me in any way. Thanks, Owen. -- www.cliquespace.net Clique Space(TM) Facebook Group: http://www.facebook.com/group.php?gid=81335296379 Owen's Garden of Thought: http://owenpaulthomas.blogspot.com/

2 3

Kantara Initiative Conference - Early bird registration & room block deadline
by Dervla O'Reilly 03 Feb '10

03 Feb '10

This is a friendly reminder regarding registration and room block deadlines approaching related to the Conference March 9-11, 2010 at Intel's campus in Oregon. - Early-bird registration deadline is Feb. 12 for $195USD, then $250USD thereafter until March 9. - Sleeping room block deadline at the Springhill Suites is Feb. 9 for $105USD + taxes. Event information is available at our conference page - review the agenda, maps and nearby hotel details. We have a great rate per night for $105USD at the SpringHill Suites by Marriott - review the discount code details at our conference page We invite you to sign up for our open-for-all dinner is Wednesday, March 10, 6:45-8:15pm at Portland's Oba Restaurant. The price for the 3-course dinner including one beverage is $45USD. Please let me know if any questions regarding the Conference. Cheers, Dervla ________________________ Dervla O’Reilly Program Manager Kantara Initiative +1 415 731 4487 business +1 415 948 3650 mobile +1 509 757 4487 fax dervla[at]kantarainitiative.org http://www.kantarainitiative.org Register for Kantara's annual workshop March 1, 2010 at the RSA Conference free of charge - http://bit.ly/8rPWVM

1 0

Announcing Government of Canada Consultation on Cyber Authentication (note IAF adoption)
by Brett McDowell 02 Feb '10

02 Feb '10

At the request of our friends to the north, I'm pleased to share this announcement from the Government of Canada. Here it is verbatim in both English and French. Note the reference to Kantara Initiative in the 3rd paragraph. I strongly endorse and recommend you participate in this consultation, if at all possible. --------------------------------------------------------------------------------------------------------------- Government of Canada Industry Consultation on Cyber Authentication Renewal Program Industry Consultation: February 16, 2010 Optional One-on-one Sessions: February 16 - 18, 2010 National Capital Region In collaboration with the Treasury Board of Canada Secretariat (TBS), Public Works and Government Services Canada (PWGSC) is inviting representatives of private-sector organizations to participate in consultations on the Cyber Authentication Renewal Program. The Government of Canada (GC) is investigating solutions that would allow individuals the option of using their existing credentials in order to gain online access to government programs and services. This proposed approach would provide flexibility to both departments and agencies, and to individuals who access these services. It would allow departments and agencies to use credentials that are appropriate to the sensitivity of their service offerings, while allowing individuals to choose the credential they wish to use to access any online GC services. The GC is considering basing its accreditation framework initially on the Kantara Initiative's* Service Assessment Criterion and Assurance Assessment Scheme. The GC is inviting industry organizations to participate in a consultation on February 16, 2010, to validate and refine its approach to electronic authentication, and to gather information on how it will solicit and accredit external credential service providers - using a federated model. The industry consultation will be followed by optional one-on-one sessions beginning the afternoon of February 16, 2010 and concluding by close of business February 18, 2010. For further information, please send an email to ConsultationSPTI.ITSSConsultation(a)tpsgc-pwgsc.gc.ca, or visit the event posting on MERX. *The Kantara Initiative (http://kantarainitiative.org/) is a group of individuals, developers, organizations, governments, and technology providers that, in 2009, amalgamated several long standing foundations and associations from the identity community. The goal of the Kantara Initiative is to harmonize and coordinate the actions of this community to help ensure secure, identity-based, online interactions while preventing misuse of personal information. --------------------------------------------------------------------------------------------------------------- Consultations auprès de l'industrie sur le programme de renouvellement de l'authentification électronique du gouvernement du Canada Consultations auprès de l'industrie : 16 février 2010 Séances individuelles facultatives : 16 au 18 février 2010 Région de la capitale nationale Travaux publics et Services gouvernementaux Canada (TPSGC), en collaboration avec le Secrétariat du Conseil du Trésor (SCT), invite les représentants des organisations du secteur privé à participer aux consultations sur le programme de renouvellement de l'authentification électronique. Le gouvernement du Canada est à la recherche de solutions qui donneraient aux utilisateurs la possibilité d'utiliser leur justificatif existant afin d'accéder en ligne à des services et à des programmes gouvernementaux. Cette approche proposée offrirait de la flexibilité aux ministères, aux organismes et aux utilisateurs. Elle permettrait aux ministères et aux organismes d'utiliser des justificatifs appropriés en fonction de la sensibilité des services offerts, tout en permettant aux utilisateurs de choisir le justificatif qu'ils veulent utiliser pour accéder à tous les services gouvernementaux en ligne. Le gouvernement du Canada envisage tout d'abord de fonder son cadre d'accréditation sur les Service Assessment Criterion (critères d'évaluation de service) et l'Assurance Assessment Scheme (programme d'évaluation de l'assurance) de l'initiative Kantara*. Le gouvernement du Canada invite les organisations de l'industrie à participer à des consultations le 16 février 2010 pour valider et préciser son approche à l'égard de l'authentification électronique et pour recueillir des renseignements sur la manière dont le gouvernement sollicitera et accréditera les fournisseurs externes de services de justificatifs en utilisant un modèle fédéré. Les consultations menées auprès de l'industrie seront suivies de séances individuelles facultatives qui commenceront le 16 février 2010 en après-midi et se termineront à la fermeture des bureaux le 18 février 2010. Pour obtenir de plus amples renseignements, envoyez un courriel à l'adresse ConsultationSPTI.ITSSConsultation(a)tpsgc-pwgsc.gc.ca, ou visitez le site du MERX pour l'annonce d'évènements. *L'initiative Kantara (http://kantarainitiative.org/)est un regroupement de gens, de développeurs, d'organismes, de gouvernements et de fournisseurs de technologie qui, en 2009, a fusionné plusieurs fondations et associations de longue date de la communauté d'identité. L'objectif de l'initiative Kantara est d'harmoniser et de coordonner les actions de cette communauté pour faire en sorte que les interactions en ligne sont sécuritaires et basées sur l'identité en plus de prévenir l'utilisation malveillante des renseignements personnels.

3 2

Institutional Web of Trust
by Michael Duffy 01 Feb '10

01 Feb '10

We believe we have *THE* *solution that will realize the vision of the Kantara Initiative*: Ensure secure, identity-based, online interactions while preventing misuse of personal information so that networks will become privacy protecting and more natively trustworthy environments. We realize that is a bold statement. We humbly ask the members of the Kantara Initiative to review our approach: *Digital credentials on NFC enabled smart phones will soon transform the world of identity management.* *The Trust Nexus* is a startup company located in Austin, TX. We hold intellectual property rights that will enable us to build the infrastructure for secure identity in the digital age. *Whoever controls the infrastructure for secure identity will also play a leading role in the emerging world of m-Commerce.* The basic question is, how can trust be established in the digital age? If you and I have never met and I come to your website or place of business, how can you be confident that I am who I say that I am? *The Trust Nexus answers this basic question regarding the establishment of trust.* A key component of our infrastructure will be an easy to use *digital wallet* where credentials can be securely provisioned and transactions occur smoothly. This digital wallet will be the *cornerstone of NFC technologies on mobile devices* and provide the interface for identity, marketing and financial services. *Every aspect of digital life that depends on identity and transactions will flow through the digital wallet. * The digital wallet on NFC enabled smart phones will be one of *the most valuable assets in the digital age*. The digital wallet and supporting infrastructure will be based on industry standards that will *enable the mobile network operators (MNOs) to meter services that flow through their networks and participate in new marketing/advertising models.* The identity infrastructure we have designed will eliminate the possibility of identity theft for all participants, protect consumers and financial institutions from fraudulent transactions, greatly reduce cyber-crime and solve many of the systemic problems of the current Public Key Infrastructure system, especially the problems of certificate revocation lists (CRLs) and on-line status checking. Our solution is simple, practical and transparent to the consumer. Consumer acceptance will be rapid and widespread. Our solution secures identity, protects individual privacy and prevents the establishment of monolithic government control. Under our system, the user is always in control of his/her credentials. The essence of our approach is very different from the "Big Brother" approach recently announced by India. Rather than creating a centralized directory of private information, we will create a central repository containing a collection of institutional decisions which will establish an *Institutional Web of Trust*. Compared to a decentralized web of trust which creates a web of individuals with, "the expectation that anyone receiving [a list of signatures] will trust at least one or two of the signatures", we will create a system where *trusted institutions legitimize individual identity*. Additionally, the *Institutional Web of Trust* established by *The Trust Nexus* will have centralized controller processes that rely greatly on self-management and automation resulting in great efficiencies. Digital wallets on NFC enabled smart phones will enable users to secure their private keys and control/present their digital credentials. Because a user's identity will be authenticated by the processes of *The Trust Nexus* (not a trust authority) there is no need for a trust authority to issue and vouch for public/private keys for individual users. It is only necessary that the public key be registered and the private key be secured. Users can self-issue their keys. *The Trust Nexus* does not secure identity by, "making personal data harder to steal". Rather, identity is secured by self-managing logical inconsistencies within the system, resolving identity conflicts and preventing fraudulent transactions. As Bruce Schneier, author and security guru, pointed out, "Proposed [identity theft] fixes tend to concentrate on the first issue--making personal data harder to steal--whereas the real problem is the second [preventing fraudulent transactions]. If we're ever going to manage the risks and effects of electronic impersonation [identity theft], *we must concentrate on preventing and detecting fraudulent transactions*." [Solving Identity Theft] In essence, there are a *limited number of institutions worldwide* (measured in thousands) that truly matter when it comes to legitimizing identity. Digital wallets on smart phones will enable the efficient association of unique public/private keys to a specific legal identity (legal name and legal address). If there is a non-unique association, an inconsistency arises in the system. If the association is unique and verified by one or more legitimate institutions an individual's identity is secure (as long as the private key which he/she controls is secure). In the process of adding a credential to a user's digital wallet, the provisioning institution (government agency, bank, university, etc.) will calculate a secure hash value (numerical representation) of the credential combined with information from the user's *primary credential* (legal identity). This hash value will be encrypted with the user's private key and then encrypted again with the provisioning institution's private key; this encrypted hash value will then be stored in *The Trust Nexus Repository* representing *an institutional validation of the user's identity.* This dual encryption establishes that the credential was associated with the user during the provisioning process rather than simply asserting the association by a reference from the repository. Also, There is no need to store any specific information (account number, balance, etc.) about user's account. The user is in complete control of the information he/she presents and his/her privacy is maintained. When a user presents a credential from his/her digital wallet a transaction ID will be sent from the authenticating system to the user's digital wallet, be encrypted with the user's private key and sent back to the authenticating system. The user can be authenticated by decrypting the transaction ID with the user's public key from *The Trust Nexus Repository*. The credential can be authenticated by calculating the hash value of the credential and then decrypting the hash value stored in *The Trust Nexus Repository* with the institution's public key and the user's public key. In a variation of this process the provisioning institution does not store the encrypted hash value in *The Trust Nexus Repository*; rather, the provisioning institution itself maintains a repository and a reference to the repository is authenticated by an entry contained within *The Trust Nexus Repository* (through the institution's primary credential). In this way an institution could *federate the identity* of it's users (or a subset of its users) simply by adding (or modifying) a credential to each of it's user's digital wallets and creating an institutional reference within *The Trust Nexus Repository*. As part of the federation process, cooperating institutions will most likely create standard authorization levels for various services and provision these levels as part of a user's credential. For example, a coalition of universities may have authorization levels for library services that will enable users to access any library within the coalition; government organizations may provision security levels within a user's credential that enable inter-agency access to resources; etc. There is significant debate regarding the effectiveness of biometrics in identity management. When a user is not present (authenticating over a network) there are fatal problems with biometric authentication. Most significantly, "The main security problem with biometrics is the inability to create a new secret. If you allow your fingerprint to be digitized and sent across a network or scanned by a compromised scanner, it can be stolen. Then someone has a digital copy of your fingerprint." Even if a method of biometric identification proved to be completely reliable, security issues would still remain. There would be opportunities to steal someone's biometric signature and forge their identity credentials, especially if there was a massive store of private personal data; one successful attack could essentially render the entire system ineffective. When a user is present bio-metric data can be an effective authenticator. It will be possible to *store bio-metric data within a user's credential* (not within a central repository) when the credential is created by the provisioning institution. When a user presents the credential verifying the biometric data in the credential against the individual in real time will provide enhanced security along with verifying the encrypted transaction code against the user's public key in *The Trust Nexus Repository* and verifying the encrypted hash code of the credential against *The Trust Nexus Repository*. While there are many types of biometric identifiers, one of the simplest and most usable is a photograph of the human face verified by a human being. Any credential in a user's digital wallet that includes a photograph (driver's license, passport, bank debit card, etc.) will be highly reliable when a user presents the credential in person. Why would a major institution (bank, university, corporation, government agency, etc.) utilize *The Trust Nexus Repository* instead of its own internal system? When there is no need for an external third party to rely on a user's credential an institution may very well utilize its own internal repository. In this same case, smaller institutions, for reasons of convenience and cost, might still utilize *The Trust Nexus Repository*. Whenever a third party (a party other than the provisioning institution) must relay on a user's credential, the key services *The Trust Nexus Repository* provides are assurance that the user is unique and trustworthy, assurance that the provisioning institution is unique and trustworthy and assurance that the credential is trustworthy. Also, *The Trust Nexus Repository* creates a "*data synergy effect*" which establishes an *Institutional Web of Trust* (when multiple institutions validate a unique user's identity the identity becomes more secure and trustworthy). If a unique user has digital credentials for a state driver's license, a passport, a bank debit card, a university ID, insurance cards, credit cards, etc., all independently validated by trustworthy institutions, that user's identity is secure and highly trustworthy. Similar to credit ratings, both individuals and institutions will have "*trust ratings*" within *The Trust Nexus Repository*. A centralized notification service will also be provided when credentials are lost or stolen. The uniqueness test for legal identities within *The Trust Nexus Repository* helps to secure identity and prevent identity theft. If there is a non-unique association, an inconsistency arises in the system. Also, easy access for online status checking establishes the currency of a user's credentials in case the user's digital wallet is lost or stolen. And most importantly, *The Trust Nexus* creates a "*data synergy effect*" which establishes an *Institutional Web of Trust*. Additionally, our system provides *the "Holy Grail" for single sign on*. All computers will soon have an interface (USB plugin or internal card) that will enable NFC interactions with mobile devices. The digital wallet on a user's cell phone will be provisioned with credentials containing specified authorizations different systems and services. Rather than logging into a directory or utilizing a complex federated identity process, a user will log onto his/her cell phone with a PIN and a voice authentication signature. The user (or the authenticating system) will then select the appropriate credential for the specified system or service with no need to enter another user name or password (the user's private key will be used to encrypt a transaction ID). This approach also *solves the "Keys to the Kingdom" problem* where a single sign on to a directory service opens access to all the user's systems and services. We are confident we have a transforming technology and a clear vision of the future. *No one has found a conceptual flaw in the system.* Existing providers of identity management services should not see *The Trust Nexus* as a competitor; rather, they should see us as an infrastructure provider (similar to the electric power grid that has hundreds of energy providers). Best regards, Michael Duffy CEO / CTO ~ The Trust Nexus http://www.thetrustnexus.com

11 18